Plat-UX-101 Salesforce Certified Platform User Experience Designer Free Practice Exam Questions (2026 Updated)

The correct answer is A. Quantitative, as explicitly stated in the uploaded study guide.

The defining requirement is to determine whether a released feature was successful and to track usability over time. That calls for measurements that can be collected repeatedly and compared across periods, which is why the study guide selects a quantitative methodology.

Quantitative research produces numerical evidence that can be monitored longitudinally. Depending on the study design, this can include measures such as completion rates, error rates, engagement, usage frequency, time-related measures, or other defined UX indicators.

Option B, Qualitative research, is better suited to questions about why users behave in a particular way, what they think about an experience, or what problems they encounter. It can explain underlying causes but is less directly suited to tracking a numerical trend over time.

Option C, Inductive, describes a reasoning approach rather than the research methodology selected by the study guide for ongoing success measurement.

The important UX distinction is between understanding experiences deeply and measuring their performance systematically. When the objective is longitudinal tracking and evidence of success, the guide points to quantitative research.

Study Guide reference/topics: Quantitative research, usability metrics, longitudinal measurement, feature success, Testing.

==================================

The correct answer is A. Heuristic Evaluation, as specified in the study guide. A heuristic evaluation is appropriate when an existing interface is known to have usability problems, but the specific problems have not yet been systematically identified. The UX Designer evaluates the interface against recognized usability principles or heuristics and documents violations, severity, and improvement opportunities. This gives the team a structured assessment of the current experience before committing to redesign solutions.

The key phrase in the scenario is that Cloud Kicks “is unsure about what should be done.” Creating a low-fidelity prototype at this stage would prematurely move into solution design without first diagnosing the existing interface. A design template likewise determines presentation structure but does not explain why the current experience is ineffective.

This aligns with the broader Salesforce UX research principle of understanding the problem before building the solution. Salesforce emphasizes that UX work should investigate the existing experience, user goals, pain points, and underlying usability problems instead of assuming what users require. A heuristic evaluation therefore creates an evidence-based baseline from which redesign decisions can be prioritized and subsequently validated through user research and usability testing.

Study Guide reference/topics: Heuristic Evaluation, usability principles, current-state assessment, UX Fundamentals, interface evaluation.

==================================

The correct answer is B. Set field-level error message to display on the page. The study guide presents this scenario and identifies B as the answer. The validation rule already determines whether the phone number satisfies the required formatting and length conditions. From a UX perspective, the next objective is to communicate the validation failure at the location where the user must correct it. A field-level error message places the feedback adjacent to the phone field, reducing the user's effort to determine what went wrong and where corrective action is required.

Option A, In-App Guidance, is better suited to onboarding, contextual instruction, feature adoption, or process coaching. It is unnecessarily indirect for a deterministic input-validation error.

Option C, making the field required, only ensures that some value is entered. A required-field setting does not validate whether the phone number contains the correct number of digits or follows the required formatting pattern.

The UX principle being tested is effective error prevention and recovery. When a user enters invalid information, the interface should provide specific, contextual, and actionable feedback instead of forcing the user to search for the affected field.

Study Guide reference/topics: Validation Rules, field-level errors, error prevention, form usability, Declarative Design.

==================================

The distinguishing advantage of a moderated usability study is the researcher's ability to interact with participants and investigate observations in real time. Therefore, A is correct, which matches the uploaded study guide answer. During a moderated session, the researcher observes a participant completing defined tasks while remaining available to ask neutral follow-up questions. For example, if the participant hesitates, misunderstands a label, or abandons a workflow, the moderator can investigate the underlying reason without simply relying on analytics or a post-session questionnaire. This enables collection of richer qualitative evidence regarding the participant's reasoning and mental model. Options B and C describe typical advantages of unmoderated research. Because no researcher needs to attend each session, participants can usually complete studies asynchronously from different locations. That model generally scales more easily and can reduce both cost and researcher time. The tradeoff is depth versus scalability. Moderated testing provides deeper contextual information and allows probing, whereas unmoderated testing provides broader reach and scheduling flexibility. Because the scenario specifically asks what would justify choosing the moderated approach, the capability to ask follow-up questions when usability issues appear is the decisive criterion.

Study Guide reference/topics: Moderated testing, unmoderated testing, qualitative research, follow-up questioning, usability study design.

==================================

The uploaded study guide identifies A. Marketing Cloud Personalization as the correct Salesforce capability for boosting B2C website engagement.

The requirement is specifically to improve business-to-consumer engagement on the website. Within the study guide's framing, Marketing Cloud Personalization is the capability aligned to tailoring digital experiences based on customer context and behavior.

Personalization can make an experience more relevant by changing which content, recommendations, or interactions are presented according to what is known about the user or their current context. Greater relevance can reduce the amount of irrelevant material a consumer must navigate and can increase meaningful engagement with the site.

Option B, Experience Cloud, is used for building external digital experiences and communities, but the question specifically asks which capability should boost B2C engagement through personalization.

Option C, Marketing Cloud Account Engagement, is not the answer selected for this B2C website scenario.

The UX distinction is between merely providing an external site and adapting that site's experience to the consumer. In the answer key, Personalization is the Salesforce capability that most directly addresses this objective.

Study Guide reference/topics: Marketing Cloud Personalization, B2C engagement, personalized experiences, website UX, Declarative Design.

==================================

The uploaded study guide identifies C. There are different writing directions (right to left vs. left to right) and layouts need to be adjusted accordingly as the correct internationalization consideration.

The site will be used across twelve countries, so the UX Designer must plan beyond simple text translation. Different languages can follow different writing directions, and that affects the structure and flow of the entire interface.

A right-to-left language may require layout adjustments to navigation, alignment, component sequencing, and the general reading flow so that the experience remains natural for the intended audience.

Option A is problematic because a country and a language are not equivalent concepts. A country can contain multiple languages, and the same language can be used across multiple countries. The study guide therefore does not select flags as the ideal language-switching mechanism.

Option B suggests that users in different countries inherently perceive color contrast differently. That is not the internationalization consideration keyed by the guide.

The broader HCD lesson is that internationalization must account for the structural characteristics of language and culture, not simply replace words. Layout direction is therefore a fundamental design requirement when supporting both left-to-right and right-to-left writing systems.

Study Guide reference/topics: Internationalization, right-to-left layouts, Experience Builder, global UX, Human-Centered Design.

==================================

The correct answer is B. Design Tokens, exactly as identified in the uploaded study guide. Design tokens are named entities that represent design decisions such as colors, spacing, typography, sizing, borders, and other visual properties. Instead of hard-coding a value such as a hexadecimal color or a fixed pixel spacing repeatedly throughout an application, designers and developers reference a standardized token. This produces two major UX and implementation advantages: consistency and scalability. If the design system later changes a brand color or spacing rule, the underlying token can be updated centrally instead of requiring manual changes throughout every component. Option A, Utility Classes, applies predefined styling behaviors to markup, but it does not represent the underlying system of named design attributes described in the question. Option C, Design Patterns, describes reusable approaches for solving recurring interface or interaction problems; patterns are not the named values used to represent foundational design properties. For Salesforce UX work, design tokens support the broader SLDS goal of maintaining visual consistency across components and experiences. They also reduce implementation drift between what designers specify and what developers build. The key examination distinction is: tokens represent reusable design values; patterns represent reusable design solutions.

Study Guide reference/topics: Design Tokens, SLDS, scalability, consistency, reusable design attributes.

==================================

The study guide identifies A. Account and Contact as the correct pair of standard Salesforce objects.

The scenario requires Salesforce to represent the people shopping for homes and the broader customer relationship that brokers need to manage. The study-guide answer uses Account and Contact as the foundational customer data model.

A Contact represents the individual person with whom the real estate company interacts. The Account provides the associated customer relationship record. Together, these two standard objects form the structure selected by the guide for tracking home buyers.

Option B introduces Case, which represents a service or support matter. Although a customer could eventually create a service issue, that is not the primary relationship described in the scenario.

Option C introduces Opportunity, which represents a potential sales transaction. An opportunity may become relevant within a real-estate sales process, but the question asks which objects should be used to represent and track the home buyers themselves.

The data-modeling principle being tested is that UX design in Salesforce often depends on correctly mapping real-world people and relationships into standard Salesforce objects before determining pages, components, or workflows.

Study Guide reference/topics: Account, Contact, Salesforce standard objects, customer data modeling, Declarative Design.

==================================

The correct answer is C. T-shirt Sizing, matching the answer contained in the UX Designer study guide. T-shirt sizing is a relative estimation technique commonly used during Agile planning when a team needs an approximate understanding of the effort, complexity, or scope associated with backlog items. Instead of attempting premature precision with hours or exact implementation durations, items are classified into categories such as XS, S, M, L, or XL. These relative sizes allow team members to compare work items and identify those requiring significantly greater effort.

That makes the technique particularly appropriate to the wording “roughly estimate the work required.” At sprint-planning time, the UX Designer may participate with developers, product owners, and other stakeholders in sizing work based on design complexity, research requirements, dependencies, implementation considerations, and validation effort.

A Prioritization Matrix serves a different purpose: it evaluates items according to criteria such as value and effort to determine priority rather than simply estimating size. “Sprint Backlogging” is not the estimation method being tested; the sprint backlog represents selected work rather than a relative sizing technique.

Therefore, T-shirt sizing provides a lightweight, collaborative method for estimating work before more detailed planning occurs.

Study Guide reference/topics: Agile ceremonies, sprint planning, relative estimation, T-shirt sizing, UX Fundamentals.

==================================