Free Practice Questions for the Salesforce Designers Plat-UX-101 Exam (2026 Updated)

The correct answer is C. Desirable, Feasible, Viable, exactly as identified in the study guide. These three criteria represent a foundational human-centered design framework. Salesforce Trailhead explains that human-centered design historically seeks solutions that are desirable, feasible, and viable. A desirable solution addresses something people genuinely need; a feasible solution can realistically be created with available technology and capabilities; and a viable solution fits the organization's business model and objectives. Successful UX design therefore requires more than satisfying the user in isolation. A proposed Salesforce experience could be highly desirable to sales representatives but technologically impractical. Likewise, a technically feasible solution that users do not need provides little value. A solution can satisfy both users and technology constraints yet still fail if it cannot support organizational objectives or sustainable operations.

V2MOM is Salesforce's organizational alignment framework covering Vision, Values, Methods, Obstacles, and Measures; it is not the conceptual product-design balance described here. Agile is an iterative delivery methodology rather than the three-dimensional HCD evaluation model.

For the redesigned sales processes, Cloud Kicks should therefore seek the intersection where user needs, implementation capability, and business sustainability are simultaneously satisfied.

Study Guide reference/topics: Human-Centered Design, desirability, feasibility, viability, design thinking.

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

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 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 uploaded study guide identifies C. Provide links to external resources, such as training videos or a company dictionary as the correct Help Menu customization.

The scenario asks specifically about customizing the Salesforce Help Menu so sales users can efficiently find assistance for important functions and processes. Providing links to relevant training videos, internal definitions, or other curated resources allows support material to be available from a centralized help location within the users' working environment.

Option A proposes a site map, which organizes content structurally but is not the Help Menu customization selected by the guide.

Option B refers to a docked prompt. Docked prompts belong to In-App Guidance and can be appropriate for contextual announcements or onboarding, but the question specifically asks how to customize the Help Menu.

The distinction is between proactive contextual prompts and a centralized collection of help resources. For recurring reference material, the study guide points to Help Menu links that connect users directly to supporting resources.

This can improve productivity because users do not have to independently locate training material every time they need clarification.

Study Guide reference/topics: Salesforce Help Menu, In-App Guidance, training resources, user enablement, Declarative Design.

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

The uploaded study guide identifies A. Reducing friction for users in achieving their goals as the correct benefit of inclusive design.

Inclusive design considers a wider range of user needs, abilities, contexts, and potential barriers. When those barriers are addressed, the resulting experience becomes easier for more people to understand and operate. The study guide therefore expresses the benefit in terms of reduced friction.

Option B contradicts the inclusive-design objective because designing exclusively for one user type risks excluding users whose circumstances or abilities differ from the assumed norm.

Option C also misrepresents inclusive design. The objective is not to simplify the experience to a generic lowest common denominator. Rather, the designer should identify barriers and create solutions that allow a broader range of people to participate successfully.

This answer is consistent with the inclusive-design principles earlier in the guide: recognize exclusion, learn from diversity, and solve for one in ways that can extend to many. When exclusion is reduced, users encounter fewer obstacles while trying to complete their intended tasks.

The practical outcome is therefore not only accessibility in a narrow sense, but a smoother and more usable experience across a broader population.

Study Guide reference/topics: Inclusive Design, reducing friction, user goals, exclusion, Human-Centered 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.

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

The correct answer is C. The CSS styles defined in the parent list component are not shared with the child items. The study guide explicitly keys this Shadow DOM behavior.

The UX Designer must account for component-level style isolation when specifying how the custom parent and child LWCs should appear. In the scenario, the parent component represents the overall To-Do List, while separate child components represent individual To-Do items.

The answer key indicates that styling defined within the parent component cannot simply be assumed to apply inside each child component. Consequently, the designer and developer need to plan styling at the appropriate component level rather than expecting the parent's stylesheet to control every repeated child item automatically.

Option B states the opposite behavior by assuming that the parent's CSS is inherited by the child components.

Option A focuses on Light DOM, but the scenario specifically asks about the impact of the LWC's Shadow DOM structure, and the guide selects style separation as the relevant consideration.

The design implication is significant: component boundaries affect implementation. A visually consistent specification must account for how styles are scoped when a user interface is decomposed into multiple Lightning Web Components.

Study Guide reference/topics: LWC, Shadow DOM, CSS scope, parent-child components, SLDS.

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

The study guide identifies A. Troubleshooting customer issues and logging activities as the correct activity set for the Case Solver persona.

Persona-based UX design requires the designer to align the interface with the user's primary responsibilities rather than with every activity that may exist somewhere within the organization. The name “Case Solver” itself points toward users whose principal work centers on resolving customer cases.

Option A directly reflects that operational role. Troubleshooting addresses the core problem-resolution responsibility, while logging activities supports documentation of the work performed while handling the customer issue. Those tasks therefore belong at the center of the Case Solver experience.

Option B shifts toward coaching, administration, or knowledge-management responsibilities. Those activities may exist within a service organization, but they are not the primary activities the study guide associates with the Case Solver persona.

Option C combines case-status visibility with campaign metrics. Campaign analysis belongs to a different business context and therefore does not form a coherent task set for this Service Cloud persona.

The design implication is that pages, actions, information hierarchy, and workflows should prioritize the activities users perform most frequently. For the Case Solver, the guide centers that experience on customer troubleshooting and activity logging.

Study Guide reference/topics: Personas, Case Solver, Service Cloud, task analysis, Discovery.

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

The correct answer is B. Add a List View component to the home page configured to show a custom list view filtered to show assigned and open cases, as specified in the study guide.

The UX requirement is to make the relevant queued Cases immediately visible so that help desk users can begin resolving work quickly. The study guide selects a filtered List View component placed directly on the team's home page.

This approach reduces the amount of navigation required before users can identify actionable cases. By filtering the list to show the appropriate assigned and open records, the home page becomes a task-oriented starting point rather than merely a general landing page.

Option A refers to a Case Assignment component, while option C refers to a Case Inbox component. Neither is the approach identified by the answer key.

The important design consideration is that the team already has a predictable record-selection criterion: the Cases must be relevant to the help desk member and remain open. A configured list view can express those conditions declaratively.

The study guide therefore favors bringing the right Salesforce records directly into the user's work context through a standard filtered list-view experience.

Study Guide reference/topics: List View component, filtered Cases, home pages, help desk productivity, Declarative Design.

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

The study guide identifies B. Engage in a friendly and informal way as the correct interview practice. Customer interviews are most productive when participants feel comfortable describing their experiences, behaviors, frustrations, goals, and workarounds. A conversational and approachable interview style can reduce formality and encourage participants to provide more natural, detailed responses.

Option A is poor research practice because vague or general answers can still contain useful signals. A skilled interviewer should probe them with neutral follow-up questions such as asking for a recent example, clarification, or description of what actually happened. Discarding vague responses immediately can result in lost insights.

Option C is also inappropriate. Researchers should avoid prematurely interpreting or judging findings during the interview itself. Doing so can introduce bias and influence subsequent questions. Analysis and synthesis should normally occur after sufficient evidence has been gathered across participants.

The Discovery objective is to understand users rather than validate assumptions. A friendly, informal interaction helps establish rapport while still allowing the designer to follow a structured research plan.

Therefore, the appropriate interviewing behavior is to create an environment where customers can speak openly and naturally while the designer listens, probes, and records evidence without forcing premature conclusions.

Study Guide reference/topics: Customer interviews, discovery research, rapport, neutral interviewing, qualitative research, Discovery.

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

The correct answer is A. Heuristic Evaluation, as specified in the study guide. A heuristic evaluation is appropriate when an existing interface is known to have usability problems, but the specific problems have not yet been systematically identified. The UX Designer evaluates the interface against recognized usability principles or heuristics and documents violations, severity, and improvement opportunities. This gives the team a structured assessment of the current experience before committing to redesign solutions.

The key phrase in the scenario is that Cloud Kicks “is unsure about what should be done.” Creating a low-fidelity prototype at this stage would prematurely move into solution design without first diagnosing the existing interface. A design template likewise determines presentation structure but does not explain why the current experience is ineffective.

This aligns with the broader Salesforce UX research principle of understanding the problem before building the solution. Salesforce emphasizes that UX work should investigate the existing experience, user goals, pain points, and underlying usability problems instead of assuming what users require. A heuristic evaluation therefore creates an evidence-based baseline from which redesign decisions can be prioritized and subsequently validated through user research and usability testing.

Study Guide reference/topics: Heuristic Evaluation, usability principles, current-state assessment, UX Fundamentals, interface evaluation.

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

The correct answer is B. Prioritization Matrix, exactly as identified in the uploaded study guide. A prioritization matrix helps a UX or product team evaluate candidate work items using explicit criteria. In this scenario, the relevant dimensions are user value and development effort. Plotting or categorizing potential user stories against these dimensions helps the team identify high-value, comparatively low-effort work and distinguish it from lower-value or significantly more expensive initiatives.

This approach provides a rational mechanism for deciding which user stories should receive attention first rather than relying on stakeholder preference or intuition alone.

Option A, Card Sorting, is a research technique for understanding how users categorize information. It is useful for navigation and information architecture but does not evaluate development effort.

Option C, Customer Journey Mapping, visualizes a user's experience across stages and touchpoints, including actions, pain points, and opportunities. It can generate candidate improvements but does not itself provide the structured value-versus-effort prioritization requested here.

The Discovery process frequently produces more opportunities than a team can implement immediately. Prioritization translates those findings into an actionable backlog by connecting user needs with delivery constraints.

Thus, a Prioritization Matrix is the appropriate technique for informing user stories according to both impact and implementation effort.

Study Guide reference/topics: Prioritization Matrix, user value, development effort, user stories, Discovery.

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

The correct answer is A. Observing user behavior, as explicitly identified by the uploaded study guide.

Human-centered design begins with understanding the people for whom a product, service, or process is being designed. Observing actual user behavior allows designers to understand what users really do, including their workflows, difficulties, workarounds, and environmental constraints. This provides evidence that may not emerge if the team relies only on assumptions or internal business objectives.

Option B places company OKRs at the center of requirements definition. Business objectives are important constraints, but they do not substitute for understanding users when adopting a human-centered approach.

Option C places rapid prototyping before ideation. Prototyping is useful for making ideas tangible and testing them, but the team first needs to understand users and generate potential solutions.

The study-guide distinction is therefore between evidence about people and organization-centered or prematurely solution-centered activities. Observing users gives the organization direct insight into needs and behavior and helps ensure subsequent design decisions are grounded in real experiences rather than assumptions.

Study Guide reference/topics: Human-Centered Design, user observation, behavioral research, user needs.

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

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 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 A. Apply brand fonts and colors, as stated in the study guide. Experience Builder includes declarative branding capabilities specifically intended to implement company identity without custom front-end development. Salesforce documentation explains that prebuilt Experience Builder themes can be customized using colors, fonts, and images, while branding sets allow these attributes to be managed for different audiences or requirements. This exactly matches Cloud Kicks' requirement to implement its existing brand style guide while avoiding a custom solution. The UX Designer can configure supported theme and branding properties through Experience Builder rather than introducing custom CSS.

Option B may fundamentally change the site's structure, component availability, or overall design architecture. Choosing a different template solely to apply branding is unnecessary when the existing theme supports declarative branding controls. Option C violates the explicit requirement to avoid custom solutions. Global CSS introduces additional maintenance and can create problems when Salesforce changes underlying platform markup or component styling.

The preferred UX architecture is therefore to exhaust supported configuration capabilities before introducing code. Using brand fonts and colors maintains consistency with the company's style guide while preserving compatibility with Salesforce's theme framework and reducing technical debt.

Study Guide reference/topics: Salesforce Themes and Branding, Experience Builder, branding sets, themes, fonts, colors, Declarative Design.

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

The uploaded study guide identifies C. Work together on setting up UX indicators as the correct response.

The problem is fundamentally one of alignment: developers do not yet see the value produced by the proposed design changes. Establishing UX indicators collaboratively creates measurable criteria that both design and development teams can use to evaluate whether the changes improve the experience.

The emphasis on working together is important. Rather than asking developers to accept a design argument based purely on the designer's authority, both groups agree on evidence that can demonstrate improvement.

Option A relies on research notes from previous projects. Those findings may not directly correspond to the current problem, users, or implementation context.

Option B attempts to resolve resistance hierarchically by persuading a development lead and relying on that person to convince the rest of the team. That may secure compliance, but it does not create shared understanding of the UX objective.

The study-guide answer therefore favors a measurable and collaborative approach. UX indicators can turn subjective disagreement into a discussion around observable outcomes, helping multidisciplinary teams evaluate whether the design actually produces the intended improvement.

Study Guide reference/topics: UX indicators, design-development collaboration, measuring UX, stakeholder alignment, UX Fundamentals.

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

The uploaded study guide identifies C. Recognizing peers with badges as the correct answer.

The question is specifically about increasing customer engagement in an Experience Cloud portal that is already performing well. The study guide selects peer recognition through badges because it introduces a direct participation and recognition mechanism within the community experience.

Badges can acknowledge contributions or activity, creating a visible form of recognition between participants. In the context of the answer key, this is considered more directly related to engagement than changes focused mainly on presentation.

Option A, personalized branding, changes how the portal looks or feels for an audience, but branding alone does not provide the same participation-oriented mechanism.

Option B, customizing page layouts, can improve information organization, yet the portal is already described as performing well. Layout changes therefore do not target engagement as directly as recognition does.

The key distinction in the study guide is between experience presentation and community participation. If the objective is specifically to encourage engagement, a mechanism that acknowledges users' contributions provides a stronger engagement-oriented feature than simply changing visual design or layout configuration.

Study Guide reference/topics: Experience Cloud, customer engagement, peer recognition, badges, Declarative Design.

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

The correct answer is A. Design tokens prefixed with "brand", exactly as identified in the uploaded UX Designer study guide.

The question is testing how a design system propagates theme-level design decisions across multiple components. Rather than hard-coding individual color values into every button, icon, or component, SLDS uses named design values represented through design tokens.

The guide specifically identifies tokens prefixed with “brand” as the mechanism used to align components with a custom theme.

This approach improves both consistency and maintainability. If a theme changes, components referencing the appropriate brand token can inherit the updated design value instead of requiring developers to locate and replace numerous hard-coded values.

Option B, JavaScript libraries loaded from a static resource, is not the design-value mechanism described in the question.

Option C, CSS hexadecimal values, represents the opposite of a scalable design-system approach. Hard-coded values make global design changes harder and can cause components to become visually inconsistent over time.

The study-guide principle is that theme-driven interfaces should rely on reusable named design entities rather than duplicated literal values.

Study Guide reference/topics: Design Tokens, brand tokens, themes, component consistency, Salesforce Lightning Design System.

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

The correct answer is A. Trailhead modules. The study guide explicitly identifies Trailhead modules as the content that can be assigned to learners through Learning Paths in this onboarding scenario.

The question is testing the distinction between Salesforce learning content that can be incorporated directly into an employee learning assignment and other forms of Trailhead achievement or assessment. Within the guide's framing, Learning Paths is being used as an onboarding mechanism, so the appropriate assigned resource is a structured Trailhead module.

Modules are suited to an onboarding context because they represent defined learning content around a subject area. The requirement is not merely to give employees an environment in which to experiment or to require a larger credential-oriented achievement. Instead, Cloud Kicks wants to assign learning material as part of a managed learning experience.

Option B, hands-on challenges, describes a specific assessment/activity format rather than the assignment type selected by the guide. Option C, Superbadges, represents a broader accomplishment and is not the answer keyed for Learning Paths here.

Therefore, when the objective is to assign structured onboarding learning through Learning Paths, the study guide points to Trailhead modules.

Study Guide reference/topics: Learning Paths, employee onboarding, Trailhead modules, assigned learning, Declarative Design.

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

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.

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

A Screen Flow allows Salesforce administrators to guide users through a multi-step process using interactive screens. The flow can collect information, display contextual instructions, make decisions based on entered data, and progressively move the user through a complex workflow. That directly addresses the requirement to make a complicated internal process more engaging and easier to follow. Rather than exposing users to a large number of fields or asking them to understand the underlying process logic, a Screen Flow can progressively present only the information and actions needed at each step. Option A, Lightning Survey, is designed primarily for collecting feedback or responses. It does not serve as a general-purpose mechanism for guiding users through operational business processes. Option B, Process Builder, concerns automation logic rather than an interactive user experience. It does not provide the guided visual interaction described in the scenario. From a UX perspective, Screen Flow reduces cognitive load by turning a complicated process into a sequence of understandable interactions. It can also provide validation and contextual information as the user proceeds.

Study Guide reference/topics: Screen Flow, guided processes, progressive disclosure, process usability, Declarative Design.

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

The study guide identifies A. Formula Field, Static Resource, and Object Page Layout as the correct combination. The scenario requires the record detail page to show a custom visual indicator that changes according to the current membership level. The tools selected in the guide support that requirement declaratively.

A Static Resource can hold the image assets required for the membership indicators. A Formula Field can determine which visual representation should be shown according to the data stored on the record. The resulting field can then be positioned on the relevant Object Page Layout so that users see the membership indicator as part of the record experience.

Option B refers to an Image Field and Dynamic Forms, but that combination is not the platform approach selected by the study guide for deriving the displayed image from membership-level logic.

Option C introduces Lightning components and SLDS icons. That could imply a more customized implementation, while the guide favors the simpler declarative combination of formula, resource, and layout configuration.

The UX value is immediate recognition: a visual membership indicator can communicate status faster than requiring users to interpret raw field values.

Study Guide reference/topics: Formula Fields, Static Resources, page layouts, visual status indicators, Declarative Design.

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

The correct answer is A. Wireframe Prototype, as explicitly keyed in the uploaded study guide.

The question states that Cloud Kicks already has requirements and user scenarios and now wants to evaluate how users respond to the content and structure of a proposed feature. A wireframe prototype gives participants something concrete enough to review or interact with while keeping attention on organization and functionality rather than polished aesthetics.

Option B, a User Flow, communicates how a user may move through steps or screens. It is useful for documenting process logic, but it does not provide the same screen-level representation of content and structure that can be shown directly to users for evaluation.

Option C, Heuristic Review results, represent an expert-evaluation output. They do not constitute a proposed feature artifact that users can inspect and react to.

The study-guide answer therefore reflects the importance of selecting the right prototype fidelity for the research question. If the team wants feedback about information placement, structure, sequence, and overall concept before investing in detailed visual design, a wireframe prototype is appropriate.

It enables early validation while changes remain comparatively inexpensive.

Study Guide reference/topics: Wireframe Prototype, early testing, content structure, user feedback, Testing.

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

The correct answer is C. Tabs, as identified in the study guide. Tabs are used to divide related information into logical sections within the same interface. For a content-rich record page, they allow the UX team to consolidate substantial amounts of information without displaying every section simultaneously. This supports information hierarchy and reduces visual overload. Users can focus on the currently relevant category while retaining easy access to other related information through clearly labeled tab controls. Option A, Data Tables, is appropriate for presenting structured records in rows and columns. A table does not solve the broader requirement to organize several categories of record-page content. Option B, Modals, temporarily display focused information or actions above the current interface. They are useful for confirmation, short forms, or specific interactions, but they are not intended as the primary architecture for persistent record-page organization. The underlying UX principle is progressive disclosure: present the information required for the current task while keeping secondary content readily accessible. Tabs accomplish this without forcing users to leave the record page. Accordingly, for consolidating a content-heavy Salesforce record experience, the SLDS Tabs component offers the most appropriate structural pattern.

Study Guide reference/topics: SLDS Tabs, content organization, progressive disclosure, information hierarchy, component design.

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

The study guide identifies C. Compact Layouts as the correct answer.

The requirement is straightforward: when a sales representative views an Opportunity record, the most important fields should be immediately available without requiring unnecessary navigation or custom development.

Compact Layouts are the standard Salesforce feature selected by the guide for surfacing key record information concisely. The UX objective is to ensure that users can quickly orient themselves to the record and access the information required for common decisions.

Option A, a custom Lightning Web Component, would introduce custom development even though the scenario can be addressed using standard Salesforce configuration. This would add implementation complexity without a demonstrated need.

Option B, Tabs, can help organize larger groups of page content, but they do not specifically solve the requirement to expose a concise group of high-value record fields.

The UX principle is prioritization of information. Not every field on an Opportunity carries equal importance during routine record viewing. A compact presentation allows the designer or administrator to surface the fields that users need most frequently while keeping the broader record available when required.

Study Guide reference/topics: Compact Layouts, key fields, Opportunity records, information prioritization, Declarative Design.

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

The correct answer is B. Page layouts or permissions can display only the fields needed for each audience. This is the answer provided by the study guide. The scenario describes different audiences that consume the same knowledge system but require different levels and presentations of information. Salesforce declarative configuration allows the organization to tailor the experience using layouts and permissions instead of duplicating content unnecessarily. Option B supports audience-specific presentation by controlling which fields are exposed and which content users are permitted to access. This reduces cognitive load for customers while allowing support representatives to retain access to more detailed operational information. Option A creates unnecessary content duplication. Maintaining separate versions of the same article for every audience can create governance problems, inconsistent updates, and additional editorial overhead. Option C incorrectly assumes that external topic organization must duplicate the organization's internal category structure. A user-centered external experience should organize information in ways meaningful to customers rather than simply mirroring internal information architecture. The broader UX principle is progressive and audience-appropriate disclosure. Users should see information relevant to their tasks and permissions without being overwhelmed by fields intended for other roles. Therefore, page-layout and permission controls provide the most maintainable declarative solution.

Study Guide reference/topics: Knowledge, audience-specific content, permissions, page layouts, Declarative Design.

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

The correct answer is C. Blueprints and tokens, as stated in the uploaded UX Designer study guide.

The question asks specifically which SLDS resources help custom applications reproduce the Salesforce visual experience. The guide identifies two design-system resources: Blueprints and tokens.

Blueprints provide reusable structural patterns for Salesforce-style components. They establish how interface elements should be represented so custom implementations can align with Salesforce's established component design.

Tokens address reusable design attributes. Instead of hard-coding values independently throughout an application, the designer or developer can rely on named design-system values to support visual consistency.

Option A describes fully functional components. The guide does not characterize SLDS itself as simply a library of complete runtime components for this purpose; rather, it emphasizes the design resources used to construct Salesforce-consistent custom experiences.

Option B, voice-and-tone guidance, relates to content and communication style rather than the visual construction of custom application interfaces requested in the question.

The broader design-system principle is consistency through reuse. Blueprints standardize component structure, while tokens standardize foundational design values. Together, they help a custom application adopt a recognizable Salesforce look and feel without inventing an independent visual language.

Study Guide reference/topics: SLDS Blueprints, design tokens, custom applications, visual consistency, Salesforce Lightning Design System.

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

The correct answer is A. Typography, Color, Imagery. The study guide explicitly identifies these three elements as the visual-design tools that translate style and branding guidelines into the interface.

Typography determines how written content is visually expressed through type choices, hierarchy, scale, and treatment. Color communicates brand identity and can establish hierarchy, emphasis, and consistency across the experience. Imagery reinforces visual identity through photography, illustrations, icons, or other graphical assets.

Options B and C contain useful UX artifacts, but they perform different functions. Wireframes communicate layout and information hierarchy; personas represent user archetypes; blueprints define component structures; sketching supports early ideation; and storyboards communicate an experience or scenario. None of those groups directly represents the core visual-language elements used to implement a brand style.

The study-guide distinction is therefore between design process artifacts and visual design attributes. When the requirement is to translate an organization's branding or style guide into an interface, typography, color, and imagery provide the direct visual mechanisms through which that identity becomes perceptible to users.

Study Guide reference/topics: Visual Design, Branding, Typography, Color, Imagery, UX Fundamentals.

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

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 study guide identifies A. Account and Contact as the correct pair of standard Salesforce objects.

The scenario requires Salesforce to represent the people shopping for homes and the broader customer relationship that brokers need to manage. The study-guide answer uses Account and Contact as the foundational customer data model.

A Contact represents the individual person with whom the real estate company interacts. The Account provides the associated customer relationship record. Together, these two standard objects form the structure selected by the guide for tracking home buyers.

Option B introduces Case, which represents a service or support matter. Although a customer could eventually create a service issue, that is not the primary relationship described in the scenario.

Option C introduces Opportunity, which represents a potential sales transaction. An opportunity may become relevant within a real-estate sales process, but the question asks which objects should be used to represent and track the home buyers themselves.

The data-modeling principle being tested is that UX design in Salesforce often depends on correctly mapping real-world people and relationships into standard Salesforce objects before determining pages, components, or workflows.

Study Guide reference/topics: Account, Contact, Salesforce standard objects, customer data modeling, Declarative Design.

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

The study guide identifies C. Menu tabs can be Visualforce and Lightning pages as the correct administrative capability for Salesforce mobile navigation setup.

The question is testing what administrators can include when configuring the navigation experience available to mobile Salesforce users. According to the answer key, navigation entries can include supported Visualforce and Lightning pages, giving administrators a mechanism to expose relevant application destinations through the mobile navigation structure.

Option A states that menu tabs can be based on different user types. Although user access can influence what users ultimately see within Salesforce, that is not the navigation capability selected by the study guide in this question.

Option B claims visibility can be based on user location. The guide does not identify geographic location as the relevant administrative mechanism for setting up mobile navigation tabs.

The broader declarative-design principle is that mobile users should have direct navigation to the Salesforce resources relevant to their workflows. Administrators can configure supported page types as destinations without requiring users to reach them through indirect navigation paths.

This allows the Salesforce mobile experience to incorporate both Lightning-based and Visualforce-based functionality where appropriate.

Study Guide reference/topics: Salesforce mobile navigation, menu tabs, Visualforce pages, Lightning pages, Declarative Design.

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

The correct answer is A. To avoid societal bias. The uploaded study guide directly identifies societal bias as the concern when demographic data is selected for AI-model use. Demographic information can contain or reflect historical social inequalities. When characteristics such as age, gender, location, ethnicity, socioeconomic indicators, or related proxies are included in a model without careful justification, the model may learn patterns that reproduce existing disparities rather than simply represent neutral relationships. The UX and responsible-design implication is that teams must question both what data is being collected and why the model needs it. Data should not be introduced simply because it is available. Instead, each attribute should have a legitimate purpose that supports the intended user or business outcome without unnecessarily increasing the risk of discriminatory behavior. Option B refers to confirmation bias, which concerns a tendency to favor evidence that supports existing beliefs. While that can affect research and decision-making, it is not the specific data-governance risk described here. Option C, interaction bias, relates more to patterns arising from how people interact with a system rather than demographic information itself. The study-guide principle is therefore that responsible AI design requires deliberate demographic-data selection to reduce the propagation of societal bias into automated decisions.

Study Guide reference/topics: Responsible AI, demographic data, societal bias, responsible design, Human-Centered Design.

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

The study guide identifies B. Install SLDS Validator extension for VS Code as the correct answer.

The issue occurs during development in VS Code and specifically involves CSS classes and properties that conflict with SLDS. The answer therefore points to a development-time validation tool integrated with the environment where the developers are writing their code.

The SLDS Validator is the option in the study guide intended to simplify identifying SLDS-related problems while building Lightning Components. This makes it more appropriate than introducing an unrelated package or a designer-focused tool.

Option A, an SLDS creator from AppExchange, is not the tool selected by the guide for CSS validation within VS Code.

Option C, the Lightning Design System Plugin for Sketch, supports visual design and prototyping workflows rather than validating CSS implementation inside a development editor.

The distinction is between design tooling and implementation validation. Once developers are actively building a custom Lightning component and need to keep its styles aligned with SLDS conventions, the source specifies the VS Code SLDS Validator as the appropriate resource.

Study Guide reference/topics: SLDS Validator, VS Code, CSS, Lightning Components, Salesforce Lightning Design System.

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

The correct answer is B. Responsive, exactly as keyed by the uploaded UX Designer study guide.

The defining requirement is that both the site's size and content should adjust according to screen size, platform, and orientation. The study guide classifies this behavior as responsive design.

Responsive design allows a single interface to reorganize itself according to the space and display conditions available. Elements may resize, wrap, move, or change their relative arrangement as the viewport changes. This helps preserve usability across desktops, tablets, mobile devices, and different device orientations.

Option A, Progressive, does not describe the responsive layout approach requested in this scenario.

Option C, Adaptive, is related to supporting different environments, but the study guide specifically identifies responsive design when the page should fluidly react to changing dimensions and orientation.

This connects with other responsive-design concepts in the UX Designer material, such as using SLDS grids and breakpoints. The objective is not to design an isolated interface for every possible device but to establish layout behavior that responds appropriately when available space changes.

Study Guide reference/topics: Responsive Design, screen size, orientation, cross-device UX, UX Fundamentals.

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

The study guide identifies B. Tabs within the app's navigation bar as the customizable app-specific user-interface element.

A custom Lightning application is intended to provide a navigation environment tailored to the users and tasks associated with that app. The navigation bar is therefore an important configuration surface because it determines which tabs and destinations users can access directly while working within the application.

For a new team of service agents, selecting the appropriate navigation tabs can expose the objects and resources they need frequently while avoiding irrelevant destinations. This supports task efficiency and reduces unnecessary navigation.

Option A refers specifically to utility items for a mobile view. That is not the app-specific customization identified by the study guide in this scenario.

Option C refers to changing icons for custom objects. The question asks which part of the user interface specific to the app can be customized, and the answer key points instead to the navigation structure.

The UX principle is that an application should reflect the workflow of its intended audience. Configuring its navigation tabs allows the designer or administrator to prioritize the Salesforce destinations most relevant to those service agents.

Study Guide reference/topics: Lightning apps, navigation bar, tabs, service-agent UX, Declarative Design.

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

The uploaded Master Study Guide identifies C. Utility Classes as the correct SLDS resource for maintaining consistency in alignment, grids, spacing, and typography.

Utility classes provide reusable styling mechanisms that can be applied to interface elements without creating a separate custom CSS solution for every layout or presentation requirement. Within the study-guide framing, they are the appropriate SLDS resource when designers and developers need consistent control over common visual properties.

Option A, Component Blueprints, is used to communicate the structure and presentation pattern of complete Salesforce-style components. Blueprints are important when implementing component patterns, but this question focuses specifically on commonly reused styling concerns such as spacing, alignment, and typography.

Option B, BEM Naming Classes, relates to CSS naming methodology and structure. It is not the resource keyed by the guide for applying the visual utilities described.

The underlying design-system principle is reuse instead of reinvention. Applying standardized utility classes helps different pages and components use common spacing and alignment behavior rather than accumulating inconsistent custom CSS rules.

That consistency makes Salesforce interfaces more predictable visually and easier to maintain.

Study Guide reference/topics: SLDS Utility Classes, alignment, spacing, grids, typography, Salesforce Lightning Design System.

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

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 UX Designer study guide identifies C. Define the goals of the study as the correct answer.

Before recruiting participants or writing detailed study procedures, the UX Designer must establish what the usability study is intended to learn. In this scenario, the broad concern is whether the Experience Cloud site is intuitive, but that concern should be translated into clear research objectives.

Defining goals determines the rest of the study design. The goals influence which tasks participants should perform, which user groups should participate, what behaviors should be observed, and which outcomes will indicate success or reveal usability problems.

Option A, recruiting the right participants, is essential, but participant criteria should be derived from the goals and target users of the study.

Option B, writing a test plan, is also important, but a useful test plan depends on first understanding the study objectives. Without clearly defined goals, the plan can become a collection of activities without a coherent research purpose.

The guide therefore establishes the planning sequence correctly: define what needs to be learned first, then design the study around that objective.

Study Guide reference/topics: Usability Studies, research goals, study planning, Experience Cloud testing, Testing.

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

The uploaded study guide identifies B. Personalize the navigation bar as the correct solution.

The problem affects only a small subset of sales users. They frequently use a particular object, but that object is not currently included in the Lightning application's standard navigation. Creating an entirely separate application would therefore be disproportionate to the size of the audience.

Personalizing the navigation bar directly addresses the usability problem by allowing the relevant users to place the object within their own accessible navigation structure. This reduces unnecessary searching or indirect navigation while avoiding organization-wide configuration solely for a small group.

Option A, creating a Dashboard action, does not solve the fundamental problem that these users need routine navigation to an object.

Option C, placing the object's related list on the Home page, would attempt to surface data in a different context rather than providing straightforward navigation to the object itself.

The guide's solution reflects a broader UX principle of appropriate personalization. When a need is specific to a limited group and does not justify a separate application, individual navigation customization can improve efficiency without increasing administrative complexity for everyone else.

Study Guide reference/topics: Lightning navigation, personalization, object access, end-user efficiency, Declarative Design.

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

The correct answer is B. Acquiescence Bias, as keyed in the uploaded study guide.

The scenario concerns survey responses that could become positively skewed. The study guide identifies acquiescence bias as the response bias the UX Designer should watch for in that situation.

Acquiescence bias refers to the tendency of respondents to agree with statements or provide affirmative responses rather than expressing their actual position with complete independence. In a survey about purchasing behavior, this can produce an artificially positive result if the questions are framed in a way that invites agreement.

Option A, Objectivity Bias, is not the response bias selected by the study guide for this scenario.

Option C, Recency Bias, concerns disproportionate influence from more recent experiences or information rather than a tendency to provide agreeable or positive responses.

The practical research lesson is that survey questions must be designed so they do not encourage respondents toward a favorable answer. Neutral wording and balanced response structures help the designer obtain a more accurate picture of user behavior.

Accordingly, the source identifies Acquiescence Bias as the primary concern when avoiding positively skewed survey results.

Study Guide reference/topics: Acquiescence Bias, surveys, response bias, research validity, Testing.

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

The study guide selects B. Economic growth, greater market share, and less employee turnover as the business outcomes representing the value of diversity, inclusion, and equality in design.

The option is internally consistent because each listed outcome is positive from an organizational perspective: business growth, broader market reach, and improved employee retention.

Option A includes lower market share, which conflicts with the positive business-value framing of the question. Even though inclusive recruitment is itself presented positively, the overall combination is not the one identified by the study guide.

Option C includes more employee turnover, which similarly represents an undesirable organizational outcome and therefore does not align with the intended value proposition.

The question is not asking only about ethical design principles; it is asking how those principles can be framed in terms of business outcomes. The guide therefore connects diversity, inclusion, and equality with both organizational sustainability and market performance.

For the UX Designer, the implication is that inclusive design considerations can be communicated to stakeholders not only as design responsibilities but also through outcomes meaningful to the organization.

Study Guide reference/topics: Diversity, inclusion, equality, business outcomes, inclusive design, Human-Centered 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 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 correct answer is C. Allows the user to share a raw stream of thought, as explicitly identified in the uploaded study guide.

The think-aloud technique asks users to verbalize what they are thinking while they interact with an interface or attempt a task. The value described by the study guide is that this provides researchers with access to the participant's immediate thought process.

Rather than observing only whether the user succeeds or fails, the researcher can hear what the user expects, what they find confusing, what assumptions they are making, and why they choose a particular path.

Option A is incorrect because asking someone to continuously verbalize thoughts does not necessarily create a more natural situation. It is a deliberate research technique.

Option B is also incorrect. Think-aloud does not eliminate bias from user behavior; instead, it provides additional qualitative information about the user's reasoning.

The important distinction is between observable behavior and expressed reasoning. A user may hesitate or select the wrong option, but the think-aloud stream can reveal why that behavior occurred.

The study guide therefore treats think-aloud as a way to obtain richer qualitative evidence during user testing.

Study Guide reference/topics: Think-Aloud Protocol, user testing, qualitative research, user reasoning, Testing.

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

The correct answer is C. Prioritize user stories, as explicitly identified in the uploaded study guide.

The sequence in the question is important. Discovery has already been completed, research has been analyzed, and ideation has produced possible directions. The UX Designer must now convert that body of knowledge into actionable work for the following phase.

Prioritizing user stories helps determine which user needs and proposed capabilities should be addressed first. The team can evaluate stories according to factors such as user value, importance, implementation effort, dependencies, or business impact.

Option A, creating a business model canvas, serves a different strategic purpose and does not directly translate the completed discovery and ideation work into an implementation-oriented sequence.

Option B, returning to users for feedback, can be an important part of iterative design, particularly once concepts or prototypes are available. However, the study guide identifies prioritization as the preparation step immediately following the stated discovery, analysis, and ideation sequence.

The concept being tested is the transition from understanding and generating possibilities to organizing the work that will move forward. Prioritized user stories give the design and delivery teams a structured foundation for subsequent design and implementation activities.

Study Guide reference/topics: User Stories, prioritization, research synthesis, ideation, Discovery.

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