Salesforce Plat-UX-101 - Salesforce Certified Platform User Experience Designer

The distinguishing advantage of a moderated usability study is the researcher's ability to interact with participants and investigate observations in real time. Therefore, A is correct, which matches the uploaded study guide answer. During a moderated session, the researcher observes a participant completing defined tasks while remaining available to ask neutral follow-up questions. For example, if the participant hesitates, misunderstands a label, or abandons a workflow, the moderator can investigate the underlying reason without simply relying on analytics or a post-session questionnaire. This enables collection of richer qualitative evidence regarding the participant's reasoning and mental model. Options B and C describe typical advantages of unmoderated research. Because no researcher needs to attend each session, participants can usually complete studies asynchronously from different locations. That model generally scales more easily and can reduce both cost and researcher time. The tradeoff is depth versus scalability. Moderated testing provides deeper contextual information and allows probing, whereas unmoderated testing provides broader reach and scheduling flexibility. Because the scenario specifically asks what would justify choosing the moderated approach, the capability to ask follow-up questions when usability issues appear is the decisive criterion.

Study Guide reference/topics: Moderated testing, unmoderated testing, qualitative research, follow-up questioning, usability study 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 B. Field-Level Security, as explicitly identified in the study guide. The important constraint is that Cloud Kicks has one standard Order page layout shared by different types of users. The requirement is therefore not to create separate layouts, but to control which fields are visible to internal versus external users.

The study guide selects Field-Level Security because it governs whether particular users can see or interact with specific fields even when the same page layout is shared. This makes it suitable for restricting sensitive or irrelevant information without duplicating the overall record-page structure.

Option A, Audience Targeting, is associated with presenting Experience Cloud or component content to different audiences, but it is not the field-visibility mechanism selected in this study-guide scenario. Option C, Dynamic Forms, can conditionally control field and section presentation on supported record pages, but the answer key specifically identifies Field-Level Security for the shared-layout visibility requirement.

From a UX standpoint, limiting users to the fields that are relevant and permitted for their role reduces unnecessary information exposure and keeps the shared record experience focused while preserving the organization's security model.

Study Guide reference/topics: Field-Level Security, shared page layouts, user-specific visibility, Sales Cloud, 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 uploaded study guide identifies C. Account Object as the correct answer.

The scenario requires Salesforce to represent existing individual customers in a way that allows financial advisors to open a customer record and see associated business opportunities. The study guide therefore selects the Account object rather than Case or Lead.

A Case represents a support or service issue rather than the customer entity itself, so it would not provide the correct foundation for representing the person whose opportunities need to be viewed. A Lead represents a prospective individual or organization before that prospect is converted into the established Salesforce customer structure. The scenario, however, refers to customers whose business opportunities must already be associated with their records.

The fact that the bank currently serves individuals rather than corporate customers does not change the study guide's selected Salesforce object. The essential UX and data-model requirement is to represent the customer using the object intended to anchor the relationship and associated opportunities.

Correct object selection directly affects the quality of the user experience because advisors need a coherent customer record from which related sales activity can be viewed.

Study Guide reference/topics: Salesforce objects, customer representation, Account records, Sales Cloud, Declarative Design.

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

The correct answer is A. The company's style guide, according to the uploaded study guide.

A corporate style guide defines the standards that govern how the brand should be represented. Depending on the organization, this can include approved logos, colors, typography, imagery, tone, spacing conventions, and rules governing how brand assets should or should not be used.

When implementing the brand within Salesforce, the UX Designer should therefore use the company's style guide as the authoritative reference. This ensures the Salesforce experience remains consistent with the organization's other customer-facing and employee-facing channels.

Option B, a design system, may provide reusable components, patterns, tokens, and implementation standards. While highly valuable, the question specifically asks for the document serving as the brand source of truth, and the study guide identifies the style guide.

Option C, project design principles, typically describes higher-level principles that guide decisions within a specific initiative. They do not necessarily contain the detailed brand specifications required for consistent implementation.

The UX objective is to avoid isolated interpretation of the company's identity. Using one authoritative brand reference helps designers make consistent decisions across pages, components, communications, and channels.

Study Guide reference/topics: Brand consistency, style guides, Salesforce branding, UX Fundamentals.

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

The correct answer is C. Lead, Contact, and Opportunity, as keyed by the uploaded study guide.

These three standard objects correspond to different parts of the realty customer's sales lifecycle. A Lead can represent a prospective home buyer before that person becomes an established customer relationship. A Contact represents the individual once that relationship is maintained within Salesforce, while an Opportunity represents the potential sales transaction being pursued.

That combination fits the scenario because brokers need to track people who begin by shopping for homes, establish contact with the real estate company, and potentially progress toward a transaction.

Option A includes Address and Property, which are not the three standard objects identified by the study guide for this lifecycle.

Option B includes Account, Person Account, and Contact, but this combination does not represent the prospect-to-sales-opportunity progression the guide is testing.

The UX significance is that the underlying object model should reflect the business stages users actually work with. Brokers need to distinguish prospective buyers, known individuals, and active sales opportunities rather than treating all information as one undifferentiated customer record.

Study Guide reference/topics: Lead, Contact, Opportunity, Salesforce standard objects, customer lifecycle, Declarative Design.

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

The uploaded study guide gives B. Tangible as the correct answer. The question wording and capitalization are preserved from the source.

Within the accessibility-oriented terminology used elsewhere in the guide, Robust and Perceivable are recognized accessibility principles. “Tangible” is not presented as part of that principle set, so it is the item that does not belong.

Perceivable concerns ensuring that information and interface content can be presented in ways users can perceive. Earlier material in the same guide links perceivability to providing content in formats that can be transformed or accessed in different ways.

Robust also appears in the guide's WCAG-focused material, where it is listed alongside Understandable and Operable.

Option B, Tangible, therefore differs from the terminology used by the guide for digital-accessibility design requirements.

This item is written very briefly in the source, so its intended distinction is best understood by comparing the terminology against the accessibility principles established elsewhere in the same question bank rather than expanding it into a different framework.

For this supplied study guide, the keyed answer is unambiguously B.

Study Guide reference/topics: Accessibility principles, Robust, Perceivable, UX Fundamentals.

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

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 correct answer is A. Understandable, Operable, Robust, according to the uploaded Master Study Guide.

The question is testing recognition of formal accessibility terminology rather than a generic collection of good UX qualities. The study guide identifies Understandable, Operable, and Robust as WCAG principles contained in the correct choice.

Understandable means that users should be able to comprehend both the information presented and the operation of the interface. Operable concerns ensuring that users can interact with navigation and interface controls. Robust addresses the ability of content to remain compatible with different user agents and assistive technologies.

Option B contains terms that sound appropriate to inclusive design, but they are not the WCAG terminology keyed by the guide.

Option C—Simple, Consistent, and Clear—contains useful interface-design qualities but again does not represent the WCAG principle terminology requested.

For certification purposes, this question requires recognition of the accessibility framework's named principles rather than selecting concepts merely because they sound beneficial.

The guide therefore selects Understandable, Operable, Robust.

Study Guide reference/topics: WCAG, accessibility, Understandable, Operable, Robust, UX Fundamentals.

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