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

The uploaded study guide identifies A. A separate layout is needed for each record type as the correct consideration.

The scenario describes two Appointment record types—Virtual and In-Person—with different information requirements. Virtual appointments may additionally require fields that vary depending on the virtual meeting software being used. The study guide therefore emphasizes the need to account for those distinct record-type layouts when designing the record-creation experience.

Option B concerns inline editing in list views and does not address the central challenge of presenting different fields during record creation.

Option C concerns mobile availability of the field-section component, but that is not the design issue selected by the study guide for this question.

The important UX consideration is that users should see fields relevant to the kind of appointment they are creating. Presenting fields intended for Virtual appointments to users creating an In-Person appointment would add unnecessary complexity. Conversely, omitting software-specific fields from the Virtual workflow could prevent users from entering required information.

The study-guide answer therefore links record types and layout structure to a more contextually appropriate record-creation experience.

Study Guide reference/topics: Dynamic Forms, record types, layouts, conditional data requirements, Declarative Design.

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

The correct answer is A. Online surveys, as stated in the uploaded study guide. The decisive factors are scale, remote participation, and the relatively straightforward nature of the information being collected. Online surveys can efficiently gather structured feedback from hundreds or thousands of participants without requiring a researcher to observe every session. They are especially effective when questions concern relatively concrete behaviors, preferences, experiences, or task-related feedback that can be expressed through predetermined choices, ratings, or concise responses. A usability study is more appropriate when the designer needs to observe users completing tasks and understand where participants encounter confusion, friction, errors, or navigation difficulties. It produces richer behavioral evidence but generally requires substantially more research effort. A/B testing compares two or more variations of an experience against a measurable behavioral outcome. It answers questions such as which version generates more clicks or successful conversions; it is not primarily a general-purpose feedback collection technique. Because the scenario specifically requires feedback from hundreds of remote users and does not demand substantial emotional exploration or imaginative discussion, a scalable quantitative or structured method is appropriate. Online surveys therefore provide the strongest balance between reach, speed, consistency, and research effort.

Study Guide reference/topics: Online surveys, remote research, research scale, usability methods, Testing.

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

The correct answer is A. Create a custom Theme in Themes and Branding, selecting logo, brand colors, and images, exactly as stated in the uploaded study guide.

The requirement is to make Lightning Experience conform to the company's existing design guidelines using declarative configuration. The study guide therefore directs the UX Designer to the standard Themes and Branding capability rather than to custom development.

A custom theme allows the organization to apply important brand assets such as the company logo, brand colors, and imagery so that the Salesforce environment presents a recognizable visual identity.

Option B is insufficient because selecting whichever built-in theme happens to be closest does not guarantee compliance with Cloud Kicks' actual design guidelines.

Option C refers to a different branding mechanism and includes font-type configuration, but it is not the declarative approach keyed by the study guide for the current Lightning Experience scenario.

The broader UX principle is to implement branding through supported Salesforce configuration whenever those tools satisfy the requirement. This preserves consistency and avoids unnecessary custom styling while still aligning the environment with company identity.

Study Guide reference/topics: Themes and Branding, Lightning Experience, brand colors, logos, Declarative Design.

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

A wireframe is the appropriate artifact when the primary requirement is to quickly establish and communicate page structure, information hierarchy, content placement, navigation areas, and functional relationships without spending unnecessary time on polished visual treatment. The uploaded study guide specifically identifies Wireframes (C) as the correct answer. This choice reflects an important UX principle: artifact fidelity should correspond to the design question currently being answered. During early structural planning, typography, branding, detailed imagery, animation, and production-quality interactions can distract stakeholders from the underlying information architecture.

A UI mockup generally introduces greater visual detail, such as typography, colors, spacing, imagery, and brand treatment. A high-fidelity prototype goes further by representing realistic interactions and application behavior, making it more appropriate for later validation or usability testing.

Salesforce's UX artifact guidance distinguishes mapping artifacts from screen-design artifacts and emphasizes progressing toward increasingly detailed screens after the designer has established user needs, hierarchy, and the structure of the solution. Therefore, when the objective is to quickly plan and communicate intended layouts, wireframes provide the required speed, flexibility, and structural clarity.

Study Guide reference/topics: Wireframes, UX artifacts, information hierarchy, fidelity levels, early-stage interface design.

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

The uploaded study guide identifies B. Grid System as the correct SLDS resource for responsive design.

A responsive interface needs its layout to adapt as the available screen width changes. The Grid System is the resource selected by the guide because it provides the structural mechanism for arranging interface content into flexible rows and columns.

This directly addresses page-level responsiveness: content can be organized so that it uses available horizontal space appropriately and can be repositioned or wrapped as the viewport changes.

Option A, Design Tokens, addresses reusable design values. Tokens can support consistency for properties such as spacing, color, or other design attributes, but the question specifically asks what the designer should use for responsive layout design.

Option C, Component Blueprints, provides structural guidance for individual SLDS components rather than serving as the primary layout system for responsive page organization.

The key study-guide distinction is therefore between component styling/resources and layout architecture. When the issue is adapting page composition to different screen sizes, the Grid System provides the relevant SLDS mechanism.

This makes the grid an essential foundation for designing Salesforce interfaces that remain organized and usable across varying viewport dimensions.

Study Guide reference/topics: SLDS Grid System, responsive design, rows and columns, adaptive layouts, Salesforce Lightning Design System.

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

The correct answer is C. `slds--size-1-of-2`, which the uploaded study guide explicitly identifies as the class that does not follow the expected SLDS convention. SLDS uses a structured naming system derived from Block-Element-Modifier (BEM) conventions. Salesforce documentation describes a block as the primary component, an element as a constituent part represented with a double underscore, and a modifier as a variation or state.

Current Salesforce guidance is particularly relevant here. Modern SLDS notation uses the single underscore for modifier syntax. For example, `slds-avatar_circle` correctly represents the circular avatar variant. `slds-box` is itself a valid SLDS utility/component class. Salesforce also confirms that older double-dash modifier syntax has been deprecated in favor of the single-underscore convention. Option C is malformed because the separator appears immediately after the `slds` namespace: `slds--size-1-of-2`. Even historical sizing syntax would have been structured around the size class, such as `slds-size--1-of-2`, rather than `slds--size-1-of-2`. Modern notation uses forms such as `slds-size_1-of-2`. Therefore, C clearly violates the expected SLDS class structure.

Study Guide reference/topics: SLDS, BEM naming, CSS classes, modifiers, Lightning Web Components.

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

The correct answer is A. Tabbing order is logical, as confirmed by the study guide. Keyboard accessibility testing evaluates whether users can navigate and operate an interface without relying on a mouse or other pointing device. One of the most important checks is whether pressing Tab and Shift+Tab moves focus through interactive controls in an order that is logical, predictable, and consistent with the visual and semantic structure of the page. For example, focus should generally move through navigation controls, form fields, buttons, and links in an understandable sequence. An unexpected jump to unrelated content can make the interface difficult or impossible to use for people who depend on keyboard navigation or assistive technologies. Option B is not a standard keyboard-navigation requirement. Keyboard actions do not need to provide audio feedback simply because they are accessible. Option C is also insufficient because accessibility cannot depend solely on a specific color to communicate interactivity or focus. Keyboard users require a perceivable focus state, but the question asks specifically what can be verified by testing the navigation sequence. Therefore, keyboard testing should verify that focus proceeds in a meaningful and usable tab order, enabling users to reach and operate interactive elements successfully.

Study Guide reference/topics: Accessibility testing, keyboard navigation, focus order, tab sequence, Testing.

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

The correct answer is A. Remove low value list views from public view, as identified in the uploaded study guide.

The problem is not primarily record access. It is that users have too many list views to choose from, making relevant views harder to locate. The study guide therefore addresses the source of the clutter directly by removing low-value views from public visibility.

Option B changes Sharing Rules, which affect which records users are permitted to access. That does not directly reduce the number of available list-view definitions and therefore does not solve the navigation problem stated in the question.

Option C would allow users to manage public list views, but that shifts administrative complexity to users rather than simplifying the experience for them.

The UX principle is reduction of unnecessary choice. When many low-value options are presented alongside useful ones, users must spend additional effort scanning and deciding which view to use. Removing low-value public views makes the remaining choices more meaningful.

The study-guide answer therefore improves the experience by simplifying the list-view environment itself rather than changing security or delegating additional management responsibility to users.

Study Guide reference/topics: List Views, information reduction, user efficiency, Salesforce configuration, Declarative Design.

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

The correct answer is B. Ability to toggle between multiple records. The uploaded UX Designer study guide explicitly identifies this requirement as a reason to recommend Console navigation. Console navigation is designed for users who work intensively with multiple records and related information during the same session. Rather than continually leaving one record page and opening another, users can maintain several records within the console workspace and switch between them efficiently. This makes the console particularly valuable for sales or service roles where users frequently compare, reference, or update multiple related records.

Option A is not the defining requirement in the study-guide scenario. Although console applications can support efficient multi-record workflows, the requirement specifically associated with the answer is the ability to toggle between multiple records.

Option C points in the opposite direction. Users whose work occurs primarily in the field generally have stronger mobile and simplified-navigation requirements rather than a desktop-oriented multi-record console workspace.

From a UX perspective, the navigation model should correspond to the user's task pattern. Standard navigation suits more linear interaction, whereas Console navigation is better suited to high-volume, multi-record work where reducing navigation overhead improves productivity.

Study Guide reference/topics: Console Navigation, Standard Navigation, multi-record workflows, productivity, Declarative 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.

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