Free Practice Questions for Salesforce Plat-UX-101 Exam

The correct answer is C. Tabs, as identified in the study guide. Tabs are used to divide related information into logical sections within the same interface. For a content-rich record page, they allow the UX team to consolidate substantial amounts of information without displaying every section simultaneously. This supports information hierarchy and reduces visual overload. Users can focus on the currently relevant category while retaining easy access to other related information through clearly labeled tab controls. Option A, Data Tables, is appropriate for presenting structured records in rows and columns. A table does not solve the broader requirement to organize several categories of record-page content. Option B, Modals, temporarily display focused information or actions above the current interface. They are useful for confirmation, short forms, or specific interactions, but they are not intended as the primary architecture for persistent record-page organization. The underlying UX principle is progressive disclosure: present the information required for the current task while keeping secondary content readily accessible. Tabs accomplish this without forcing users to leave the record page. Accordingly, for consolidating a content-heavy Salesforce record experience, the SLDS Tabs component offers the most appropriate structural pattern.

Study Guide reference/topics: SLDS Tabs, content organization, progressive disclosure, information hierarchy, component design.

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

The study guide identifies C. Personalize the Navigation bar as the correct recommendation.

The question focuses specifically on an individual sales representative who wants more intuitive access to regularly used content. Personalized navigation directly addresses that need by allowing the user's frequently accessed destinations to be easier to reach within their normal Salesforce workflow.

Option A, customizing the Home page theme, changes visual presentation rather than improving direct access to regularly used content.

Option B, setting up Quick Links in the Utility bar, may appear plausible as a shortcut mechanism, but it is not the personalization approach selected by the source. The study guide consistently associates Navigation bar personalization with adapting frequently accessed Salesforce items to an individual user's working pattern.

The UX principle is to reduce unnecessary navigation for high-frequency tasks. When users repeatedly access the same objects or destinations, allowing those resources to be represented directly in their navigation reduces search effort and supports faster task completion.

Thus, according to the guide, the appropriate user-level personalization is to personalize the Navigation bar.

Study Guide reference/topics: Personalized Navigation, frequently used content, Salesforce user experience, Declarative Design.

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

The uploaded study guide identifies C. User Flow as the correct UX method.

The key phrase is “series of steps to achieve a meaningful goal.” A User Flow represents how a user progresses through actions, decisions, screens, or states while attempting to complete a task. It therefore makes the relationship between individual steps and the final objective visible.

Option A, a User Persona, represents the user rather than the sequence of actions the user performs. Personas capture characteristics, needs, goals, behaviors, or pain points, but they do not primarily visualize task progression.

Option B, a Wireframe, represents the structure of an individual page or screen. Wireframes are useful for determining information hierarchy and interface layout, but they do not inherently document the complete sequence a user follows from one interaction to another.

The study-guide distinction is consequently straightforward: persona = who the user is; wireframe = how a screen is structured; user flow = how the user moves through steps toward a goal.

User flows help designers identify unnecessary steps, decision points, and transitions before detailed interface design is finalized.

Study Guide reference/topics: User Flow, task sequence, user goals, UX artifacts, UX Fundamentals.

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

The uploaded study guide identifies A. A separate layout is needed for each record type as the correct consideration.

The scenario describes two Appointment record types—Virtual and In-Person—with different information requirements. Virtual appointments may additionally require fields that vary depending on the virtual meeting software being used. The study guide therefore emphasizes the need to account for those distinct record-type layouts when designing the record-creation experience.

Option B concerns inline editing in list views and does not address the central challenge of presenting different fields during record creation.

Option C concerns mobile availability of the field-section component, but that is not the design issue selected by the study guide for this question.

The important UX consideration is that users should see fields relevant to the kind of appointment they are creating. Presenting fields intended for Virtual appointments to users creating an In-Person appointment would add unnecessary complexity. Conversely, omitting software-specific fields from the Virtual workflow could prevent users from entering required information.

The study-guide answer therefore links record types and layout structure to a more contextually appropriate record-creation experience.

Study Guide reference/topics: Dynamic Forms, record types, layouts, conditional data requirements, Declarative Design.

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

The correct answer is B. Inclusive design is a methodology and accessible design is based on guidelines, as explicitly stated in the study guide. The distinction matters because inclusive and accessible design are closely related but are not interchangeable concepts. According to the framing used by the study guide, inclusive design is a methodology. It influences how designers approach a problem by considering exclusion, human diversity, varying contexts, and the range of people who may interact with a solution. Accessible design, in contrast, is grounded in defined accessibility requirements and guidelines. Within digital interfaces, this includes structured requirements such as those represented by accessibility standards and WCAG principles. Option A incorrectly categorizes both concepts as methodologies based on guidelines. Option C reverses the study guide's distinction by treating accessible design as the methodology. The two practices reinforce one another. Inclusive design broadens the design process by asking whose needs may be missed, while accessibility guidance provides concrete criteria against which interface implementation can be assessed. For a Salesforce UX Designer, the practical lesson is that meeting accessibility requirements is necessary, but inclusive design asks a broader question about whether the overall experience accommodates a diverse range of users and circumstances.

Study Guide reference/topics: Inclusive Design, Accessible Design, accessibility guidelines, Human-Centered 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.

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

The correct answer is C. Expert Review, as explicitly identified in the uploaded study guide.

The key wording is that Cloud Kicks wants to independently audit the current website for possible usability issues. An Expert Review fits that purpose because a UX professional examines the existing interface and identifies usability concerns based on established UX knowledge and evaluation criteria.

Option A, Task Analysis, focuses on understanding the activities, steps, and requirements involved in users completing a task. It can be highly valuable during research, but it is not primarily an independent audit of an existing interface.

Option B, User Shadowing, is an observational research method in which designers observe users working in their real context. That requires direct user involvement and therefore does not match the request for an independent audit.

The distinction is between expert inspection and user research. Both can identify important problems, but the scenario specifically asks for a designer-led evaluation of the current site.

An Expert Review can therefore provide Cloud Kicks with an initial inventory of usability issues that can later inform redesign priorities and, where appropriate, further user testing.

Study Guide reference/topics: Expert Review, usability audit, Experience Cloud, evaluation methods, Testing.

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

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 uploaded study guide identifies A. Marketing Cloud Personalization as the correct Salesforce capability for boosting B2C website engagement.

The requirement is specifically to improve business-to-consumer engagement on the website. Within the study guide's framing, Marketing Cloud Personalization is the capability aligned to tailoring digital experiences based on customer context and behavior.

Personalization can make an experience more relevant by changing which content, recommendations, or interactions are presented according to what is known about the user or their current context. Greater relevance can reduce the amount of irrelevant material a consumer must navigate and can increase meaningful engagement with the site.

Option B, Experience Cloud, is used for building external digital experiences and communities, but the question specifically asks which capability should boost B2C engagement through personalization.

Option C, Marketing Cloud Account Engagement, is not the answer selected for this B2C website scenario.

The UX distinction is between merely providing an external site and adapting that site's experience to the consumer. In the answer key, Personalization is the Salesforce capability that most directly addresses this objective.

Study Guide reference/topics: Marketing Cloud Personalization, B2C engagement, personalized experiences, website UX, Declarative Design.

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

The correct answer is B. Responsive, exactly as keyed by the uploaded UX Designer study guide.

The defining requirement is that both the site's size and content should adjust according to screen size, platform, and orientation. The study guide classifies this behavior as responsive design.

Responsive design allows a single interface to reorganize itself according to the space and display conditions available. Elements may resize, wrap, move, or change their relative arrangement as the viewport changes. This helps preserve usability across desktops, tablets, mobile devices, and different device orientations.

Option A, Progressive, does not describe the responsive layout approach requested in this scenario.

Option C, Adaptive, is related to supporting different environments, but the study guide specifically identifies responsive design when the page should fluidly react to changing dimensions and orientation.

This connects with other responsive-design concepts in the UX Designer material, such as using SLDS grids and breakpoints. The objective is not to design an isolated interface for every possible device but to establish layout behavior that responds appropriately when available space changes.

Study Guide reference/topics: Responsive Design, screen size, orientation, cross-device UX, UX Fundamentals.

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