Salesforce Certified Platform User Experience Designer (Plat-UX-101) Exam Topics and Questions
These Salesforce Certified Platform User Experience Designer (Plat-UX-101) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Salesforce Certified Platform User Experience Designer (Plat-UX-101) sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Platform User Experience Designer certification exam.
Let's Practice Free Salesforce Certified Platform User Experience Designer (Plat-UX-101) Questions Aligned with Official Exam Topics
Discovery sets the foundation for everything else on this exam. The domain is about knowing which research lever to pull before a single screen is designed, and about reading a business scenario well enough to map it to the right Salesforce UX approach. Where candidates lose ground here is confusing a research method with a design method, or misreading which Salesforce persona owns a given workflow. Get the personas and the research toolkit straight early. β Research methods and requirements...
Discovery sets the foundation for everything else on this exam. The domain is about knowing which research lever to pull before a single screen is designed, and about reading a business scenario well enough to map it to the right Salesforce UX approach. Where candidates lose ground here is confusing a research method with a design method, or misreading which Salesforce persona owns a given workflow. Get the personas and the research toolkit straight early.
β Research methods and requirements gathering
When the exam gives you a set of business requirements and asks what to do first, it is testing whether you can distinguish between research methods that reveal what users need versus methods that validate a design that already exists. Contextual inquiry, surveys, interviews, and observational studies each serve a different moment in the design process. Knowing which one fits a scenario where you have no baseline data is different from knowing which one fits a scenario where a prototype is already in users' hands.
Requirements gathering on this exam is tied to planning: given a current user experience, you need to identify gaps, map pain points, and propose a strategy. The trap is treating requirements gathering as a documentation exercise rather than a diagnostic one. The exam rewards candidates who understand that the output of a requirements session should directly shape design decisions, not just produce a list of features the client wants.
β Salesforce personas and platform value
Salesforce defines a set of UX personas, and the exam expects you to know which processes each one normally handles. This is not about memorising job titles. It is about understanding that different personas interact with the platform at different levels of complexity, and that a design choice appropriate for one persona can create friction for another.
The second angle here is understanding where Salesforce adds genuine value to a user experience in context. A scenario might describe a sales team juggling disconnected tools, and you need to identify which Salesforce capabilities address the specific friction described, not just list platform features in general. The exam is looking for targeted reasoning: this scenario has this problem, and this Salesforce capability addresses it for this reason. Vague answers about 'improving productivity' do not score.
How Discovery: is tested
At 13% of the exam, Discovery produces a meaningful share of items, and almost all of them are scenario-based. You will be given a situation, a user context, or a business constraint, and asked to choose a research method or describe a planning approach. The items reward precision: research methods are not interchangeable, and the exam is built to catch candidates who treat them as roughly equivalent.
The most common trap is selecting a method that sounds plausible for the domain rather than the one that fits the specific moment in the design process the scenario describes. Read the scenario for timing clues. Is a design already in place? Is this the very beginning of a project? Is there an existing user experience being evaluated? Those details change the answer.
Persona questions test whether you know the difference between what a persona does and what a persona needs. Candidates who have only a surface-level understanding of Salesforce personas tend to answer based on job title logic rather than platform behaviour, and that costs marks.
The ITExamsTopics practice test for this exam covers all six topics, including Discovery. Running through a bank of scenario-based items lets you see which research and persona scenarios trip you up before you sit the real exam, so you can focus your review where it counts.
The question below tests your ability to match a research method to a specific design scenario. Work through it before checking where you land.
Cloud Kicks has identified that users are getting anxious over a multiple-step custom Screen Flow with no way of visualizing its completeness.
What should be done to improve the user experience?
Where Discovery is about finding the right problem, UX Fundamentals is about knowing the right design response. At 16%, this is one of the heavier topics on the exam, and it pulls in four distinct areas: method selection, branding impact, accessibility and engagement principles, and mobile design. The breadth is the challenge. Candidates who are strong on visual design principles sometimes underestimate how much the mobile and accessibility angles are tested here. β Choosing a UX method and applying design...
Where Discovery is about finding the right problem, UX Fundamentals is about knowing the right design response. At 16%, this is one of the heavier topics on the exam, and it pulls in four distinct areas: method selection, branding impact, accessibility and engagement principles, and mobile design. The breadth is the challenge. Candidates who are strong on visual design principles sometimes underestimate how much the mobile and accessibility angles are tested here.
β Choosing a UX method and applying design principles
The exam distinguishes between UX methods: wireframing, journey mapping, card sorting, prototyping, and others each serve a specific design purpose. When a scenario asks which method to use, the answer depends on what stage of design you are in and what decision you are trying to make. Candidates who treat these methods as roughly equivalent will pick plausible-sounding options that do not fit the scenario's constraints.
Design principles for accessibility and engagement are tested at the application level, not the definition level. Knowing what contrast ratio means is less useful than knowing what a designer should do when a client's brand palette fails accessibility thresholds. The exam rewards the practical move, not the textbook term. Engagement principles such as progressive disclosure, visual hierarchy, and feedback loops are tested through scenarios where you have to identify which principle is being violated or which one would fix a described problem.
β Branding, styling, and mobile design
Corporate branding and styling questions test whether you understand the constraints that branding places on design decisions. A client's brand guidelines are not optional inputs; they shape what is and is not a valid design choice. The exam will present scenarios where branding requirements and UX best practices appear to conflict, and you need to know how to navigate that tension without abandoning either.
Mobile UX design fundamentals cover the specific ways that designing for mobile differs from designing for desktop. Touch targets, screen real estate, thumb zones, and the behaviour of users in mobile contexts are all fair territory. The trap on mobile questions is applying desktop-first thinking to a mobile scenario. The exam is looking for candidates who understand that mobile is a distinct context with its own constraints, not simply a smaller version of the desktop experience. Responsive design logic and Salesforce's mobile-first guidance are both relevant here.
How UX Fundamentals: is tested
At 16%, this topic generates a significant number of items, and the range of sub-topics means you cannot afford a weak area within it. Items tend to be scenario-based and ask you to apply a principle or select a method, not define one.
Accessibility questions are a known difficulty. Candidates often know the principle but apply it incorrectly when a scenario introduces a constraint, such as a client insisting on a colour scheme that creates contrast problems. The exam rewards the response that resolves the tension correctly, not the one that simply restates the accessibility rule.
Mobile items catch candidates who default to desktop UX reasoning. Watch for scenario details that specify a mobile context: those details are there to change the answer, and ignoring them is where marks are lost.
Branding items reward understanding that brand constraints are real inputs to design decisions. The strongest responses treat branding guidance as a design parameter, not an obstacle to work around.
With UX Fundamentals spanning four distinct sub-areas, a timed practice test is one of the better ways to find out which of the four is actually your weak spot, rather than assuming you have the whole topic covered.
The question below sits squarely in UX Fundamentals. Read the scenario carefully before you select your answer.
A UX Designer wants to ensurenew Salesforce users are given the appropriate onboarding experience.
Which two on-App Guidance customizations should be used?
Human-Centered Design asks a more focused question than the broader UX Fundamentals topic: when you are building a Salesforce solution for a real customer, how do you keep the user's perspective at the centre of every decision, and what does inclusive design require of you? At 12%, the topic is lean in sub-topic count but not in depth. The exam expects you to apply HCD thinking to concrete scenarios, not recite its definition. How Human-Centered Design: is tested With only...
Human-Centered Design asks a more focused question than the broader UX Fundamentals topic: when you are building a Salesforce solution for a real customer, how do you keep the user's perspective at the centre of every decision, and what does inclusive design require of you? At 12%, the topic is lean in sub-topic count but not in depth. The exam expects you to apply HCD thinking to concrete scenarios, not recite its definition.
How Human-Centered Design: is tested
With only two sub-topics, this topic's items concentrate on application. You will not be asked to define human-centered design. You will be given a customer scenario and asked to identify the design move that best keeps users at the centre of the solution, or to explain why inclusive design considerations change a specific decision.
Inclusive design questions are where candidates most often lose marks. Inclusive design on this exam is broader than accessibility compliance. It covers designing for varied cognitive loads, language differences, and the full range of users who will interact with a solution, including those who were not the primary persona in the discovery phase.
Items reward candidates who treat HCD as a constraint that shapes decisions throughout the design process, not a phase that happens at the beginning and then ends. Scenarios often place HCD principles in tension with a client's preference or a time constraint, and the exam is looking for the response that correctly prioritises the user's needs within those real-world pressures.
Because Human-Centered Design items are scenario-heavy, seeing a range of different customer situations in the ITExamsTopics question bank builds the pattern recognition you need to apply HCD principles quickly under exam conditions.
The question below presents a customer scenario that calls for human-centered design reasoning. Work out your answer before moving on.
Declarative Design is the largest topic on this exam at 27%, and its weight reflects how central platform configuration is to the Salesforce UX Designer role. This is where abstract design thinking meets the actual Salesforce product. You need to know which declarative tools do what, when to use them, and what effect each one has on the user's experience. Candidates who treat this as a configuration topic rather than a design topic will answer from the wrong frame of...
Declarative Design is the largest topic on this exam at 27%, and its weight reflects how central platform configuration is to the Salesforce UX Designer role. This is where abstract design thinking meets the actual Salesforce product. You need to know which declarative tools do what, when to use them, and what effect each one has on the user's experience. Candidates who treat this as a configuration topic rather than a design topic will answer from the wrong frame of reference.
β Core objects and their effect on user experience
Salesforce's core objects, standard and custom, are not neutral containers. The way an object is structured, related to other objects, and surfaced to users directly shapes what the user can and cannot do efficiently. The exam tests whether you understand that object design decisions are UX decisions. A scenario might describe a user workflow that is slow or confusing, and the answer lies in how the underlying objects are configured, not in adding a new component on top of a broken data model.
Knowing when to use a standard object versus when to customise it, or when to create a custom object, is tested through scenarios that describe specific business needs. The trap is defaulting to customisation when a standard object already serves the need, or assuming a standard object is always sufficient when the scenario's requirements genuinely exceed its defaults.
β Information presentation, hierarchy, and architecture
Declarative features that improve how information is presented and organised include page layouts, record types, list views, related lists, and Lightning App Builder configurations, among others. The exam tests your ability to match a specific presentation problem to the right declarative tool.
Information hierarchy is a design concept here, not just a configuration one. When a scenario describes users struggling to find what they need on a record page, the answer is not simply 'add more fields.' It requires understanding which declarative features control what appears at the top, what is grouped together, and what is hidden until needed. Candidates who know the tools but have not thought about them in terms of visual hierarchy and cognitive load will tend to over-engineer solutions when simpler declarative options would serve the user better.
β Guided processes, global configuration, and onboarding
Declarative features that guide users through a series of steps, such as flows, path configurations, and quick actions, are tested through efficiency scenarios. The exam asks you to identify which feature best reduces friction across a multi-step process, and the answer depends on the specific type of task and user context described.
Global Salesforce configuration options, including app settings, navigation menus, and home page components, are tested for their effect on user flow. The distinction between what is configured globally versus what is configured at the record or page level is an important one, and the exam will test whether you know which lever to pull for a given scenario.
Onboarding, support, and learning tools within Salesforce, such as in-app guidance and help text, are tested for appropriateness: which tool fits which user moment, and when does one option serve users better than another.
β Applying branding through declarative tools
Branding within the Salesforce platform is applied declaratively, and the exam tests whether you know which tools control which aspects of the visual experience. Themes, colours, logos, and custom branding options in Experience Cloud and Lightning are all fair territory. The key distinction is between what can be changed declaratively and what requires custom development, because the exam is specifically about declarative design.
Scenarios in this group often describe a client's branding requirements and ask you to identify the declarative approach that meets them. The trap is either reaching for a development solution when a declarative one exists, or applying a branding tool in the wrong context, such as confusing internal app branding options with Experience Cloud branding controls. Knowing the scope and limits of each tool is what separates a confident answer from a guess.
How Declarative Design: is tested
At 27%, Declarative Design will determine your result more than any other topic. Items are almost entirely scenario-based, and they test selection and reasoning, not recall. You will not be asked to name a feature. You will be asked which feature solves a described problem, and why one option is better than another.
The most common error is feature-matching without reading the scenario's constraints. A candidate who knows that flows guide users through steps might select a flow for every multi-step scenario, missing the cases where a path configuration or a quick action is the better fit for the context described.
Object-related items catch candidates who think about objects as data structures rather than user-facing tools. Read those scenarios for the user's experience, not just the data requirement.
Branding items reward knowing the boundaries between declarative tools. Candidates who are fuzzy on which branding options apply to which Salesforce context tend to select plausible but wrong tools.
Declarative Design's 27% weight means gaps here are expensive. Working through a full question bank lets you measure your coverage across all six sub-areas and find the specific declarative tools you are less confident on before exam day.
The scenario in the question below requires you to select the right declarative tool for a specific user experience problem. Take your time with it.
After the design work covered in Declarative Design, Testing is where you validate that the work actually serves users. At 11%, this topic is smaller than the design topics, but it is not forgiving. The exam expects you to know how to plan a testing approach for a given scenario, choose the right testing technique, and manage what happens when testing reveals that changes are needed. Candidates who conflate testing with quality assurance in a technical sense will be answering...
After the design work covered in Declarative Design, Testing is where you validate that the work actually serves users. At 11%, this topic is smaller than the design topics, but it is not forgiving. The exam expects you to know how to plan a testing approach for a given scenario, choose the right testing technique, and manage what happens when testing reveals that changes are needed. Candidates who conflate testing with quality assurance in a technical sense will be answering from the wrong frame.
How Testing: is tested
Testing items are scenario-driven. You will be given a design situation, a user context, or a point in the design process, and asked to identify the appropriate validation method or describe how to manage a design change that testing has surfaced.
The distinction between testing techniques matters here. Usability testing, A/B testing, prototype walkthroughs, and heuristic evaluations each serve a different purpose and are appropriate at different points. Items reward candidates who match the technique to the moment in the design process, not just the type of design problem.
Managing design changes is the sub-topic where candidates most often underestimate what the exam expects. It is not enough to know that changes should be documented. The exam rewards understanding of how to evaluate the scope of a change, communicate it to stakeholders, and decide whether it requires another round of user validation.
Candidates who treat testing as a final phase rather than an iterative one tend to select responses that do not account for the feedback loops the exam expects you to build into a design process.
Testing is a topic where reading about techniques feels sufficient until you try to apply them under time pressure. The ITExamsTopics practice test puts you in timed conditions so you can check whether your testing knowledge holds up when the clock is running.
The question below places you at a specific point in the design process and asks you to make a testing decision. Read the scenario details carefully.
SLDS is the topic most specific to the Salesforce platform's implementation layer. At 21%, it carries serious weight, and it sits at the intersection of design and technical execution. Where the earlier topics asked you to think like a designer, SLDS asks you to know the platform's design system well enough to use it correctly: when to apply it out of the box, when to extend it, and what it is actually for. How Salesforce Lightning Design System (SLDS): is...
SLDS is the topic most specific to the Salesforce platform's implementation layer. At 21%, it carries serious weight, and it sits at the intersection of design and technical execution. Where the earlier topics asked you to think like a designer, SLDS asks you to know the platform's design system well enough to use it correctly: when to apply it out of the box, when to extend it, and what it is actually for.
How Salesforce Lightning Design System (SLDS): is tested
At 21%, SLDS items appear frequently, and they test three related but distinct skills. The first is understanding what SLDS is and what problem it solves: it provides a shared visual and interaction language for Lightning Experience, and knowing its purpose shapes how you answer questions about when to use it.
The second skill is recognising out-of-the-box configurations that are already consistent with Lightning Experience. Items in this area reward candidates who know what is available without customisation, because reaching for custom solutions when standard SLDS components already exist is a common and costly mistake.
The third skill is knowing how to use SLDS to build or extend component functionality. These items are the most demanding. They test whether you understand the design token system, component variants, and the rules for extending SLDS without breaking visual consistency.
The trap across all three areas is treating SLDS as a style guide rather than a design system with specific implementation rules. Candidates who know what SLDS looks like but not how it works tend to select answers that are visually plausible but technically incorrect for the scenario.
SLDS questions cover a range from conceptual purpose to specific component usage. Seeing the full variety of item styles in the ITExamsTopics question bank before the exam means the format of these questions will not slow you down on the day.
The question below focuses on a specific SLDS scenario. Decide how you would approach it, then check your reasoning.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Salesforce Certified Platform User Experience Designer (Plat-UX-101) Exam Questions π