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

The correct answer is A. Provide clear explanations of AI predictions or recommendations. The study guide explicitly keys this response as the action associated with responsible and transparent AI.

The wording of the question places emphasis on transparency. A transparent AI experience should help the person interacting with the system understand what the AI is presenting rather than simply exposing an unexplained prediction or recommendation.

Option A directly addresses that requirement by communicating an explanation alongside the AI output. In UX terms, this gives the user more context for interpreting the system's recommendation and makes the interaction less opaque.

Option B emphasizes collecting a maximum amount of user data. Regardless of whether additional data might support personalization, that choice does not directly satisfy the transparency requirement being tested in the guide.

Option C describes an internal demonstration or education session. That could inform employees about AI, but it does not make the actual user-facing AI prediction or recommendation more understandable.

The guide therefore distinguishes between organizational activity around AI and transparency within the user experience itself. The appropriate design step is to make AI-generated outcomes understandable to the person receiving them.

Study Guide reference/topics: Responsible AI, transparency, explainability, AI recommendations, Human-Centered Design.

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

The uploaded study guide identifies C. Specify prompt scheduling as the available In-App Guidance customization.

The requirement is specifically about delivering an appropriate onboarding experience to new Salesforce users. Scheduling is relevant because onboarding guidance is most useful when it appears at an intentional point in the user's adoption journey rather than indiscriminately.

Within the answer choices, the guide distinguishes scheduling from presentation-level customization and permission concepts. Option B, selecting a prompt font, is not identified as the supported customization. Visual styling of individual prompt typography is therefore not the feature being tested.

Option A, setting prompt permissions, is likewise not the customization keyed by the guide in this scenario.

The important UX concept is timing. Guidance can be technically correct yet ineffective if users encounter it too early, too late, or repeatedly without regard to onboarding stage. The availability of prompt scheduling gives the designer or administrator a mechanism for controlling when that assistance is presented.

This is consistent with the role of In-App Guidance as contextual onboarding support. The study guide therefore identifies prompt scheduling as the configuration capability that can be used to shape the new-user experience.

Study Guide reference/topics: In-App Guidance, onboarding, prompt scheduling, user adoption, Declarative Design.

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

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. Distinguishable, matching the uploaded study guide. Within WCAG's Perceivable principle, the distinguishable guidance focuses on making visual and auditory content sufficiently separable so that users can perceive important information. For text, buttons, and other interface elements, adequate color contrast is one of the central implementation requirements.

Salesforce's accessibility guidance explains that ordinary text should maintain sufficient contrast against its background and notes additional WCAG 2.1 contrast requirements for visual information needed to identify user-interface components and states, including button and input boundaries. Consequently, when a UX Designer selects foreground text and button-background colors, contrast and distinguishability must be evaluated rather than relying only on aesthetic brand preferences.

Adaptable concerns presenting information in ways that can be transformed or interpreted through different structures or presentation modes without losing meaning. Navigable addresses the user's ability to locate content, move through interfaces, understand focus, and determine their position. Neither directly describes the color-contrast requirement posed by the scenario.

Therefore, the UX Designer must ensure text and button treatments remain visually distinguishable, particularly for users with low vision or reduced color perception.

Study Guide reference/topics: WCAG, accessibility, distinguishable content, color contrast, Experience Builder, UX Fundamentals.

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

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 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 uploaded study guide identifies C. There are different writing directions (right to left vs. left to right) and layouts need to be adjusted accordingly as the correct internationalization consideration.

The site will be used across twelve countries, so the UX Designer must plan beyond simple text translation. Different languages can follow different writing directions, and that affects the structure and flow of the entire interface.

A right-to-left language may require layout adjustments to navigation, alignment, component sequencing, and the general reading flow so that the experience remains natural for the intended audience.

Option A is problematic because a country and a language are not equivalent concepts. A country can contain multiple languages, and the same language can be used across multiple countries. The study guide therefore does not select flags as the ideal language-switching mechanism.

Option B suggests that users in different countries inherently perceive color contrast differently. That is not the internationalization consideration keyed by the guide.

The broader HCD lesson is that internationalization must account for the structural characteristics of language and culture, not simply replace words. Layout direction is therefore a fundamental design requirement when supporting both left-to-right and right-to-left writing systems.

Study Guide reference/topics: Internationalization, right-to-left layouts, Experience Builder, global UX, Human-Centered 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 uploaded study guide identifies B. Clarity, Efficiency, Consistency, Beauty as Salesforce's core design principles for making design decisions.

Within the guide's framing, Clarity means that users should be able to understand information, controls, and next actions without unnecessary ambiguity. Efficiency emphasizes helping users accomplish tasks with minimal unnecessary work. Consistency supports predictable interaction by applying recognizable patterns and behaviors across the interface. Beauty addresses the visual quality of the experience while working alongside—not replacing—the functional principles.

Option A contains positive characteristics, but it is not the set of Salesforce core design principles keyed by this study guide. Option C includes concepts that can be relevant in usability and interface design, but again it is not the four-part framework identified in the source.

The important examination point is to recognize the exact Salesforce terminology rather than choosing a collection of generally reasonable UX qualities. The study guide expects the designer to understand the framework as Clarity, Efficiency, Consistency, and Beauty, which collectively support usable, predictable, and visually coherent Salesforce experiences.

Study Guide reference/topics: Salesforce design principles, Clarity, Efficiency, Consistency, Beauty, UX Fundamentals.

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

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.

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