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 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 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 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 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 uploaded study guide identifies B. Only the body, footer, and header helper components can be styled using styling hooks as the correct answer.

The item tests an implementation constraint that matters when a UX Designer is attempting to align a Lightning modal with organizational branding. The guide distinguishes between the primary modal framework and its associated helper components.

According to the answer key, the relevant styling-hook support applies to the body, footer, and header helper components, rather than to the primary Lightning Modal component as described in option A.

Option C is too broad because the study guide does identify supported styling-hook usage within the modal's helper-component structure.

The UX implication is that brand requirements must be evaluated against the styling capabilities Salesforce actually exposes. A designer should not assume that every visual property of every base component can be overridden freely. Design-system components deliberately constrain customization so that accessibility, structure, and platform consistency can be maintained.

Therefore, when preparing specifications for a custom modal experience, the designer must account for the specific styling surfaces supported by the Lightning modal architecture rather than designing treatments that cannot be implemented through the available hooks.

Study Guide reference/topics: Lightning Modal, styling hooks, LWC, branding constraints, SLDS.

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

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 correct artifact is a journey map, and the uploaded study guide explicitly identifies B as the answer. A journey map documents an experience from the user's perspective across its stages and touchpoints. Salesforce Trailhead explains that journey maps can capture actions, thoughts, feelings, touchpoints, contextual factors, and opportunities. Critically, the artifact highlights where friction or pain occurs and where improvements could produce the greatest impact. Salesforce's UX artifact guidance similarly states that journey maps help identify process optimizations, pain points, and potential solutions. That directly corresponds to the scenario. The UX Designer needs to understand the call center's existing experience before proposing a Salesforce solution. Observation supplies empirical information about how agents currently perform complaint logging; the journey map then organizes those findings around activities, problems, and opportunities. A business process diagram is useful for documenting process mechanics and decision paths but normally provides less emphasis on the user's emotional and experiential context. A prototype would be premature because it represents a proposed solution rather than documenting the current-state experience. The Discovery principle is therefore: understand and visualize the existing user journey before designing the future solution.

Study Guide reference/topics: Discovery research, journey mapping, current-state analysis, pain points, opportunities.

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

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 study guide identifies A. Perform common tasks without navigating away from the page as the correct use case for the Utility Bar.

The Utility Bar is intended to provide quick access to frequently needed productivity tools while users remain in the context of their current Salesforce work. That makes it especially valuable when sellers repeatedly perform auxiliary tasks and would otherwise need to navigate to another page or application area.

The UX benefit is reduced context switching. Keeping commonly used tools immediately available allows users to maintain focus on the record or workflow they are currently handling.

Option B refers to quick access to favorite records or items, but the study-guide scenario specifically associates the Utility Bar with performing common tasks without leaving the current page.

Option C is also inconsistent with the answer key. The Utility Bar is not presented here as a mobile-specific enhancement.

The broader UX principle is efficiency of interaction. High-frequency activities should be available in a persistent, convenient location when doing so reduces unnecessary navigation and interruption.

Therefore, when discovery shows sellers value productivity and immediate access to tools, the standard Utility Bar use case is to allow them to complete common supporting tasks while remaining on their current page.

Study Guide reference/topics: Utility Bar, productivity, task efficiency, Lightning applications, Declarative Design.

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