Free Plat-UX-101 Questions Attempt

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 C. Blueprints and tokens, as stated in the uploaded UX Designer study guide.

The question asks specifically which SLDS resources help custom applications reproduce the Salesforce visual experience. The guide identifies two design-system resources: Blueprints and tokens.

Blueprints provide reusable structural patterns for Salesforce-style components. They establish how interface elements should be represented so custom implementations can align with Salesforce's established component design.

Tokens address reusable design attributes. Instead of hard-coding values independently throughout an application, the designer or developer can rely on named design-system values to support visual consistency.

Option A describes fully functional components. The guide does not characterize SLDS itself as simply a library of complete runtime components for this purpose; rather, it emphasizes the design resources used to construct Salesforce-consistent custom experiences.

Option B, voice-and-tone guidance, relates to content and communication style rather than the visual construction of custom application interfaces requested in the question.

The broader design-system principle is consistency through reuse. Blueprints standardize component structure, while tokens standardize foundational design values. Together, they help a custom application adopt a recognizable Salesforce look and feel without inventing an independent visual language.

Study Guide reference/topics: SLDS Blueprints, design tokens, custom applications, visual consistency, Salesforce Lightning Design System.

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

The correct answer is A. Use the theme editor to adjust fonts, text case, colors, and site logo. The study guide explicitly selects this option for an Experience Builder implementation that must remain within out-of-the-box styling and component capabilities.

The important constraint is that the UX Designer cannot depend on custom styling or custom components. The Theme Editor is therefore the appropriate declarative mechanism because it allows the visual identity of the site to be adapted while remaining inside the standard Experience Builder framework.

Fonts, capitalization treatment, colors, and the site logo are all fundamental brand-expression elements. Adjusting these values allows the Experience Cloud site to reflect the organization's established visual identity without creating a separate custom presentation layer.

Option B affects footer content rather than the overall branded experience. Social-media links can be useful, but their presence does not establish the site's primary visual language.

Option C concerns page variations based on user behavior. That is a personalization technique rather than the direct brand-configuration solution requested.

The study-guide principle is therefore to use supported declarative theme controls first when the requirement is brand customization without custom development.

Study Guide reference/topics: Experience Builder, Theme Editor, branding, out-of-the-box configuration, Declarative Design.

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

The correct answer is C. Conduct a workshop with stakeholders to align on the current state and build consensus, as explicitly keyed in the study guide.

The discovery interviews have revealed that the fundamental problem is not simply poor adoption; Cloud Kicks lacks a clear and consistent sales process. Implementing user guidance before the organization agrees on the process would therefore attempt to teach users a workflow that is not yet defined.

Option A is premature. In-App Guidance may support adoption after a process is established, but it cannot resolve disagreement about what that process should be.

Option B gathers additional individual preferences, but the problem described is organizational alignment rather than a shortage of opinions. More isolated responses could actually increase ambiguity if different representatives prefer different approaches.

The study guide therefore favors a collaborative workshop. Bringing stakeholders together allows the team to make the current process visible, identify inconsistencies, establish shared understanding, and build consensus before designing the future experience.

The Discovery principle is clear: align on the problem and current state before implementing the solution.

Study Guide reference/topics: Discovery, stakeholder workshops, current-state alignment, consensus building, adoption strategy.

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