Free Salesforce-Platform-User-Experience-Designer Practice Test Questions (2026)

Explanation

To allow administrators to modify a Lightning Web Component's (LWC) appearance directly within the Lightning App Builder, developers must expose component properties. This declarative approach empowers non-technical users to adapt the component’s style or behavior based on the specific page context—such as Home, Record, or App pages—without writing code.

✅ Correct Option: C. App Builder styling property
An App Builder styling property (defined via @api properties in JavaScript and in the XML configuration file) is the standard way to expose "design attributes." This allows administrators to see a configuration panel in the App Builder where they can toggle checkboxes, select colors, or enter text to change the component's look and feel for each specific page instance.

❌ Incorrect Option: A. Styling hooks
Styling hooks are CSS custom properties used by developers to modify the internal styles of Salesforce base components or custom blueprints. While they are powerful for theme-level changes, they are controlled within the CSS files of the code bundle. Administrators cannot interact with styling hooks through a point-and-click interface like the Lightning App Builder to change individual component instances.

❌ Incorrect Option: B. CSS loaded as a static resource
Loading CSS as a static resource is a method for applying global or shared styles across components using the loadStyle service. This is a technical implementation detail handled by developers. Administrators do not have the ability to swap or configure these static resources on the fly while designing a page in the App Builder to change specific component aesthetics.

❌ Incorrect Option: D. SLDS utility classes
SLDS utility classes are predefined CSS classes (like slds-p-around_small) used within the component's markup to handle spacing, alignment, and visibility. These are "hard-coded" into the HTML template by the developer. Since they are part of the component’s source code, administrators cannot change or swap these classes through the App Builder UI.

📝 Summary
The App Builder styling property is the correct recommendation because it enables declarative customization. By exposing properties in the component's metadata, developers allow administrators to define unique "look and feel" settings for different page types. This ensures the component remains flexible and reusable across the entire Salesforce org.

Reference:
Salesforce Developers: Configure a Component for Lightning App Builder

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

Shadow DOM is a web standard that provides encapsulation for Lightning Web Components. It ensures that a component’s internal structure and styles are isolated from the rest of the application. This prevents "CSS leakage," where styles from one part of the page accidentally change the appearance of another. When working with a parent-child structure like a To-Do List, designers and developers must account for this boundary.

Correct Option: B. The CSS styles defined in the parent list component are not shared with the child items ✅
Because of Shadow DOM encapsulation, CSS selectors in a parent component's stylesheet cannot reach into the child component's internal elements. For example, if you define a class .to-do-text { color: blue; } in the parent List component, it will not apply to an element with that same class name inside the child Item component. Each component is responsible for its own styling rules.

Correct Option: C. Any custom shared between the list and child items should be imported from a shared CSS file ✅
To avoid duplicating code and ensure visual consistency, the best practice is to create a shared CSS module. This is a separate Lightning Web Component that contains only a CSS file (and a metadata file). Both the parent list and the child items can then import this shared file, allowing them to use the same branding and layout constants without violating Shadow DOM rules.

Incorrect Option: A. Any needed Salesforce Lightning Design System (SLDS) classes and styles must be imported ❌
This is incorrect because SLDS is globally available in the Salesforce Lightning Experience environment. You do not need to manually import SLDS classes (like slds-p-around_medium) into every individual LWC. The platform provides these styles automatically to all components rendered within the Salesforce UI.

Incorrect Option: D. The CSS style defined in the parent list component are inherited by the child items ❌
This is a common misconception. While some standard CSS properties (like color or font-family) may naturally inherit through the DOM tree, custom CSS rules and selectors do not "cascade" across the Shadow DOM boundary from parent to child. The boundary effectively blocks the standard CSS cascade to ensure the child component remains self-contained and predictable.

Summary
Shadow DOM creates a strict boundary that prevents parent styles from leaking into child components. To manage this effectively in an LWC To-Do List, designers must understand that each component needs its own styling definitions, and shared styles should be managed through a centralized, imported CSS module to maintain a single source of truth.

Reference:
Style Components with CSS Stylesheets

Explanation:

Correct Option:

✅ D. Conduct a workshop with stakeholders to align on the current state and build consensus:
Conducting a workshop fosters collaboration among stakeholders to define a consistent sales process. This aligns with human-centered design by involving users and stakeholders in co-creating solutions. It ensures clarity on the current state, builds consensus, and sets a foundation for designing effective Salesforce improvements, enhancing adoption.

Incorrect Options:

❌ A. Tell the customer they need to improve operations before any work can be done:
This approach dismisses the designer's role in facilitating solutions and risks alienating stakeholders. Human-centered design emphasizes collaboration, not ultimatums. Without addressing the lack of process through engagement, adoption issues persist, and no actionable progress is made.

❌ B. Log the findings and move forward with presenting possible solutions:
Moving directly to solutions without stakeholder alignment risks proposing irrelevant or unaccepted changes. Human-centered design requires consensus on the problem before solving it. Skipping this step may lead to solutions that do not address the core issue of an inconsistent process.

❌ C. Recommend Field Level Validation to ensure users are entering the correct data:
Field Level Validation addresses data entry accuracy but does not solve the root issue of an inconsistent sales process. It is a technical solution that fails to address process alignment, making it ineffective for improving overall Salesforce adoption in this context.

Summary:
The UX Designer identifies an inconsistent sales process as a barrier to Salesforce adoption at Cloud Kicks. Conducting a stakeholder workshop, as in option D, aligns with human-centered design by fostering collaboration and consensus. This step ensures a clear, unified process is defined, paving the way for effective solutions.

Reference:
Salesforce Trailhead: Human-Centered Design Basics

Explanation

The goal is to boost productivity by providing persistent, always-visible tools that allow agents to multi-task—viewing their case list and taking notes—without leaving the current case record they are working on. This requires features that are "docked" or fixed to the screen.

Correct Options

(A) Docked Utility Bar
This is correct. The Docked Utility Bar can be configured to contain components that remain visible at the bottom of the screen across all pages. A "Notes" component can be added here, providing a persistent place to create notes regardless of which tab or record is open, meeting the second requirement perfectly.

(B) List View - Split View
This is correct. Split View is a display mode for list views. When enabled, agents can select a case from their queue list on the left and see its details on the right in the same window. This allows them to view their queue while actively working on a specific case, fulfilling the first requirement.

Incorrect Options

(C) Dynamic Forms
This is incorrect. Dynamic Forms is a powerful tool for customizing the field layout on a record page. While it improves how case data is displayed, it does not address the core need for a persistent queue view or a dedicated note-taking area that works across different records.

(D) Activity Timeline
This is incorrect. The Activity Timeline is a component on the record page that shows a history of emails, tasks, and notes. It is not a persistent, global tool for creating new notes, nor does it provide a way to view the agent's case queue simultaneously.

📝 Summary
To help the help desk work efficiently, recommend Split View to see the case queue and case details side-by-side, and the Docked Utility Bar to keep a Notes component always accessible. Together, these features enable multitasking without navigating away from the active case.

🔗 Reference
• Salesforce Help: Use the Utility Bar – Configuring the docked Utility Bar.
• Salesforce Help: View List Records in Split View – Using Split View with list views.

Explanation:

✅ Correct Option: B
A field-level error message provides immediate, contextual feedback when a validation rule fails. It is the simplest and most user-friendly method as it clearly identifies the erroneous field and explains the exact format requirement right where the error occurs, preventing save attempts and guiding correction efficiently.

❌ Incorrect Option: A
In-App Guidance is a proactive tool for prompting or training users on how to use a feature. It is not designed for reactive validation of specific data formats and cannot prevent a record from being saved, making it an ineffective solution for this requirement.

❌ Incorrect Option: C
Marking the field as required only ensures it is not blank. It does not validate the format or number of digits of the phone number, allowing incorrectly formatted data to be saved, which fails to meet the specific business rule.

Summary:
The goal is to enforce a specific data format and provide a simple, error-preventing user experience. A validation rule with a field-level error message is the standard, targeted solution for validating input format and providing instant feedback upon failure.

Reference:
Salesforce Help: Define Validation Rules

Explanation:

✅ Correct Option: A
Experience Cloud is the platform for building branded digital experiences like customer and partner portals. It provides the tools to create the external site with the required features: case management, Knowledge integration, and embedding live chat, all within a single, customizable experience.

❌ Incorrect Option: B
Sales Cloud is a CRM application focused on the internal sales process (e.g., leads, opportunities, accounts). It is not designed for building external-facing customer support sites, though it can share data with an Experience Cloud site.

❌ Incorrect Option: C
Marketing Cloud is a digital marketing platform for email, social media, advertising, and journey automation. It is not designed for building interactive support sites with case management and knowledge base functionalities.

❌ Incorrect Option: D
Service Cloud is the application that powers the backend support operations (e.g., case routing, omni-channel routing, Knowledge Base). While it provides the data and logic, the external-facing site itself must be built and delivered to customers via Experience Cloud.

Summary:
The requirement is to build an external website with specific self-service and support features. Experience Cloud is the delivery platform for such sites, leveraging data and functionality from Service Cloud (which provides the Knowledge and Case objects) to create the user experience.

Explanation

SLDS styling hooks are CSS custom properties (also known as CSS variables) defined by the design system. They provide a standardized, maintainable way to apply and customize design tokens—like colors, spacing, and fonts—across both base Lightning components and custom-built LWCs for brand consistency.

Correct Option: (D) They use custom CSS properties to easily style base and custom components.
This is correct. Styling hooks are custom CSS properties (e.g., --sds-c-button-brand-color-background). Developers reference these variables in their component CSS to theme components, ensuring visual alignment with SLDS and allowing for easier, scalable brand customization across the entire application.

Incorrect Options

(A) They use standard CSS properties to directly style HTML elements.
This is incorrect. While standard CSS properties (like color or margin) are used for styling, styling hooks are specifically custom properties, not standard ones. They do not style HTML elements directly but provide reusable design token values.

(B) They use standard CSS properties to easily style base and custom components.
This is incorrect. The key differentiator of styling hooks is that they are custom properties, not standard CSS. Using standard properties alone does not leverage the centralized design tokens and theming capabilities provided by SLDS.

(C) They use custom CSS properties to directly style HTML elements.
This is incorrect. Although styling hooks are custom CSS properties, their primary purpose is not to style raw HTML elements directly. They are designed to theme and style components within the Salesforce Lightning UI framework, ensuring consistency.

📝 Summary
SLDS styling hooks are CSS custom properties that serve as design tokens. They enable developers to consistently apply branded styles—such as colors and spacing—to both standard and custom Lightning components, ensuring a unified and maintainable user interface.

🔗 Reference
• Salesforce Lightning Design System: Styling Hooks Overview – Official documentation on using CSS custom properties for theming in Lightning.

Explanation:

Correct Option: B. Share list views to Public Groups and only add relevant users.
Sharing list views to Public Groups and adding only relevant users is an effective way to improve the user experience. By sharing list views with specific, smaller groups instead of making them visible to all users, the overall number of list views a single user sees is reduced. This targeted sharing approach helps users quickly find the list views pertinent to their roles and tasks, thus decluttering their interface and enhancing productivity.

Correct Option: C. Remove irrelevant public list views.
Removing irrelevant public list views is a direct and impactful solution. Public list views that are no longer in use, are duplicates, or are not relevant to the majority of users contribute to the clutter. Deleting these unnecessary views reduces the total number of options available to users, making it easier for them to locate the list views they actually need. This action requires administrative permissions and a good understanding of which views are no longer serving a purpose.

Incorrect Option: A. Request users to create and share their list views.
Requesting users to create and share their list views can potentially exacerbate the problem. If users are encouraged to create more list views, it could lead to an even greater proliferation of views, further increasing the clutter. This approach doesn't address the root cause of too many available list views and could make the situation worse if not properly managed with guidelines and best practices.

Incorrect Option: D. Recommend using related lists instead of list views.
Recommending using related lists instead of list views is not a suitable solution. Related lists show records related to the current record being viewed, while list views show a collection of records of the same object. They serve entirely different purposes. A related list cannot replace the functionality of a list view, which is to provide a filtered and sortable list of records for a user to work with.

Summary:
The service team is overwhelmed by the sheer number of available list views, which makes it difficult to find the necessary ones. The problem is one of information overload and poor organization. The goal is to reduce the number of list views a user sees, making the interface cleaner and more efficient. The solutions should focus on managing and controlling the visibility and existence of list views to improve the user's navigational experience.

Reference:
Manage List Views: Salesforce Help Documentation

Explanation:

This scenario describes a standard CRM sales process for tracking potential customers (home buyers). The correct answers are the core standard objects that manage a person's journey from an initial inquiry to a closed sale. While "Property" is critical for real estate, it is not a standard Salesforce object and must be custom-built.

✅ Correct Option: B. Lead
The Lead object is designed for potential customers who are not yet qualified. A visitor submitting contact information on the website to learn about homes is a classic example of a Lead in Salesforce.

✅ Correct Option: C. Contact
The Contact object represents an individual person, typically associated with an Account. Once a Lead is qualified and converted in Salesforce, a Contact record is created to manage the ongoing relationship with that home buyer.

✅ Correct Option: D. Opportunity
The Opportunity object tracks a specific sales deal, such as a home purchase. It is used to manage stages (e.g., "Prospecting," "Closing"), forecast revenue, and record the likelihood of a successful transaction with a home buyer.

❌ Incorrect Option: A. Property
While essential for a realty business, Property is not a standard Salesforce object. According to Salesforce documentation, a custom object must be created to track property listings, as there is no pre-built standard object for this purpose.

❌ Incorrect Option: E. Address
Address is a standard field type (e.g., on Account or Contact objects) and not a standalone standard object for tracking business relationships or sales processes. It stores location data but does not manage customer interactions.

Summary:
The question tests knowledge of standard Salesforce sales objects. Lead, Contact, and Opportunity form the core pipeline for tracking a prospect to a customer. Property requires a custom object, and Address is a field type, not a trackable object.

Reference:
This aligns with the official exam guide's Data Modeling domain. The standard objects (Lead, Contact, Opportunity) are part of Salesforce's core Sales Cloud functionality, while objects like Property are industry-specific customizations.