Salesforce Updated Plat-UX-101 Exam Questions and Answers by avery

The uploaded Master Study Guide identifies C. Utility Classes as the correct SLDS resource for maintaining consistency in alignment, grids, spacing, and typography.

Utility classes provide reusable styling mechanisms that can be applied to interface elements without creating a separate custom CSS solution for every layout or presentation requirement. Within the study-guide framing, they are the appropriate SLDS resource when designers and developers need consistent control over common visual properties.

Option A, Component Blueprints, is used to communicate the structure and presentation pattern of complete Salesforce-style components. Blueprints are important when implementing component patterns, but this question focuses specifically on commonly reused styling concerns such as spacing, alignment, and typography.

Option B, BEM Naming Classes, relates to CSS naming methodology and structure. It is not the resource keyed by the guide for applying the visual utilities described.

The underlying design-system principle is reuse instead of reinvention. Applying standardized utility classes helps different pages and components use common spacing and alignment behavior rather than accumulating inconsistent custom CSS rules.

That consistency makes Salesforce interfaces more predictable visually and easier to maintain.

Study Guide reference/topics: SLDS Utility Classes, alignment, spacing, grids, typography, Salesforce Lightning Design System.

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

The correct answer is A. Journey Maps, as specified in the uploaded UX Designer study guide.

Journey maps are a core Discovery artifact because they document how users experience a process or service across stages and touchpoints. A journey map can capture user actions, goals, pain points, interactions, and opportunities for improvement.

For an Experience Cloud website redesign, this helps the UX Designer understand how users currently navigate and interact with the service before deciding how the redesigned site should work.

Option B, User Stories, are typically produced when research insights are translated into actionable requirements or backlog items. They are useful after the team has developed sufficient understanding of the user and problem space.

Option C, Interactive Prototypes, belong later in the design process. They represent proposed solutions and are commonly used for evaluation and usability testing. Creating them during early Discovery can cause the team to commit prematurely to an interface before the underlying journey has been sufficiently understood.

The study-guide sequence is therefore important: first understand the user experience, then define and prioritize requirements, then prototype potential solutions.

For Cloud Kicks, preparing Journey Maps gives the redesign effort an evidence-based foundation and highlights the moments where the new Experience Cloud site can improve the overall customer experience.

Study Guide reference/topics: Journey Maps, Experience Cloud discovery, current-state experience, pain points, opportunities, Discovery.

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

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.

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

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.

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