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

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 correct answer is A. Understand the problem before moving to solutions, which is explicitly stated in the uploaded study guide.

Discovery exists to establish a reliable understanding of the problem space before the team commits to a particular solution. This includes learning about users, business context, current workflows, pain points, constraints, and desired outcomes.

Moving into solution definition too early creates a risk that the team will optimize the wrong problem or merely implement stakeholder assumptions.

Option B, writing user stories for potential solutions, is more appropriate after sufficient discovery evidence has been collected and the team has begun translating findings into implementation requirements.

Option C is especially problematic because discovery should challenge personal assumptions rather than use them as evidence of what users want. The designer should investigate users directly through appropriate research methods.

This is one of the most fundamental principles across the UX Designer study guide: separate the problem space from the solution space. Research should establish what needs to be solved before the team decides how it should be solved.

A disciplined Discovery phase therefore reduces rework, prevents premature commitment, and increases the likelihood that subsequent design decisions address genuine user and organizational needs.

Study Guide reference/topics: Discovery strategy, problem definition, research before solutions, user needs, Discovery.

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

The study guide identifies C. Configure a pre-filtered opportunity list view for each key attribute with the partner group as the correct answer. The requirement is for partners to quickly browse opportunities according to predetermined business criteria. The guide's selected solution is therefore a declarative one: create list views that are already filtered for the relevant opportunity attributes and expose those views to the appropriate partner audience.

This approach directly addresses both conditions stated in the scenario. One view can focus on opportunities closing within two weeks, while another can focus on opportunities valued above $100,000. Partners do not need to repeatedly construct their own filters or understand the underlying filtering logic.

Option A introduces a custom Lightning Web Component even though the requirement can be addressed using standard list-view functionality. That adds unnecessary implementation complexity.

Option B delegates filter creation to each partner, which conflicts with the requirement for a quick, standardized browsing experience.

The design principle reflected by the study guide is to prefer configured, reusable Salesforce functionality when it satisfies the user need. Pre-filtered list views reduce interaction effort and provide consistent segmentation across the partner experience.

Study Guide reference/topics: Experience Builder, opportunity list views, partner experience, filtering, Declarative Design.

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

The uploaded study guide identifies A. Rich Text, images, and links as the correct content for Path's Guidance for Success area.

The scenario requires stage-specific guidance telling sales representatives what they should be doing during the opportunity lifecycle. Rich instructional content is therefore the best fit because it can communicate guidance and provide supporting resources in the context of each stage.

The important distinction is between the Path itself and the guidance displayed within it. The Path already represents progression through a process. The Guidance for Success area supplements that progression with information that helps the user understand what actions, considerations, or resources are relevant.

Option B, Merge Fields, is not the content mechanism selected by the study guide for Guidance for Success.

Option C, Progress Indicator, would duplicate the stage-progress concept rather than provide the instructional content required by the scenario.

This supports a broader declarative UX principle: when Salesforce already provides a standard contextual-guidance capability, the designer should use it to place helpful information at the point where users need it. Here, rich text, imagery, and links can support representatives without requiring a separate training interface.

Study Guide reference/topics: Salesforce Path, Guidance for Success, contextual guidance, Opportunity lifecycle, Declarative 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 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 study guide identifies A. Traits similar to customer personas as the correct criterion when recruiting users for testing.

A usability study is valuable only when the participants meaningfully represent the users for whom the feature is being designed. Customer personas summarize relevant user characteristics, behaviors, goals, needs, and task patterns. Recruiting participants with similar traits therefore makes the test findings more relevant to the intended experience.

Option B, friends and family, is convenient but does not ensure that participants share the behaviors or needs represented by the actual target audience. Their feedback could reflect personal preference rather than the experience of representative customers.

Option C narrows recruitment to the most common demographic and ability. That approach could exclude important user groups and does not necessarily correspond to the personas the solution is meant to serve. A representative study should be guided by the relevant user characteristics established through UX research rather than by selecting only the statistical majority.

The study-guide principle is therefore representative participant recruitment. Testing should be performed with people whose characteristics align with the intended users so that observed usability issues and responses are meaningful to the design team.

Study Guide reference/topics: User testing, participant recruitment, personas, representative users, Testing.

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

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 C. Sketch Plugin. The study guide explicitly associates this tool with the requirement to rapidly create Salesforce-oriented designs and prototypes using SLDS resources such as components, tokens, and patterns.

The key phrase is “quickly mock up Salesforce User Interface experiences.” The designer needs a design-oriented resource rather than an implementation or validation mechanism. According to the guide, the Sketch Plugin provides the appropriate design workflow for working with reusable SLDS assets while creating prototypes.

Option A, the Lightning Design System Unmanaged Package, is not the design-tool solution keyed for this mockup requirement.

Option B, SLDS Validator, is oriented toward checking or validating implementation rather than providing the prebuilt design resources the UX Designer needs to compose a visual prototype.

The question reinforces the distinction between design tooling and development tooling. At the prototyping stage, the designer needs assets that can be quickly assembled into Salesforce-consistent screens without recreating base interface patterns from scratch.

Using a plugin built around SLDS resources also improves consistency between proposed designs and Salesforce visual conventions. Therefore, the study guide selects the Sketch Plugin as the tool best suited to rapid SLDS-based mockup creation.

Study Guide reference/topics: SLDS resources, Sketch Plugin, prototypes, prebuilt components, design patterns.

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

The study guide identifies C. Service Design as the correct answer.

The key clue is that the designer wants to move beyond focusing exclusively on an individual user and instead considers a broader network of interactions, connections, and value creation. According to the answer provided by the study guide, this broader design perspective is categorized as Service Design.

The scenario therefore shifts attention away from a single screen or isolated interaction and toward the wider experience created through multiple connected parts of a service.

Option A, User Experience Design, is centered on designing the quality of a person's interaction with a product or experience. Although it remains highly relevant, the question explicitly says the designer wants to go beyond the individual person.

Option B, Relationship Design, may sound plausible because the scenario mentions connected and social value, but it is not the answer selected by the supplied UX Designer study guide.

Within the guide's framing, Service Design provides the broader lens for thinking about how people, processes, interactions, and service touchpoints collectively create value. It extends the human-centered mindset from an isolated user interaction toward the overall service experience.

Study Guide reference/topics: Service Design, connected experiences, human-centered design, broader service systems, Human-Centered Design.

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