The study guide identifies B. Semantic and accessible component markup as the correct answer. SLDS is a design system that provides resources for creating interfaces aligned with Salesforce's visual and interaction conventions. In the context of this question, its relevant contribution is component markup designed around semantic structure and accessibility considerations. Semantic markup is important because the structure of an interface conveys meaning beyond its visual appearance. Properly structured controls, labels, states, and component relationships can be interpreted more reliably by browsers and assistive technologies. Option A is incorrect within the study guide's framing because SLDS itself is not simply a library of Lightning Web Components. The system provides design specifications, patterns, markup, styling, and associated guidance that can be applied when developing components. Option C describes JavaScript modules and plugins rather than the core SLDS resource identified by the answer key. This question reinforces the distinction between a design system and a component runtime framework. SLDS provides the standards and building blocks that support consistent interface implementation. For custom development, using its semantic and accessible markup patterns helps preserve Salesforce UX conventions while reducing the risk of inconsistent component behavior.

Study Guide reference/topics: SLDS, semantic markup, accessibility, component patterns, Salesforce Lightning Design System.

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

The uploaded study guide identifies B. Clarity, Efficiency, Consistency, Beauty as Salesforce's core design principles for making design decisions.

Within the guide's framing, Clarity means that users should be able to understand information, controls, and next actions without unnecessary ambiguity. Efficiency emphasizes helping users accomplish tasks with minimal unnecessary work. Consistency supports predictable interaction by applying recognizable patterns and behaviors across the interface. Beauty addresses the visual quality of the experience while working alongside—not replacing—the functional principles.

Option A contains positive characteristics, but it is not the set of Salesforce core design principles keyed by this study guide. Option C includes concepts that can be relevant in usability and interface design, but again it is not the four-part framework identified in the source.

The important examination point is to recognize the exact Salesforce terminology rather than choosing a collection of generally reasonable UX qualities. The study guide expects the designer to understand the framework as Clarity, Efficiency, Consistency, and Beauty, which collectively support usable, predictable, and visually coherent Salesforce experiences.

Study Guide reference/topics: Salesforce design principles, Clarity, Efficiency, Consistency, Beauty, UX Fundamentals.

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

The correct answer is B. Docked prompt using In-App Guidance, as specified in the uploaded study guide.

The requirement is to inform users that a new feature has become available and provide a short explanatory video in the context of their Salesforce experience. In-App Guidance is specifically intended for contextual onboarding, feature announcements, adoption support, and targeted instructional content.

A Docked Prompt is appropriate because it can remain visible while allowing the user to continue interacting with the application. It provides enough space for explanatory content without necessarily blocking the entire workflow.

Option A, using the Utility Bar, would place the video in a persistent productivity area, but that does not provide the same contextual announcement mechanism for a newly enabled feature.

Option C requires a custom component even though Salesforce provides an out-of-the-box onboarding capability suited to this requirement. Introducing custom development would add unnecessary implementation and maintenance effort.

The study-guide principle is to use contextual, declarative guidance when users need timely help or feature education. Rather than forcing users to search external documentation, guidance can be delivered directly within their working environment.

Study Guide reference/topics: In-App Guidance, Docked Prompts, onboarding, feature adoption, Declarative Design.

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

The correct answer is C. Search, as identified in the uploaded study guide.

Alternative text for a functional icon should communicate the purpose of the control, not merely describe its visual appearance. In this case, the magnifying-glass icon is clickable and performs a search action within a Lookup field.

Therefore, the text “Search” tells users what will happen when they activate the control.

Option B, “Magnifying glass,” describes what the icon looks like rather than what it does. That description is less useful to someone using assistive technology because knowing the graphical shape does not necessarily explain the interaction.

Option A, “Finder,” is also less direct and does not use the clear action-oriented label selected by the study guide.

This question reflects an important accessibility principle: when an icon is interactive, text alternatives should express its functional meaning. A screen-reader user should receive information equivalent to what a sighted user infers from the familiar icon.

For UX Designers, the practical rule is to label actions according to their function or outcome, rather than translating visual metaphors literally into text.

Study Guide reference/topics: Alternative text, functional icons, accessibility, Lookup fields, UX Fundamentals.

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

The uploaded study guide keys A. Survey as the correct answer. The abbreviated wording is preserved exactly from the supplied source.

Within the choices provided, a survey is the method that directly gathers information from users or a broader participant population. That makes it consistent with the study guide's broader human-centered emphasis on understanding people rather than making design decisions entirely from internal assumptions.

Option B, heuristic analysis, is an expert-led evaluation method. It can identify usability problems by comparing an interface against established principles, but it does not directly collect perspectives from the diverse users whose needs an inclusive design should address.

Option C, stakeholder analysis, focuses on understanding relevant organizational or project stakeholders. While stakeholders can supply important business and operational context, their perspectives do not automatically represent the full range of end-user experiences.

The source itself provides only the question, options, and keyed answer; it does not provide a deeper rationale for why “Survey” was selected. Accordingly, the supported interpretation is that the survey is the option most directly associated with collecting user input across a broader group.

For this study guide, the answer remains A.

Study Guide reference/topics: Inclusive Design, surveys, user input, Human-Centered Design.

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

The uploaded study guide identifies C. Work together on setting up UX indicators as the correct response.

The problem is fundamentally one of alignment: developers do not yet see the value produced by the proposed design changes. Establishing UX indicators collaboratively creates measurable criteria that both design and development teams can use to evaluate whether the changes improve the experience.

The emphasis on working together is important. Rather than asking developers to accept a design argument based purely on the designer's authority, both groups agree on evidence that can demonstrate improvement.

Option A relies on research notes from previous projects. Those findings may not directly correspond to the current problem, users, or implementation context.

Option B attempts to resolve resistance hierarchically by persuading a development lead and relying on that person to convince the rest of the team. That may secure compliance, but it does not create shared understanding of the UX objective.

The study-guide answer therefore favors a measurable and collaborative approach. UX indicators can turn subjective disagreement into a discussion around observable outcomes, helping multidisciplinary teams evaluate whether the design actually produces the intended improvement.

Study Guide reference/topics: UX indicators, design-development collaboration, measuring UX, stakeholder alignment, UX Fundamentals.

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

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. Dynamic Forms, exactly as stated in the uploaded study guide.

The scenario describes two related requirements: fields and sections should be treated as individual page components, and their visibility should vary according to the current reservation process context. Dynamic Forms is the feature selected by the guide for precisely this page-composition requirement.

Because all fields remain necessary, simply deleting fields from the object or layout would not solve the problem. Instead, the experience needs to show relevant information conditionally so that agents are not confronted with every field simultaneously.

Option B, In-App Guidance, would provide instructional prompts but would not restructure the underlying field presentation.

Option C, Flow Builder, can guide users through a defined process, but the requirement here is specifically to control the visibility and arrangement of fields and sections on the record page itself.

The study-guide principle is contextual presentation: maintain the required data model while reducing visual clutter by showing information when it becomes relevant. Dynamic Forms enables that page-level flexibility without requiring a completely custom interface.

Study Guide reference/topics: Dynamic Forms, field visibility, record pages, conditional presentation, Declarative Design.

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

The uploaded study guide specifies B. Page headers as the correct answer. A corporate logo is a persistent identity element normally associated with the site's header or theme-level branding area. In an Experience Cloud site, the logo should therefore be implemented within the portion of the experience responsible for global page identity rather than unrelated content channels.

Salesforce's Experience Builder documentation confirms that images can be uploaded and selected for areas including the header and logo, with those assets stored for reuse within the site's asset library. This aligns directly with the purpose of a prominent site-wide brand logo.

Visualforce pages would only be appropriate where a specific custom Visualforce implementation requires its own markup. Updating separate Visualforce pages would also risk inconsistent branding across the experience. Email templates control outbound email presentation and have no role in displaying the primary logo in the Digital Experience site's interface.

From a UX standpoint, common branding elements should be located at the appropriate global or reusable presentation level. This provides consistency, maintainability, and predictable placement across pages.

Accordingly, the page header is the correct target for prominently incorporating the updated company logo.

Study Guide reference/topics: Experience Cloud branding, page headers, logo placement, reusable site elements, Declarative Design.

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

The correct approach is to leverage Salesforce Lightning Design System (SLDS) using UI kits or plugins. The study guide explicitly identifies option C as correct. SLDS exists specifically to accelerate the creation of interfaces that are visually and behaviorally consistent with Salesforce. Rather than designing common interface patterns from scratch, UX Designers can reuse established component patterns, spacing conventions, typography, iconography, accessibility guidance, and design-system resources. Salesforce describes SLDS as a collection of resources for creating interfaces consistent with Salesforce UX principles, design language, and best practices. Official Salesforce Trailhead material also identifies APIs, plugins, and design kits as resources that make building with SLDS faster and easier. This directly addresses the requirement to accelerate the visual design process. Option A would increase fragmentation because separate custom stylesheets can create inconsistent styling and additional maintenance. Option B is not a standard Salesforce design workflow for producing reusable visual assets from layouts. Therefore, using established SLDS designer resources minimizes redundant design work while improving consistency, accessibility, and implementation alignment between UX Designers and developers.

Study Guide reference/topics: SLDS resources, design systems, UI kits, reusable components, visual consistency.

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