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) isgoing to conduct some interviews surveys with users to better understand their
Purchasing habits. CK’s UX Designer wants to get the most accurate view of customers’ purchasing behaviors using these research methods.
Which two response biases should the designer be aware of when interviewing or surveying users? Choose 2 answers
- A . Social Desirability Bias
- B . Randimized Bias
- C . Objectivity Bias
- D . Recency Bias
A,D
Explanation:
When interviewing or surveying users, the UX designer should be aware of the following response biases that can affect the accuracy of the data collected:
Social desirability bias: This is the tendency of respondents to answer questions in a way that they think will make them look good or conform to social norms and expectations. For example, when asked about their purchasing habits, respondents may underreport their spending on luxury items or impulse buys, or overreport their spending on charitable causes or environmentally friendly products. Social desirability bias can be reduced by ensuring anonymity and confidentiality, using indirect or less sensitive questions, or using implicit measures12.
Recency bias: This is the tendency of respondents to recall and emphasize the most recent events or experiences, rather than the ones that occurred earlier or more frequently. For example, when asked about their purchasing habits, respondents may base their answers on their last purchase or the last month, rather than their average or typical behavior over a longer period of time. Recency bias can be reduced by using specific and clear time frames, using multiple sources of data, or using longitudinal methods34.
Reference:
: [What Is Response Bias? | Definition & Examples]
: [Types of User Research Bias and How to Avoid It in Your UX Design]
: [Social Desirability Bias: Definition, Examples, and Solutions]
: [Recency Bias: Definition, Examples, and Solutions]
: [Recency Bias in User Research]
: [Social Desirability Bias in Survey Research]
Cloud Kicks (CK) has not migrated to Lightning Experience but wants to leverage the Salesforce Lightning Design System (SLDS) in its custom applications.
Which three solutions should CK’s designers use to deliver applications with a consistent Lightning Experience Look and feel? Choose 3 answers
- A . Local Development Server
- B . iOS Static Library
- C . Lightning Stylesheets for Visualforce
- D . Standard Design Tokens
- E . Heroku
C D E
Explanation:
Cloud Kicks (CK) can use the following three solutions to leverage the Salesforce Lightning Design System (SLDS) in its custom applications, without migrating to Lightning Experience:
Lightning Stylesheets for Visualforce: This solution allows CK to apply the SLDS styles to its existing Visualforce pages, without having to rewrite the markup or use a static resource. By adding the attribute lightning Stylesheets="true" to the <apex:page> tag, CK can automatically transform the standard Visualforce components into their SLDS equivalents, and give the pages a consistent Lightning Experience look and feel12.
Standard Design Tokens: This solution allows CK to use the SLDS design tokens, which are predefined variables that store the visual design attributes of the SLDS, such as colors, fonts, sizes, and spacing. By using the design tokens, CK can ensure that its custom applications follow the SLDS guidelines and remain consistent with the Lightning Experience theme. CK can access the design tokens through the Lightning Design System Scoping tool, or by downloading them as a static resource3.
Heroku: This solution allows CK to build and deploy its custom applications on Heroku, a cloud platform that supports various languages and frameworks, such as Node.js, Java, or PHP. By using Heroku, CK can leverage the SLDS resources, such as the base components, the tokens, and the design patterns, to create web applications that have a consistent Lightning Experience look and feel. CK can also use the Lightning Out feature to embed Lightning components into its Heroku applications, and use the Lightning Web Components framework to create reusable UI elements.
Reference: [Lightning Stylesheets for Visualforce | Salesforce Trailhead]1 [Lightning Stylesheets for Visualforce | Salesforce Developers]2 [Design Tokens | Lightning Design System]3
[Using Design Tokens | Lightning Aura Components Developer Guide | Salesforce Developers] [Build Apps with Lightning Design System | Salesforce Trailhead] [Lightning Web Components | Salesforce Developers]
Cloud Kicks’ Sales team needs In-App Guidance for key functions and processes so they can maximize their time.
In which way should a UX Designer customize the Salesforce Help Menu to meet this request?
- A . Show a site map of all the content.
- B . Create a docked prompt based on new feature rollouts.
- C . Provide links to external resources, such as training videos or a company dictionary.
A
Explanation:
Confirmation bias is the tendency to seek, interpret, and remember information that confirms one’s preexisting beliefs or hypotheses, while ignoring or discounting information that contradicts them1. Confirmation bias can affect user feedback sessions by influencing how the researcher designs the test, asks the questions, observes the behavior, and analyzes the data of the users. Confirmation bias can lead to inaccurate or incomplete insights, and ultimately to poor design decisions2.
One way to avoid confirmation bias in user feedback sessions is to allow the user to explore the application without specific questions regarding which tasks to perform. This can help the researcher to observe the user’s natural and spontaneous interaction with the application, without imposing any expectations or assumptions on them. This can also help the user to express their honest opinions and feelings about the application, without being influenced by the researcher’s questions or suggestions. This can result in more authentic and unbiased feedback, and more reliable and valid insights3.
Asking open-ended questions staying away from questions regarding feelings is not a good way to avoid confirmation bias in user feedback sessions, because it can limit the depth and richness of the feedback, and miss the opportunity to understand the user’s emotions and motivations. Open-ended questions are questions that allow the user to answer in their own words, rather than choosing from a predefined set of options. Open-ended questions are useful for eliciting more detailed and nuanced feedback, and for exploring the user’s thoughts and feelings about the application. However, asking open-ended questions alone is not enough to prevent confirmation bias, as the researcher may still unconsciously frame the questions in a way that leads the user to confirm their hypotheses, or interpret the answers in a way that supports their beliefs. Asking questions regarding feelings is also important, as it can help the researcher to understand the user’s emotional response to the application, and how it affects their satisfaction, engagement, and loyalty4.
Asking specific questions about known pain points to confirm your hypothesis is a bad way to avoid confirmation bias in user feedback sessions, because it can introduce the researcher’s bias into the feedback process, and influence the user’s perception and behavior. Asking specific questions about known pain points can lead the researcher to focus only on the information that confirms their hypothesis, and ignore or dismiss the information that challenges or contradicts it. It can also lead the user to pay more attention to the pain points that the researcher mentions, and overlook or downplay the other aspects of the application. This can result in skewed and distorted feedback, and misleading and invalid insights5.
Reference: 1: Confirmation bias – Wikipedia 2: How Confirmation Bias can affect user research | by
Caroline Galipeau | UX Collective 3: 11 Types of Cognitive Biases to Avoid in User Research | Maze 4:
How to Ask Good Questions in User Research | by Nick Babich | UX Planet 5: How to Avoid Confirmation Bias in User Research | by Sarah Doody | Medium
How would a UX Designer Differentiate between voice and tone?
- A . Voice reflects the expression and tone is the way one designs.
- B . Voice reflects the character and tone is one’s strength.
- C . Voice reflects the frequency and tone is one’s pitch.
- D . Voice reflects the personality and tone is the way one speaks.
D
Explanation:
Voice and tone are two important aspects of UX writing that affect how users perceive and interact with a product. According to the Salesforce User Experience Designer Exam Guide, voice and tone are defined as follows:
Voice reflects the personality of the brand or product. It is consistent and does not change depending on the context or situation. Voice conveys the values, mission, and identity of the brand or product through the choice of words, phrases, and style of communication.
Tone reflects the way the voice speaks to the users. It is context-specific and can change depending on the user’s mood, goal, and situation. Tone conveys the attitude, emotion, and empathy of the voice through the use of punctuation, grammar, and formatting.
For example, Mailchimp is a brand that has a distinctive voice and tone. Their voice is friendly, humorous, and quirky. Their tone varies depending on the user’s experience, such as congratulating them for a successful campaign, or apologizing for an error. They use a tone map to guide their writers on how to adjust their tone for different scenarios.
Reference:
: [Salesforce User Experience Designer Exam Guide]
: [Voice and Tone | Salesforce Style Guide for Documentation and UX Writing]
: [Voice and Tone | Salesforce Trailhead]
: [UX writing 101: A beginner’s guide to mastering tone of voice]
: [Tone of Voice and User Experience | UX Magazine]
: [Things I learned designing the voice and tone for our company]
: [How to use voice and tone in UX writing]
: [Voice and Tone | Mailchimp Content Style Guide]
Cloud Kicks (CK) has made a commitment to incorporating human-centered design and is now collaborating with its Sales team to redesign some of its key sales processes in Salesforce.
Which conceptual approach would describe CK’s new design solutions?
- A . V2MOM
- B . Agile
- C . Desirable, Feasible, Viable
C
Explanation:
Cloud Kicks’ new design solutions would be described by the conceptual approach of desirable, feasible, and viable. This approach is based on the human-centered design (HCD) methodology, which aims to create solutions that meet the needs, preferences, and expectations of the users or customers, while also being technically possible and economically sustainable. HCD is a creative problem-solving process that starts with identifying the user’s problems and ends with creating solutions that address them. The desirable, feasible, and viable framework helps designers evaluate their solutions according to these three criteria:
Desirable: A solution that people want or need, that solves a real problem for them, and that provides a meaningful and relevant experience.
Feasible: A solution that can be created with new or existing technology, that is within the scope and capabilities of the organization, and that can be tested and validated.
Viable: A solution that fits the organization’s business model, that generates value for the stakeholders, and that is sustainable in the long term.
By applying this framework, Cloud Kicks can ensure that its new design solutions for its sales processes in Salesforce are not only user-friendly, but also technically sound and profitable. This can help Cloud Kicks achieve its business goals, while also delivering more satisfying and delightful customer experiences.
Reference: Explore Human-Centered Design
IDEO’s Desirability, Viability, Feasibility Framework: A Practical Guide
A company provides away for customers to shop for homes and contact real estate agents online. The company’s brokers use some of the Salesforce standard functionality to track home buyers.
Which three standard Salesforce objects should be used in this experience? Choose 3 answers
- A . Property
- B . Lead
- C . Contact
- D . Opportunity
- E . Address
B C D
Explanation:
The three standard Salesforce objects that should be used in this experience are:
Lead: A lead is a person who has shown interest in the company’s products or services, but has not yet been qualified as a potential customer. Leads can be captured from various sources, such as web forms, referrals, events, or marketing campaigns. Leads can store information such as name, email, phone, company, and status. Leads can be converted into accounts, contacts, and opportunities when they are ready to buy.
Contact: A contact is a person who is associated with an account and has a role in a sales process. Contacts can store information such as name, email, phone, title, and address. Contacts can be related to multiple accounts, opportunities, cases, activities, and other objects. Contacts can be used to track the communication and interaction history with the customers.
Opportunity: An opportunity is a sales deal that is in progress or has been closed. Opportunities can store information such as name, amount, stage, probability, close date, and owner. Opportunities can be linked to accounts, contacts, products, price books, quotes, contracts, and other objects. Opportunities can be used to forecast revenue, manage sales pipeline, and track sales performance.
Reference: Standard Objects
Leads and Opportunities
Contacts
Cloud kicks wants to incorporates human-centered design across its organization.
Which two practices should beadopted
- A . Including innovative ideas to showcase technology
- B . observing user behavior
- C . putting oneself in the situation of the end-user
- D . creating requirements based on business leaders priorities
B C
Explanation:
Human-centered design is a process that starts with the people you are designing for and ends with new solutions that are tailor-made to suit their needs. It involves understanding the problem from the perspective of the end-users, empathizing with their needs and preferences, and creating solutions that are desirable, feasible, and viable. To incorporate human-centered design across an organization, two practices that should be adopted are:
Observing user behavior: This involves watching how users interact with a product or service, what they do, say, think, and feel. Observing user behavior can help identify pain points, needs, goals, motivations, and emotions that drive user behavior. It can also reveal insights that users may not be able to articulate or may not be aware of themselves. Observing user behavior can be done through methods such as user interviews, contextual inquiry, usability testing, and analytics.
Putting oneself in the situation of the end-user: This involves imagining or experiencing what the user goes through when using a product or service, and how they perceive and respond to it. Putting oneself in the situation of the end-user can help build empathy, understand the user’s context and environment, and generate ideas that address the user’s needs and expectations. Putting oneself in the situation of the end-user can be done through methods such as personas, scenarios, journey maps, and empathy maps.
Reference:
: [What is Human-Centered Design?]
: [Human-Centered Design: The Definitive Guide]
: [UX Research: What is User Behavior?]
: [Observing the User Experience: A Practitioner’s Guide to User Research]
: [UX Research Methods: Observation]
: [Empathy in Design Thinking]
: [UX Research Methods: Empathy]
Universal Containers (UC) operates worldwide with offices in more than 100 regions in 10 different countries role hierarchy to control data visibility. In the new fiscal year, UC is planned to reorganize the roles and reassign accounts owners.
Which two points should an Architect consider in this situation? Choose 2 answers
- A . Using a temporary parking lot account to improve performance.
- B . Changing complex role hierarchy can cause a high level of sharing recalculation.
- C . Restricting the organization-sharing configurations to private.
- D . Replacing Account records ownerships massively can cause data skew.
B,D
Explanation:
Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce.
An architect should consider the following points in this situation:
Changing complex role hierarchy can cause a high level of sharing recalculation. Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources. Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours1.
Replacing account records ownerships massively can cause data skew. Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities. Therefore, replacing account records ownerships massively should be avoided or minimized23.
Reference:
: [Design Your Data Model Unit | Salesforce Trailhead]
: [Data Skew in Salesforce – Why it Matters | Salesforce Ben]
: [Ownership Data Skew | Designing Record Access for Enterprise Scale | Salesforce Developers]
Sales managers want their team members to help each other close Opportunities. The Opportunity and Account organization-wide defaults are private. To grant Opportunity access to sales reps on the same team, owner ship-based sharing rules were created for each team.
What is the side effect of this approach?
- A . All sales reps will have Read access to Accounts for all Opportunities.
- B . Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
- C . Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
- D . All sales reps will have Read access to all Accounts.
C
Explanation:
When the organization-wide default for Accounts is private, users can only access the accounts they own or are explicitly shared with them. However, when the organization-wide default for Opportunities is private, users can access the opportunities they own, are explicitly shared with them, or are associated with accounts they can access1. Therefore, when ownership-based sharing rules are created for each team to grant access to opportunities owned by their team members, the sales reps on the same team will also have Read access to the accounts for those opportunities. This is because the sharing rules for opportunities automatically grant access to the parent accounts2. However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities3. The sales reps will also not have access to all accounts or all opportunities, only those that are owned by their team members or themselves.
Reference: Sharing Records Owned by High-Volume Portal Users | Salesforce Security Guide, Sharing Rules | Salesforce Security Guide, Create Owner-Based Sharing Rules | Salesforce Security Guide
Cloud Kicks wants its Discovery team to help explain the relationships between process steps and business teams.
Which types of process map should they produce?
- A . SIPOC Map
- B . High-Level Process Map
- C . Cross-Functional Flowchart
- D . Value Stream Map
C
Explanation:
: A cross-functional flowchart is a type of process map that shows the relationships between process steps and business teams. A cross-functional flowchart uses horizontal or vertical swimlanes to group the process steps by the roles or departments that are responsible for them. A cross-functional flowchart can help Cloud Kicks’ Discovery team to explain how different teams collaborate and communicate in the process, as well as identify any gaps, overlaps, or inefficiencies in the process. A cross-functional flowchart can also show the inputs, outputs, and decisions at each step, and the flow of information and materials across the swimlanes12.
Reference: Cross-Functional Flowchart
Create a Cross-Functional Flowchart