Pass the Salesforce Salesforce Designers Plat-UX-101 Questions and answers with CertsForce

The uploaded study guide identifies A. Reducing friction for users in achieving their goals as the correct benefit of inclusive design.

Inclusive design considers a wider range of user needs, abilities, contexts, and potential barriers. When those barriers are addressed, the resulting experience becomes easier for more people to understand and operate. The study guide therefore expresses the benefit in terms of reduced friction.

Option B contradicts the inclusive-design objective because designing exclusively for one user type risks excluding users whose circumstances or abilities differ from the assumed norm.

Option C also misrepresents inclusive design. The objective is not to simplify the experience to a generic lowest common denominator. Rather, the designer should identify barriers and create solutions that allow a broader range of people to participate successfully.

This answer is consistent with the inclusive-design principles earlier in the guide: recognize exclusion, learn from diversity, and solve for one in ways that can extend to many. When exclusion is reduced, users encounter fewer obstacles while trying to complete their intended tasks.

The practical outcome is therefore not only accessibility in a narrow sense, but a smoother and more usable experience across a broader population.

Study Guide reference/topics: Inclusive Design, reducing friction, user goals, exclusion, Human-Centered Design.

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

The correct answer is B. Field-Level Security, as explicitly identified in the study guide. The important constraint is that Cloud Kicks has one standard Order page layout shared by different types of users. The requirement is therefore not to create separate layouts, but to control which fields are visible to internal versus external users.

The study guide selects Field-Level Security because it governs whether particular users can see or interact with specific fields even when the same page layout is shared. This makes it suitable for restricting sensitive or irrelevant information without duplicating the overall record-page structure.

Option A, Audience Targeting, is associated with presenting Experience Cloud or component content to different audiences, but it is not the field-visibility mechanism selected in this study-guide scenario. Option C, Dynamic Forms, can conditionally control field and section presentation on supported record pages, but the answer key specifically identifies Field-Level Security for the shared-layout visibility requirement.

From a UX standpoint, limiting users to the fields that are relevant and permitted for their role reduces unnecessary information exposure and keeps the shared record experience focused while preserving the organization's security model.

Study Guide reference/topics: Field-Level Security, shared page layouts, user-specific visibility, Sales Cloud, Declarative Design.

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

The correct answer is B. Empathy Map. The uploaded UX Designer study guide identifies the Empathy Map as the appropriate tool for synthesizing knowledge about users after personas have already been established.

An empathy map provides a structured way for a design team to consolidate what it knows about a user or persona. It commonly captures what users think, feel, say, and do, helping stakeholders develop a shared understanding of user motivations, concerns, behaviors, and needs. This makes it particularly useful after research findings have been gathered and personas are already available.

Option A, an Executive Summary, can communicate high-level findings to stakeholders, but it is primarily a reporting artifact. It does not organize user-centered observations in the same structured, empathy-oriented format.

Option C, Prioritize Backlog, belongs to planning and delivery. Backlog prioritization helps determine which work should be implemented first, but it does not synthesize user understanding.

The critical distinction is between understanding users and prioritizing solutions. At this stage, Cloud Kicks needs to create organizational alignment around what is known about its users. An Empathy Map supports that objective directly.

Study Guide reference/topics: Empathy Maps, personas, research synthesis, shared user understanding, Discovery.

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

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 uploaded study guide gives B. Tangible as the correct answer. The question wording and capitalization are preserved from the source.

Within the accessibility-oriented terminology used elsewhere in the guide, Robust and Perceivable are recognized accessibility principles. “Tangible” is not presented as part of that principle set, so it is the item that does not belong.

Perceivable concerns ensuring that information and interface content can be presented in ways users can perceive. Earlier material in the same guide links perceivability to providing content in formats that can be transformed or accessed in different ways.

Robust also appears in the guide's WCAG-focused material, where it is listed alongside Understandable and Operable.

Option B, Tangible, therefore differs from the terminology used by the guide for digital-accessibility design requirements.

This item is written very briefly in the source, so its intended distinction is best understood by comparing the terminology against the accessibility principles established elsewhere in the same question bank rather than expanding it into a different framework.

For this supplied study guide, the keyed answer is unambiguously B.

Study Guide reference/topics: Accessibility principles, Robust, Perceivable, UX Fundamentals.

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

The correct answer is B. Replace the current solution with two independent Validation Rules and select 'Field' as the error location. This is the answer provided in the uploaded study guide.

The usability problem is not merely that validation fails; it is that the error appears at the top of the page and requires the user to locate the affected fields manually. By associating each validation rule with the relevant field, the interface can display the error closer to the location where corrective action is required.

Separating the logic into two field-specific validation rules also makes each failure message more precise. Users can immediately identify which field is missing or invalid rather than interpreting a combined top-level error.

Option A adds explanatory help text, but help text is static and does not directly identify the field responsible for a current validation failure.

Option C misuses In-App Guidance. In-App Guidance is intended primarily for onboarding and contextual instruction rather than transactional validation.

The UX principle is that error messages should be specific, contextual, and actionable. Errors should appear as close as reasonably possible to the source of the problem so users can recover efficiently.

Study Guide reference/topics: Validation Rules, field-level errors, error recovery, Salesforce forms, Declarative Design.

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

The correct answer is B. Exhaust the list of available base Lightning components in the Component Library. This is the best practice explicitly selected in the uploaded study guide.

The scenario begins with a proposed custom Lightning component, but the guide indicates that customization should not be the first assumption. Before developing something new, the designer and implementation team should first determine whether an existing base Lightning component already satisfies the requirement.

This approach promotes consistency with the standard Salesforce user experience and avoids unnecessary duplication. Existing components already embody Salesforce interaction and presentation conventions, making them the logical starting point for a Lightning-based solution.

Option A immediately moves toward custom HTML and separately linked styling resources. That bypasses the study guide's preferred sequence of first checking whether established Salesforce functionality already exists.

Option C is too absolute. SLDS blueprints are useful resources for component construction, but the guide does not recommend choosing blueprint markup over existing base Lightning components in every case.

The principle being tested is reuse before customization. Custom development should be justified by a genuine gap in standard functionality, not merely by the existence of a specialized business requirement.

Study Guide reference/topics: Base Lightning Components, Component Library, custom components, SLDS, reuse before customization.

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

The uploaded Master Study Guide identifies C. Utility Classes as the correct SLDS resource for maintaining consistency in alignment, grids, spacing, and typography.

Utility classes provide reusable styling mechanisms that can be applied to interface elements without creating a separate custom CSS solution for every layout or presentation requirement. Within the study-guide framing, they are the appropriate SLDS resource when designers and developers need consistent control over common visual properties.

Option A, Component Blueprints, is used to communicate the structure and presentation pattern of complete Salesforce-style components. Blueprints are important when implementing component patterns, but this question focuses specifically on commonly reused styling concerns such as spacing, alignment, and typography.

Option B, BEM Naming Classes, relates to CSS naming methodology and structure. It is not the resource keyed by the guide for applying the visual utilities described.

The underlying design-system principle is reuse instead of reinvention. Applying standardized utility classes helps different pages and components use common spacing and alignment behavior rather than accumulating inconsistent custom CSS rules.

That consistency makes Salesforce interfaces more predictable visually and easier to maintain.

Study Guide reference/topics: SLDS Utility Classes, alignment, spacing, grids, typography, Salesforce Lightning Design System.

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

The study guide identifies C. Service Design as the correct answer.

The key clue is that the designer wants to move beyond focusing exclusively on an individual user and instead considers a broader network of interactions, connections, and value creation. According to the answer provided by the study guide, this broader design perspective is categorized as Service Design.

The scenario therefore shifts attention away from a single screen or isolated interaction and toward the wider experience created through multiple connected parts of a service.

Option A, User Experience Design, is centered on designing the quality of a person's interaction with a product or experience. Although it remains highly relevant, the question explicitly says the designer wants to go beyond the individual person.

Option B, Relationship Design, may sound plausible because the scenario mentions connected and social value, but it is not the answer selected by the supplied UX Designer study guide.

Within the guide's framing, Service Design provides the broader lens for thinking about how people, processes, interactions, and service touchpoints collectively create value. It extends the human-centered mindset from an isolated user interaction toward the overall service experience.

Study Guide reference/topics: Service Design, connected experiences, human-centered design, broader service systems, Human-Centered Design.

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

The correct answer is A. To avoid societal bias. The uploaded study guide directly identifies societal bias as the concern when demographic data is selected for AI-model use. Demographic information can contain or reflect historical social inequalities. When characteristics such as age, gender, location, ethnicity, socioeconomic indicators, or related proxies are included in a model without careful justification, the model may learn patterns that reproduce existing disparities rather than simply represent neutral relationships. The UX and responsible-design implication is that teams must question both what data is being collected and why the model needs it. Data should not be introduced simply because it is available. Instead, each attribute should have a legitimate purpose that supports the intended user or business outcome without unnecessarily increasing the risk of discriminatory behavior. Option B refers to confirmation bias, which concerns a tendency to favor evidence that supports existing beliefs. While that can affect research and decision-making, it is not the specific data-governance risk described here. Option C, interaction bias, relates more to patterns arising from how people interact with a system rather than demographic information itself. The study-guide principle is therefore that responsible AI design requires deliberate demographic-data selection to reduce the propagation of societal bias into automated decisions.

Study Guide reference/topics: Responsible AI, demographic data, societal bias, responsible design, Human-Centered Design.

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