Free Practice Questions for Salesforce Plat-UX-101 Exam

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 correct answer is C. Search, as identified in the uploaded study guide.

Alternative text for a functional icon should communicate the purpose of the control, not merely describe its visual appearance. In this case, the magnifying-glass icon is clickable and performs a search action within a Lookup field.

Therefore, the text “Search” tells users what will happen when they activate the control.

Option B, “Magnifying glass,” describes what the icon looks like rather than what it does. That description is less useful to someone using assistive technology because knowing the graphical shape does not necessarily explain the interaction.

Option A, “Finder,” is also less direct and does not use the clear action-oriented label selected by the study guide.

This question reflects an important accessibility principle: when an icon is interactive, text alternatives should express its functional meaning. A screen-reader user should receive information equivalent to what a sighted user infers from the familiar icon.

For UX Designers, the practical rule is to label actions according to their function or outcome, rather than translating visual metaphors literally into text.

Study Guide reference/topics: Alternative text, functional icons, accessibility, Lookup fields, UX Fundamentals.

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

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 uploaded study guide identifies A. Reducing friction for users in achieving their goals as the correct benefit of inclusive design.

Inclusive design considers a wider range of user needs, abilities, contexts, and potential barriers. When those barriers are addressed, the resulting experience becomes easier for more people to understand and operate. The study guide therefore expresses the benefit in terms of reduced friction.

Option B contradicts the inclusive-design objective because designing exclusively for one user type risks excluding users whose circumstances or abilities differ from the assumed norm.

Option C also misrepresents inclusive design. The objective is not to simplify the experience to a generic lowest common denominator. Rather, the designer should identify barriers and create solutions that allow a broader range of people to participate successfully.

This answer is consistent with the inclusive-design principles earlier in the guide: recognize exclusion, learn from diversity, and solve for one in ways that can extend to many. When exclusion is reduced, users encounter fewer obstacles while trying to complete their intended tasks.

The practical outcome is therefore not only accessibility in a narrow sense, but a smoother and more usable experience across a broader population.

Study Guide reference/topics: Inclusive Design, reducing friction, user goals, exclusion, Human-Centered Design.

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

The correct answer is A. Create a Progress Indicator component that displays the flow's relevant stages, as stated in the uploaded study guide.

The problem described is not with the Screen Flow's logic itself; it is with the user's inability to understand how much of the multi-step process remains. The study guide addresses this by adding a visual Progress Indicator.

A progress indicator gives users an immediate representation of their current position within the flow and the stages that remain. That directly addresses the anxiety caused by uncertainty about completion.

Option B refers to a Status Tracker, but the study guide does not identify that as the appropriate component for this use case.

Option C introduces Salesforce Path with Guidance for Success. Path is used for stage-oriented record processes, whereas the question specifically concerns a custom multi-step Screen Flow. Adding Path would therefore not directly solve the progress-visibility issue identified in the scenario.

The UX principle represented by the answer is visibility of progress. In longer interactions, users should be able to understand where they are and how much work remains. A Progress Indicator makes that process state visible without forcing users to infer it.

Study Guide reference/topics: Screen Flow, Progress Indicator, multi-step processes, process visibility, Declarative Design.

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

The correct answer is B. Distinguishable, matching the uploaded study guide. Within WCAG's Perceivable principle, the distinguishable guidance focuses on making visual and auditory content sufficiently separable so that users can perceive important information. For text, buttons, and other interface elements, adequate color contrast is one of the central implementation requirements.

Salesforce's accessibility guidance explains that ordinary text should maintain sufficient contrast against its background and notes additional WCAG 2.1 contrast requirements for visual information needed to identify user-interface components and states, including button and input boundaries. Consequently, when a UX Designer selects foreground text and button-background colors, contrast and distinguishability must be evaluated rather than relying only on aesthetic brand preferences.

Adaptable concerns presenting information in ways that can be transformed or interpreted through different structures or presentation modes without losing meaning. Navigable addresses the user's ability to locate content, move through interfaces, understand focus, and determine their position. Neither directly describes the color-contrast requirement posed by the scenario.

Therefore, the UX Designer must ensure text and button treatments remain visually distinguishable, particularly for users with low vision or reduced color perception.

Study Guide reference/topics: WCAG, accessibility, distinguishable content, color contrast, Experience Builder, UX Fundamentals.

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

The correct answer is B. Identify the message, audience, and purpose for content, as confirmed by the uploaded study guide. Effective onboarding begins by understanding who the users are, what they need to learn, and why the information matters to them. Identifying the message determines what information must be communicated. Identifying the audience allows content to be adapted to users' roles, prior knowledge, and workflow needs. Identifying the purpose ensures that onboarding material drives a meaningful outcome rather than simply presenting information.

Option A is too restrictive. Written documentation can support onboarding, but treating it as the only learning mechanism ignores differences in learning context and user experience.

Option C treats pop-ups as a default solution before the communication need has been defined. Pop-ups may sometimes support contextual guidance, but they are only one delivery mechanism and can become intrusive if poorly targeted.

The HCD principle is to design onboarding around users rather than around a preferred content format. Understanding message, audience, and purpose therefore precedes selecting the specific onboarding mechanism.

Study Guide reference/topics: Onboarding, audience analysis, communication design, user needs, Human-Centered Design.

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

The study guide identifies C. Components Library on developer.salesforce.com as the correct answer. The key requirement is to locate a centralized resource containing Lightning component code, documentation, and specifications so the implementation team can work efficiently. The Components Library is designed for that purpose: it gives designers and developers access to component references, supported attributes, implementation details, examples, and behavioral expectations. Option A, Salesforce Extensions for VS Code, is a development-tooling environment. It helps developers work with Salesforce metadata and code, but it is not the primary reference library for exploring Lightning component specifications. Option B, Design Tokens, provides reusable design values such as spacing, colors, and other design attributes. Tokens help maintain visual consistency, but they do not function as a comprehensive component reference. From a UX implementation perspective, using documented Lightning components reduces unnecessary custom development and helps ensure that components behave consistently with Salesforce interaction patterns. It also improves implementation speed because teams can begin with an established component rather than inventing a new one.

Study Guide reference/topics: Lightning Components, LWC implementation, component documentation, SLDS, reusable UI architecture.

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

The correct answer is B. Lightning Design System Website. The study guide explicitly keys the Lightning Design System Website for this requirement.

The decisive requirements are that the UX Designer wants to explore sample code, observe how code changes affect the visual presentation, and do so without deploying anything to a Salesforce org. In the context of the study guide, the SLDS website is the resource designed to support exploration of Salesforce design-system patterns and component presentation without requiring an org deployment cycle.

Option A, the Developer Center's Lightning Component Library, is associated with component reference information and documentation, but it is not the resource keyed here for the real-time design exploration described.

Option C, a Sandbox Org, would require an actual Salesforce environment. That directly conflicts with the condition that the designer wants to experiment without deploying code to an org.

The broader SLDS principle is that designers and developers should be able to explore Salesforce visual patterns and component structures before committing implementation work to an environment. This accelerates iteration and reduces unnecessary deployment overhead during early experimentation.

Study Guide reference/topics: SLDS website, component exploration, sample code, rapid experimentation, Salesforce Lightning Design System.

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

The correct answer is A. App Builder property, as keyed in the uploaded Master Study Guide.

The key requirement is that administrators, rather than developers, should be able to change the component's functionality or styling depending on the page where the component is placed. An App Builder property provides the configuration surface identified by the guide for exposing component-level settings to administrators.

This enables a reusable custom Lightning Web Component to behave differently according to the configuration selected in Lightning App Builder. Instead of creating separate components for every page context, the component can expose configurable properties.

Option B, Styling hooks, addresses styling customization but does not satisfy the broader requirement to allow an administrator to change both functionality or styling through page-specific component configuration.

Option C, Audience page variations, concerns delivering page variations according to different audiences rather than configuring reusable properties of the component itself.

The design principle is configurable reuse: a well-designed custom component can expose meaningful settings so administrators can adapt it to multiple page contexts without modifying source code or duplicating the component.

Study Guide reference/topics: App Builder properties, Lightning Web Components, configurable components, administrator customization, Declarative Design.

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