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 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. Quantitative, as explicitly stated in the uploaded study guide.

The defining requirement is to determine whether a released feature was successful and to track usability over time. That calls for measurements that can be collected repeatedly and compared across periods, which is why the study guide selects a quantitative methodology.

Quantitative research produces numerical evidence that can be monitored longitudinally. Depending on the study design, this can include measures such as completion rates, error rates, engagement, usage frequency, time-related measures, or other defined UX indicators.

Option B, Qualitative research, is better suited to questions about why users behave in a particular way, what they think about an experience, or what problems they encounter. It can explain underlying causes but is less directly suited to tracking a numerical trend over time.

Option C, Inductive, describes a reasoning approach rather than the research methodology selected by the study guide for ongoing success measurement.

The important UX distinction is between understanding experiences deeply and measuring their performance systematically. When the objective is longitudinal tracking and evidence of success, the guide points to quantitative research.

Study Guide reference/topics: Quantitative research, usability metrics, longitudinal measurement, feature success, Testing.

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

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 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 correct answer is B. 44 pixels wide x 44 pixels tall, which is the minimum target size identified by the study guide for interactive mobile elements. Touch interfaces require larger interaction targets than pointer-based desktop interfaces because users interact with them using fingers rather than a precise mouse cursor. A sufficiently large target makes buttons, links, icons, and other controls easier to activate accurately while reducing accidental selection of neighboring elements. The 44 × 44 pixel minimum therefore supports both usability and accessibility. The requirement is particularly important for users with limited dexterity, motor impairments, tremors, or users interacting with a mobile device while moving. Small targets can create repeated selection errors even for users without disabilities. Option A, 24 × 24 pixels, can be visually appropriate for some icons, but an icon's visual dimensions do not necessarily represent an adequate interactive touch area. Option C, 64 × 64 pixels, would certainly provide a large target but exceeds the minimum being tested. A UX Designer should distinguish between the visual size of an icon and its effective clickable or tappable area. A small-looking icon can still be enclosed within a larger interactive target.

Study Guide reference/topics: Mobile UX, touch targets, accessibility, interactive controls, UX Fundamentals.

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

The correct answer is C. Conduct a workshop with stakeholders to align on the current state and build consensus, as explicitly keyed in the study guide.

The discovery interviews have revealed that the fundamental problem is not simply poor adoption; Cloud Kicks lacks a clear and consistent sales process. Implementing user guidance before the organization agrees on the process would therefore attempt to teach users a workflow that is not yet defined.

Option A is premature. In-App Guidance may support adoption after a process is established, but it cannot resolve disagreement about what that process should be.

Option B gathers additional individual preferences, but the problem described is organizational alignment rather than a shortage of opinions. More isolated responses could actually increase ambiguity if different representatives prefer different approaches.

The study guide therefore favors a collaborative workshop. Bringing stakeholders together allows the team to make the current process visible, identify inconsistencies, establish shared understanding, and build consensus before designing the future experience.

The Discovery principle is clear: align on the problem and current state before implementing the solution.

Study Guide reference/topics: Discovery, stakeholder workshops, current-state alignment, consensus building, adoption strategy.

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

The correct answer is B. Heuristic Evaluation, exactly as provided by the study guide. A heuristic evaluation is a structured expert-review technique in which an interface is examined against recognized usability principles or heuristics. It is therefore the most appropriate method when the explicit objective is to assess whether an existing portal conforms to standard usability principles. Evaluators systematically review the experience for issues such as poor feedback, inconsistent behavior, confusing terminology, weak error handling, excessive memory demands, or lack of user control. Findings can then be categorized and prioritized for remediation. Option A, “Intuitive Review,” is not the formal evaluation method referenced by the study guide. A UX professional may informally assess an experience, but that does not provide the same systematic framework as a heuristic evaluation. Option C, User Testing, involves representative users performing realistic tasks while researchers observe behavior. It is valuable for identifying real-world usability problems, but the question specifically asks about compliance with established principles, not observation of task performance. The distinction is important: heuristic evaluation is an expert inspection method, while usability testing is an empirical user-research method. For this Experience Cloud portal, a heuristic evaluation provides the appropriate structured mechanism for reviewing usability against recognized standards.

Study Guide reference/topics: Heuristic Evaluation, usability inspection, expert review, usability principles, 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 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.

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