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
Cloud Kicks wants to implement its company colors in all UIcomponents, like buttons and icons, using a custom themes.
How does the Salesforce Lightning Design System (SLDS) ensure the UI components align with the theme?
- A . Design tokens prefixed with "brand"
- B . JS libraries loaded from a static resource
- C . CSS Hexcolors
- D . Builder panels
A
Explanation:
The Salesforce Lightning Design System (SLDS) is a set of design guidelines and resources for creating consistent and beautiful user experiences on the Salesforce platform. It provides UI components, icons, fonts, colors, and more that follow the best practices and accessibility standards of Salesforce. One of the features of SLDS is the ability to create custom themes that reflect the brand identity and personality of a company or an app. Custom themes can be implemented using design tokens, which are variables that store the values of the UI elements, such as colors, sizes, spacing, fonts, etc. Design tokens can be overridden or customized to change the appearance of the UI components without modifying the CSS or HTML code. To implement the company colors in all UI components, such as buttons and icons, using a custom theme, the UX designer should use the design tokens prefixed with “brand”, such as $brand-primary, $brand-secondary, $brand-accessible, etc. These design tokens control the color scheme of the UI components and can be assigned the values of the company colors. For example, to change the color of the primary button to the company’s blue color, the UX designer can use the following design token: $brand-primary: #0070d2;
Reference:
: User Experience Designer Certification Prep: Module 7: Implement User Interfaces
: Salesforce Lightning Design System: Customization
: Salesforce Lightning Design System: Design Tokens
Cloud Kicks wants to apply branding to its current Salesforce org, currently using Lightning Experience. The look and feel must follow company design guidelines.
Which declarative design properties should be used to achieve this?
- A . Create a custom Theme in Themes and Branding, selecting logo, brand colors, and images.
- B . Design a custom Branding set in use interface, selecting a logo,colors, and font type.
- C . Develop a custom Layout in user interface, attaching a new stylesheet in static resources.
- D . Choose one of the built-in Salesforce themes that closest matches the design guidelines
A
Explanation:
The best way to apply branding to a Salesforce org using Lightning Experience is to create a custom theme in Themes and Branding. Themes and Branding is a feature that allows the administrator to customize the look and feel of Salesforce to match the branding of the organization. The administrator can add logos, default images, and colors to the theme. The administrator can also choose one of the built-in Salesforce themes, or create their own custom themes with just a few clicks. To create a custom theme, from Setup, enter Themes and Branding in the Quick Find box, then select Themes and Branding. Click New Theme and upload the logo, brand colors, and images that follow the company design guidelines. The administrator can also preview and activate the theme for the entire org 1.
Reference: [Brand Your Org in Lightning Experience] (https://help.salesforce.com/s/articleView?id=sf.brand_your_org_in_lightning_experience.htm&lan guage=en_US&type=5)
Which two would be considered responsive design best practices? Choose 2 answers
- A . Specify breakpoint sizes.
- B . Use separate URLs per device.
- C . Utilize pop-up windows.
- D . Minimize page weight.
A D
Explanation:
Responsive design is a web design approach that aims to make web pages adapt to different screen sizes and resolutions, ensuring good usability and user experience across all devices.
Some of the best practices for responsive design are:
Specify breakpoint sizes: Breakpoints are the points at which the layout of a web page changes based on the width of the viewport. For example, a web page may have a two-column layout on a desktop, a single-column layout on a tablet, and a stacked layout on a mobile phone. Specifying breakpoint sizes helps to create a fluid and flexible layout that responds to the device capabilities and user preferences. Breakpoints can be specified using media queries in CSS, which allow applying different styles depending on the media features, such as width, height, orientation, resolution, etc.
For example:
@media (max-width: 600px) { /* Styles for screens that are 600px or smaller */ }
@media (min-width: 601px) and (max-width: 900px) { /* Styles for screens that are between 601px and 900px */ }
@media (min-width: 901px) { /* Styles for screens that are 901px or larger */ }
Minimize page weight: Page weight is the amount of data that a web page transfers to load on a browser. It includes the size of the HTML, CSS, JavaScript, images, fonts, and other resources that make up the web page. Minimizing page weight helps to improve the performance, speed, and user satisfaction of a web page, especially on mobile devices that may have limited bandwidth, battery, and processing power.
Some of the ways to minimize page weight are:
Optimize images: Images are often the largest contributors to page weight, so it is important to optimize them for the web. This means choosing the right format, size, resolution, and compression level for each image, as well as using responsive images techniques, such as the srcset and sizes attributes, to deliver the most appropriate image for each device and screen size.
Implement caching: Caching is a technique that stores a copy of a web page or its resources on the browser or the server, so that they can be reused without having to be downloaded again. This reduces the amount of data that needs to be transferred and improves the loading time of a web page. Caching can be implemented using HTTP headers, such as Cache-Control and Expires, or using service workers, which are scripts that run in the background and intercept network requests. Minify and concatenate files: Minification is a process that removes unnecessary characters, such as whitespace, comments, and formatting, from the code files, such as HTML, CSS, and JavaScript, to reduce their size. Concatenation is a process that combines multiple code files into one, to reduce the number of HTTP requests that the browser needs to make. Both minification and concatenation can help to reduce the page weight and improve the performance of a web page.
Use a content delivery network (CDN): A CDN is a network of servers that are distributed across different locations and regions, and that store and deliver copies of a web page or its resources to the users. A CDN can help to reduce the page weight and improve the speed of a web page by serving the content from the nearest server to the user, reducing the latency and bandwidth consumption.
The other two options, using separate URLs per device and utilizing pop-up windows, are not considered responsive design best practices, as they can create usability and accessibility issues for the users. Using separate URLs per device means creating different versions of a web page for different devices, such as example.com for desktop, m.example.com for mobile, and t.example.com for tablet. This approach can lead to inconsistent and fragmented user experiences, as well as duplicate content and SEO problems. Utilizing pop-up windows means creating new browser windows that open on top of the current web page, usually to display advertisements, notifications, or forms. This approach can be annoying and intrusive for the users, as well as difficult to close or navigate on small screens.
Reference: Responsive Design: Best Practices and Considerations | Toptal®, Responsive design – Learn web development | MDN, The Beginner’s Guide to Responsive Web Design in 2023 – Kinsta, Responsive Design Best Practices. by Nick Babich – UX Planet
A Sales team is having trouble interacting with Contact records in Sales Cloud. They cannot find the information they need, and many of the visible record fields are not relevant to sales activities. On top of that, they complain the page load time is very long.
Which approach should be recommended to improve their experience?
- A . Run the Salesforce Optimizer App to identify fields not in use.
- B . Move all unused fields to a separate section at the bottom of the page.
- C . Implement In-App Guidance to help users focus on the most important fields.
A
Explanation:
The best approach to improve the Sales team’s experience with Contact records in Sales Cloud is to run the Salesforce Optimizer App to identify fields not in use. The Salesforce Optimizer App is a free tool that scans the Salesforce org and provides a diagnostic report on the performance and health of the org1. It analyzes how the org uses various features, such as fields, triggers, layouts, profiles, reports, and more, and suggests customizations and improvements based on best practices1. By running the Salesforce Optimizer App, the Sales team can find out which fields are not being used or are redundant, and remove or hide them from the Contact record page. This way, they can simplify the page layout, reduce the page load time, and focus on the fields that are relevant to their sales activities2.
Moving all unused fields to a separate section at the bottom of the page is not a good option, as it does not solve the problem of having too many fields on the page. It would still affect the page load time and the user experience, as the users would have to scroll down to see the entire page. Moreover, it would not help the users to find the information they need, as the fields would not be organized in a logical or meaningful way3.
Implementing In-App Guidance to help users focus on the most important fields is also not a good option, as it does not address the root cause of the problem, which is having too many fields on the page. In-App Guidance is a feature that allows admins to create custom prompts and walkthroughs to guide users through tasks or processes on Salesforce Lightning pages4. It can be useful for user training, onboarding, or adoption, but it cannot replace the need for a clean and efficient page layout. In fact, having too many prompts or walkthroughs on the page can be distracting and annoying for the users, especially if they are not relevant or helpful4.
Reference: Run the Salesforce Optimizer App
Improve Your Implementation with Salesforce Optimizer
Page Layouts
In-App Guidance in Lightning Experience
Cloud Kicks needs functional components thatwill be used on many pages. The components need to be consistent with the look and feel of Lightning Experience.
What does the Salesforce Lightning Design System (SLDS) provide that will ensure consistency?
- A . Experience Lightning Components
- B . ComponentBlueprints
- C . JavaScript Frameworks
- D . Custom Lightning components
B
Explanation:
The Salesforce Lightning Design System (SLDS) provides component blueprints that will ensure consistency for Cloud Kicks’ functional components. Component blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. They follow the design guidelines, accessibility standards, and best practices of Lightning Experience. They also include variants, states, and modifiers to handle different use cases and scenarios. By using component blueprints, Cloud Kicks can create functional components that are consistent with the look and feel of Lightning Experience without writing custom code or CSS.
Reference: Component Blueprints
Introduction to the Salesforce Lightning Design System
What is a benefit of inclusive design?
- A . Reducing friction for users in achieving their goals
- B . Tailoring a solution to one type of user
- C . Creating a lowest-common-denominator design
A
Explanation:
Inclusive design is a methodology aimed at creating products that are accessible to as many people as possible, regardless of their abilities or circumstances. The benefit of inclusive design is that it focuses on reducing friction for users in achieving their goals by:
Considering a wide range of human diversity, including ability, language, culture, gender, age, and other forms of human difference.
Identifying and eliminating unnecessary barriers that might prevent people from effectively using a product or service.
Ensuring that products and services can be used by everyone, to the greatest extent possible, without the need for adaptation.
Inclusive design does not mean tailoring a solution to one type of user (B) or creating a lowest-
common-denominator design that meets only the most basic needs of all users (C). Instead, it seeks
to understand and address the needs of a broad audience to create more usable and accessible
experiences for everyone.
Reference: The Interaction Design Foundation provides extensive resources on inclusive design, its principles, and how to apply them in the design process. These resources offer valuable insights into creating designs that are accessible and beneficial to a wide audience.
Cloud Kicks plans to release a new Salesforce product to its employees, who all have different backgrounds and experience levels within Salesforce.
Which onboarding design best practice would best support the product release?
- A . Provide written help documentation as the single source of truth for learning about new features.
- B . Identify the message, audience, and purpose for content.
- C . Create pop-ups to give users a full visualization of a product.
B
Explanation:
The best onboarding design practice for Cloud Kicks would be to identify the message, audience, and purpose for content. This would help them tailor the content to the different needs and preferences of their employees, and provide them with the most relevant and useful information. Providing written help documentation as the single source of truth for learning about new features (A) might not be engaging or effective for all users, especially those who prefer visual or interactive learning.
Creating pop-ups to give users a full visualization of a product © might be intrusive or overwhelming for some users, and might not explain the benefits or features of the product clearly. Identifying the message, audience, and purpose for content (B) is a key step in creating user-centered onboarding design, as it helps to define the goals, scope, and tone of the content, and to align it with the user’s needs, expectations, and motivations.
Reference: [UX Designer Certification Prep: Onboarding Design]
[UX Designer Certification Prep: Content Strategy] [Salesforce Certified User Experience Designer Exam Guide]
A UX Designer is in the process of designing a new page layout for a custom object in Salesforce.
How should the designer ensure thebest end-user experience?
- A . Include all potentially useful fields.
- B . Make field labels and API names identical.
- C . Mark all fields as required.
- D . Group similar fields using sections.
D
Explanation:
The best way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce is to group similar fields using sections. Sections are UI components that allow you to organize fields into logical groups and provide headings and descriptions for each group. Sections help to improve the readability, scannability, and usability of the page layout by reducing the visual clutter and providing a clear structure and hierarchy for the information. Sections also help to align the page layout with the user’s mental model and expectations, as well as the business processes and workflows. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]
Including all potentially useful fields is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create a crowded and overwhelming interface that is hard to navigate and understand. It can also increase the cognitive load and the scrolling effort for the user, as well as the maintenance cost for the designer. It is better to include only the essential and relevant fields that the user needs to perform their tasks and goals, and use other methods such as related lists, tabs, or modals to display additional information. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]
Making field labels and API names identical is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create confusion and inconsistency for the user and the developer. Field labels are the text that appear on the user interface to identify the fields, while API names are the unique identifiers that are used by the system and the code to reference the fields. Field labels and API names should be different, because they have different purposes and audiences. Field labels should be clear, concise, and descriptive, using natural language and proper capitalization, punctuation, and spacing. API names should be concise, unique, and consistent, using underscores and camel case to separate words. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]
Marking all fields as required is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create frustration and annoyance for the user, as well as increase the error rate and the abandonment rate. Required fields are fields that the user must fill in before they can save or submit the record. Required fields should be used sparingly and only for the fields that are absolutely necessary for the system or the business logic. Marking all fields as required can make the user feel pressured and constrained, and force them to enter irrelevant or inaccurate data. It can also make the user miss the truly important fields, or give up on completing the record altogether. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]
Reference: [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]
A UX Designer wants to communicate the value of diversity, inclusion, and equality in design.
Which business outcomes represent these values?
- A . Inclusive recruitment, lower market share, and less employee turnover
- B . Economic growth, greater market share, and less employee turnover
- C . Critical investing, more employee turnover, and greater market share
B
Explanation:
Diversity, inclusion, and equality in design are values that aim to create products, services, and environments that are accessible, welcoming, and fair for all people, regardless of their age, gender, ethnicity, disability, sexual orientation, religion, or other characteristics. Diversity, inclusion, and equality in design can also bring positive business outcomes, such as economic growth, greater market share, and less employee turnover12.
Economic growth is a business outcome that represents the increase in the value of goods and services produced by an organization or a country over time. Economic growth can be influenced by various factors, such as innovation, productivity, efficiency, and competitiveness. Diversity, inclusion, and equality in design can contribute to economic growth by fostering creativity, innovation, and problem-solving, as well as by attracting and retaining diverse talent, customers, and partners12. Greater market share is a business outcome that represents the percentage of sales or customers that an organization has in a particular market or industry. Greater market share can indicate the success and competitiveness of an organization, as well as its potential for growth and profitability. Diversity, inclusion, and equality in design can help achieve greater market share by expanding the reach and appeal of products, services, and environments to diverse and underserved markets, as well as by enhancing customer satisfaction, loyalty, and advocacy12.
Less employee turnover is a business outcome that represents the rate at which employees leave an organization and are replaced by new ones. Less employee turnover can indicate the stability and quality of an organization, as well as its ability to retain and develop its human capital. Diversity, inclusion, and equality in design can help reduce employee turnover by creating a positive and inclusive work culture, where employees feel valued, respected, and engaged, as well as by providing opportunities for learning, development, and career progression12.
Reference: 1: The business value of design | McKinsey 2: The Business Case for Diversity, Equity, and Inclusion – Salesforce.com
Cloud Kicks (CK) allows its partners to manage leads and opportunities. CK’s relationship manager has requested that partners are able to quickly browse and see their opportunities segmented by key attributes:
If the opportunity is closing within 2 weeks If it is valued at more than $100,000.
Which approach should be used in Experience Builder to enable this?
- A . Create a custom Lightning Web Component using a data table for each key attribute.
- B . Allow each user to create a filter for each key attribute and link to the opportunities list view.
- C . Configure a pre-filtered opportunity list view for each key attribute with the partner group.
C
Explanation:
The best approach to enable partners to quickly browse and see their opportunities segmented by key attributes is to configure a pre-filtered opportunity list view for each key attribute with the partner group. This way, the partners can easily access the list views that show only the opportunities that match the criteria, such as closing within 2 weeks or valued at more than $100,000. Creating a custom Lightning Web Component using a data table for each key attribute (A) might be too complex and time-consuming, and it might not be compatible with the Experience Builder. Allowing each user to create a filter for each key attribute and link to the opportunities list view (B) might be too tedious and inconsistent, and it might not provide a quick and easy way to browse the opportunities. Configuring a pre-filtered opportunity list view for each key attribute with the partner group © is a simple and effective solution that leverages the existing functionality of the Experience Builder and the list view component12.
Reference: List View Component | Salesforce Experience Cloud
Create and Edit List Views | Salesforce Help