Free Salesforce Plat-UX-101 Practice Exam with Questions & Answers | Set: 5

The correct answer is B. Page layouts or permissions can display only the fields needed for each audience. This is the answer provided by the study guide. The scenario describes different audiences that consume the same knowledge system but require different levels and presentations of information. Salesforce declarative configuration allows the organization to tailor the experience using layouts and permissions instead of duplicating content unnecessarily. Option B supports audience-specific presentation by controlling which fields are exposed and which content users are permitted to access. This reduces cognitive load for customers while allowing support representatives to retain access to more detailed operational information. Option A creates unnecessary content duplication. Maintaining separate versions of the same article for every audience can create governance problems, inconsistent updates, and additional editorial overhead. Option C incorrectly assumes that external topic organization must duplicate the organization's internal category structure. A user-centered external experience should organize information in ways meaningful to customers rather than simply mirroring internal information architecture. The broader UX principle is progressive and audience-appropriate disclosure. Users should see information relevant to their tasks and permissions without being overwhelmed by fields intended for other roles. Therefore, page-layout and permission controls provide the most maintainable declarative solution.

Study Guide reference/topics: Knowledge, audience-specific content, permissions, page layouts, Declarative Design.

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

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 B. Personas, as identified in the uploaded UX Designer study guide.

A persona is a research-based representation of an archetypical user. It consolidates recurring characteristics such as goals, behaviors, common tasks, motivations, and pain points into a form that designers and stakeholders can use throughout the design process.

This is especially relevant when Cloud Kicks is designing for both internal and external audiences. Different user groups can have substantially different objectives and interaction patterns, so documenting representative personas helps prevent the team from designing around assumptions or around a single generic “user.”

Option A, Storyboards, illustrate scenarios or sequences of activity. They are useful for showing how a person interacts with a solution over time, but they do not primarily document the archetypical characteristics of the user.

Option C, User Stories, capture requirements from a user's perspective, typically describing what a user wants to accomplish and why. They support backlog definition but are not a full representation of the user's characteristics and pain points.

The study-guide distinction is therefore straightforward: personas describe who the user is; user stories describe what the user needs; storyboards show an experience unfolding over time.

Study Guide reference/topics: Personas, archetypes, user goals, tasks, pain points, Discovery.

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

The correct answer is C. Conduct a workshop with stakeholders to align on the current state and build consensus, as explicitly keyed in the study guide.

The discovery interviews have revealed that the fundamental problem is not simply poor adoption; Cloud Kicks lacks a clear and consistent sales process. Implementing user guidance before the organization agrees on the process would therefore attempt to teach users a workflow that is not yet defined.

Option A is premature. In-App Guidance may support adoption after a process is established, but it cannot resolve disagreement about what that process should be.

Option B gathers additional individual preferences, but the problem described is organizational alignment rather than a shortage of opinions. More isolated responses could actually increase ambiguity if different representatives prefer different approaches.

The study guide therefore favors a collaborative workshop. Bringing stakeholders together allows the team to make the current process visible, identify inconsistencies, establish shared understanding, and build consensus before designing the future experience.

The Discovery principle is clear: align on the problem and current state before implementing the solution.

Study Guide reference/topics: Discovery, stakeholder workshops, current-state alignment, consensus building, adoption strategy.

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

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 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 correct answer is C. Lookup, as explicitly shown in the study guide. A Lookup relationship is Salesforce's flexible mechanism for linking records between objects where one record can be associated with another without imposing the stronger dependency characteristics of a Master-Detail relationship. This makes it appropriate for common many-to-one relationships, where many child-side records may reference one record on another object.

The key distinction is relationship strength. A Master-Detail relationship creates a tightly coupled dependency. The detail record depends strongly on the master, and the relationship can affect ownership, sharing, roll-up summaries, and deletion behavior. It should therefore be used only when those stronger semantics are actually required.

A Hierarchical relationship is a specialized relationship available for the User object and is intended to create user-to-user hierarchy relationships. It is not the general-purpose solution for linking arbitrary business objects.

For a UX Designer, data-model decisions matter because they affect how related information is displayed, edited, navigated, and maintained in the user experience. Choosing the correct relationship type allows the designer and administrator to support the intended business interaction without introducing unnecessary data dependencies.

Therefore, for the generic one-to-many or many-to-one relationship described, Lookup is the appropriate choice.

Study Guide reference/topics: Salesforce data model, Lookup relationships, object relationships, Declarative Design.

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

The uploaded study guide identifies A. Group similar fields using sections as the correct page-layout practice.

A record page can contain many fields, and users need to understand the information quickly rather than scan an undifferentiated collection of inputs and values. Grouping related fields into meaningful sections creates structure and makes the page easier to navigate.

Option B recommends including every field that might potentially be useful. That approach increases visual clutter and places additional cognitive demands on users because they must repeatedly distinguish important information from peripheral information.

Option C concerns making field labels identical to API names. API names exist primarily for technical implementation purposes and do not define the organization or usability of the user-facing page layout.

The study-guide answer therefore focuses on information organization. Related content should be presented together so users can predict where information belongs and locate it more efficiently.

For example, fields concerning customer information, reservation details, scheduling, or status can be grouped according to their functional relationship rather than presented as one continuous list.

The result is a clearer visual hierarchy and a more efficient Salesforce record experience.

Study Guide reference/topics: Page layouts, field sections, information organization, visual hierarchy, Declarative Design.

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

The correct answer is A. Wireframe Prototype, as explicitly keyed in the uploaded study guide.

The question states that Cloud Kicks already has requirements and user scenarios and now wants to evaluate how users respond to the content and structure of a proposed feature. A wireframe prototype gives participants something concrete enough to review or interact with while keeping attention on organization and functionality rather than polished aesthetics.

Option B, a User Flow, communicates how a user may move through steps or screens. It is useful for documenting process logic, but it does not provide the same screen-level representation of content and structure that can be shown directly to users for evaluation.

Option C, Heuristic Review results, represent an expert-evaluation output. They do not constitute a proposed feature artifact that users can inspect and react to.

The study-guide answer therefore reflects the importance of selecting the right prototype fidelity for the research question. If the team wants feedback about information placement, structure, sequence, and overall concept before investing in detailed visual design, a wireframe prototype is appropriate.

It enables early validation while changes remain comparatively inexpensive.

Study Guide reference/topics: Wireframe Prototype, early testing, content structure, user feedback, Testing.

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

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.

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