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 (CK) has been tracking the details of its storage facilities in an Excel sheet, where each facility is represented as a row and the details about each facility are represented by columns.
How should CK store this information in Salesforce?
- A . Objects to represent facility details and fields to store storage facilities
- B . Objects to represent both storage facilities and facility details
- C . Objects to represent storage facilities and fields to store facility details
C
Explanation:
The best way to store the information of Cloud Kicks’ storage facilities in Salesforce is to use objects to represent storage facilities and fields to store facility details. This is because objects and fields in Salesforce are analogous to database tables and columns, respectively1. Each object contains a set of fields that store data values, and each record is an instance of an object1. Therefore, if Cloud Kicks wants to store the same information that they have in their Excel sheet, they can create a custom object called Storage Facility, and add fields for each detail that they want to track, such as location, capacity, inventory, and so on. Then, they can create records for each storage facility and populate the fields with the corresponding data. This way, they can store and manage their data in a structured and consistent way, and leverage the features and benefits of Salesforce, such as reports, dashboards, automation, and security23.
Using objects to represent facility details and fields to store storage facilities is not a valid option, as it does not make sense to use objects as data values. Objects are meant to represent entities or concepts, not attributes or properties1. Using objects to represent both storage facilities and facility details is also not a good option, as it would create unnecessary complexity and redundancy in the data model. Objects can be related to each other through various types of relationships, such as lookup, master-detail, or many-to-many4. However, in this case, there is no need to create a separate object for each facility detail, as they are not independent entities, but rather characteristics of the storage facilities. Creating a separate object for each detail would also require creating more fields, records, and relationships, which would increase the maintenance and storage costs, and reduce the performance and usability of the system5.
Reference: Learn All About Objects and Fields in Salesforce – Forcetalks
Mastering Salesforce CRM Administration – Packt Subscription Overview of Salesforce Objects and Fields Object Reference for the Salesforce Platform
Understand Custom & Standard Objects Unit | Salesforce Trailhead
Cloud Kicks wants to create a new service experience, increasing user satisfaction for internal and external users Both a customer community and a service console win be created.
Which tool should a UX Designer use to document user goals, common tasks, and pain points?
- A . Storyboards
- B . Wireframes
- C . User Personas
- D . User Journeys
C
Explanation:
: To document user goals, common tasks, and pain points for a new service experience, the tool that a UX Designer should use is user personas. User personas are fictional representations of the target users, based on real data and research. User personas help the designer to understand the needs, motivations, behaviors, and expectations of the users, as well as their challenges and frustrations. User personas can also help the designer to prioritize features, create scenarios, and design solutions that are relevant and meaningful for the users.
Reference:
: UX Designer Certification Prep: Designing for User Research | Trailhead: User Personas | Salesforce Developer Guide
Cloud Kicks has a content-rich set of record pages and wants its UX Design team to organize and consolidate them.
Which Salesforce Lightning Design System (SLDS) component should be used to organize and consolidate content?
- A . Data Tables
- B . Modals
- C . Q Tabs
C
Explanation:
Q Tabs are a type of SLDS component that can be used to organize and consolidate content on a record page. Q Tabs are a variant of the Tabs component that are designed for use in the Lightning App Builder. Q Tabs allow users to switch between different views of related information within the same context. Q Tabs can also be nested to create subtabs within a tab. Q Tabs can help UX designers to create content-rich record pages that are easy to navigate and consume. Q Tabs can also help to reduce clutter and scrolling on a record page by grouping related content into tabs. Q Tabs can be customized with different icons, labels, and badges to indicate the type and status of the content in each tab. Q Tabs can also be configured to load content dynamically or on demand, which can improve the performance and user experience of the record page.
Reference: Q Tabs Component Blueprint | Lightning Design System, Tabs Component Blueprint | Lightning Design System, Tabs | Lightning Web Components Developer Guide | Salesforce Developers
Cloud Kicks wants to prevent its sales agents from being able to save a new account unless they have entered the phone number in the correct format and with the correct number of digits. A validation rule would then prevent the new account from saving.
Which method should be used to improve the user experience in the simplest way while preventing errors?
- A . Set a prompt to display on the page using In-App Guidance.
- B . Set field-level error message to display on the page.
- C . Mark the field as Required.
B
Explanation:
A field-level error message is a message that appears next to a specific field when the user enters invalid data or omits required data. It helps the user to correct the error and proceed with the action.
A field-level error message is more user-friendly than a validation rule, which displays a generic message at the top of the page and prevents the user from saving the record. A field-level error message can also provide guidance on the correct format and number of digits for the phone number field. Marking the field as required would not ensure that the user enters the phone number in the correct format and with the correct number of digits. Setting a prompt to display on the page using In-App Guidance would not prevent the user from entering invalid data or omitting required data.
Reference: [Field-Level Error Messages], [Validation Rules], [In-App Guidance]
Cloud Kicks wants to use Paths for onboarding its sales representatives.
Which Path feature should be used to add onboarding value?
- A . Integrated buttons to automate approvals
- B . Actions and recommendations component
- C . A Key fields to complete before next Path stage
C
Explanation:
The Path feature that should be used to add onboarding value for the sales representatives is the Key fields component. The Key fields component allows the admin to specify up to five fields that are important or required for each stage of the Path. The sales reps can see and edit these fields directly from the Path, without scrolling through the record page. This helps to guide the reps on what information they need to gather or update at each stage, and ensures data quality and completeness. The Key fields component can also be used to enforce validation rules or required fields, by preventing the reps from moving to the next stage until they fill out the necessary fields.
Reference:
: Set Up a Path
: Considerations and Guidelines for Creating Paths
: Optimize Sales Processes with Path in Salesforce
The service team at Cloud Kicks has complained about the quantity of list views available, making it hard find the relevant ones.
In which two ways should their experience be improved? Choose 2 answers
- A . Request users to create and share their list views.
- B . Share list views to Public Groups and only add relevant users.
- C . Remove irrelevant public list views.
- D . Recommend using related lists instead of list views.
B C
Explanation:
To improve the experience of the service team at Cloud Kicks, their UX Designer should do the following12:
B) Share list views to Public Groups and only add relevant users. This will help to organize and manage the list views based on the roles and responsibilities of the service team members, and to avoid cluttering their list view menu with unnecessary or irrelevant list views. Public Groups are collections of users, roles, or other groups that can be used to share list views, reports, dashboards, and other records3.
C) Remove irrelevant public list views. This will help to reduce the number of list views available, and to make it easier for the service team members to find the relevant ones. Irrelevant public list views are those that are outdated, duplicated, unused, or not applicable to the service team’s needs or goals.
Reference: List Views – Salesforce Help, Your Complete Guide to Salesforce List Views in Lightning, Public Groups – Salesforce Help, Improve List View Performance – Salesforce
Cloud Kicks is incorporating Relationship Design principles into its business model and customer offerings wherever possible.
Which principle would represent their company strategy?
- A . Reframing products in terms of outputs over outcomes
- B . Prioritizing engagement over number of impressions
- C . Highlighting product benefits over uncovering customer needs
B
Explanation:
The principle that would represent Cloud Kicks’ company strategy is prioritizing engagement over number of impressions. This principle is based on the intention mindset of Relationship Design, which means engaging with clear purpose and focusing on the quality of interactions rather than the quantity1. Reframing products in terms of outputs over outcomes (A) is not a Relationship Design principle, as it does not consider the value or impact of the products for the customers. Highlighting product benefits over uncovering customer needs © is also not a Relationship Design principle, as it does not show empathy or understanding of the customers’ problems or goals.
Reference: Embrace the Relationship Design Mindsets Unit | Salesforce Trailhead
A UXDesigner is asked to design a new application built on Salesforce.
What should be their first step?
- A . Create branding sets for each audience using Experience Builder.
- B . Find and review relevant AppExchange packages.
- C . Become familiar with theSalesforce Lightning Design System (SLDS) component blueprints.
- D . Design a series of custom web component for the app.
C
Explanation:
The Salesforce Lightning Design System (SLDS) is a collection of design guidelines, resources, and tools that help create consistent, beautiful, and accessible user experiences across the Salesforce platform1. Component blueprints are one of the key resources that the SLDS provides. They are framework-agnostic, accessible HTML and CSS code snippets that can be used to create UI elements such as buttons, cards, menus, and more2. A UX Designer who is asked to design a new application built on Salesforce should become familiar with the SLDS component blueprints as their first step, because they can help them to3:
Understand the structure, behavior, and appearance of the standard Salesforce components and how they can be customized or extended.
Follow the SLDS design principles and best practices, such as clarity, efficiency, consistency, and beauty.
Ensure that the application is responsive, adaptive, and compatible with different devices and screen sizes.
Leverage the SLDS design tokens, icons, and utilities to create a coherent and scalable visual language.
Reduce the development time and effort by reusing the existing code and avoiding duplication. The other options are not the best first steps for a UX Designer who is asked to design a new application built on Salesforce. Creating branding sets for each audience using Experience Builder is a later step that involves applying the visual identity and style of the application to different user segments and channels4. Finding and reviewing relevant AppExchange packages is a research step that can help to identify existing solutions or features that can be integrated or adapted to the application5. Designing a series of custom web components for the app is a development step that can be done after defining the requirements, wireframes, and prototypes of the application.
Reference: Lightning Design System, Lightning Design System Create the World’s Best Enterprise App Experiences Design System Fundamentals Component Blueprints Ready-to-use HTML and CSS UI elements provide the foundation for Salesforce experience development Go to Blueprints Tokens Visual design values and attributes that ensure branding and UI consistency at scale View Tokens Design Guidelines Design principles and best practices that guide beautiful, consistent, user-friendly product experiences Read Guidelines Tools New! Easy-to-use tools help all Trailblazers optimize workflows and bring Salesforce ideas to life Get Tools
Blueprint Overview – Lightning Design System, Blueprint Overview – Lightning Design System What’s New Getting Started Platforms Design Guidelines Kinetics Accessibility Component Blueprints Overview Accordion Activity Timeline Alert App Launcher Avatar Avatar Group Badges Brand Band Breadcrumbs Builder Header Button Icons Cards Chat Docked Utility Bar Dueling Picklist Dynamic Icons Dynamic Menu Expandable Section Feeds File Selector Files Form Element Global Header Global Navigation Icons Illustration Input List Builder Lookups Map Menus Notifications Page Headers Panels Path Picklist Pills Progress Indicator Prompt Radio Button Group Rich Text Editor Scoped Notifications Scoped Tabs Select Spinners Tabs Textarea Tiles Timepicker Toast Tooltips Tree Grid Trees Trial Bar Vertical Navigation Vertical Tabs Visual Picker Welcome Mat Utilities Design Tokens Icons Tools Resources Blueprint Overview Component blueprints are framework agnostic, accessible HTML and CSS used to create components in conjunction with our implementation guidelines. For more details, check out the glossary on the FAQ page. Show Filters Showing 85 blueprints, 183 variants. Accordion Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark nActivity Timeline Responsive Adaptive Styling Hooks Prototype Base n n Alert Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark nApp Launcher Responsive Adaptive Styling Hooks Prototype Base Checkmark n nAvatar Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark nInitials Checkmark nCheckmark nAvatar Group Responsive Adaptive Styling Hooks Prototype Base Checkmark n nGrouped Checkmark n nBadges Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark nBrand Band Responsive Adaptive Styling Hooks Prototype Base Checkmark n nBreadcrumbs Lightning Component Responsive Adaptive Styling Hooks Prototype Base n Checkmark nBuilder Header Responsive Adaptive Styling Hooks Prototype Base n n Toolbar n n Button Groups Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark n nList Checkmark n nRow Checkmark n nButton Icons Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark n nBordered Filled Container Checkmark n nBordered Inverse Checkmark n nBordered Transparent Container Checkmark n nBrand Checkmark n nInverse Checkmark n nStateful Checkmark n nTransparent Container Checkmark n nButtons Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark nDual Stateful Checkmark nCheckmark nStateful Checkmark nCheckmark nWith Icon Checkmark nCheckmark nCards Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark
nEinstein Checkmark nCheckmark nWrapper Checkmark nCheckmark nCarousel Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark n nChat Responsive Adaptive Styling Hooks Prototype Base Checkmark n nPast Checkmark n nCheckbox Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark nCheckmark nForm Element Checkmark nCheckmark nCheckbox Button Lightning Component Responsive Adaptive Styling Hooks Prototype Base Checkmark n nCheckbox Button Group Responsive Adaptive Styling Hooks Prototype Base Checkmark n nCheckbox Toggle
UX Designer Certification Prep: Design System Fundamentals, UX Designer Certification Prep: Design System Fundamentals Learn how to use the Salesforce Lightning Design System (SLDS) to create consistent, beautiful, and accessible user experiences across the Salesforce platform. Add to Favorites Add to Trailmix tags ~1 hr 30 mins +500 points Module Design System Fundamentals Learn about the Salesforce Lightning Design System (SLDS) and how it can help you create consistent, beautiful, and accessible user experiences across the Salesforce platform. 4 hrs 15 mins +800 points Project Build a Bear-Tracking App with Lightning Web Components Use Lightning Web Components and the Salesforce Lightning Design System to build a bear-tracking app. 2 hrs 15 mins +500 points Project Build a Conference Management App with Aura Components Use Aura Components and the Salesforce Lightning Design System to build a conference management app. 2 hrs 15 mins +500 points Project Build a Discount Calculator with Visualforce Use Visualforce and the Salesforce Lightning Design System to build a discount calculator. 2 hrs 15 mins +500 points Project Build a Survey App with Experience Builder Use Experience Builder and the Salesforce Lightning Design System to build a survey app. 2 hrs 15 mins +500 points Project Build a Travel Approval App with Lightning Flow Use Lightning Flow and the Salesforce Lightning Design System to build a travel approval app. 2 hrs 15 mins +500 points Project Build a Volunteer Management App with Lightning App Builder Use Lightning App Builder and the Salesforce Lightning Design System to build a volunteer management app. 2 hrs 15 mins +500 points Project Build an Expense Tracker App with Lightning Web Components Use Lightning Web Components and the Salesforce Lightning Design System to build an expense tracker app. 2 hrs 15 mins +500 points Project Build an Inventory Management App with Aura Components Use Aura Components and the Salesforce Lightning Design System to build an inventory management app. 2 hrs 15 mins +500 points Project Build an Order Management App with Visualforce Use Visualforce and the Salesforce Lightning Design System to build an order management app. 2 hrs 15 mins +500 points Project Build an RSVP Management App with Experience Builder Use Experience Builder and the Salesforce Lightning Design System to build an RSVP management app. 2 hrs 15 mins +500 points Project Build an SMS Notification App with Lightning Flow Use Lightning Flow and the Salesforce Lightning Design System to build an SMS notification app. 2 hrs 15 mins +500 points Project Build an Branding Sets Unit | Salesforce Trailhead, Branding Sets Unit | Salesforce Trailhead Branding Sets Learn how to use branding sets to apply different styles to your digital experiences. Add to Favorites Add to Trailmix tags ~20 mins Incomplete Branding Sets Customize the look and feel of your digital experiences with branding sets. 15 mins +200 points Quiz +200 points Get Started with Branding Sets Learn how to create and apply branding sets to your digital experiences. 5 mins +200 points Quiz +200 points
AppExchange Basics Unit | Salesforce Trailhead, AppExchange Basics Unit | Salesforce Trailhead AppExchange Basics Learn how to find, try, buy, and install AppExchange solutions. Add to Favorites Add to Trailmix tags ~25 mins Incomplete AppExchange Basics Learn how to find, try, buy, and install AppExchange solutions. 20 mins +200 points Quiz +200 points Get Started with AppExchange Learn what AppExchange is and how it can help you extend Salesforce functionality. 5 mins +200 points Quiz +200 points
A UX Designer has been asked to improve Salesforce adoption among sales representatives at Cloud Kicks. After conducting stakeholder and user interviews, the designer finds there is no clear, consistent sales process.
What should the designer do next?
- A . Tell the customer they need to improve operations before any work can be done.
- B . Log the findings and move forward with presenting possible solutions.
- C . Recommend Field Level Validation to ensure users are entering the correct data.
- D . Conduct a workshop with stakeholders to align on the current state and build consensus.
D
Explanation:
A UX designer’s role is not only to design solutions, but also to facilitate collaboration and communication among stakeholders and users. A clear, consistent sales process is essential for Salesforce adoption, as it defines the steps and actions that sales representatives need to take to close deals. Without a common understanding of the sales process, the UX designer cannot design a Salesforce solution that meets the needs and expectations of the users and the business. Therefore, the designer should conduct a workshop with stakeholders to align on the current state and build consensus on the desired future state. A workshop is an interactive session where the designer can use various techniques, such as journey mapping, persona creation, user stories, and prioritization, to elicit the pain points, goals, and requirements of the stakeholders and users. A workshop can also help the designer to establish trust and rapport with the participants, and to gain their buy-in and feedback for the proposed solution12.
Reference: Salesforce Adoption Strategies | Salesforce Trailhead, 6 Guiding Principles to Maximize Your Salesforce Adoption | Salesforce Admins
Cloud Kicks (CK) is building a new community portal using Experience Cloud. CK’s Designer is asked to provide examples of out-of-box functionality that will make for great customer enagement.
In which three Ways Could CK’s customers engage? Choose 3 answers
- A . Endorsement of skills and expertise
- B . Customize page layouts
- C . Choose personalized branding
- D . Join affinity groups
- E . Recognize peers with badges
A,D E
Explanation:
CK’s customers can engage in the following three ways using the out-of-box functionality of Experience Cloud:
Endorsement of skills and expertise: Customers can endorse each other’s skills and expertise on their profiles, which helps to build trust and credibility within the community.
Join affinity groups: Customers can join groups based on their interests, preferences, or needs, which allows them to connect with like-minded people and share relevant information.
Recognize peers with badges: Customers can recognize each other’s contributions and achievements by awarding badges, which helps to motivate and appreciate the community members.
Reference:
: Endorse Skills and Expertise
: Create and Manage Groups
: Award Badges to Recognize Members