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

The correct answer is B. Ability to toggle between multiple records. The uploaded UX Designer study guide explicitly identifies this requirement as a reason to recommend Console navigation. Console navigation is designed for users who work intensively with multiple records and related information during the same session. Rather than continually leaving one record page and opening another, users can maintain several records within the console workspace and switch between them efficiently. This makes the console particularly valuable for sales or service roles where users frequently compare, reference, or update multiple related records.

Option A is not the defining requirement in the study-guide scenario. Although console applications can support efficient multi-record workflows, the requirement specifically associated with the answer is the ability to toggle between multiple records.

Option C points in the opposite direction. Users whose work occurs primarily in the field generally have stronger mobile and simplified-navigation requirements rather than a desktop-oriented multi-record console workspace.

From a UX perspective, the navigation model should correspond to the user's task pattern. Standard navigation suits more linear interaction, whereas Console navigation is better suited to high-volume, multi-record work where reducing navigation overhead improves productivity.

Study Guide reference/topics: Console Navigation, Standard Navigation, multi-record workflows, productivity, Declarative Design.

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

The correct answer is B. Bring together a cross-functional group with varied experiences, as explicitly keyed in the uploaded UX Designer study guide.

Consequence Scanning is represented in the guide as an activity strengthened by diverse perspectives. Bringing together people from different functional areas and with different experiences increases the likelihood that the group will identify consequences that a homogeneous team might overlook.

Option A focuses on organizational OKRs. Those objectives may inform product planning, but they are not the consideration selected by the guide for a Consequence Scanning workshop.

Option C places inclusivity examination after the product has already been built. That timing weakens the preventive value of the exercise. The study-guide framing treats consequence-oriented thinking as something that should influence design decisions rather than merely audit them after implementation.

A cross-functional workshop can expose different technical, business, user, operational, and social perspectives. This is particularly important when evaluating possible intended and unintended outcomes.

The main Human-Centered Design lesson is that responsible design analysis improves when teams deliberately include viewpoints beyond the immediate product or design group.

Study Guide reference/topics: Consequence Scanning, cross-functional collaboration, diverse perspectives, responsible design, Human-Centered Design.

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

The uploaded UX Designer study guide identifies C. Define the goals of the study as the correct answer.

Before recruiting participants or writing detailed study procedures, the UX Designer must establish what the usability study is intended to learn. In this scenario, the broad concern is whether the Experience Cloud site is intuitive, but that concern should be translated into clear research objectives.

Defining goals determines the rest of the study design. The goals influence which tasks participants should perform, which user groups should participate, what behaviors should be observed, and which outcomes will indicate success or reveal usability problems.

Option A, recruiting the right participants, is essential, but participant criteria should be derived from the goals and target users of the study.

Option B, writing a test plan, is also important, but a useful test plan depends on first understanding the study objectives. Without clearly defined goals, the plan can become a collection of activities without a coherent research purpose.

The guide therefore establishes the planning sequence correctly: define what needs to be learned first, then design the study around that objective.

Study Guide reference/topics: Usability Studies, research goals, study planning, Experience Cloud testing, Testing.

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

Responsible AI requires users to understand how an AI-supported experience reaches or communicates consequential outputs. Therefore, providing clear explanations of predictions and recommendations directly supports transparency and explainability. The uploaded study guide explicitly identifies A as the correct response. Salesforce's AI guidance similarly treats explainability as fundamental to useful predictive experiences. Salesforce describes predictive outputs as not merely providing an outcome but also enabling users to understand factors contributing to that outcome and take appropriate action. This supports the UX principle that AI should not behave as an opaque decision mechanism.

Option B is incorrect because responsible data practices do not advocate indiscriminate data collection. Data collection should be purposeful and proportionate to the intended experience. Collecting more data simply because it is available creates privacy, bias, and governance concerns. Option C may support organizational education, but an internal demonstration does not make the actual user-facing AI interaction transparent.

The strongest UX solution is therefore to expose understandable reasoning or contextual explanations around AI-generated predictions and recommendations.

Study Guide reference/topics: Responsible AI, transparency, explainability, trustworthy user experiences, Human-Centered Design.

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

A Screen Flow allows Salesforce administrators to guide users through a multi-step process using interactive screens. The flow can collect information, display contextual instructions, make decisions based on entered data, and progressively move the user through a complex workflow. That directly addresses the requirement to make a complicated internal process more engaging and easier to follow. Rather than exposing users to a large number of fields or asking them to understand the underlying process logic, a Screen Flow can progressively present only the information and actions needed at each step. Option A, Lightning Survey, is designed primarily for collecting feedback or responses. It does not serve as a general-purpose mechanism for guiding users through operational business processes. Option B, Process Builder, concerns automation logic rather than an interactive user experience. It does not provide the guided visual interaction described in the scenario. From a UX perspective, Screen Flow reduces cognitive load by turning a complicated process into a sequence of understandable interactions. It can also provide validation and contextual information as the user proceeds.

Study Guide reference/topics: Screen Flow, guided processes, progressive disclosure, process usability, Declarative Design.

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

The correct answer is A. Create a custom Theme in Themes and Branding, selecting logo, brand colors, and images, exactly as stated in the uploaded study guide.

The requirement is to make Lightning Experience conform to the company's existing design guidelines using declarative configuration. The study guide therefore directs the UX Designer to the standard Themes and Branding capability rather than to custom development.

A custom theme allows the organization to apply important brand assets such as the company logo, brand colors, and imagery so that the Salesforce environment presents a recognizable visual identity.

Option B is insufficient because selecting whichever built-in theme happens to be closest does not guarantee compliance with Cloud Kicks' actual design guidelines.

Option C refers to a different branding mechanism and includes font-type configuration, but it is not the declarative approach keyed by the study guide for the current Lightning Experience scenario.

The broader UX principle is to implement branding through supported Salesforce configuration whenever those tools satisfy the requirement. This preserves consistency and avoids unnecessary custom styling while still aligning the environment with company identity.

Study Guide reference/topics: Themes and Branding, Lightning Experience, brand colors, logos, 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 correct answer is B. Learning about the user's behavior and preferences. The uploaded study guide directly confirms this answer. Usability testing evaluates how representative users actually interact with a product, prototype, or workflow. Designers observe where users succeed, hesitate, misunderstand information, make errors, or adopt unexpected approaches. These behavioral observations reveal whether the experience aligns with users' mental models and expectations.

Option A contradicts proper usability-testing methodology. The objective is not to train participants to operate the interface correctly. Excessive instructions or coaching can contaminate the study because they prevent researchers from observing whether the design itself communicates what users need to know. The participant should generally attempt representative tasks while the researcher observes behavior and gathers feedback.

Option C describes a narrower comparative optimization technique associated more directly with A/B testing, where different interface variations are exposed to users and measured against a defined outcome. Usability testing instead concentrates on understanding why users experience particular successes or problems.

The critical examination distinction is therefore:

Usability testing = understand user behavior and usability problems.

A/B testing = compare alternative variations quantitatively.

That makes option B the only response aligned with the purpose of usability research.

Study Guide reference/topics: Usability testing, user behavior, user preferences, observational research, Testing.

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

The correct answer is C. The CSS styles defined in the parent list component are not shared with the child items. The study guide explicitly keys this Shadow DOM behavior.

The UX Designer must account for component-level style isolation when specifying how the custom parent and child LWCs should appear. In the scenario, the parent component represents the overall To-Do List, while separate child components represent individual To-Do items.

The answer key indicates that styling defined within the parent component cannot simply be assumed to apply inside each child component. Consequently, the designer and developer need to plan styling at the appropriate component level rather than expecting the parent's stylesheet to control every repeated child item automatically.

Option B states the opposite behavior by assuming that the parent's CSS is inherited by the child components.

Option A focuses on Light DOM, but the scenario specifically asks about the impact of the LWC's Shadow DOM structure, and the guide selects style separation as the relevant consideration.

The design implication is significant: component boundaries affect implementation. A visually consistent specification must account for how styles are scoped when a user interface is decomposed into multiple Lightning Web Components.

Study Guide reference/topics: LWC, Shadow DOM, CSS scope, parent-child components, SLDS.

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