Salesforce User Experience Designer Practice Exams
Last updated on Nov 16,2026- Exam Code: User Experience Designer
- Exam Name: Salesforce Certified User Experience Designer
- Certification Provider: Salesforce
- Latest update: Nov 16,2026
A UX Designer has recently released a feature on experience Cloud and wants to know if the feature
was successful and track usability over time.
Which research methodology should be used?
- A . Qualification
- B . Quantitative
- C . Qualitative
- D . Quantizing
B
Explanation:
Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested.
Quantitative research can help answer questions such as:
How many users are using the feature?
How often are they using it?
How long does it take them to complete a task with the feature?
How satisfied are they with the feature?
How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?
Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking. These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.
Qualitative research methodology, on the other hand, involves collecting and analyzing non-
numerical data that can reveal users’ attitudes, behaviors, motivations, and preferences.
Qualitative research can help answer questions such as:
Why are users using or not using the feature?
What are their pain points, needs, and goals with the feature?
How do they feel about the feature?
What are their expectations and feedback for the feature?
How does the feature fit into their context and workflow?
Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.
Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.
Reference: User Research Methods, Quantitative vs. Qualitative Usability Testing, 8 Essential Usability Testing Methods for UX Insights
Cloud kicks is planning its einstein Bot implementation and has identified common issues the Bot can resolve. CK has determined that extensive technical planning is needed for bot effectiveness and customer satisfaction
- A . Training and support for planning
- B . user interface planning
- C . deboarding planning
- D . voice and tone planning
B
Explanation:
User interface planning is an essential part of the Einstein Bot implementation process, as it involves designing the bot’s appearance, behavior, and interactions with the customers. User interface planning can affect the bot’s effectiveness and customer satisfaction, as it can influence the clarity, efficiency, consistency, and beauty of the bot’s experience. User interface planning includes1: Choosing a bot avatar and name that match the brand and tone of the company
Configuring the bot greeting and fallback messages that set the expectations and boundaries of the bot’s capabilities
Designing the bot dialogues and menus that guide the customers through the conversation and provide relevant options and information
Testing and iterating the bot user interface based on user feedback and analytics
Reference: Einstein Bots Project Planning | Salesforce Trailhead
During discovery, a UX Designer finds that most sellers like the idea of using the utility bar for easy access and productivity.
Which three standarduse cases could be recommended for using the utility bar to enhance the user experience? Choose 3 answers
- A . Quick access to Lightning Dialer
- B . Perform common tasks without navigating away from page
- C . Access to view a list of records favorited for quickaccess
- D . Access to a consistent custom help menu across the org for all users
- E . Access at any time to a customized set of items specific to an app
B C E
Explanation:
The utility bar is a fixed footer that gives users quick access to productivity tools, such as notes, history, and recent items. It can be customized for each Lightning app to enhance the user experience and efficiency. Some of the standard use cases for using the utility bar are: Perform common tasks without navigating away from the page: Users can use the utility bar to perform tasks such as creating notes, logging calls, or sending emails without leaving their current context. This reduces the need for switching tabs or opening new windows, and saves time and clicks.
Access to view a list of records favorited for quick access: Users can use the utility bar to access their favorites, which are records, lists, groups, or other items that they have marked with a star icon for easy access. This allows users to quickly navigate to the items they use most frequently, and organize them in a personalized way.
Access at any time to a customized set of items specific to an app: Users can use the utility bar to access items that are relevant and useful for the app they are using. For example, in the Sales app, users can access the Lightning Dialer, the Assistant, or the Today’s Events utility. In the Service app, users can access the Omni-Channel, the Macros, or the Case Timer utility. The utility bar can be configured to show different items for different apps, depending on the user’s needs and preferences.
Reference:
: User Experience Designer Certification Prep: Module 5: Design User Interfaces
: Lightning App Builder: Utility Bar
Cloud Kicks has updated its logo and wants it prominently displayed on its Digital Experience site. Where does their UX Designer need to code to update the logo?
- A . Visualforce pages
- B . Page headers
- C . Email templates
B
Explanation:
A page header is a component that appears at the top of every page on a Digital Experience site, and usually contains the site logo, the site name, the navigation menu, and other elements that provide a consistent and recognizable look and feel for the site. A UX Designer can code the page header to update the logo for Cloud Kicks by using the Experience Builder or the Developer Console1. The Experience Builder is a point-and-click tool that allows creating and customizing the page header using predefined templates, themes, and components. The Developer Console is a code editor that allows creating and editing the page header using HTML, CSS, JavaScript, and Lightning components2. Both tools provide the option to upload and insert the new logo image file into the page header, and to adjust its size, position, and alignment.
The other two options, Visualforce pages and email templates, are not the places where the UX Designer needs to code to update the logo for Cloud Kicks. Visualforce pages are web pages that can be used to create custom user interfaces for Digital Experience sites, but they do not affect the page header, which is a separate component that can be added to any page3. Email templates are predefined layouts and content that can be used to send emails to the site users, but they do not have any impact on the site appearance or functionality.
Reference: Create a Custom Header for Your Site | Salesforce Trailhead and Customize Your Site Header and Footer | Salesforce Trailhead
Users from a small group within a sales teams have complained about an object that is often used only by them that has not been a edit to their lighting app due to small volume of users the administrator is not considering a new app for them
Which two salesforce features should be suggested to improve the end-user experience?
- A . Favorite the often used object
- B . add the objects related list to the home page
- C . personalized the navigation bar
- D . create a custom component on a dashboard
A C
The users can improve their end-user experience by favoriting the often used object and personalizing the navigation bar. Favoriting the object allows the users to access it quickly from the Favorites menu in the header. Personalizing the navigation bar allows the users to add, remove, or reorder the items that they use frequently. These features do not require the administrator to create a new app or modify the existing one, and they can be customized by the users themselves according to their preferences and needs.
Reference: [Salesforce Certified User Experience Designer Exam Guide], Section 3.1: Design and implement solutions that meet user needs
[UX Designer Certification Prep: User-Centered Design], Unit 4: Design for User Needs
[Prepare for Your UX Designer Credential], Trailmix: User-Centered Design
[Salesforce Help: Favorites in Lightning Experience]
[Salesforce Help: Personalize Your Navigation Bar]
Which elements of visual design should be used to better translate style and branding guidelines?
- A . Typography, Color, Imagery
- B . Wireframes, Personas, Blueprints
- C . Sketching, Wireframes, Storyboards
A
Explanation:
In visual design, especially within the context of translating style and branding guidelines, certain elements play crucial roles in ensuring that the design effectively communicates the intended brand identity and aesthetic. These elements include:
Typography: The choice of fonts and how text is styled and arranged can significantly impact the brand’s voice and how content is perceived by the audience. Typography can convey feelings, create hierarchy, and guide the user’s attention through the design.
Color: Color schemes are fundamental in visual design as they can evoke emotions, communicate brand values, and improve the user’s experience by creating visual interest and guiding focus. Imagery: The use of images, icons, illustrations, and other visual media must align with the brand’s style and values. Imagery can help tell a brand’s story, convey complex information quickly, and connect with users on an emotional level.
Options B and C, such as Wireframes, Personas, Blueprints, Sketching, and Storyboards, are crucial in the early stages of the design process for conceptualization and planning but do not directly translate style and branding guidelines in the same way that typography, color, and imagery do.
A UX Designer is creating a custom To-Do List component to replace the standard Salesforce one. Their developer is using a parent-child Lightning Web Component (LWC) structure to build the component, creating a parent component for the list and a single repeated child component for each To-Do Item within the list.
Which two impacts of the LWC’s Shadow DOM should be considered when designing or developing
the stylesheets for these components? Choose 2 answers
- A . Any needed Saleforce Lightning Design System (SLDS) classes and styles must be imported into both the parent list and child items.
- B . The CSS styles defined in the parent list component are not shared with the child items.
- C . Any custom shared between the list and child items should be imported from a shared CSS file.
- D . The CSS style defined in the parent list component are inherited by the child items
B,C
Explanation:
Shadow DOM is a web standard that encapsulates the internal document object model (DOM) structure of a web component. It isolates the component’s markup and styles from the rest of the page, and prevents the component from being affected by or affecting the global DOM. When designing or developing the stylesheets for a parent-child LWC structure, the following impacts of the shadow DOM should be considered:
The CSS styles defined in the parent list component are not shared with the child items. This is because the shadow DOM creates a boundary between the parent and the child components, and the styles defined in the parent component do not cascade down to the child components. This means that each component needs to define its own styles, or import them from a common source. This also means that the parent component cannot directly style the child components, or vice versa12.
Any custom styles shared between the list and child items should be imported from a shared CSS file. This is a recommended practice to avoid duplicating the same styles in multiple components, and to maintain consistency and reusability. A shared CSS file can be created as a static resource, and imported into the components using the loadStyle() method from the platformResourceLoader module. Alternatively, a shared CSS file can be created as a LWC component, and imported into the components using the @import directive134.
Reference:
: [Shadow DOM | Lightning Web Components Developer Guide | Salesforce Developers]
: [Light DOM | Lightning Web Components Developer Guide | Salesforce Developers]
: [Understanding Shadow DOM and Template in LWC C SFDC Lightning]
: [Shadow DOM, CSS and Styling Hooks in LWC what you need to know]
: [How to Share CSS Between Lightning Web Components | Salesforce Developers Blog]
: [How to Use a Shared CSS File in a Lightning Web Component | Salesforce Developers Blog]
A UX Designer has been tasked with designing a custom Lightning Web Component (LWC) that uses the Salesforce Lightning Design System (SLDS).
Where on the SLDS website should the designer find accessible HTML and CSS used to create components along with implementation guidelines?
- A . Component Blueprints
- B . Design Tokens
- C . Development Tools
A
Explanation:
The best place on the SLDS website for the designer to find accessible HTML and CSS used to create components along with implementation guidelines is the Component Blueprints1. Component Blueprints are framework-agnostic, accessible HTML and CSS that provide the basic structure and style for Lightning components1. The designer can use the Component Blueprints to create custom Lightning Web Components that are consistent with the Lightning Design System. Design Tokens (B) are not the best place to find HTML and CSS, as they are variables that store design attributes, such as colors, fonts, and spacing2. Development Tools © are not the best place to find implementation guidelines, as they are tools and resources that help developers build and test Lightning components, such as VS Code extensions, LWC recipes, and Playground3.
Reference: Component Blueprints | Salesforce Lightning Design System Design Tokens | Salesforce Lightning Design System Development Tools | Salesforce Lightning Design System
After conducting user interviews, a UX Designer finds that an equal amount of users prefer to use the Comfy density setting as the Compact density setting while viewing record details.
Which approach should be avoided by developers when building custom components to make sure their components take advantage of this setting?
- A . Using the varSpacingMedium design token in CSS to set spacing
- B . Using REM_based spacing values when styling components.
- C . Using existing Lightning Components such as the card or page header
B
Explanation:
When developers are building custom components in Salesforce and need to ensure that these components adapt to user preferences for density settings (Comfy or Compact), they should avoid using REM-based spacing values. This is because REM-based spacing does not automatically adjust based on the density setting chosen by the user, leading to a lack of consistency with the rest of the Salesforce UI, which does adapt to these settings. Instead, developers should:
A) Use the varSpacingMedium design token in CSS, as Salesforce Lightning Design System (SLDS) design tokens are context-aware and can adjust their values based on the density setting, ensuring a consistent user experience across different user preferences.
C) Use existing Lightning Components such as the card or page header, which are pre-built to adapt
to density settings, ensuring that custom components align with the overall Salesforce UI and respect
user settings for density.
Reference: Salesforce Lightning Design System (SLDS) documentation provides guidelines on using design tokens and building responsive components that respect user settings like density preferences. You can find more information on the official Salesforce Developers website or the SLDS documentation section.
Cloud Kicks (CK) wants to display contact information, including avatar, name, and title, for people who are related to a customer on a Record page. However, title space is available.
Which standard component’s design should be used given CK’s constraints?
- A . Table
- B . Tree Grid
- C . Tiles
- D . Interactive Cards
C
Explanation:
Tiles are standard components that display records or objects as a collection of boxes that contain a photo and additional information1. Tiles are suitable for Cloud Kicks (CK) to display contact information, including avatar, name, and title, for people who are related to a customer on a Record page, as they provide a compact and visual way to show the relevant data. Tiles also allow users to interact with the records by clicking or tapping on them1. Tiles can be customized to fit the available space and layout of the Record page2.
Reference: Components – Salesforce Lightning Component Library, Tiles – Lightning Design System
Interactive cards are compact components that can display information such as avatars, names, and titles in an organized way. Additionally, Interactive Cards are designed to be responsive and can be used to display information on smaller screens, such as mobile devices, without taking up too much space. This makes them ideal for CK’s use case, as they can display all of the required information within the limited title space. For more information, see the Salesforce Lightning Design System documentation (https://lightningdesignsystem.com/components/cards/#interactive-cards).