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

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 A. Heuristic Evaluation, as specified in the study guide. A heuristic evaluation is appropriate when an existing interface is known to have usability problems, but the specific problems have not yet been systematically identified. The UX Designer evaluates the interface against recognized usability principles or heuristics and documents violations, severity, and improvement opportunities. This gives the team a structured assessment of the current experience before committing to redesign solutions.

The key phrase in the scenario is that Cloud Kicks “is unsure about what should be done.” Creating a low-fidelity prototype at this stage would prematurely move into solution design without first diagnosing the existing interface. A design template likewise determines presentation structure but does not explain why the current experience is ineffective.

This aligns with the broader Salesforce UX research principle of understanding the problem before building the solution. Salesforce emphasizes that UX work should investigate the existing experience, user goals, pain points, and underlying usability problems instead of assuming what users require. A heuristic evaluation therefore creates an evidence-based baseline from which redesign decisions can be prioritized and subsequently validated through user research and usability testing.

Study Guide reference/topics: Heuristic Evaluation, usability principles, current-state assessment, UX Fundamentals, interface evaluation.

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

The correct answer is B. Design Tokens, exactly as identified in the uploaded study guide. Design tokens are named entities that represent design decisions such as colors, spacing, typography, sizing, borders, and other visual properties. Instead of hard-coding a value such as a hexadecimal color or a fixed pixel spacing repeatedly throughout an application, designers and developers reference a standardized token. This produces two major UX and implementation advantages: consistency and scalability. If the design system later changes a brand color or spacing rule, the underlying token can be updated centrally instead of requiring manual changes throughout every component. Option A, Utility Classes, applies predefined styling behaviors to markup, but it does not represent the underlying system of named design attributes described in the question. Option C, Design Patterns, describes reusable approaches for solving recurring interface or interaction problems; patterns are not the named values used to represent foundational design properties. For Salesforce UX work, design tokens support the broader SLDS goal of maintaining visual consistency across components and experiences. They also reduce implementation drift between what designers specify and what developers build. The key examination distinction is: tokens represent reusable design values; patterns represent reusable design solutions.

Study Guide reference/topics: Design Tokens, SLDS, scalability, consistency, reusable design attributes.

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

The uploaded study guide identifies A. Rich Text, images, and links as the correct content for Path's Guidance for Success area.

The scenario requires stage-specific guidance telling sales representatives what they should be doing during the opportunity lifecycle. Rich instructional content is therefore the best fit because it can communicate guidance and provide supporting resources in the context of each stage.

The important distinction is between the Path itself and the guidance displayed within it. The Path already represents progression through a process. The Guidance for Success area supplements that progression with information that helps the user understand what actions, considerations, or resources are relevant.

Option B, Merge Fields, is not the content mechanism selected by the study guide for Guidance for Success.

Option C, Progress Indicator, would duplicate the stage-progress concept rather than provide the instructional content required by the scenario.

This supports a broader declarative UX principle: when Salesforce already provides a standard contextual-guidance capability, the designer should use it to place helpful information at the point where users need it. Here, rich text, imagery, and links can support representatives without requiring a separate training interface.

Study Guide reference/topics: Salesforce Path, Guidance for Success, contextual guidance, Opportunity lifecycle, Declarative Design.

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