Plat-UX-101 Salesforce Certified Platform User Experience Designer Free Practice Exam Questions (2026 Updated)

The correct answer is B. Docked prompt using In-App Guidance, as specified in the uploaded study guide.

The requirement is to inform users that a new feature has become available and provide a short explanatory video in the context of their Salesforce experience. In-App Guidance is specifically intended for contextual onboarding, feature announcements, adoption support, and targeted instructional content.

A Docked Prompt is appropriate because it can remain visible while allowing the user to continue interacting with the application. It provides enough space for explanatory content without necessarily blocking the entire workflow.

Option A, using the Utility Bar, would place the video in a persistent productivity area, but that does not provide the same contextual announcement mechanism for a newly enabled feature.

Option C requires a custom component even though Salesforce provides an out-of-the-box onboarding capability suited to this requirement. Introducing custom development would add unnecessary implementation and maintenance effort.

The study-guide principle is to use contextual, declarative guidance when users need timely help or feature education. Rather than forcing users to search external documentation, guidance can be delivered directly within their working environment.

Study Guide reference/topics: In-App Guidance, Docked Prompts, onboarding, feature adoption, Declarative Design.

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

The correct answer is B. Community Manager. The uploaded study guide explicitly associates a user who moderates forums, enforces community standards, and supports members with the Community Manager persona. Persona identification is important during UX discovery because different user archetypes have different goals, responsibilities, pain points, and workflow expectations. A Community Manager typically focuses on maintaining the health and quality of an online community. Their activities commonly include monitoring member participation, moderating discussions, responding to inappropriate content, applying community policies, encouraging engagement, and assisting members.

A Site Admin is more closely associated with administration and configuration responsibilities, such as site settings, access, technical configuration, or platform maintenance. Although a Site Admin can support an Experience Cloud environment, the activities described in the question are primarily community-governance activities rather than system-administration activities.

A Support Manager would normally focus on support operations, service teams, escalations, case management, agent performance, or customer-service delivery rather than ongoing forum moderation and community-policy enforcement.

From a UX perspective, correctly identifying the persona helps the designer build navigation, moderation tools, dashboards, workflows, and information architecture around the user's real operational responsibilities.

Study Guide reference/topics: Personas, user research, Experience Cloud users, role identification, Discovery.

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

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.

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

The correct answer is B. Have users sort the cards based on similar categories or groups, as confirmed by the study guide. Card sorting is a UX research method used to understand how users naturally categorize and mentally organize information. Salesforce Trailhead specifically describes card sorting as suitable for grouping things into categories, giving navigation-menu items as an example. For an Experience Cloud site's navigation structure, the designer can represent pages, tasks, topics, or content items as cards and ask representative users to organize them into groups that make sense to them. Depending on the research design, participants may also label those groups. The resulting patterns help inform the site's information architecture, including menu categories, grouping, hierarchy, and terminology.

Option A describes a comparative evaluation of alternative menu designs and is closer to usability comparison or A/B-style testing than card sorting. Option C imposes an arbitrary alphabetical structure instead of investigating users' mental models and expectations.

The core Discovery principle is that information architecture should reflect how users understand the domain rather than how the organization's internal structure happens to be arranged. Card sorting therefore converts user-generated grouping patterns into evidence for designing more intuitive navigation.

Study Guide reference/topics: Discovery research, card sorting, information architecture, navigation, mental models.

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

The uploaded study guide keys A. Survey as the correct answer. The abbreviated wording is preserved exactly from the supplied source.

Within the choices provided, a survey is the method that directly gathers information from users or a broader participant population. That makes it consistent with the study guide's broader human-centered emphasis on understanding people rather than making design decisions entirely from internal assumptions.

Option B, heuristic analysis, is an expert-led evaluation method. It can identify usability problems by comparing an interface against established principles, but it does not directly collect perspectives from the diverse users whose needs an inclusive design should address.

Option C, stakeholder analysis, focuses on understanding relevant organizational or project stakeholders. While stakeholders can supply important business and operational context, their perspectives do not automatically represent the full range of end-user experiences.

The source itself provides only the question, options, and keyed answer; it does not provide a deeper rationale for why “Survey” was selected. Accordingly, the supported interpretation is that the survey is the option most directly associated with collecting user input across a broader group.

For this study guide, the answer remains A.

Study Guide reference/topics: Inclusive Design, surveys, user input, Human-Centered Design.

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

The study guide identifies A. Formula Field, Static Resource, and Object Page Layout as the correct combination. The scenario requires the record detail page to show a custom visual indicator that changes according to the current membership level. The tools selected in the guide support that requirement declaratively.

A Static Resource can hold the image assets required for the membership indicators. A Formula Field can determine which visual representation should be shown according to the data stored on the record. The resulting field can then be positioned on the relevant Object Page Layout so that users see the membership indicator as part of the record experience.

Option B refers to an Image Field and Dynamic Forms, but that combination is not the platform approach selected by the study guide for deriving the displayed image from membership-level logic.

Option C introduces Lightning components and SLDS icons. That could imply a more customized implementation, while the guide favors the simpler declarative combination of formula, resource, and layout configuration.

The UX value is immediate recognition: a visual membership indicator can communicate status faster than requiring users to interpret raw field values.

Study Guide reference/topics: Formula Fields, Static Resources, page layouts, visual status indicators, Declarative Design.

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

The correct answer is C. Lead, Contact, and Opportunity, as keyed by the uploaded study guide.

These three standard objects correspond to different parts of the realty customer's sales lifecycle. A Lead can represent a prospective home buyer before that person becomes an established customer relationship. A Contact represents the individual once that relationship is maintained within Salesforce, while an Opportunity represents the potential sales transaction being pursued.

That combination fits the scenario because brokers need to track people who begin by shopping for homes, establish contact with the real estate company, and potentially progress toward a transaction.

Option A includes Address and Property, which are not the three standard objects identified by the study guide for this lifecycle.

Option B includes Account, Person Account, and Contact, but this combination does not represent the prospect-to-sales-opportunity progression the guide is testing.

The UX significance is that the underlying object model should reflect the business stages users actually work with. Brokers need to distinguish prospective buyers, known individuals, and active sales opportunities rather than treating all information as one undifferentiated customer record.

Study Guide reference/topics: Lead, Contact, Opportunity, Salesforce standard objects, customer lifecycle, Declarative Design.

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

The correct answer is A. Component Blueprints, exactly as identified in the study guide. The key phrases are accessible HTML and CSS and implementation guidelines. Component Blueprints are the SLDS resource the study guide associates with these needs. They provide the structural patterns required to build components that visually and semantically align with the Salesforce Lightning Design System.

This is especially important when a UX Designer and developer are implementing a custom Lightning Web Component rather than relying entirely on an existing base component. Starting from a documented blueprint helps maintain consistency with established Salesforce component structure.

Option B, Design Tokens, serves another purpose. Tokens represent reusable design values such as spacing, sizing, or color. They support visual consistency but do not provide complete component markup and implementation patterns.

Option C, Development Tools, may support implementation workflow, but it does not represent the specific SLDS location described in the question.

The study-guide distinction is therefore precise: when a designer requires the HTML/CSS structure and implementation guidance for an SLDS component, the appropriate reference is the Component Blueprint.

This also reinforces the design-system objective of reducing custom reinvention and promoting consistent, accessible interface construction.

Study Guide reference/topics: SLDS Component Blueprints, accessible markup, component implementation, LWC, Salesforce Lightning Design System.

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

The correct answer is A. In-App Guidance, as explicitly stated in the study guide.

The question contains two direct indicators: users need Floating or Docked Prompts, and administrators want to evaluate adoption through Salesforce reporting capabilities. The study guide associates those requirements with the out-of-the-box In-App Guidance feature.

In-App Guidance is used to provide contextual assistance directly within the Salesforce experience. The prompts can support users as they learn a new process without requiring them to leave their workflow for separate training material.

Option B introduces an AppExchange solution even though the requirement specifically asks for an out-of-the-box feature.

Option C, Screen Flow, can guide users through a business process, but it is not the feature identified by the guide for Floating and Docked Prompts.

The distinction is important: Screen Flow guides users through a structured transactional workflow, whereas In-App Guidance provides contextual adoption and learning assistance around the interface and process.

Because the administrative team also wants to assess adoption of the guidance, the study guide's answer fits both the instructional and measurement aspects of the requirement.

Study Guide reference/topics: In-App Guidance, Floating Prompts, Docked Prompts, adoption measurement, Declarative Design.

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

The correct answer is C. Key fields to complete before next Path stage, which the uploaded study guide confirms. Salesforce Path provides stage-oriented guidance for processes such as opportunities. Its major UX value comes from showing users where they are within the process and surfacing the information most relevant to each stage. Salesforce documentation states that a Path can expose up to five key fields per step, helping users focus on important information, together with contextual Guidance for Success. This makes key fields especially useful for onboarding. A new sales representative does not need to memorize every field or requirement associated with the opportunity lifecycle. Instead, the interface progressively surfaces the important information at the relevant stage, reducing cognitive load and reinforcing the intended business process.

Option A is not a standard defining capability of Path. Path does not primarily exist to supply integrated approval-automation buttons. Option B refers to a separate component and does not represent the core stage-specific onboarding functionality being tested.

One nuance is important: Path highlights key fields but does not inherently make those fields mandatory solely because they appear there; validation rules may be required when true enforcement is needed.

Study Guide reference/topics: Salesforce Path, key fields, onboarding, Guidance for Success, process guidance.

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

The correct answer is A. Observing user behavior, as explicitly identified by the uploaded study guide.

Human-centered design begins with understanding the people for whom a product, service, or process is being designed. Observing actual user behavior allows designers to understand what users really do, including their workflows, difficulties, workarounds, and environmental constraints. This provides evidence that may not emerge if the team relies only on assumptions or internal business objectives.

Option B places company OKRs at the center of requirements definition. Business objectives are important constraints, but they do not substitute for understanding users when adopting a human-centered approach.

Option C places rapid prototyping before ideation. Prototyping is useful for making ideas tangible and testing them, but the team first needs to understand users and generate potential solutions.

The study-guide distinction is therefore between evidence about people and organization-centered or prematurely solution-centered activities. Observing users gives the organization direct insight into needs and behavior and helps ensure subsequent design decisions are grounded in real experiences rather than assumptions.

Study Guide reference/topics: Human-Centered Design, user observation, behavioral research, user needs.

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

The uploaded UX Designer study guide identifies A. Specifying breakpoint sizes as the responsive design best practice.

Responsive design must account for changes in available screen width. Breakpoints provide defined thresholds at which the layout can adapt so that content remains usable and appropriately structured across different screen sizes.

The study guide therefore selects specifying breakpoint sizes as the practice that directly supports responsive behavior.

Option B, using interaction models, is not the responsive-layout mechanism described in this question. Interaction models can define how users work with an interface, but they do not themselves establish when the visual layout should change in response to screen dimensions.

Option C, creating a separate mobile-specific site, is not the best practice identified by the guide. The responsive approach is intended to allow one experience to adapt according to available space rather than requiring an entirely separate site merely because the device is smaller.

The important distinction is between adaptive layout behavior and maintaining separate experiences. Breakpoints allow the design to respond systematically as the viewport changes.

For the UX Designer, the practical objective is to define when content should resize, reorganize, wrap, or otherwise change presentation so that the experience remains usable across device dimensions.

Study Guide reference/topics: Responsive Design, breakpoints, screen sizes, adaptive layouts, UX Fundamentals.

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

The correct answer is B. Field-Level Security, as explicitly identified in the study guide. The important constraint is that Cloud Kicks has one standard Order page layout shared by different types of users. The requirement is therefore not to create separate layouts, but to control which fields are visible to internal versus external users.

The study guide selects Field-Level Security because it governs whether particular users can see or interact with specific fields even when the same page layout is shared. This makes it suitable for restricting sensitive or irrelevant information without duplicating the overall record-page structure.

Option A, Audience Targeting, is associated with presenting Experience Cloud or component content to different audiences, but it is not the field-visibility mechanism selected in this study-guide scenario. Option C, Dynamic Forms, can conditionally control field and section presentation on supported record pages, but the answer key specifically identifies Field-Level Security for the shared-layout visibility requirement.

From a UX standpoint, limiting users to the fields that are relevant and permitted for their role reduces unnecessary information exposure and keeps the shared record experience focused while preserving the organization's security model.

Study Guide reference/topics: Field-Level Security, shared page layouts, user-specific visibility, Sales Cloud, Declarative Design.

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

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 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 uploaded study guide identifies C. Recognizing peers with badges as the correct answer.

The question is specifically about increasing customer engagement in an Experience Cloud portal that is already performing well. The study guide selects peer recognition through badges because it introduces a direct participation and recognition mechanism within the community experience.

Badges can acknowledge contributions or activity, creating a visible form of recognition between participants. In the context of the answer key, this is considered more directly related to engagement than changes focused mainly on presentation.

Option A, personalized branding, changes how the portal looks or feels for an audience, but branding alone does not provide the same participation-oriented mechanism.

Option B, customizing page layouts, can improve information organization, yet the portal is already described as performing well. Layout changes therefore do not target engagement as directly as recognition does.

The key distinction in the study guide is between experience presentation and community participation. If the objective is specifically to encourage engagement, a mechanism that acknowledges users' contributions provides a stronger engagement-oriented feature than simply changing visual design or layout configuration.

Study Guide reference/topics: Experience Cloud, customer engagement, peer recognition, badges, Declarative Design.

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

The study guide identifies A. Perform common tasks without navigating away from the page as the correct use case for the Utility Bar.

The Utility Bar is intended to provide quick access to frequently needed productivity tools while users remain in the context of their current Salesforce work. That makes it especially valuable when sellers repeatedly perform auxiliary tasks and would otherwise need to navigate to another page or application area.

The UX benefit is reduced context switching. Keeping commonly used tools immediately available allows users to maintain focus on the record or workflow they are currently handling.

Option B refers to quick access to favorite records or items, but the study-guide scenario specifically associates the Utility Bar with performing common tasks without leaving the current page.

Option C is also inconsistent with the answer key. The Utility Bar is not presented here as a mobile-specific enhancement.

The broader UX principle is efficiency of interaction. High-frequency activities should be available in a persistent, convenient location when doing so reduces unnecessary navigation and interruption.

Therefore, when discovery shows sellers value productivity and immediate access to tools, the standard Utility Bar use case is to allow them to complete common supporting tasks while remaining on their current page.

Study Guide reference/topics: Utility Bar, productivity, task efficiency, Lightning applications, Declarative Design.

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

The uploaded UX Designer study guide identifies B. Service-Blueprinting Workshop as the correct answer.

The scenario places Cloud Kicks after the research and synthesis stages. The team already understands the issues discovered through research and now needs a collaborative process for redesigning the service with stakeholders. A service-blueprinting workshop is therefore the appropriate next activity because it gives participants a structured way to examine how the service works across customer-facing interactions and the supporting processes behind those interactions.

The key distinction is that the team is no longer primarily trying to discover problems; it is using established findings to collaboratively shape an improved service.

Option A, Service Usability Testing, would be more appropriate when evaluating a proposed or existing service experience with users. Testing does not itself provide the collaborative service-redesign framework described in the question.

Option C, a Pitch Session, is primarily about presenting or advocating for an idea rather than jointly mapping and redesigning service delivery.

The guide therefore positions service blueprinting as the bridge between synthesized research and collaborative redesign.

Study Guide reference/topics: Service Blueprinting, collaborative design, service redesign, stakeholder participation, Human-Centered Design.

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

The correct answer is B. Visual, Content, and Interaction Design, exactly as identified in the uploaded study guide. The question makes an important distinction between configuring a Salesforce Theme and creating a complete brand experience. A theme establishes some foundational visual properties, but the study guide indicates that brand experience also depends on three broader UX dimensions: visual design, content design, and interaction design.

Visual design influences how users perceive the organization's identity through presentation choices and interface styling. Content design affects brand expression through the information users encounter, including wording, hierarchy, and communication style. Interaction design influences how the experience behaves as users navigate, select actions, complete tasks, and receive feedback.

Option A includes harmony and responsiveness, which are relevant design concerns but do not constitute the three categories identified in this study-guide scenario.

Option C includes shapes and typography, which are individual visual-design elements rather than the broader set of UX disciplines required to communicate brand consistently.

The central study-guide lesson is that branding is not produced by colors or theme configuration alone. Users experience a brand through what the interface looks like, what it communicates, and how it behaves.

Study Guide reference/topics: Brand Experience, Visual Design, Content Design, Interaction Design, UX Fundamentals.

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