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

The correct answer is C. Import Lightning stylesheets in Visualforce, according to the uploaded study guide.

The scenario is specifically about an organization that has not yet migrated to Lightning Experience but still wants custom Salesforce applications to present a Lightning-consistent visual appearance.

Within the study-guide framing, importing Lightning stylesheets into Visualforce provides the appropriate bridge between legacy Visualforce applications and the visual language associated with Lightning Experience.

Option A references an SLDS package, but the question is not asking how to build an independent front-end application using package-managed CSS resources. It asks for the Salesforce-based solution appropriate to the existing Visualforce context.

Option B, importing standard design tokens into a stylesheet, would not by itself reproduce the broader Lightning component styling required to give the application a consistent Lightning appearance.

The essential UX objective is visual consistency across platform generations. Users should encounter familiar spacing, typography, control treatments, and general presentation even when some applications remain on older Salesforce technology.

The study guide therefore points to Visualforce's ability to use Lightning styling as the appropriate way to achieve this transition-oriented design requirement.

Study Guide reference/topics: SLDS, Visualforce, Lightning Experience styling, legacy application consistency, Salesforce Lightning Design System.

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

The correct answer is B. Ability to toggle between multiple records. The uploaded UX Designer study guide explicitly identifies this requirement as a reason to recommend Console navigation. Console navigation is designed for users who work intensively with multiple records and related information during the same session. Rather than continually leaving one record page and opening another, users can maintain several records within the console workspace and switch between them efficiently. This makes the console particularly valuable for sales or service roles where users frequently compare, reference, or update multiple related records.

Option A is not the defining requirement in the study-guide scenario. Although console applications can support efficient multi-record workflows, the requirement specifically associated with the answer is the ability to toggle between multiple records.

Option C points in the opposite direction. Users whose work occurs primarily in the field generally have stronger mobile and simplified-navigation requirements rather than a desktop-oriented multi-record console workspace.

From a UX perspective, the navigation model should correspond to the user's task pattern. Standard navigation suits more linear interaction, whereas Console navigation is better suited to high-volume, multi-record work where reducing navigation overhead improves productivity.

Study Guide reference/topics: Console Navigation, Standard Navigation, multi-record workflows, productivity, Declarative Design.

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

The correct answer is C. Dynamic Actions, as explicitly stated in the uploaded study guide. Dynamic Actions allow actions displayed on a Lightning record page to vary according to specified conditions. This is exactly what Cloud Kicks needs because users only require particular actions at particular record statuses.

Instead of displaying every available action at all times, the designer can configure visibility rules so that relevant actions appear contextually. This reduces visual clutter in the Highlights panel and helps users focus on actions that make sense at the current stage of the workflow.

Option A, Audiences, is primarily used to tailor Experience Cloud or Lightning content for particular user groups or contexts. It does not directly solve conditional record-action visibility based on record state.

Option B, Dynamic Forms, controls field and field-section placement and visibility. Dynamic Forms can simplify a record page by displaying relevant fields conditionally, but the requirement here specifically concerns action buttons, making Dynamic Actions the correct capability.

From a UX standpoint, contextual actions support recognition over recall and reduce decision fatigue. Users should not have to mentally filter a long list of irrelevant commands before locating the action they need.

Study Guide reference/topics: Dynamic Actions, Highlights Panel, Lightning Record Pages, conditional visibility, Declarative 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 C. Invite team members to observe usability sessions, as keyed in the uploaded study guide.

The problem is not that usability findings are unavailable; the Development team does not sufficiently value or accept them. Allowing developers to observe users directly provides first-hand evidence of where participants struggle, hesitate, misunderstand the interface, or encounter barriers.

Option A adds external best-practice articles to each finding. Those resources may support a recommendation, but they remain indirect evidence. They do not allow developers to witness actual users interacting with the team's product.

Option B focuses on how much effort the research team has invested. Research effort does not establish that a finding is valid or important. Acceptance should be based on user evidence rather than on the amount of work already spent collecting it.

The study guide therefore favors direct exposure to the research process. When team members observe usability sessions themselves, findings become less abstract and are harder to dismiss as merely the UX Designer's interpretation.

This also strengthens multidisciplinary ownership: usability becomes something the whole product team can observe and understand rather than a report delivered by one specialist group.

Study Guide reference/topics: Usability testing, observation, stakeholder buy-in, research acceptance, Testing.

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

The study guide identifies A. Reframe the product objectives from multiple, diverse perspectives as the correct answer. Consequence Scanning is a responsible-design activity intended to help teams think beyond the immediate intended benefits of a product. Before launch, designers and stakeholders consider how the product could affect different people, communities, systems, and contexts, including outcomes that may not have been part of the original product requirements. Reframing objectives from multiple perspectives is therefore central to the exercise. A design team may initially view a feature primarily through business or technical goals; consequence-oriented analysis broadens the discussion by considering who may be excluded, harmed, disadvantaged, or affected unintentionally. Option B describes a potentially positive result of collaborative work, but improving team well-being is not the principal goal of Consequence Scanning. Option C concerns marketing and public relations rather than responsible product design. Within Human-Centered Design, this technique helps challenge assumptions and exposes downstream implications before they become embedded in a released product. The study-guide answer therefore emphasizes diversity of perspective as a mechanism for improving responsible design decisions.

Study Guide reference/topics: Consequence Scanning, responsible design, diverse perspectives, unintended consequences, Human-Centered Design.

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

The study guide identifies C. Menu tabs can be Visualforce and Lightning pages as the correct administrative capability for Salesforce mobile navigation setup.

The question is testing what administrators can include when configuring the navigation experience available to mobile Salesforce users. According to the answer key, navigation entries can include supported Visualforce and Lightning pages, giving administrators a mechanism to expose relevant application destinations through the mobile navigation structure.

Option A states that menu tabs can be based on different user types. Although user access can influence what users ultimately see within Salesforce, that is not the navigation capability selected by the study guide in this question.

Option B claims visibility can be based on user location. The guide does not identify geographic location as the relevant administrative mechanism for setting up mobile navigation tabs.

The broader declarative-design principle is that mobile users should have direct navigation to the Salesforce resources relevant to their workflows. Administrators can configure supported page types as destinations without requiring users to reach them through indirect navigation paths.

This allows the Salesforce mobile experience to incorporate both Lightning-based and Visualforce-based functionality where appropriate.

Study Guide reference/topics: Salesforce mobile navigation, menu tabs, Visualforce pages, Lightning pages, Declarative Design.

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

The correct answer is A. The company's style guide, according to the uploaded study guide.

A corporate style guide defines the standards that govern how the brand should be represented. Depending on the organization, this can include approved logos, colors, typography, imagery, tone, spacing conventions, and rules governing how brand assets should or should not be used.

When implementing the brand within Salesforce, the UX Designer should therefore use the company's style guide as the authoritative reference. This ensures the Salesforce experience remains consistent with the organization's other customer-facing and employee-facing channels.

Option B, a design system, may provide reusable components, patterns, tokens, and implementation standards. While highly valuable, the question specifically asks for the document serving as the brand source of truth, and the study guide identifies the style guide.

Option C, project design principles, typically describes higher-level principles that guide decisions within a specific initiative. They do not necessarily contain the detailed brand specifications required for consistent implementation.

The UX objective is to avoid isolated interpretation of the company's identity. Using one authoritative brand reference helps designers make consistent decisions across pages, components, communications, and channels.

Study Guide reference/topics: Brand consistency, style guides, Salesforce branding, UX Fundamentals.

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

The correct answer is C. Account, Contact, Opportunity, according to the uploaded study guide.

The question tests the Salesforce data-model transition associated with converting a Lead. The study guide identifies the resulting business records as Account, Contact, and Opportunity.

Conceptually, each record represents a different part of the emerging customer relationship. The Account represents the customer or organization context, the Contact represents the individual person involved, and the Opportunity represents potential sales business being pursued.

Option A includes an Order. An Order represents a later transactional concept and is not one of the three records identified by the guide as the typical outcome of lead conversion.

Option B refers to a “Converted Lead” and Activity, but the guide does not identify those as the three resulting records in the standard lead-to-opportunity flow being tested.

For a UX Designer, understanding this record lifecycle matters because a user interface should align with what happens to users' data as they advance a sales process. Navigation, record context, and process guidance all depend on understanding how a Lead transitions into the customer and opportunity records sales users subsequently work with.

Study Guide reference/topics: Lead Conversion, Account, Contact, Opportunity, Sales process, Declarative Design.

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

The study guide identifies C. Configure a pre-filtered opportunity list view for each key attribute with the partner group as the correct answer. The requirement is for partners to quickly browse opportunities according to predetermined business criteria. The guide's selected solution is therefore a declarative one: create list views that are already filtered for the relevant opportunity attributes and expose those views to the appropriate partner audience.

This approach directly addresses both conditions stated in the scenario. One view can focus on opportunities closing within two weeks, while another can focus on opportunities valued above $100,000. Partners do not need to repeatedly construct their own filters or understand the underlying filtering logic.

Option A introduces a custom Lightning Web Component even though the requirement can be addressed using standard list-view functionality. That adds unnecessary implementation complexity.

Option B delegates filter creation to each partner, which conflicts with the requirement for a quick, standardized browsing experience.

The design principle reflected by the study guide is to prefer configured, reusable Salesforce functionality when it satisfies the user need. Pre-filtered list views reduce interaction effort and provide consistent segmentation across the partner experience.

Study Guide reference/topics: Experience Builder, opportunity list views, partner experience, filtering, Declarative Design.

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

The uploaded study guide identifies B. Grid System as the correct SLDS resource for responsive design.

A responsive interface needs its layout to adapt as the available screen width changes. The Grid System is the resource selected by the guide because it provides the structural mechanism for arranging interface content into flexible rows and columns.

This directly addresses page-level responsiveness: content can be organized so that it uses available horizontal space appropriately and can be repositioned or wrapped as the viewport changes.

Option A, Design Tokens, addresses reusable design values. Tokens can support consistency for properties such as spacing, color, or other design attributes, but the question specifically asks what the designer should use for responsive layout design.

Option C, Component Blueprints, provides structural guidance for individual SLDS components rather than serving as the primary layout system for responsive page organization.

The key study-guide distinction is therefore between component styling/resources and layout architecture. When the issue is adapting page composition to different screen sizes, the Grid System provides the relevant SLDS mechanism.

This makes the grid an essential foundation for designing Salesforce interfaces that remain organized and usable across varying viewport dimensions.

Study Guide reference/topics: SLDS Grid System, responsive design, rows and columns, adaptive layouts, Salesforce Lightning Design System.

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

The correct answer is A. To avoid societal bias. The uploaded study guide directly identifies societal bias as the concern when demographic data is selected for AI-model use. Demographic information can contain or reflect historical social inequalities. When characteristics such as age, gender, location, ethnicity, socioeconomic indicators, or related proxies are included in a model without careful justification, the model may learn patterns that reproduce existing disparities rather than simply represent neutral relationships. The UX and responsible-design implication is that teams must question both what data is being collected and why the model needs it. Data should not be introduced simply because it is available. Instead, each attribute should have a legitimate purpose that supports the intended user or business outcome without unnecessarily increasing the risk of discriminatory behavior. Option B refers to confirmation bias, which concerns a tendency to favor evidence that supports existing beliefs. While that can affect research and decision-making, it is not the specific data-governance risk described here. Option C, interaction bias, relates more to patterns arising from how people interact with a system rather than demographic information itself. The study-guide principle is therefore that responsible AI design requires deliberate demographic-data selection to reduce the propagation of societal bias into automated decisions.

Study Guide reference/topics: Responsible AI, demographic data, societal bias, responsible design, Human-Centered Design.

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

The uploaded study guide identifies B. Grid as the correct SLDS utility.

The requirement describes a responsive layout in which content must adapt as available screen width changes. Elements may occupy multiple columns on wider screens and then wrap into additional rows when horizontal space becomes constrained.

A Grid system is designed precisely for this type of flexible page structure. It allows designers and developers to organize content into responsive rows and columns rather than relying on fixed positioning.

Option A, Float, can affect how individual elements position themselves relative to surrounding content, but it does not provide the structured, flexible responsive-layout system required by the scenario.

Option C, Alignment, controls positioning or distribution of content but does not itself define the responsive column-and-row layout architecture described.

The underlying UX principle is that responsive design should adapt the interface to varying screen sizes without requiring a completely separate page for each device. A grid gives the layout a systematic structure for resizing, wrapping, and repositioning content while retaining hierarchy.

Therefore, when the design requirement explicitly describes columns that can expand and wrap into new rows, the SLDS Grid utility is the appropriate solution.

Study Guide reference/topics: SLDS Grid, responsive design, flexible layouts, columns and rows, Salesforce Lightning Design System.

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

The uploaded UX Designer study guide identifies C. Define the goals of the study as the correct answer.

Before recruiting participants or writing detailed study procedures, the UX Designer must establish what the usability study is intended to learn. In this scenario, the broad concern is whether the Experience Cloud site is intuitive, but that concern should be translated into clear research objectives.

Defining goals determines the rest of the study design. The goals influence which tasks participants should perform, which user groups should participate, what behaviors should be observed, and which outcomes will indicate success or reveal usability problems.

Option A, recruiting the right participants, is essential, but participant criteria should be derived from the goals and target users of the study.

Option B, writing a test plan, is also important, but a useful test plan depends on first understanding the study objectives. Without clearly defined goals, the plan can become a collection of activities without a coherent research purpose.

The guide therefore establishes the planning sequence correctly: define what needs to be learned first, then design the study around that objective.

Study Guide reference/topics: Usability Studies, research goals, study planning, Experience Cloud testing, Testing.

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

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. Learning about the user's behavior and preferences. The uploaded study guide directly confirms this answer. Usability testing evaluates how representative users actually interact with a product, prototype, or workflow. Designers observe where users succeed, hesitate, misunderstand information, make errors, or adopt unexpected approaches. These behavioral observations reveal whether the experience aligns with users' mental models and expectations.

Option A contradicts proper usability-testing methodology. The objective is not to train participants to operate the interface correctly. Excessive instructions or coaching can contaminate the study because they prevent researchers from observing whether the design itself communicates what users need to know. The participant should generally attempt representative tasks while the researcher observes behavior and gathers feedback.

Option C describes a narrower comparative optimization technique associated more directly with A/B testing, where different interface variations are exposed to users and measured against a defined outcome. Usability testing instead concentrates on understanding why users experience particular successes or problems.

The critical examination distinction is therefore:

Usability testing = understand user behavior and usability problems.

A/B testing = compare alternative variations quantitatively.

That makes option B the only response aligned with the purpose of usability research.

Study Guide reference/topics: Usability testing, user behavior, user preferences, observational research, Testing.

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

The correct answer is A. Rich Text, images, and links, which is also the answer explicitly provided by the uploaded study guide. Salesforce Path is intended to guide users through stages of a business process. For each Path stage, an administrator can designate key fields and provide contextual Guidance for Success. Salesforce documentation describes this guidance as a place for information such as tips, links, questions, and company policy information that assists users in successfully completing that stage. This distinction is important. A Path already acts as a visual representation of progress through values such as Opportunity Stage. The Guidance for Success area supplements that progression with useful instructional material. Rich content and links can explain activities, remind representatives of procedures, provide supporting resources, or direct users toward relevant information. A Progress Indicator is therefore not the appropriate content element for Guidance for Success because Path itself visually represents progression. Merge fields are also not the expected answer in this configuration context. Consequently, rich instructional content provides the strongest fit for stage-specific coaching and supports Salesforce's declarative approach to improving process usability without developing a custom interface.

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

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

According to the uploaded Master Study Guide, the correct answer is B. Up to 10. The source specifically presents an Unlimited Edition Salesforce org and keys the dynamic-dashboard limit as ten.

This item is primarily testing a Salesforce platform limit rather than a general UX design principle. The UX context is that dynamic dashboards can improve the experience by allowing dashboard information to be presented in a way relevant to the viewing user, but their use is constrained by the platform limits represented in the study material.

Option A, up to 50, is not the value provided by the study guide. Option C assumes that an Unlimited Edition license means every feature is literally unlimited; the source explicitly rejects that assumption by providing a finite dashboard limit.

For certification purposes, the important point is to distinguish the edition name from individual feature entitlements or limits. “Unlimited Edition” does not mean that every configurable Salesforce resource has no limit.

Because this batch is being answered from the supplied study guide, 10 is the answer supported by that source.

Study Guide reference/topics: Dynamic Dashboards, Salesforce limits, Unlimited Edition, Declarative Design.

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

The correct answer is A. Tabbing order is logical, as confirmed by the study guide. Keyboard accessibility testing evaluates whether users can navigate and operate an interface without relying on a mouse or other pointing device. One of the most important checks is whether pressing Tab and Shift+Tab moves focus through interactive controls in an order that is logical, predictable, and consistent with the visual and semantic structure of the page. For example, focus should generally move through navigation controls, form fields, buttons, and links in an understandable sequence. An unexpected jump to unrelated content can make the interface difficult or impossible to use for people who depend on keyboard navigation or assistive technologies. Option B is not a standard keyboard-navigation requirement. Keyboard actions do not need to provide audio feedback simply because they are accessible. Option C is also insufficient because accessibility cannot depend solely on a specific color to communicate interactivity or focus. Keyboard users require a perceivable focus state, but the question asks specifically what can be verified by testing the navigation sequence. Therefore, keyboard testing should verify that focus proceeds in a meaningful and usable tab order, enabling users to reach and operate interactive elements successfully.

Study Guide reference/topics: Accessibility testing, keyboard navigation, focus order, tab sequence, Testing.

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