Salesforce Designers Changed Plat-UX-101 Questions

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 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 correct answer is B. Personas, as identified in the uploaded UX Designer study guide.

A persona is a research-based representation of an archetypical user. It consolidates recurring characteristics such as goals, behaviors, common tasks, motivations, and pain points into a form that designers and stakeholders can use throughout the design process.

This is especially relevant when Cloud Kicks is designing for both internal and external audiences. Different user groups can have substantially different objectives and interaction patterns, so documenting representative personas helps prevent the team from designing around assumptions or around a single generic “user.”

Option A, Storyboards, illustrate scenarios or sequences of activity. They are useful for showing how a person interacts with a solution over time, but they do not primarily document the archetypical characteristics of the user.

Option C, User Stories, capture requirements from a user's perspective, typically describing what a user wants to accomplish and why. They support backlog definition but are not a full representation of the user's characteristics and pain points.

The study-guide distinction is therefore straightforward: personas describe who the user is; user stories describe what the user needs; storyboards show an experience unfolding over time.

Study Guide reference/topics: Personas, archetypes, user goals, tasks, pain points, Discovery.

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

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.

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