Free Practice Questions for Salesforce Plat-UX-101 Exam

The correct answer is C. Expand the first section by default, exactly as keyed in the uploaded study guide.

An accordion is intended to reduce vertical complexity by grouping content into expandable and collapsible sections. On a mobile screen, however, presenting every section collapsed can introduce an additional interaction before users see any substantive content. Expanding the first section by default gives users an immediate entry point and demonstrates how the accordion behaves.

Option A is unsuitable because the browser Back control normally represents navigation history. Using it as the primary mechanism for collapsing accordion content would conflict with users' established expectations about browser behavior.

Option B would cause the interface to reposition content whenever a section is expanded. That can produce unexpected movement and interfere with the user's spatial understanding of the page.

Within the study guide's framing, option C provides the most predictable mobile experience: the user immediately sees useful content while retaining the ability to expand other sections when required.

This reflects a broader UX principle of minimizing unnecessary interaction while keeping content organized through progressive disclosure.

Study Guide reference/topics: Accordion usability, mobile UX, progressive disclosure, content organization, UX Fundamentals.

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

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 study guide identifies A. Run the Salesforce Optimizer App to identify fields not in use as the correct answer. The scenario presents two related UX problems: the Contact page contains too many irrelevant fields, and users experience long page-load times. The selected approach begins by identifying which configuration elements are no longer providing value.

Using Salesforce Optimizer gives the organization evidence about unnecessary or underused configuration so that administrators can make informed decisions about simplifying the experience. This is stronger than merely relocating unused information.

Option B does not actually solve the underlying problem. Moving unused fields to another section still leaves those fields in the interface and can retain unnecessary page complexity.

Option C, In-App Guidance, could help explain where important fields are located, but it would layer guidance on top of an already cluttered experience rather than addressing the clutter itself.

The UX implication is that unnecessary interface elements should be evaluated and removed rather than simply documented or rearranged. A cleaner Contact experience can make relevant sales information easier to find while reducing the amount of configuration presented on the page.

Study Guide reference/topics: Salesforce Optimizer, page simplification, unused fields, Sales Cloud UX, Declarative Design.

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

The correct answer is C. Card Sorting, as stated in the uploaded study guide.

The question emphasizes two related needs: understanding employees' mental model and creating an information architecture that matches user expectations. Card sorting is directly suited to this because participants organize items into categories according to how they naturally perceive relationships between them.

The results reveal how users group concepts, which labels make sense to them, and how content or functions might be organized within navigation. That makes the method particularly useful before finalizing the structure of a new community.

Option A, Cognitive Walkthrough, evaluates whether users can successfully progress through an existing or proposed interaction based on their expected knowledge and goals. It does not primarily generate an information architecture.

Option B, Mind Mapping, can help organize ideas or concepts but is not the user-research technique selected by the guide for uncovering how users classify information.

The study-guide principle is that information architecture should reflect the way users mentally organize the domain rather than merely mirror an internal organizational structure. Card sorting supplies evidence for designing that structure.

Study Guide reference/topics: Card Sorting, information architecture, mental models, user expectations, Discovery.

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

The correct answer is C. Objects to represent storage facilities and fields to store facility details, as stated in the uploaded study guide. The spreadsheet analogy maps directly to the Salesforce data model. In the spreadsheet, each row represents an individual storage facility, while each column represents an attribute of that facility.

In Salesforce, the collection of facilities should therefore be represented by an object. Each individual facility becomes a record of that object. Properties that describe the facility—such as location, capacity, facility type, or status—should be represented by fields on that object.

Option A reverses these concepts by treating facility details as objects and storage facilities as fields. This would not correctly model the entities represented by spreadsheet rows.

Option B creates separate objects for both facilities and their attributes even though the scenario describes the details simply as characteristics of each facility rather than separate related entities.

A useful conceptual mapping is:

Spreadsheet → Salesforce

Row → Record

Column → Field

Dataset/entity type → Object

Correct data modeling directly affects UX because well-structured objects and fields produce clearer forms, record pages, reports, filtering, and navigation. Therefore, storage facilities belong as object records, with their descriptive details represented as fields.

Study Guide reference/topics: Salesforce data model, objects, records, fields, spreadsheet migration, Declarative Design.

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

The correct answer is B. Prioritization Matrix, exactly as identified in the uploaded study guide. A prioritization matrix helps a UX or product team evaluate candidate work items using explicit criteria. In this scenario, the relevant dimensions are user value and development effort. Plotting or categorizing potential user stories against these dimensions helps the team identify high-value, comparatively low-effort work and distinguish it from lower-value or significantly more expensive initiatives.

This approach provides a rational mechanism for deciding which user stories should receive attention first rather than relying on stakeholder preference or intuition alone.

Option A, Card Sorting, is a research technique for understanding how users categorize information. It is useful for navigation and information architecture but does not evaluate development effort.

Option C, Customer Journey Mapping, visualizes a user's experience across stages and touchpoints, including actions, pain points, and opportunities. It can generate candidate improvements but does not itself provide the structured value-versus-effort prioritization requested here.

The Discovery process frequently produces more opportunities than a team can implement immediately. Prioritization translates those findings into an actionable backlog by connecting user needs with delivery constraints.

Thus, a Prioritization Matrix is the appropriate technique for informing user stories according to both impact and implementation effort.

Study Guide reference/topics: Prioritization Matrix, user value, development effort, user stories, Discovery.

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

The correct answer is A. Dynamic Forms, exactly as stated in the uploaded study guide.

The scenario describes two related requirements: fields and sections should be treated as individual page components, and their visibility should vary according to the current reservation process context. Dynamic Forms is the feature selected by the guide for precisely this page-composition requirement.

Because all fields remain necessary, simply deleting fields from the object or layout would not solve the problem. Instead, the experience needs to show relevant information conditionally so that agents are not confronted with every field simultaneously.

Option B, In-App Guidance, would provide instructional prompts but would not restructure the underlying field presentation.

Option C, Flow Builder, can guide users through a defined process, but the requirement here is specifically to control the visibility and arrangement of fields and sections on the record page itself.

The study-guide principle is contextual presentation: maintain the required data model while reducing visual clutter by showing information when it becomes relevant. Dynamic Forms enables that page-level flexibility without requiring a completely custom interface.

Study Guide reference/topics: Dynamic Forms, field visibility, record pages, conditional presentation, Declarative Design.

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

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 B. Recognize exclusion. Learn from diversity. Solve for one, extend to many. The uploaded study guide explicitly identifies these as the inclusive-design action-oriented principles. Recognize exclusion means designers actively identify where products, processes, assumptions, or environmental conditions prevent certain people from participating effectively. Exclusion should be treated as a design problem rather than simply as an edge case.

Learn from diversity means incorporating perspectives and lived experiences from people with different capabilities, backgrounds, circumstances, and interaction needs. A team composed of people with similar experiences can easily overlook barriers that are obvious to users outside that group.

Solve for one, extend to many recognizes that addressing a specific exclusion can produce benefits for a much broader population. For example, interface improvements created for users with permanent motor limitations may also benefit someone temporarily injured or a user operating a device with one hand.

Option A incorrectly frames inclusive design around imperfection and “one size fits one.” Option C incorrectly substitutes learning from experts for learning from diverse users.

The central principle is that inclusive design deliberately examines exclusion and uses human diversity as a source of innovation rather than treating accessibility requirements as isolated exceptions.

Study Guide reference/topics: Inclusive design, exclusion, diversity, human-centered design, Human-Centered Design.

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