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

The uploaded UX Designer study guide identifies B. Using REM-based spacing values when styling components as the approach that should be avoided.

The scenario is specifically concerned with ensuring that custom components can respond appropriately when users choose between Comfy and Compact display density. The study guide contrasts approaches that participate in Salesforce's design-system behavior with manually defined spacing.

Option A uses the `SpacingMedium` design token. Within the framing of the question, this allows spacing to be governed by the Salesforce design system rather than being fixed independently inside the component.

Option C likewise uses existing Lightning components such as cards or page headers. Those components already participate in the Salesforce UI framework and are therefore preferable when the goal is to preserve consistency with platform-level design behavior.

Option B instead applies REM-based spacing values directly in custom styling. According to the study guide answer, that approach should be avoided when the component needs to benefit from Salesforce density settings.

The central design-system principle tested here is to avoid hard-coding presentation decisions that should instead be inherited from reusable Salesforce design resources.

Study Guide reference/topics: Display Density, Compact and Comfy settings, design tokens, reusable Lightning components, SLDS.

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

The uploaded UX Designer study guide identifies B. Optimize for color contrast-ratio and screen-reading technology as the correct answer.

The research finding is specifically that the solution does not adequately account for users with visual impairments. The study guide therefore directs the UX Designer toward accessibility improvements that affect how information can be perceived visually and through assistive technology.

Improving color contrast supports users who may have difficulty distinguishing foreground content from its background. Supporting screen-reading technology allows users who cannot rely on visual presentation to access the interface through an alternative presentation of its structure and content.

Option A proposes a separate version of the portal. The study guide does not recommend segregating visually impaired users into a different experience; instead, accessibility should be incorporated into the main design.

Option C concerns HIPAA requirements and does not address the visual-accessibility problem described.

The key UX principle is that accessibility should be integrated into the product experience. The correct response is therefore to improve the existing design so that it works with relevant accessibility needs and assistive technologies.

Study Guide reference/topics: Accessibility, color contrast, screen readers, visually impaired users, UX Fundamentals.

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

The uploaded study guide identifies A. Group similar fields using sections as the correct page-layout practice.

A record page can contain many fields, and users need to understand the information quickly rather than scan an undifferentiated collection of inputs and values. Grouping related fields into meaningful sections creates structure and makes the page easier to navigate.

Option B recommends including every field that might potentially be useful. That approach increases visual clutter and places additional cognitive demands on users because they must repeatedly distinguish important information from peripheral information.

Option C concerns making field labels identical to API names. API names exist primarily for technical implementation purposes and do not define the organization or usability of the user-facing page layout.

The study-guide answer therefore focuses on information organization. Related content should be presented together so users can predict where information belongs and locate it more efficiently.

For example, fields concerning customer information, reservation details, scheduling, or status can be grouped according to their functional relationship rather than presented as one continuous list.

The result is a clearer visual hierarchy and a more efficient Salesforce record experience.

Study Guide reference/topics: Page layouts, field sections, information organization, visual hierarchy, Declarative Design.

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

The study guide identifies B. Semantic and accessible component markup as the correct answer. SLDS is a design system that provides resources for creating interfaces aligned with Salesforce's visual and interaction conventions. In the context of this question, its relevant contribution is component markup designed around semantic structure and accessibility considerations. Semantic markup is important because the structure of an interface conveys meaning beyond its visual appearance. Properly structured controls, labels, states, and component relationships can be interpreted more reliably by browsers and assistive technologies. Option A is incorrect within the study guide's framing because SLDS itself is not simply a library of Lightning Web Components. The system provides design specifications, patterns, markup, styling, and associated guidance that can be applied when developing components. Option C describes JavaScript modules and plugins rather than the core SLDS resource identified by the answer key. This question reinforces the distinction between a design system and a component runtime framework. SLDS provides the standards and building blocks that support consistent interface implementation. For custom development, using its semantic and accessible markup patterns helps preserve Salesforce UX conventions while reducing the risk of inconsistent component behavior.

Study Guide reference/topics: SLDS, semantic markup, accessibility, component patterns, Salesforce Lightning Design System.

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