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’ website serves two primary authenticated audiences: suppliers and installers. Their overall experience is the same, but the presentations for the audience should have a unique look and feel. Experience Builder will used to create a unique for each audience that includes colors, image, and typography.
Which out-of-the-box design approach should be recommended?
- A . Use custom CSS to override the default template and Theme panel styles.
- B . Create branding sets and assign them to each audience using audience targeting.
- C . Use unique sites under digital experiences for each audience and tailor the look and feel of each.
- D . Create a custom theme for each audience and apply it to the same site.
B
Explanation:
To create a unique experience for each audience that includes colors, images, and typography, the
recommended out-of-the-box design approach is to use branding sets and assign them to each audience using audience targeting. Branding sets are collections of branding attributes, such as logos, fonts, colors, and images, that can be applied to a site or a page to customize its look and feel. Audience targeting is a feature that allows the designer to deliver different content and experiences to different groups of users based on criteria such as profile, location, or behavior. By creating branding sets and assigning them to each audience using audience targeting, the designer can easily create a unique and consistent experience for each audience without creating separate sites or custom themes.
Reference:
: Branding Sets | Salesforce Help: Audience Targeting | Salesforce Help: UX Designer Certification Prep: Designing with Experience Builder | Trailhead
The best approach for Cloud Kicks to create a unique look and feel for each audience is to create branding sets and assign them to each audience using audience targeting. With this approach, the same website can be used for both audiences, while the look and feel of each page can be tailored to each audience.
Branding sets allow you to create unique designs and apply them to specific audiences. You can create unique colors, images, and typography for each audience and then target them to the appropriate audiences using the audience targeting feature. This will ensure that each audience has a unique look and feel that meets their needs.
Reference: [1] https://help.salesforce.com/articleView?id=siteforce_editing_audience_targeting.htm&type=5 [2] https://help.salesforce.com/articleView?id=siteforce_branding_sets.htm&type=5 [3] https://help.s alesforce.com/articleView?id=siteforce_creating_branding_sets.htm&type=5
Cloud Kicks wants to create an external facing site where users can:
* Manage and submit cases via the web.
* Browse and search Knowledge Base articles.
* Contact Support via lice chat.
Which cloud should be used to design an appropriate solution for CK’s users?
- A . Experience Cloud
- B . Sales Cloud
- C . Marketing Cloud
- D . Service Cloud
A
Explanation:
Experience Cloud is the best cloud to design an appropriate solution for Cloud Kicks’ users. Experience Cloud allows the business to create an external facing site where users can manage and submit cases via the web, browse and search Knowledge Base articles, and contact Support via live chat. Experience Cloud also provides branding options, personalization features, and collaboration tools to enhance the user experience and engagement. Experience Cloud integrates with Service Cloud, which is the cloud that provides the case management, knowledge base, and live chat functionalities. Therefore, Experience Cloud is the cloud that enables the design of the user interface, while Service Cloud is the cloud that enables the backend service
processes.
Reference: [Experience Cloud Overview] (https://www.getapp.com/operations-management-software/a/salesforce-1-service-cloud/compare/salesforce-community-cloud/), [Service Cloud Overview] (https://titandxp.com/salesforce-experience-cloud-vs-service-cloud/)
Cloud Kicks asks its UX Designer to create a B2B sales portal that can easily integrate customer relationship management.
Which Salesforce solution should be used?
- A . Commerce Cloud
- B . Experience Cloud
- C . Sales Cloud
B
Explanation:
Experience Cloud is the Salesforce solution that enables businesses to create engaging and personalized digital experiences for their customers, partners, and employees. Experience Cloud can easily integrate customer relationship management (CRM) data from Sales Cloud, Service Cloud, and other Salesforce products to provide a seamless and consistent experience across different touchpoints. Experience Cloud can also leverage the power of Commerce Cloud to create B2B sales portals that allow buyers to browse, order, and pay for products online. Experience Cloud offers various templates, components, and tools to design and build customized and branded B2B sales portals that meet the needs and expectations of the target audience.
Reference: Experience Cloud Overview, Learn About B2B Commerce, Salesforce B2B Commerce Basics
A UX Designerhas created a new form for a call center that takes special delivery information from its customers.
The designer wants to ensure the call center staff finds the form easy and intuitive to use.
Which kind of testing should be conducted to validate this?
- A . Usability Testing
- B . Survery
- C . Focus Groups
- D . Qualitative
A
Explanation:
Usability testing is a type of testing that evaluates how easy and intuitive a product or service is to use by observing real users performing specific tasks. Usability testing can help the UX Designer to measure the effectiveness, efficiency, and satisfaction of the new form for the call center staff.
Usability testing can also help to identify any usability issues or areas for improvement in the form design. Usability testing can be conducted in various ways, such as moderated or unmoderated, remote or in-person, qualitative or quantitative, or using various tools and methods12.
Reference: Usability Testing
Usability Testing Methods
Following a human-centered design process approach, Cloud Kicks is preparing a user feedback session for an app that is not performance as anticipated.
In which two ways could confirmation bias be avoided? Choose 2 answers
- A . Interview users about the intended use of the product to support the questionnaire creation.
- B . Obtain user feedback to reinforce known assumptions and support design decisions.
- C . Diversity feedback by ensuring it features as many unique perspective as possible.
- D . Review questions to remove assumptions about issues or problem not supported by quantitative data.
A C
Explanation:
Confirmation bias is the tendency to seek out and prefer information that supports our preexisting beliefs, while ignoring or rejecting information that contradicts them. Confirmation bias can affect the validity and reliability of user feedback, as it can lead to biased questions, selective interpretation, and skewed results. To avoid confirmation bias in user feedback, Cloud Kicks can follow these two strategies:
Interview users about the intended use of the product to support the questionnaire creation. This can help Cloud Kicks to understand the user needs, expectations, and goals, and to design questions that are relevant, clear, and unbiased. By interviewing users, Cloud Kicks can also avoid making assumptions about the user behavior, preferences, and pain points, and instead base their questions on real user data and insights 1.
Diversify feedback by ensuring it features as many unique perspectives as possible. This can help Cloud Kicks to reduce the risk of sampling bias, which occurs when the feedback is collected from a group of users that is not representative of the target population. By diversifying feedback, Cloud Kicks can capture a wider range of user opinions, experiences, and feedback, and avoid overlooking or dismissing important user segments or viewpoints 2.
Reference: [How to Avoid Confirmation Bias in UX Research] (https://www.smashingmagazine.com/2017/10/avoid-bias-ux-feedback/), [How to Avoid Sampling Bias in User Research] (https://bing.com/search?q=confirmation+bias+in+user+feedback)
Financial advisor should be able to access a customer’s record in Sales Cloud and see all potential business opportunities related to each individual customer. The bank does not have any corporate or business customers at this time.
How should a UX Designer suggest the bank represent its customers within its Salesforce instance?
- A . Standard Person Account Object
- B . Standard Lead Object
- C . Standard Opportunity object.
- D . Standard Account object.
A
Explanation:
A standard person account object is the best option for representing the bank’s customers within its Salesforce instance. A person account is a type of account that represents an individual rather than a company. Person accounts are a hybrid of the account and contact objects, combining their characteristics into one. They allow the bank to store information that applies to humans, such as first and last names, email, phone, address, etc. When a person account is created, a contact is automatically created and associated with the account. Person accounts are the Salesforce official model for representing an individual and can be used alongside business accounts for B2B and B2C activities. In Financial Services Cloud, person accounts can be used for a simplified, customizable user experience1. A person account can also have related opportunities, which are potential sales or revenue-generating events. This way, the financial advisor can access a customer’s record and see all potential business opportunities related to each individual customer2.
The other options are not suitable for the bank’s scenario. A standard lead object is a prospect or
potential customer who has expressed interest in the bank’s products or services, but has not yet
qualified as a sales opportunity. A lead can be converted into an account, a contact, and an
opportunity when it is ready to be pursued3. However, the bank does not need to use leads to track
its customers, as they are already existing customers who have accounts with the bank. A standard
opportunity object is a sales or revenue-generating event that is related to an account. An
opportunity can have multiple stages, products, amounts, and probabilities of closing. An
opportunity can also be linked to a campaign, which is a marketing initiative to generate leads or
contacts4. However, the bank cannot use opportunities alone to represent its customers, as they are
not standalone objects, but rather depend on accounts. A standard account object is a company or
organization that the bank does business with. An account can have multiple contacts, which are the
people who work at the account and interact with the bank. An account can also have related
opportunities, cases, activities, and other records5. However, the bank does not have any corporate
or business customers at this time, so using standard accounts would not reflect the nature of its
individual customers.
Reference: Convert Salesforce Business Accounts to Person Accounts, In Financial Services Cloud, Person Accounts can be used for a simplified, customizable user experience.
Person Accounts – Salesforce, Person Accounts Sales Cloud Basics Content Close Select Filters Product Area Feature Impact Edition Developer Edition Enterprise Edition Essentials Edition Professional Edition Unlimited Edition Experience Salesforce Classic Mobile Lightning Experience Done 632 Results Configure Access to Thanks Badges Set Up WDC Configure Thanks in the Chatter Publisher and Salesforce Mobile App… Build a Culture of Recognition with WDC Manage WDC Enable or Disable WDC Settings WDC Editions and Permissions Skills Limitations Skills Customization Recommended WDC Profiles Recommended WDC Permission Sets Enable WDC Features Configure WDC Assign WDC Only User Licenses Assign WDC Licenses Configure WDC Features Assign a WDC Administrator Create a Support Case Considerations for Setting Up WDC Thanks and Skills Features Assign Publisher Layout to Profiles Assign WDC User Feature Licenses Assign WDC Profiles Assign WDC Permission Sets Endorse a Skill Via Record Detail Pages Add a Skill Via Record Detail Pages Remove a Skill Via Record Detail Pages Schedule Reminders to Update Opportunities View a List of the Accounts or Opportunities in Your Territories Things to Know About Enterprise Territory Management Territory Type Priority Optimizing Your Territory Model Continuously Designing Territory Models Territory Model Managing Territories Enterprise Territory Management Concepts Planning and Managing Territories Territory Model State Territory Type Territory Hierarchy Bird’s-Eye View of Planning and Managing Territories Report on Territories with Assigned Users Report on Territories Without Assigned Accounts Run Assignment Rules for a Territory Reporting on Territories Report on Users Not Assigned to Territories Report on Summarizable Account Fields by Territory Enterprise Territory Management Identify Territory Users by Territory Role Territory Run the Opportunity Territory Assignment Filter Preview Territory Assignments for Accounts Report on Accounts Assigned to Territories Manage Territories with Enterprise Territory Management View and Manage Assignment Rules at the Territory Model Level Enterprise Territory Management: What’s Different or Not Available… Show Your Reps Other Users Assigned to Their Leads’ Territories Enable Features for Enterprise Territory Management Maintain Enterprise Territory Management Find Out.
Which Territories an Assignment Rule Applies To Enable Enterprise Territory Management Report on the Accounts and Opportunities in Your Territories Explore Your Company’s Territory Model Identify Users in Territories Assigned to Accounts Enable Filter-Based Opportunity Territory Assignment Identify an Account’s Sales Territories Disable Enterprise Territory Management How Account Assignment Rules Work How Do Permissions for Territories Affect Feature and Data Access? Requirements for Assigning Opportunities to Territories Manually Assigning Opportunities to Territories Manually Delete a Territory Model Create a Territory Model Record Preparing Sales Management for Territory Reporting Setting Up and Managing Territory Assignments Define Default User Access for Territory Records
Account | Object Reference for the Salesforce Platform | Salesforce …, Account | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter ’24 (API version 59.0) Summer ’23 (API version 58.0) Spring ’23 (API version 57.0) Winter ’23 (API version 56.0) Summer ’22 (API version 55.0) Spring ’22 (API version 54.0) Winter ’22 (API version 53.0) Summer ’21 (API version 52.0) Spring ’21 (API version 51.0) Winter ’21 (API version 50.0) Summer ’20 (API version 49.0) Spring ’20 (API version 48.0) Winter ’20 (API version 47.0) Summer ’19 (API version 46.0) Spring ’19 (API version 45.0) Winter ’19 (API version 44.0) Summer ’18 (API version 43.0) Spring ’18 (API version 42.0) Winter ’18 (API version 41.0) Summer ’17 (API version 40.0) Spring ’17 (API version 39.0) Winter ’17 (API version 38.0) Summer ’16 (API version 37.0) Spring ’16 (API version 36.0) Winter ’16 (API version 35.0) Summer ’15 (API version 34.0) Spring ’15 (API version 33.0) Winter ’15 (API version 32.0) Summer ’14 (API version 31.0) Spring ’14 (API version 30.0) j Overview of Salesforce Objects and Fields Reference Associated Objects (Feed, History, OwnerSharingRule, Share, and ChangeEvent Objects) Custom Objects Object Interfaces Standard Objects AcceptedEventRelation Account AccountBrand AccountContactRelation AccountCleanInfo AccountContactRole AccountInsight AccountOwnerSharingRule AccountPartner AccountRelationship AccountRelationshipShareRule AccountShare AccountTag AccountTeamMember AccountTerritoryAssignmentRule AccountTerritoryAssignmentRuleItem AccountTerritorySharingRule AccountUserTerritory2View ActionCadence ActionCadenceRule ActionCadenceRuleCondition ActionCadenceStep ActionCadenceStepTracker ActionCadenceStepVariant ActionCadenceTracker
ActionCdncStpMonthlyMetric ActionLinkGroupTemplate ActionLinkTemplate ActionPlan ActionPlanItem ActionPlanTemplate ActionPlanTemplateItem ActionPlanTemplateItemValue ActionPlanTemplateVersion ActiveFeatureLicenseMetric ActivePermSetLicenseMetric ActiveProfileMetric ActiveScratchOrg ActivityHistory ActivityMetric ActivityUsrConnectionStatus AdAvailabilityDimensions AdAvailabilityJob AdAvailabilityViewConfig AdBuyServerAccount AdCreativeSizeType AdDigitalAvailability AdditionalNumber Address AdLinearAvailability AdOpportunity AdOrderItem AdOrderItemCreativeSizeType AdOrderLineAdTarget AdPageLayoutType AdProductTargetCategory AdQuote AdQuoteLine AdQuoteLineCreativeSizeType AdQuoteLineAdTarget AdServer AdServerAccount AdServerUser AdSpaceCreativeSizeType AdSpaceGroupMember AdSpaceSpecification AdSpecMediaPrintIssue AdTargetCategory AdTargetCategorySegment AgentWork AgentWorkSkill AIApplication AIApplicationConfig AIInsightAction AIInsightFeedback AIInsightReason AIInsightValue AiModelLanguage AIRecordInsight AllowedEmailDomain AlternativePaymentMethod AnalyticsLicensedAsset Announcement ApexClass ApexComponent ApexLog ApexPage ApexPageInfo ApexTestQueueItem ApexTestResult ApexTestResultLimits ApexTestRunResult ApexTestSuite ApexTrigger ApexTypeImplementor AppAnalyticsQueryRequest AppDefinition AppExtension ApplicationFormTemplate AppMenuItem AppointmentAssignmentPolicy AppointmentScheduleAggr
Lead | Object Reference for the Salesforce Platform | Salesforce …, Lead | Object Reference for the Salesforce Platform | Salesforce Developers Object Reference for the Salesforce Platform English Pages Winter ’24 (API version 59.0) Summer ’23 (API version 58.0) Spring ’23 (API version 57.0) Winter ’23 (API version 56.0) Summer ’22 (API version 55.0) Spring ’22 (API version 54.0) Winter ’22 (API version 53.0) Summer ’21 (API version 52.0) Spring ’21 (API version 51.0) Winter ’21 (API version 50.0) Summer ’20 (API version 49.0) Spring ’20 (API version 48.0) Winter ’20 (API version 47.0) Summer ’19 (API version 46.0) Spring ’19 (API version 45.0) Winter ’19 (API version 44.0) Summer ’18 (API version 43.0) Spring ’18 (API version 42.0) Winter ’18 (API version 41.0) Summer ’17 (API version 40.0) Spring ’17 (API version 39.0) Winter ’17 (API version 38.0) Summer ’16 (API version 37.0) Spring ’16 (API version
A UX Design team is doing a review of a new Lightning Web Component (IWC). They are following the Salesforce Lightning Design System (SLDS) block, element, modifier (BEM) naming conventions.
Which class does NOT follow this convention?
- A . .slds-avatar_circle
- B . .slds-box
- C . .slds–size-l-of-2
C
Explanation:
The SLDS BEM naming convention consists of three parts: block, element, and modifier. A block is a standalone component that can be reused across projects, such as a button, a card, or a modal. An element is a part of a block that has no standalone meaning, such as a label, an icon, or a header. A modifier is a flag that changes the appearance or behavior of a block or an element, such as size, color, or state. The modifier is separated from the block or element by two hyphens (C), and can have a value separated by a single hyphen (-), such as .slds-buttonCbrand or .slds-buttonCneutral. The class .sldsCsize-l-of-2 does not follow this convention because it has no block or element name before the modifier. It should be something like .slds-gridCsize-l-of-2 or .slds-colCsize-l-of-2.
Reference: [1]: Salesforce Lightning Design System – Introduction [2]: Salesforce Lightning Design System – Naming Con
Cloud Kicks hired a UX Designer to help improve the design of its Experience Cloud site. The company knows the interface needs updating but is unsure about what should be done.
Which tool should the designer utilize first?
- A . Heuristic Evaluation
- B . Low-Fidelity Prototype
- C . Design Template
A
Explanation:
A heuristic evaluation is a method of inspecting the usability of an interface by comparing it to a set of general principles or heuristics. It can help identify potential problems and areas for improvement in the design. A heuristic evaluation is usually done before creating any prototypes, as it can provide insights and guidance for the design process. A low-fidelity prototype is a rough sketch or mockup of an interface that can be used to test and validate design ideas with users. It is usually created after conducting some research and analysis of the user needs and goals. A design template is a pre-made layout or structure that can be used to create an interface. It can help save time and ensure consistency in the design, but it may not suit the specific needs and preferences of the users or the business. A design template is usually applied after defining the content and functionality of the interface.
Reference: [Heuristic Evaluation]: This is a Trailhead module that explains what a heuristic evaluation is, how to conduct one, and how to use the results to improve the design of an interface.
[Low-Fidelity Prototyping]: This is a Trailhead module that covers the benefits and best practices of creating and testing low-fidelity prototypes with users.
[Design Templates]: This is a Trailhead module that introduces the concept of design templates and how to use them in Experience Cloud.
Cloud Kicks is considering whether it should implement the Standard Salesforce Navigation or use the Console for its Sales team.
What is one requirement that could lead to recommending the Console?
- A . Need for viewing multiple list views at the same time
- B . Ability to toggle between multiple records
- C . Work that is mostly in the field
B
Explanation:
The Console is a tab-based workspace that allows users to access multiple records and related information on a single screen. This can help users who need to switch between different records quickly and easily, without losing context or wasting time. For example, a salesperson who needs to compare different opportunities, check account details, or update contact information can benefit from using the Console. The Standard Salesforce Navigation, on the other hand, only allows users to open one record at a time, which can be limiting for some use cases.
Reference:
: Salesforce Console: Explore the Service Console
A developer is creating a Lightning Web Component (LWC) and wants to make sure the visual experience is consistent with Cloud Kicks’ branding. The developer asks their UX Designer about the Salesforce Lightning Design System (SLDS) styling hooks.
How should the designer describe them?
- A . They use standard CSS properties to directly style HTML elements.
- B . They use standard CSS properties to easily style base and custom components.
- C . They use custom CSS properties to directly style HTML elements.
- D . They use custom CSS properties to easily style base and custom components.
D
Explanation:
Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the —
slds namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example, –slds-c-button-brand-color-background-hover is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the var() function.
Reference: Styling Hooks – Lightning Design System
SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers Cdxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers
The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that “SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel” [1].
[1] https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styling_hooks