Plat-UX-101 Exam Dumps - Salesforce Designers Questions and Answers

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 uploaded UX Designer study guide identifies B. Using REM-based spacing values when styling components as the approach that should be avoided.

The scenario is specifically concerned with ensuring that custom components can respond appropriately when users choose between Comfy and Compact display density. The study guide contrasts approaches that participate in Salesforce's design-system behavior with manually defined spacing.

Option A uses the `SpacingMedium` design token. Within the framing of the question, this allows spacing to be governed by the Salesforce design system rather than being fixed independently inside the component.

Option C likewise uses existing Lightning components such as cards or page headers. Those components already participate in the Salesforce UI framework and are therefore preferable when the goal is to preserve consistency with platform-level design behavior.

Option B instead applies REM-based spacing values directly in custom styling. According to the study guide answer, that approach should be avoided when the component needs to benefit from Salesforce density settings.

The central design-system principle tested here is to avoid hard-coding presentation decisions that should instead be inherited from reusable Salesforce design resources.

Study Guide reference/topics: Display Density, Compact and Comfy settings, design tokens, reusable Lightning components, SLDS.

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

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 UX Designer study guide identifies A. Specifying breakpoint sizes as the responsive design best practice.

Responsive design must account for changes in available screen width. Breakpoints provide defined thresholds at which the layout can adapt so that content remains usable and appropriately structured across different screen sizes.

The study guide therefore selects specifying breakpoint sizes as the practice that directly supports responsive behavior.

Option B, using interaction models, is not the responsive-layout mechanism described in this question. Interaction models can define how users work with an interface, but they do not themselves establish when the visual layout should change in response to screen dimensions.

Option C, creating a separate mobile-specific site, is not the best practice identified by the guide. The responsive approach is intended to allow one experience to adapt according to available space rather than requiring an entirely separate site merely because the device is smaller.

The important distinction is between adaptive layout behavior and maintaining separate experiences. Breakpoints allow the design to respond systematically as the viewport changes.

For the UX Designer, the practical objective is to define when content should resize, reorganize, wrap, or otherwise change presentation so that the experience remains usable across device dimensions.

Study Guide reference/topics: Responsive Design, breakpoints, screen sizes, adaptive layouts, UX Fundamentals.

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

The correct answer is A. Use the theme editor to adjust fonts, text case, colors, and site logo. The study guide explicitly selects this option for an Experience Builder implementation that must remain within out-of-the-box styling and component capabilities.

The important constraint is that the UX Designer cannot depend on custom styling or custom components. The Theme Editor is therefore the appropriate declarative mechanism because it allows the visual identity of the site to be adapted while remaining inside the standard Experience Builder framework.

Fonts, capitalization treatment, colors, and the site logo are all fundamental brand-expression elements. Adjusting these values allows the Experience Cloud site to reflect the organization's established visual identity without creating a separate custom presentation layer.

Option B affects footer content rather than the overall branded experience. Social-media links can be useful, but their presence does not establish the site's primary visual language.

Option C concerns page variations based on user behavior. That is a personalization technique rather than the direct brand-configuration solution requested.

The study-guide principle is therefore to use supported declarative theme controls first when the requirement is brand customization without custom development.

Study Guide reference/topics: Experience Builder, Theme Editor, branding, out-of-the-box configuration, Declarative Design.

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

The correct answer is B. Neutral button for "Cancel" and "Back"; Brand button for "Continue". This is the configuration identified by the uploaded UX Designer study guide. Button hierarchy communicates the relative importance of available actions. In this scenario, Continue advances the user through the primary three-step process, making it the principal action within the modal. It should therefore receive the visually prominent Brand treatment. Back and Cancel are secondary actions. Back reverses navigation within the flow, while Cancel exits or abandons the current interaction. Giving both actions the same visual prominence as Continue would weaken the action hierarchy and increase the possibility of users selecting the wrong control. Option A incorrectly emphasizes Cancel alongside Continue. Option C makes all three controls primary, effectively eliminating visual prioritization entirely. The SLDS design principle is that visual emphasis should correspond to action priority. A modal or flow should normally provide an obvious primary action while secondary navigation or dismissal controls use less prominent styling. This improves scanability, predictability, and task completion. Therefore, using a Brand button for Continue and Neutral buttons for Back and Cancel provides a clear and consistent interaction hierarchy.

Study Guide reference/topics: SLDS buttons, Brand button, Neutral button, action hierarchy, modal design.

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

The study guide identifies B. Use Salesforce Flow to help complete fields required for case closure as the correct answer.

The support agents must work with information distributed across several Salesforce objects while resolving and closing cases. The study-guide solution is to use Salesforce Flow to guide the agent through the required information and process steps.

This approach reduces the amount of information the agent has to locate manually. Instead of expecting agents to navigate independently between records and remember every required field, a Flow can structure the activity around the case-closing task described in the question.

Option A would increase navigation overhead by opening additional windows. That approach can fragment the user's context instead of simplifying it.

Option C focuses on components completed by the customer, while the scenario is specifically concerned with making the support agent's experience more efficient.

The UX principle is task-oriented simplification. When users must collect or update information across multiple parts of Salesforce to complete a defined business process, a guided declarative experience can reduce cognitive load and unnecessary navigation.

The guide therefore favors Salesforce Flow as the mechanism for streamlining the case-closure process.

Study Guide reference/topics: Salesforce Flow, support-agent productivity, case closure, guided processes, Declarative Design.

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

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 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 study guide keys A. Survey as the correct answer. The abbreviated wording is preserved exactly from the supplied source.

Within the choices provided, a survey is the method that directly gathers information from users or a broader participant population. That makes it consistent with the study guide's broader human-centered emphasis on understanding people rather than making design decisions entirely from internal assumptions.

Option B, heuristic analysis, is an expert-led evaluation method. It can identify usability problems by comparing an interface against established principles, but it does not directly collect perspectives from the diverse users whose needs an inclusive design should address.

Option C, stakeholder analysis, focuses on understanding relevant organizational or project stakeholders. While stakeholders can supply important business and operational context, their perspectives do not automatically represent the full range of end-user experiences.

The source itself provides only the question, options, and keyed answer; it does not provide a deeper rationale for why “Survey” was selected. Accordingly, the supported interpretation is that the survey is the option most directly associated with collecting user input across a broader group.

For this study guide, the answer remains A.

Study Guide reference/topics: Inclusive Design, surveys, user input, Human-Centered Design.

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