Plat-UX-101 Exam Dumps - Salesforce Certified Platform User Experience Designer

The correct solution is C. Enablement Site to build and assign custom modules, exactly as specified in the uploaded study guide. An Enablement Site is appropriate because the requirement is broader than simply showing users contextual assistance. Cloud Kicks requires structured, custom product training that can be delivered as learning content to internal users and leadership. Salesforce's Enablement functionality supports publishing modules and assigning relevant learning content to users. Salesforce documentation specifically explains that administrators can assign modules published on an enablement site and that users can complete assigned content from within Salesforce. Option A addresses a narrower use case. In-App Guidance prompts are effective for contextual onboarding, feature announcements, and short instructional interventions within the user's workflow, but they are not a replacement for a structured custom learning curriculum.

Option B provides an environment where users can experiment, but a sandbox does not inherently provide organized learning modules, assignments, learning progression, or formal enablement content.

The UX requirement here is therefore solved by selecting the platform capability that supports repeatable, organized, assignable learning experiences, rather than merely contextual assistance or an experimentation environment.

Study Guide reference/topics: Enablement Sites, custom learning modules, onboarding, internal user education, Declarative Design.

==================================

The correct answer is B. Page layouts or permissions can display only the fields needed for each audience. This is the answer provided by the study guide. The scenario describes different audiences that consume the same knowledge system but require different levels and presentations of information. Salesforce declarative configuration allows the organization to tailor the experience using layouts and permissions instead of duplicating content unnecessarily. Option B supports audience-specific presentation by controlling which fields are exposed and which content users are permitted to access. This reduces cognitive load for customers while allowing support representatives to retain access to more detailed operational information. Option A creates unnecessary content duplication. Maintaining separate versions of the same article for every audience can create governance problems, inconsistent updates, and additional editorial overhead. Option C incorrectly assumes that external topic organization must duplicate the organization's internal category structure. A user-centered external experience should organize information in ways meaningful to customers rather than simply mirroring internal information architecture. The broader UX principle is progressive and audience-appropriate disclosure. Users should see information relevant to their tasks and permissions without being overwhelmed by fields intended for other roles. Therefore, page-layout and permission controls provide the most maintainable declarative solution.

Study Guide reference/topics: Knowledge, audience-specific content, permissions, page layouts, Declarative Design.

==================================

The study guide identifies A. Run the Salesforce Optimizer App to identify fields not in use as the correct answer. The scenario presents two related UX problems: the Contact page contains too many irrelevant fields, and users experience long page-load times. The selected approach begins by identifying which configuration elements are no longer providing value.

Using Salesforce Optimizer gives the organization evidence about unnecessary or underused configuration so that administrators can make informed decisions about simplifying the experience. This is stronger than merely relocating unused information.

Option B does not actually solve the underlying problem. Moving unused fields to another section still leaves those fields in the interface and can retain unnecessary page complexity.

Option C, In-App Guidance, could help explain where important fields are located, but it would layer guidance on top of an already cluttered experience rather than addressing the clutter itself.

The UX implication is that unnecessary interface elements should be evaluated and removed rather than simply documented or rearranged. A cleaner Contact experience can make relevant sales information easier to find while reducing the amount of configuration presented on the page.

Study Guide reference/topics: Salesforce Optimizer, page simplification, unused fields, Sales Cloud UX, Declarative Design.

==================================

The study guide identifies C. Compact Layouts as the correct answer.

The requirement is straightforward: when a sales representative views an Opportunity record, the most important fields should be immediately available without requiring unnecessary navigation or custom development.

Compact Layouts are the standard Salesforce feature selected by the guide for surfacing key record information concisely. The UX objective is to ensure that users can quickly orient themselves to the record and access the information required for common decisions.

Option A, a custom Lightning Web Component, would introduce custom development even though the scenario can be addressed using standard Salesforce configuration. This would add implementation complexity without a demonstrated need.

Option B, Tabs, can help organize larger groups of page content, but they do not specifically solve the requirement to expose a concise group of high-value record fields.

The UX principle is prioritization of information. Not every field on an Opportunity carries equal importance during routine record viewing. A compact presentation allows the designer or administrator to surface the fields that users need most frequently while keeping the broader record available when required.

Study Guide reference/topics: Compact Layouts, key fields, Opportunity records, information prioritization, Declarative Design.

==================================

The study guide identifies A. Troubleshooting customer issues and logging activities as the correct activity set for the Case Solver persona.

Persona-based UX design requires the designer to align the interface with the user's primary responsibilities rather than with every activity that may exist somewhere within the organization. The name “Case Solver” itself points toward users whose principal work centers on resolving customer cases.

Option A directly reflects that operational role. Troubleshooting addresses the core problem-resolution responsibility, while logging activities supports documentation of the work performed while handling the customer issue. Those tasks therefore belong at the center of the Case Solver experience.

Option B shifts toward coaching, administration, or knowledge-management responsibilities. Those activities may exist within a service organization, but they are not the primary activities the study guide associates with the Case Solver persona.

Option C combines case-status visibility with campaign metrics. Campaign analysis belongs to a different business context and therefore does not form a coherent task set for this Service Cloud persona.

The design implication is that pages, actions, information hierarchy, and workflows should prioritize the activities users perform most frequently. For the Case Solver, the guide centers that experience on customer troubleshooting and activity logging.

Study Guide reference/topics: Personas, Case Solver, Service Cloud, task analysis, Discovery.

==================================

The uploaded study guide identifies B. Personalize the navigation bar as the correct solution.

The problem affects only a small subset of sales users. They frequently use a particular object, but that object is not currently included in the Lightning application's standard navigation. Creating an entirely separate application would therefore be disproportionate to the size of the audience.

Personalizing the navigation bar directly addresses the usability problem by allowing the relevant users to place the object within their own accessible navigation structure. This reduces unnecessary searching or indirect navigation while avoiding organization-wide configuration solely for a small group.

Option A, creating a Dashboard action, does not solve the fundamental problem that these users need routine navigation to an object.

Option C, placing the object's related list on the Home page, would attempt to surface data in a different context rather than providing straightforward navigation to the object itself.

The guide's solution reflects a broader UX principle of appropriate personalization. When a need is specific to a limited group and does not justify a separate application, individual navigation customization can improve efficiency without increasing administrative complexity for everyone else.

Study Guide reference/topics: Lightning navigation, personalization, object access, end-user efficiency, Declarative Design.

==================================

The study guide explicitly identifies C. Become familiar with the Salesforce Lightning Design System (SLDS) component blueprints as the correct first step.

Before designing a new Lightning component, the UX Designer should understand the established Salesforce patterns applicable to that type of interface. SLDS Component Blueprints provide the structural and visual reference for Salesforce-style components and therefore give the designer a foundation before introducing custom decisions.

Option A begins with design tokens. Tokens are useful for consistent values such as spacing, sizing, or visual attributes, but importing them before understanding the component pattern would start at too low a level. The designer first needs to understand the component architecture and behavior.

Option B focuses on AppExchange packages. AppExchange can provide complete applications and extensions, but reviewing packages is not the first design step identified in this scenario.

The underlying principle is design-system-first thinking. Before creating a new component, designers should understand how Salesforce already represents similar controls and interactions. This reduces inconsistency and makes it easier for developers and users to recognize established Lightning patterns.

Study Guide reference/topics: SLDS Component Blueprints, component design, Lightning, design-system consistency, Salesforce Lightning Design System.

==================================

The correct answer is B. Set field-level error message to display on the page. The study guide presents this scenario and identifies B as the answer. The validation rule already determines whether the phone number satisfies the required formatting and length conditions. From a UX perspective, the next objective is to communicate the validation failure at the location where the user must correct it. A field-level error message places the feedback adjacent to the phone field, reducing the user's effort to determine what went wrong and where corrective action is required.

Option A, In-App Guidance, is better suited to onboarding, contextual instruction, feature adoption, or process coaching. It is unnecessarily indirect for a deterministic input-validation error.

Option C, making the field required, only ensures that some value is entered. A required-field setting does not validate whether the phone number contains the correct number of digits or follows the required formatting pattern.

The UX principle being tested is effective error prevention and recovery. When a user enters invalid information, the interface should provide specific, contextual, and actionable feedback instead of forcing the user to search for the affected field.

Study Guide reference/topics: Validation Rules, field-level errors, error prevention, form usability, Declarative Design.

==================================