Pass the Salesforce Designers Plat-UX-101 Questions and answers with Dumpstech

The correct answer is B. Empathy Map. The uploaded UX Designer study guide identifies the Empathy Map as the appropriate tool for synthesizing knowledge about users after personas have already been established.

An empathy map provides a structured way for a design team to consolidate what it knows about a user or persona. It commonly captures what users think, feel, say, and do, helping stakeholders develop a shared understanding of user motivations, concerns, behaviors, and needs. This makes it particularly useful after research findings have been gathered and personas are already available.

Option A, an Executive Summary, can communicate high-level findings to stakeholders, but it is primarily a reporting artifact. It does not organize user-centered observations in the same structured, empathy-oriented format.

Option C, Prioritize Backlog, belongs to planning and delivery. Backlog prioritization helps determine which work should be implemented first, but it does not synthesize user understanding.

The critical distinction is between understanding users and prioritizing solutions. At this stage, Cloud Kicks needs to create organizational alignment around what is known about its users. An Empathy Map supports that objective directly.

Study Guide reference/topics: Empathy Maps, personas, research synthesis, shared user understanding, Discovery.

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

The correct answer is A. Create a custom Theme in Themes and Branding, selecting logo, brand colors, and images, exactly as stated in the uploaded study guide.

The requirement is to make Lightning Experience conform to the company's existing design guidelines using declarative configuration. The study guide therefore directs the UX Designer to the standard Themes and Branding capability rather than to custom development.

A custom theme allows the organization to apply important brand assets such as the company logo, brand colors, and imagery so that the Salesforce environment presents a recognizable visual identity.

Option B is insufficient because selecting whichever built-in theme happens to be closest does not guarantee compliance with Cloud Kicks' actual design guidelines.

Option C refers to a different branding mechanism and includes font-type configuration, but it is not the declarative approach keyed by the study guide for the current Lightning Experience scenario.

The broader UX principle is to implement branding through supported Salesforce configuration whenever those tools satisfy the requirement. This preserves consistency and avoids unnecessary custom styling while still aligning the environment with company identity.

Study Guide reference/topics: Themes and Branding, Lightning Experience, brand colors, logos, Declarative Design.

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

The correct answer is A. Distributed Marketing and Journey Builder, as provided by the study guide. The requirement is not simply to create branded emails. Cloud Kicks needs to ensure that communications delivered by individual agents remain aligned with organization-wide branding and communication standards across customer touchpoints.

The study guide therefore pairs Distributed Marketing with Journey Builder. This combination supports centrally governed marketing content and coordinated customer communications while still enabling distributed teams or individual users to participate in customer engagement.

Option B includes Email Builder and Customer 360, but that pairing does not directly address the stated requirement for centrally controlled, consistently branded agent communications across a coordinated journey.

Option C combines Service Cloud and Letterhead. Letterheads can contribute to email presentation, but they do not provide the broader orchestration and distributed-brand-governance capability described.

The UX issue is consistency. Customers should experience a coherent brand voice and presentation regardless of which employee initiates a communication. Inconsistent messages can weaken trust and create a fragmented customer experience.

The study-guide solution therefore favors tools that support centralized communication design combined with distributed execution, preserving consistent branding while supporting operational flexibility.

Study Guide reference/topics: Distributed Marketing, Journey Builder, brand consistency, customer communications, Declarative Design.

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

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 correct answer is C. Expand the first section by default, exactly as keyed in the uploaded study guide.

An accordion is intended to reduce vertical complexity by grouping content into expandable and collapsible sections. On a mobile screen, however, presenting every section collapsed can introduce an additional interaction before users see any substantive content. Expanding the first section by default gives users an immediate entry point and demonstrates how the accordion behaves.

Option A is unsuitable because the browser Back control normally represents navigation history. Using it as the primary mechanism for collapsing accordion content would conflict with users' established expectations about browser behavior.

Option B would cause the interface to reposition content whenever a section is expanded. That can produce unexpected movement and interfere with the user's spatial understanding of the page.

Within the study guide's framing, option C provides the most predictable mobile experience: the user immediately sees useful content while retaining the ability to expand other sections when required.

This reflects a broader UX principle of minimizing unnecessary interaction while keeping content organized through progressive disclosure.

Study Guide reference/topics: Accordion usability, mobile UX, progressive disclosure, content organization, UX Fundamentals.

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

The study guide keys C. Lower-resolution monitors will have a better user experience as the feature or statement that is NOT relevant to recommending Console navigation.

A Salesforce Console application is appropriate for users who process many records and need to maintain context while moving between related pieces of work. That directly fits these service representatives, who handle multiple cases each hour through several channels.

Option A describes Split View, which is relevant because it can keep a list of records visible while the user works in the surrounding workspace. That reduces unnecessary navigation between the queue and the active record.

Option B is also relevant because console navigation supports related workspace organization, including multiple subtabs associated with a parent record. This is valuable when representatives need several related records or resources open simultaneously.

Option C, however, describes screen resolution rather than a console productivity capability. A denser multi-record workspace does not inherently mean that lower-resolution monitors provide a better experience.

The study-guide distinction is therefore between genuine console navigation benefits—such as maintaining record context—and an unsupported claim about display resolution.

Study Guide reference/topics: Console Navigation, Split View, subtabs, service-agent productivity, 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 uploaded study guide identifies C. Configure the Experience Builder Theme panel as the correct answer.

The scenario specifically asks how a branding and marketing team should customize an external customer support site's theme to align with the company's style guide. The study-guide answer favors the standard declarative capability available in Experience Builder.

Option A introduces an external or company stylesheet, while option B introduces custom CSS. Both approaches add custom styling logic that is unnecessary when the branding requirement can be handled through the platform's built-in theme configuration.

The Theme panel is therefore the appropriate first step because it allows designers to modify the supported presentation properties of the Experience Cloud site without immediately resorting to custom code.

This also aligns with a recurring pattern throughout the study guide: when a Salesforce declarative capability satisfies a UX requirement, use that capability before introducing custom development. This generally produces a more consistent and maintainable experience.

For the branding team, the practical implication is that the company's style-guide requirements should first be translated into the configuration options available through Experience Builder's theme controls.

Study Guide reference/topics: Experience Builder, themes, branding, style-guide implementation, Declarative Design.

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

The correct answer is A. Rich Text, images, and links, which is also the answer explicitly provided by the uploaded study guide. Salesforce Path is intended to guide users through stages of a business process. For each Path stage, an administrator can designate key fields and provide contextual Guidance for Success. Salesforce documentation describes this guidance as a place for information such as tips, links, questions, and company policy information that assists users in successfully completing that stage. This distinction is important. A Path already acts as a visual representation of progress through values such as Opportunity Stage. The Guidance for Success area supplements that progression with useful instructional material. Rich content and links can explain activities, remind representatives of procedures, provide supporting resources, or direct users toward relevant information. A Progress Indicator is therefore not the appropriate content element for Guidance for Success because Path itself visually represents progression. Merge fields are also not the expected answer in this configuration context. Consequently, rich instructional content provides the strongest fit for stage-specific coaching and supports Salesforce's declarative approach to improving process usability without developing a custom interface.

Study Guide reference/topics: Salesforce Path, Guidance for Success, key fields, contextual guidance, Declarative Design.

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

The correct answer is C. Key fields to complete before next Path stage, which the uploaded study guide confirms. Salesforce Path provides stage-oriented guidance for processes such as opportunities. Its major UX value comes from showing users where they are within the process and surfacing the information most relevant to each stage. Salesforce documentation states that a Path can expose up to five key fields per step, helping users focus on important information, together with contextual Guidance for Success. This makes key fields especially useful for onboarding. A new sales representative does not need to memorize every field or requirement associated with the opportunity lifecycle. Instead, the interface progressively surfaces the important information at the relevant stage, reducing cognitive load and reinforcing the intended business process.

Option A is not a standard defining capability of Path. Path does not primarily exist to supply integrated approval-automation buttons. Option B refers to a separate component and does not represent the core stage-specific onboarding functionality being tested.

One nuance is important: Path highlights key fields but does not inherently make those fields mandatory solely because they appear there; validation rules may be required when true enforcement is needed.

Study Guide reference/topics: Salesforce Path, key fields, onboarding, Guidance for Success, process guidance.

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