Salesforce Plat-UX-101 Salesforce Certified Platform User Experience Designer Exam Practice Test

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. 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 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 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 correct answer is C. The content should be presented in a way that can be convertible between different formats, as explicitly stated in the study guide.

“Perceivable” is one of the accessibility concepts tested throughout the UX Designer material. Within this question's framing, information must not be locked into only one sensory presentation. Users should be able to access the underlying content through forms that can support different ways of perceiving it.

Option A limits content exclusively to a visual format, which would create barriers for users who cannot rely on visual presentation.

Option B creates the opposite problem by limiting the content exclusively to audio.

Option C reflects the study guide's expectation that content should be capable of being represented or converted between formats. The underlying goal is to prevent important information from being available only through one mode.

This question therefore reinforces the accessibility principle that interface content should be designed so that different users and technologies can obtain equivalent information even when they do not consume it through the same presentation mechanism.

Study Guide reference/topics: Perceivable content, accessibility, alternative formats, WCAG concepts, UX Fundamentals.

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

The uploaded study guide identifies C. There are different writing directions (right to left vs. left to right) and layouts need to be adjusted accordingly as the correct internationalization consideration.

The site will be used across twelve countries, so the UX Designer must plan beyond simple text translation. Different languages can follow different writing directions, and that affects the structure and flow of the entire interface.

A right-to-left language may require layout adjustments to navigation, alignment, component sequencing, and the general reading flow so that the experience remains natural for the intended audience.

Option A is problematic because a country and a language are not equivalent concepts. A country can contain multiple languages, and the same language can be used across multiple countries. The study guide therefore does not select flags as the ideal language-switching mechanism.

Option B suggests that users in different countries inherently perceive color contrast differently. That is not the internationalization consideration keyed by the guide.

The broader HCD lesson is that internationalization must account for the structural characteristics of language and culture, not simply replace words. Layout direction is therefore a fundamental design requirement when supporting both left-to-right and right-to-left writing systems.

Study Guide reference/topics: Internationalization, right-to-left layouts, Experience Builder, global UX, Human-Centered Design.

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

The correct answer is A. Be specific about the issues testers encountered, as stated in the uploaded study guide.

Usability findings become actionable when stakeholders understand exactly what happened, where it happened, and how it affected the participant's ability to complete the task. Specific descriptions therefore provide a stronger basis for design and development decisions than vague observations such as “users found the page confusing.”

Option B recommends excluding issues merely because they were already known. Existing problems encountered again during testing can still be meaningful evidence about their impact on users, so selectively omitting them would weaken the representation of the session.

Option C proposes identifying participants by name. The study guide does not support that approach; participant identities are not necessary for communicating the usability problem itself.

The broader testing principle is to translate observations into precise findings that the product team can understand and act upon. A specific finding connects the observed problem to the relevant part of the experience rather than leaving stakeholders to interpret ambiguous research notes.

Accordingly, the study guide prioritizes clear, concrete reporting of encountered issues.

Study Guide reference/topics: Usability Testing, reporting findings, research observations, actionable UX findings, Testing.

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

The uploaded study guide identifies C. User Flow as the correct UX method.

The key phrase is “series of steps to achieve a meaningful goal.” A User Flow represents how a user progresses through actions, decisions, screens, or states while attempting to complete a task. It therefore makes the relationship between individual steps and the final objective visible.

Option A, a User Persona, represents the user rather than the sequence of actions the user performs. Personas capture characteristics, needs, goals, behaviors, or pain points, but they do not primarily visualize task progression.

Option B, a Wireframe, represents the structure of an individual page or screen. Wireframes are useful for determining information hierarchy and interface layout, but they do not inherently document the complete sequence a user follows from one interaction to another.

The study-guide distinction is consequently straightforward: persona = who the user is; wireframe = how a screen is structured; user flow = how the user moves through steps toward a goal.

User flows help designers identify unnecessary steps, decision points, and transitions before detailed interface design is finalized.

Study Guide reference/topics: User Flow, task sequence, user goals, UX artifacts, UX Fundamentals.

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

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

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

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

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

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

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

The guide therefore selects Understandable, Operable, Robust.

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

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

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 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.

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

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 UX Designer study guide identifies C. Determine the change in scope and impact of each enhancement request as the correct answer.

User acceptance testing has produced enhancement requests, but the next step should not be to implement them immediately. The study guide first requires the team to evaluate how each requested change affects the existing solution.

Assessing scope and impact allows the team to understand whether an enhancement is minor or substantial, what parts of the solution it could affect, and how it may change the originally planned work.

Option A moves directly into prioritization. Prioritization can be useful, but the guide's answer indicates that the requests first need to be understood in terms of their impact and scope before deciding how to implement them.

Option B suggests developing all requests in a sandbox. That assumes all requests should proceed to development, which is premature before their implications have been analyzed.

The testing principle represented here is controlled response to feedback. UAT findings may reveal valid improvements, but each change should be assessed systematically before implementation so that the team understands what the enhancement means for the overall solution.

Study Guide reference/topics: User Acceptance Testing, enhancement requests, scope analysis, impact analysis, Testing.

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

The correct answer is C. Invite team members to observe usability sessions, as keyed in the uploaded study guide.

The problem is not that usability findings are unavailable; the Development team does not sufficiently value or accept them. Allowing developers to observe users directly provides first-hand evidence of where participants struggle, hesitate, misunderstand the interface, or encounter barriers.

Option A adds external best-practice articles to each finding. Those resources may support a recommendation, but they remain indirect evidence. They do not allow developers to witness actual users interacting with the team's product.

Option B focuses on how much effort the research team has invested. Research effort does not establish that a finding is valid or important. Acceptance should be based on user evidence rather than on the amount of work already spent collecting it.

The study guide therefore favors direct exposure to the research process. When team members observe usability sessions themselves, findings become less abstract and are harder to dismiss as merely the UX Designer's interpretation.

This also strengthens multidisciplinary ownership: usability becomes something the whole product team can observe and understand rather than a report delivered by one specialist group.

Study Guide reference/topics: Usability testing, observation, stakeholder buy-in, research acceptance, Testing.

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

The study guide identifies A. Master-Detail as the correct relationship type.

The decisive requirement is that a Container Bid must be tightly dependent on its associated Container. The question provides a specific behavior: if the parent Container is deleted, the related Container Bids should also be deleted automatically. That dependency aligns with the relationship behavior the study guide associates with Master-Detail.

A many-to-one Lookup would create an association between records, but the scenario explicitly calls for a stronger dependency rather than a loose reference. The UX Designer therefore needs to consider the underlying data model, not merely how related records appear on the page.

A Hierarchical Lookup is also not appropriate for this general object-to-object relationship. The question is centered on two business objects—Container and Container Bids—and on enforcing dependent lifecycle behavior between them.

The study-guide answer illustrates that data architecture affects usability. If dependent child records remain after their parent is deleted, users can encounter orphaned or misleading information. A correctly modeled Master-Detail relationship keeps the related data aligned with the business relationship represented in the interface.

Study Guide reference/topics: Master-Detail relationships, dependent records, Salesforce data modeling, related objects, Declarative Design.

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

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 correct solution is C. Enablement Site to build and assign custom modules, exactly as specified in the uploaded study guide. An Enablement Site is appropriate because the requirement is broader than simply showing users contextual assistance. Cloud Kicks requires structured, custom product training that can be delivered as learning content to internal users and leadership. Salesforce's Enablement functionality supports publishing modules and assigning relevant learning content to users. Salesforce documentation specifically explains that administrators can assign modules published on an enablement site and that users can complete assigned content from within Salesforce. Option A addresses a narrower use case. In-App Guidance prompts are effective for contextual onboarding, feature announcements, and short instructional interventions within the user's workflow, but they are not a replacement for a structured custom learning curriculum.

Option B provides an environment where users can experiment, but a sandbox does not inherently provide organized learning modules, assignments, learning progression, or formal enablement content.

The UX requirement here is therefore solved by selecting the platform capability that supports repeatable, organized, assignable learning experiences, rather than merely contextual assistance or an experimentation environment.

Study Guide reference/topics: Enablement Sites, custom learning modules, onboarding, internal user education, Declarative Design.

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

The uploaded study guide identifies C. Usability Testing as the correct method.

The question asks whether the form is easy and intuitive to use. That is directly a usability question, so the most appropriate validation method is to observe representative call-center staff interacting with the form and determining whether they can complete the required tasks effectively.

Option A, Qualitative, describes a broad category of research rather than the specific testing method selected by the guide. Usability testing itself can generate qualitative observations, but the question asks what kind of testing should validate the interface.

Option B, Survey, collects self-reported responses from users. Surveys can capture satisfaction or preferences but do not directly demonstrate whether users can successfully understand and complete the form in practice.

Usability Testing is therefore the more targeted method because it evaluates the interface through actual task interaction. The designer can determine where users hesitate, misunderstand labels, enter information incorrectly, or encounter unnecessary friction.

The study-guide distinction is between asking users what they think and observing whether the interface actually works for them.

Study Guide reference/topics: Usability Testing, forms, task completion, ease of use, Testing.

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

The uploaded UX Designer study guide identifies A. Specifying breakpoint sizes as the responsive design best practice.

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

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

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

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

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

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

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

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

The 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 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 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 correct answer is C. `slds--size-1-of-2`, which the uploaded study guide explicitly identifies as the class that does not follow the expected SLDS convention. SLDS uses a structured naming system derived from Block-Element-Modifier (BEM) conventions. Salesforce documentation describes a block as the primary component, an element as a constituent part represented with a double underscore, and a modifier as a variation or state.

Current Salesforce guidance is particularly relevant here. Modern SLDS notation uses the single underscore for modifier syntax. For example, `slds-avatar_circle` correctly represents the circular avatar variant. `slds-box` is itself a valid SLDS utility/component class. Salesforce also confirms that older double-dash modifier syntax has been deprecated in favor of the single-underscore convention. Option C is malformed because the separator appears immediately after the `slds` namespace: `slds--size-1-of-2`. Even historical sizing syntax would have been structured around the size class, such as `slds-size--1-of-2`, rather than `slds--size-1-of-2`. Modern notation uses forms such as `slds-size_1-of-2`. Therefore, C clearly violates the expected SLDS class structure.

Study Guide reference/topics: SLDS, BEM naming, CSS classes, modifiers, Lightning Web Components.

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

The study guide identifies A. Visibility of system status as the correct answer. The visual indicators communicate important information about the current state and requirements of the interface before the user attempts submission. By clearly showing which fields are required, the system makes its expectations visible rather than forcing users to discover them only after making an error.

Option B, User Control and Freedom, concerns providing users with mechanisms to recover from or reverse unwanted actions, such as canceling, backing out, or undoing operations. That is not the main issue here.

Option C, Error diagnosis and recovery, relates to helping users understand and recover from errors once they occur. Required-field indicators can help prevent such errors, but in this study-guide question the emphasis is on making necessary status and requirements visibly apparent.

Consistent patterns are especially important. If required fields are indicated differently on different screens, users must repeatedly relearn the interface. A shared pattern creates predictable behavior and enables faster form completion.

Therefore, the visual indicator acts as continuous system communication: users can immediately perceive what the form expects from them before attempting to complete the process.

Study Guide reference/topics: Usability Heuristics, visibility of system status, required fields, form design, UX Fundamentals.

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

The correct answer is B. Visual, Content, and Interaction Design, exactly as identified in the uploaded study guide. The question makes an important distinction between configuring a Salesforce Theme and creating a complete brand experience. A theme establishes some foundational visual properties, but the study guide indicates that brand experience also depends on three broader UX dimensions: visual design, content design, and interaction design.

Visual design influences how users perceive the organization's identity through presentation choices and interface styling. Content design affects brand expression through the information users encounter, including wording, hierarchy, and communication style. Interaction design influences how the experience behaves as users navigate, select actions, complete tasks, and receive feedback.

Option A includes harmony and responsiveness, which are relevant design concerns but do not constitute the three categories identified in this study-guide scenario.

Option C includes shapes and typography, which are individual visual-design elements rather than the broader set of UX disciplines required to communicate brand consistently.

The central study-guide lesson is that branding is not produced by colors or theme configuration alone. Users experience a brand through what the interface looks like, what it communicates, and how it behaves.

Study Guide reference/topics: Brand Experience, Visual Design, Content Design, Interaction Design, UX Fundamentals.

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

The correct answer is C. Card Sorting, as stated in the uploaded study guide.

The question emphasizes two related needs: understanding employees' mental model and creating an information architecture that matches user expectations. Card sorting is directly suited to this because participants organize items into categories according to how they naturally perceive relationships between them.

The results reveal how users group concepts, which labels make sense to them, and how content or functions might be organized within navigation. That makes the method particularly useful before finalizing the structure of a new community.

Option A, Cognitive Walkthrough, evaluates whether users can successfully progress through an existing or proposed interaction based on their expected knowledge and goals. It does not primarily generate an information architecture.

Option B, Mind Mapping, can help organize ideas or concepts but is not the user-research technique selected by the guide for uncovering how users classify information.

The study-guide principle is that information architecture should reflect the way users mentally organize the domain rather than merely mirror an internal organizational structure. Card sorting supplies evidence for designing that structure.

Study Guide reference/topics: Card Sorting, information architecture, mental models, user expectations, Discovery.

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

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. 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. Objects to represent storage facilities and fields to store facility details, as stated in the uploaded study guide. The spreadsheet analogy maps directly to the Salesforce data model. In the spreadsheet, each row represents an individual storage facility, while each column represents an attribute of that facility.

In Salesforce, the collection of facilities should therefore be represented by an object. Each individual facility becomes a record of that object. Properties that describe the facility—such as location, capacity, facility type, or status—should be represented by fields on that object.

Option A reverses these concepts by treating facility details as objects and storage facilities as fields. This would not correctly model the entities represented by spreadsheet rows.

Option B creates separate objects for both facilities and their attributes even though the scenario describes the details simply as characteristics of each facility rather than separate related entities.

A useful conceptual mapping is:

Spreadsheet → Salesforce

Row → Record

Column → Field

Dataset/entity type → Object

Correct data modeling directly affects UX because well-structured objects and fields produce clearer forms, record pages, reports, filtering, and navigation. Therefore, storage facilities belong as object records, with their descriptive details represented as fields.

Study Guide reference/topics: Salesforce data model, objects, records, fields, spreadsheet migration, Declarative Design.

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

The correct answer is B. Accordion, according to the uploaded UX Designer study guide.

An Accordion component is designed specifically to divide content into sections that users can expand and collapse. This directly matches the requirement to organize a substantial amount of information while preventing all sections from occupying screen space simultaneously.

The UX value is progressive disclosure. Users can initially see the section headings and open only the information relevant to their current task. This reduces visual overload and makes content-heavy experiences easier to scan.

Option A, Lightning Toggle, represents a control for switching a state or setting between alternatives. It is not a structural component for organizing multiple groups of content.

Option C, Dynamic Actions Bar, relates to presenting contextual actions rather than organizing information into collapsible content regions.

The study-guide answer therefore maps the interaction requirement directly to the appropriate Lightning component. When information can be logically divided into discrete sections and users do not need to view every section simultaneously, an Accordion provides an efficient presentation model.

A UX Designer should still use meaningful section labels so users can predict the contents of each collapsed area without repeatedly opening sections to discover what they contain.

Study Guide reference/topics: Accordion, collapsible content, progressive disclosure, information organization, SLDS.

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

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 C. Lookup, as explicitly shown in the study guide. A Lookup relationship is Salesforce's flexible mechanism for linking records between objects where one record can be associated with another without imposing the stronger dependency characteristics of a Master-Detail relationship. This makes it appropriate for common many-to-one relationships, where many child-side records may reference one record on another object.

The key distinction is relationship strength. A Master-Detail relationship creates a tightly coupled dependency. The detail record depends strongly on the master, and the relationship can affect ownership, sharing, roll-up summaries, and deletion behavior. It should therefore be used only when those stronger semantics are actually required.

A Hierarchical relationship is a specialized relationship available for the User object and is intended to create user-to-user hierarchy relationships. It is not the general-purpose solution for linking arbitrary business objects.

For a UX Designer, data-model decisions matter because they affect how related information is displayed, edited, navigated, and maintained in the user experience. Choosing the correct relationship type allows the designer and administrator to support the intended business interaction without introducing unnecessary data dependencies.

Therefore, for the generic one-to-many or many-to-one relationship described, Lookup is the appropriate choice.

Study Guide reference/topics: Salesforce data model, Lookup relationships, object relationships, Declarative Design.

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

The uploaded study guide identifies B. Grid as the correct SLDS utility.

The requirement describes a responsive layout in which content must adapt as available screen width changes. Elements may occupy multiple columns on wider screens and then wrap into additional rows when horizontal space becomes constrained.

A Grid system is designed precisely for this type of flexible page structure. It allows designers and developers to organize content into responsive rows and columns rather than relying on fixed positioning.

Option A, Float, can affect how individual elements position themselves relative to surrounding content, but it does not provide the structured, flexible responsive-layout system required by the scenario.

Option C, Alignment, controls positioning or distribution of content but does not itself define the responsive column-and-row layout architecture described.

The underlying UX principle is that responsive design should adapt the interface to varying screen sizes without requiring a completely separate page for each device. A grid gives the layout a systematic structure for resizing, wrapping, and repositioning content while retaining hierarchy.

Therefore, when the design requirement explicitly describes columns that can expand and wrap into new rows, the SLDS Grid utility is the appropriate solution.

Study Guide reference/topics: SLDS Grid, responsive design, flexible layouts, columns and rows, Salesforce Lightning Design System.

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

The uploaded UX Designer study guide identifies B. Service-Blueprinting Workshop as the correct answer.

The scenario places Cloud Kicks after the research and synthesis stages. The team already understands the issues discovered through research and now needs a collaborative process for redesigning the service with stakeholders. A service-blueprinting workshop is therefore the appropriate next activity because it gives participants a structured way to examine how the service works across customer-facing interactions and the supporting processes behind those interactions.

The key distinction is that the team is no longer primarily trying to discover problems; it is using established findings to collaboratively shape an improved service.

Option A, Service Usability Testing, would be more appropriate when evaluating a proposed or existing service experience with users. Testing does not itself provide the collaborative service-redesign framework described in the question.

Option C, a Pitch Session, is primarily about presenting or advocating for an idea rather than jointly mapping and redesigning service delivery.

The guide therefore positions service blueprinting as the bridge between synthesized research and collaborative redesign.

Study Guide reference/topics: Service Blueprinting, collaborative design, service redesign, stakeholder participation, Human-Centered Design.

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

The 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 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 C. Human Centered Design, as explicitly stated in the uploaded study guide.

Human-Centered Design begins by understanding people—their needs, motivations, constraints, environments, and pain points—and then develops solutions around that understanding. The wording of the question describes exactly this sequence: first identify end-user needs, then create solutions intended to satisfy those needs.

The important point is that the solution does not begin with technology, business process, or implementation convenience. It begins with the people who will ultimately use or experience the product or service.

Option A, User Experience Design, is closely related and often operates within a human-centered approach, but the study guide is testing the broader problem-solving philosophy that starts with human needs and iteratively develops solutions around them.

Option B, Communication Design, is more specifically concerned with how information, messages, and visual communication are structured and presented. It does not describe the broader end-to-end approach stated in the question.

The study-guide framing therefore positions Human-Centered Design as an approach that connects user understanding, problem definition, ideation, and solution creation around real human needs.

Study Guide reference/topics: Human-Centered Design, user needs, problem solving, solution design, Human-Centered Design.

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

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 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.

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

The correct answer is B. Ability to toggle between multiple records. The uploaded UX Designer study guide explicitly identifies this requirement as a reason to recommend Console navigation. Console navigation is designed for users who work intensively with multiple records and related information during the same session. Rather than continually leaving one record page and opening another, users can maintain several records within the console workspace and switch between them efficiently. This makes the console particularly valuable for sales or service roles where users frequently compare, reference, or update multiple related records.

Option A is not the defining requirement in the study-guide scenario. Although console applications can support efficient multi-record workflows, the requirement specifically associated with the answer is the ability to toggle between multiple records.

Option C points in the opposite direction. Users whose work occurs primarily in the field generally have stronger mobile and simplified-navigation requirements rather than a desktop-oriented multi-record console workspace.

From a UX perspective, the navigation model should correspond to the user's task pattern. Standard navigation suits more linear interaction, whereas Console navigation is better suited to high-volume, multi-record work where reducing navigation overhead improves productivity.

Study Guide reference/topics: Console Navigation, Standard Navigation, multi-record workflows, productivity, 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 uploaded study guide identifies A. Group similar fields using sections as the correct page-layout practice.

A record page can contain many fields, and users need to understand the information quickly rather than scan an undifferentiated collection of inputs and values. Grouping related fields into meaningful sections creates structure and makes the page easier to navigate.

Option B recommends including every field that might potentially be useful. That approach increases visual clutter and places additional cognitive demands on users because they must repeatedly distinguish important information from peripheral information.

Option C concerns making field labels identical to API names. API names exist primarily for technical implementation purposes and do not define the organization or usability of the user-facing page layout.

The study-guide answer therefore focuses on information organization. Related content should be presented together so users can predict where information belongs and locate it more efficiently.

For example, fields concerning customer information, reservation details, scheduling, or status can be grouped according to their functional relationship rather than presented as one continuous list.

The result is a clearer visual hierarchy and a more efficient Salesforce record experience.

Study Guide reference/topics: Page layouts, field sections, information organization, visual hierarchy, Declarative Design.

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

The correct answer is A. App Builder property, as keyed in the uploaded Master Study Guide.

The key requirement is that administrators, rather than developers, should be able to change the component's functionality or styling depending on the page where the component is placed. An App Builder property provides the configuration surface identified by the guide for exposing component-level settings to administrators.

This enables a reusable custom Lightning Web Component to behave differently according to the configuration selected in Lightning App Builder. Instead of creating separate components for every page context, the component can expose configurable properties.

Option B, Styling hooks, addresses styling customization but does not satisfy the broader requirement to allow an administrator to change both functionality or styling through page-specific component configuration.

Option C, Audience page variations, concerns delivering page variations according to different audiences rather than configuring reusable properties of the component itself.

The design principle is configurable reuse: a well-designed custom component can expose meaningful settings so administrators can adapt it to multiple page contexts without modifying source code or duplicating the component.

Study Guide reference/topics: App Builder properties, Lightning Web Components, configurable components, administrator customization, Declarative Design.

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

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 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 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 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 B. Docked prompt using In-App Guidance, as specified in the uploaded study guide.

The requirement is to inform users that a new feature has become available and provide a short explanatory video in the context of their Salesforce experience. In-App Guidance is specifically intended for contextual onboarding, feature announcements, adoption support, and targeted instructional content.

A Docked Prompt is appropriate because it can remain visible while allowing the user to continue interacting with the application. It provides enough space for explanatory content without necessarily blocking the entire workflow.

Option A, using the Utility Bar, would place the video in a persistent productivity area, but that does not provide the same contextual announcement mechanism for a newly enabled feature.

Option C requires a custom component even though Salesforce provides an out-of-the-box onboarding capability suited to this requirement. Introducing custom development would add unnecessary implementation and maintenance effort.

The study-guide principle is to use contextual, declarative guidance when users need timely help or feature education. Rather than forcing users to search external documentation, guidance can be delivered directly within their working environment.

Study Guide reference/topics: In-App Guidance, Docked Prompts, onboarding, feature adoption, Declarative Design.

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

The uploaded study guide identifies C. Account Object as the correct answer.

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

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

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

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

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

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