Explanation

When viewing individual records in Salesforce, sales representatives need immediate access to critical information. Salesforce provides layout and display features that present key fields prominently on record pages. These features ensure essential data is visible at the top or in persistent areas, enabling quick decision-making and efficient record management.

✅ Correct Option B: Highlights Panel
The Highlights Panel displays at the top of Lightning record pages, showing up to 10 key fields in an easy-to-scan format. This panel remains visible as users scroll, ensuring critical information stays accessible. It's ideal for sales reps who need immediate visibility of opportunity details like amount, stage, or close date.

✅ Correct Option C: Compact Layout
Compact Layouts control which fields display in the record header area and when hovering over record links. This shows up to 10 fields in a condensed format at the top of record pages. For opportunities, this might include owner, amount, and stage—perfect for rapid information scanning without opening the full record.

✅ Correct Option D: Tabs
Tabs on Lightning record pages organize information into sections like Details, Related, News, and custom tabs. They allow logical content segmentation while keeping key fields visible in the Details tab. Custom tabs can group related information, ensuring sales reps quickly navigate to specific data and reducing clutter.

❌ Incorrect Option A: Customer Links (Custom Links)
Custom Links are buttons or links that execute actions like opening URLs or running JavaScript. They don't display field values or make existing fields more visible on record pages. They're action-oriented rather than display-oriented features and don't address the requirement of seeing key field data when viewing opportunities.

❌ Incorrect Option E: List Views
List Views display multiple records in tabular format on object list pages, not when viewing individual records. They're used for filtering and organizing groups of records. When a sales rep opens a specific opportunity record, List Views are no longer visible and don't provide field visibility within single-record view.

Summary
The Highlights Panel, Compact Layout, and Tabs enable quick access to key fields when viewing individual opportunity records. These features present critical information prominently at the top or in organized sections. Custom Links and List Views serve different purposes and don't address field visibility on single record pages.

Reference
https://help.salesforce.com/s/articleView?id=sf.compact_layout_overview.htm
https://help.salesforce.com/s/articleView?id=sf.lightning_page_components.htm

Explanation

One-to-many relationships let one parent record connect to multiple child records (or vice versa for many-to-one), which is the standard for most Salesforce data models like Accounts to Contacts. UX Designers choose flexible links that maintain data independence while enabling related lists and lookups on Lightning record pages for intuitive navigation.

✅ Correct Option

✅ C. Lookup
Lookup relationships create loose one-to-many connections where child records can exist independently—delete the parent Account and related Contacts survive. Perfect for UX scenarios needing flexible associations like linking custom objects to Opportunities without cascade deletes or sharing inheritance, supporting up to 40 lookups per object.

❌ Incorrect Options

❌ A. Master-Detail
Master-Detail enforces tight coupling where detail records require a master parent and cascade delete on parent removal. This breaks UX flexibility for standard one-to-many needs, as child records can't exist standalone and inherit parent's sharing/security—too restrictive for most linking scenarios.

❌ B. Hierarchical
Hierarchical relationships only work on the User object for manager reports, creating self-referencing trees within Users only. Standard objects can't use this type, making it irrelevant for linking arbitrary objects like custom Project to Task in typical UX design data models.

Summary
Use Lookup for flexible one-to-many object linking without dependencies. Master-Detail too rigid; Hierarchical User-only. Lookups power most Lightning related lists and record page UX.

Reference
Salesforce Official: Salesforce Object Relationships

Explanation

Service Cloud follows standard Salesforce Account-Contact-Case relationship model where cases roll up to contacts first, then accounts. Reps start from Accounts for B2B customer context, drill to related Contacts, then access Case related list showing complete submission history. This Account > Contact > Cases path provides comprehensive customer service visibility.

✅ Correct Option

✅ D. All Accounts > Account Detail > Contact Detail > Case Related List
Service reps navigate Accounts list → specific Account record → Related Contacts list → individual Contact → Cases related list. This reveals all cases submitted by that customer across time, including closed ones. Perfect for service history review while maintaining account-level context for escalations or account teams. ​

❌ Incorrect Options

❌ A. All Contacts > Contact Detail > Account Detail > Case Related List
Starting from Contacts skips account context; cases appear on Contact detail anyway, but Account detail navigation afterward creates inefficient backtracking. Service Cloud prioritizes account hierarchy for B2B where multiple contacts share case history under one customer record.

❌ B. All Contacts > Contact Detail > Case Related List > Account Detail
Cases live on Contact related list directly, making extra Account navigation redundant. Reps see complete history immediately after Contact selection without account detour, but this path ignores standard Service Console account-centric workflows.

❌ C. All Cases > Case Detail > Contact Detail > Account Related List
Case-down approach shows one case at a time, not customer history. Reps need reverse navigation (Account→Contact→Cases) to see complete submission patterns chronologically, not individual case drilling which fragments service context.

Summary
Navigate Accounts → Contact → Cases for complete customer service history. Account-centric path matches Service Cloud B2B model perfectly. Contact-first skips essential account relationship context.

Reference
Salesforce Official: Set Up and Manage Cases in Service Cloud

Explanation

In UX and brand design, voice and tone are key elements of communication style. Voice is the consistent, overarching personality of the brand (e.g., friendly, professional, witty), while tone is the flexible adjustment of that voice to fit the context, emotion, or situation (e.g., empathetic during errors, celebratory on success). A UX designer must clearly differentiate them to create coherent, human-centered experiences across all touchpoints.

Correct Option: D ✅ Voice reflects the personality and tone is the way one speaks
Voice is the enduring character and identity of the brand—stable traits like “helpful,” “bold,” or “approachable” that stay the same everywhere. Tone adapts that personality to the moment: it’s how the brand speaks in a specific situation (e.g., calm and reassuring in an error message, excited in onboarding). This distinction ensures consistent yet context-appropriate communication.

Incorrect Option: A ❌ Voice reflects the expression and the tone is the way one designs
This mixes up concepts incorrectly. Voice isn’t just “expression,” and tone has nothing to do with design methods or visual styling. Both voice and tone are about written/spoken language—design process or visual elements fall under separate guidelines like style guides or mood boards.

Incorrect Option: B ❌ Voice reflects the character and tone is one's strength
While voice does reflect character (correct part), tone is not about “strength” or capability. Tone describes the emotional nuance or attitude applied in a specific interaction—strength implies power or quality, which doesn’t align with how tone functions in UX writing or brand voice guidelines.

Incorrect Option: C ❌ Voice reflects the frequency and tone is one's pitch
This borrows audio/music terminology (frequency = pitch range, tone = sound quality), but in UX and branding, voice and tone are linguistic/psychological concepts—not sound properties. Using audio metaphors confuses learners and misrepresents how brands communicate in text and interfaces.

Summary
A UX designer should define voice as the brand’s fixed personality (consistent across all touchpoints) and tone as the adaptable way that personality is expressed in context (e.g., formal vs. casual, empathetic vs. direct). Option D captures this classic distinction accurately. Clear separation helps create empathetic, on-brand experiences that feel human and appropriate in every situation.

Reference:
Voice and Tone – Salesforce Lightning Design System (SLDS)
Brand Voice and Tone Guidelines – Salesforce Help & Trailhead

Explanation

The foundational first step for a UX Designer on the Salesforce platform is to understand the official design language. Familiarity with SLDS component blueprints is essential for maintaining consistency with the core Salesforce UI and for maximizing the use of reusable, platform-standard components. This knowledge prevents rework and ensures the app is inherently accessible and easy to build.

Correct Option

✅ C. Become familiar with the Salesforce Lightning Design System (SLDS) component blueprints.
SLDS is the platform's standard design system, providing the visual and interaction guides for all components. Understanding these blueprints is critical as it dictates the look, feel, and expected behavior of the application, ensuring consistency and leveraging Salesforce's built-in usability and accessibility standards.

Incorrect Options

❌ A. Create branding sets for each audience using Experience Builder.
Branding sets involve customizing colors and themes, which is a visual refinement step. Before adding visual polish, the designer must establish the core structure and interaction patterns, which are governed by SLDS. Starting here skips the foundational design phase.

❌ B. Find and review relevant AppExchange packages.
Reviewing AppExchange is a technical discovery task for solutioning and integrating functionality, not the initial design step. The UX Designer must first focus on the user experience and interface consistency using the native SLDS components before evaluating third-party solutions.

❌ D. Design a series of custom web component for the app.
Designing custom components is a high-effort step reserved for scenarios where standard SLDS components are insufficient. The best practice is to leverage existing SLDS components first; therefore, this should not be the initial design step.

Summary
The essential starting point for a UX Designer is to study the Salesforce Lightning Design System (SLDS). This design system provides the component blueprints and guidelines necessary to create an application that looks and functions natively within the Salesforce platform. This familiarity ensures design consistency, high usability, and efficient development, which is foundational to a successful project.

Reference
Lightning Design System 2