Explanation

Financial Services Cloud for individual banking customers requires Person Accounts, which combine Account and Contact fields into single records perfect for B2C scenarios. Advisors access one record showing all customer details plus related Opportunities directly—no separate Contacts needed. This streamlined UX eliminates navigation between Account/Contact while maintaining standard Opportunity rollups.

✅ Correct Option

✅ A. Standard Person Account Object
Person Accounts store individual customer data (First Name, Last Name, Email, Phone) with direct Opportunity relationships visible in related lists. Advisors click one record to see complete financial picture plus all business opportunities—no corporate hierarchy needed. Native Sales Cloud feature enabled via Setup for B2C banking UX.

❌ Incorrect Options

❌ B. Standard Lead Object
Leads represent prospects before conversion, not established customers with active Opportunities. Financial advisors need ongoing relationship management with Opportunity tracking, which Leads can't support—requires conversion to Person Account first, creating unnecessary workflow steps.

❌ C. Standard Opportunity object
Opportunities track individual deals, not customer master records. Advisors need customer-centric navigation showing all opportunities per person, not scattered Opportunity records requiring reverse lookup to find client context.

❌ D. Standard Account object
Business Accounts expect Account Name + separate Contacts, forcing advisors to navigate Account → Contact → Opportunities for individual customers. No First/Last Name fields; creates fragmented UX for pure B2C banking without corporate structure.

Summary
Person Accounts = perfect B2C customer record with direct Opportunity visibility. One-click access to individual + all business opportunities. Business Accounts overcomplicated for individual banking customers.

Reference
Salesforce Official: Person Accounts

Explanation

When a researcher needs to understand long-term behavior, habits, or patterns that evolve over time (longitudinal data), they must choose a method that captures data as it happens in the user's natural environment. Observing a "2-month period" requires a method that doesn't rely on a single point in time or the user's memory of past events.

Correct Option: C. Diary Study ✅
A Diary Study is a longitudinal research method where participants keep a log (a "diary") of their activities, thoughts, and behaviors over a defined period—ranging from a few days to several months.

Context: It captures buying patterns in "real-time" as the customer actually makes purchases.
Duration: It is specifically designed for long-term observation (like CK's 2-month requirement).
Remote: Since participants record their own data, the designer can observe these patterns remotely without being physically present for every transaction.

Incorrect Option: A. Usability Study ❌
A Usability Study is typically a short, focused session (usually 30–60 minutes) where a user performs specific tasks on a prototype or live system. While it is great for finding friction in a checkout process, it cannot track "buying patterns" over two months.

Incorrect Option: B. Focus Group ❌
A Focus Group is a moderated discussion with a group of people. It captures what people say they do (attitudinal data), but it is highly susceptible to "recall bias," where people forget or misrepresent their actual habits. It also only captures a snapshot in time.

Incorrect Option: D. Survey ❌
A Survey can reach a large audience, but it is a "snapshot" method. While you could send multiple surveys, it lacks the depth and contextual "in-the-moment" detail that a diary study provides for behavioral patterns.

Summary
To capture authentic purchasing habits over a 2-month period, the UX Designer should implement a Diary Study. This will provide rich, contextual data on the "why" and "when" of customer buying patterns that a one-time interview or survey would miss.

Reference:
Official Salesforce Trailhead: UX Research Methods

Explanation

When a form has too many fields, the primary UX goal is to reduce cognitive load and make the form appear manageable. The best approach is to organize the fields logically so users can process information in chunks, rather than seeing a long, overwhelming list.

Correct Option: (D) Add section headers to visually separate fields into groups
This is correct. Grouping related fields under clear section headers (a technique called "chunking") is a fundamental UX principle for improving form readability. It breaks a long form into logical, scannable sections, reducing perceived complexity and helping users focus on one set of information at a time.

Incorrect Options

(A) Improve form security by adding a challenge-response test
This is incorrect. Adding a CAPTCHA or security test is unrelated to improving form readability. It adds a step that can increase friction and abandonment, making the usability problem worse, not better.

(B) Create a three-column grid to reduce the form length
This is incorrect. While multi-column layouts can shorten vertical length, they often harm readability and scannability on forms. They create a Z-pattern for the eyes, which can be confusing and lead to users missing fields. A single-column flow is the standard for accessible, readable forms.

(C) Replace field labels with placeholder text
This is incorrect. Placeholder text as a label replacement is a major anti-pattern. Placeholders disappear when users type, causing them to forget what information is required. This severely hurts usability and accessibility, especially for users with cognitive impairments or when reviewing entered data.

📝 Summary
To improve readability of a form with many fields, use section headers to group related fields. This "chunking" technique organizes information logically, reduces cognitive overload, and makes the form feel more manageable, guiding users through it step-by-step.

🔗 Reference
• Salesforce Lightning Design System: Form Layout – Best practices for organizing forms, including the use of field groups and sections for clarity.

Explanation

The best end-user experience is achieved by organizing the page layout logically and intuitively. Grouping related fields into sections reduces visual clutter, guides the user through a logical data entry flow, and makes information easier to find and understand at a glance.

✅ Correct Option: D
Grouping similar fields using sections is a core UX best practice for page layout design. It applies information architecture principles to organize content into digestible chunks. This significantly improves scannability, reduces cognitive load, and enhances efficiency for both data entry and record review tasks.

❌ Incorrect Option: A
Including all fields creates a cluttered and overwhelming layout, violating the principle of progressive disclosure. It forces users to sift through irrelevant information, which hinders their ability to complete key tasks quickly and accurately, damaging the overall user experience.

❌ Incorrect Option: B
While consistency is valuable, making labels and API names identical is a technical constraint, not a UX principle. User-friendly labels should use plain language, while API names follow developer conventions. Optimizing for technical parity often results in poor, non-intuitive labels for end-users.

❌ Incorrect Option: C
Marking all fields as required creates a frustrating and error-prone experience. It prevents users from saving records unless they have every piece of information immediately, which is often impractical. This prioritizes rigid data completeness over a flexible, user-centered workflow.

📝 Summary
This question tests your understanding of information architecture and reducing cognitive load. The best approach uses logical grouping to enhance scannability and task efficiency. Avoid solutions that clutter the interface or create unnecessary friction for the user.

🔖 Reference
Salesforce Help: "Page Layouts" and the Salesforce Lightning Design System (SLDS) guidelines on layout and design principles emphasize structured, user-centric information grouping.

Explanation

Experience Builder allows UX Designers to create branded sites using out-of-the-box styling and components without custom development. The platform provides built-in theming capabilities, pre-configured components, and styling options that maintain Salesforce's standard framework while enabling brand customization through declarative configuration.

✅ Correct Option A: Select a footer and configure which social media links to display
Experience Builder provides standard footer components that can be configured with social media links, contact information, and branding elements without custom code. This out-of-the-box component allows content customization and delivers brand consistency across all pages while maintaining supported functionality.

✅ Correct Option C: Select a theme and customize content including copy and imagery
Experience Builder offers pre-built themes that can be customized with brand-specific content, copy, and imagery. This declarative approach maintains brand identity through content updates without modifying code. Themes provide consistent styling while allowing flexibility in messaging and visual elements through standard configuration.

✅ Correct Option D: Use the theme editor to adjust fonts, text case, colors, and site logo
The theme editor is an out-of-the-box tool that customizes fonts, colors, text case, and logos without custom CSS. These settings apply globally across the site, ensuring brand consistency. This declarative approach maintains supportability while delivering comprehensive brand styling through Salesforce's standard theming framework.

❌ Incorrect Option B: Display custom variations of pages based on user behavior
Displaying page variations based on user behavior requires audience targeting and personalization rules beyond basic out-of-the-box styling. While Experience Builder supports this, it involves behavioral tracking and dynamic content rules rather than straightforward branding configuration. This is advanced functionality beyond basic branded experience delivery.

❌ Incorrect Option E: Create flexible layouts for pages with unique background images
Creating truly flexible layouts with unique backgrounds per page often requires custom CSS or component development beyond strict out-of-the-box constraints. Standard page templates with theme-controlled backgrounds are available, but extensive layout flexibility typically needs customization beyond purely declarative configuration methods.

Summary
Out-of-the-box Experience Builder features deliver branded experiences through configurable footers, theme selection with custom content, and the theme editor for fonts and colors. These declarative methods maintain supportability while achieving brand consistency. Behavioral personalization and highly flexible layouts require advanced configuration beyond basic styling.

Reference
Customize Sites with Experience Builder