Salesforce Updated Plat-UX-101 Exam Questions and Answers by kyro

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 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 study guide identifies C. Compact Layouts as the correct answer.

The requirement is straightforward: when a sales representative views an Opportunity record, the most important fields should be immediately available without requiring unnecessary navigation or custom development.

Compact Layouts are the standard Salesforce feature selected by the guide for surfacing key record information concisely. The UX objective is to ensure that users can quickly orient themselves to the record and access the information required for common decisions.

Option A, a custom Lightning Web Component, would introduce custom development even though the scenario can be addressed using standard Salesforce configuration. This would add implementation complexity without a demonstrated need.

Option B, Tabs, can help organize larger groups of page content, but they do not specifically solve the requirement to expose a concise group of high-value record fields.

The UX principle is prioritization of information. Not every field on an Opportunity carries equal importance during routine record viewing. A compact presentation allows the designer or administrator to surface the fields that users need most frequently while keeping the broader record available when required.

Study Guide reference/topics: Compact Layouts, key fields, Opportunity records, information prioritization, Declarative Design.

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

The correct answer is B. Neutral button for "Cancel" and "Back"; Brand button for "Continue". This is the configuration identified by the uploaded UX Designer study guide. Button hierarchy communicates the relative importance of available actions. In this scenario, Continue advances the user through the primary three-step process, making it the principal action within the modal. It should therefore receive the visually prominent Brand treatment. Back and Cancel are secondary actions. Back reverses navigation within the flow, while Cancel exits or abandons the current interaction. Giving both actions the same visual prominence as Continue would weaken the action hierarchy and increase the possibility of users selecting the wrong control. Option A incorrectly emphasizes Cancel alongside Continue. Option C makes all three controls primary, effectively eliminating visual prioritization entirely. The SLDS design principle is that visual emphasis should correspond to action priority. A modal or flow should normally provide an obvious primary action while secondary navigation or dismissal controls use less prominent styling. This improves scanability, predictability, and task completion. Therefore, using a Brand button for Continue and Neutral buttons for Back and Cancel provides a clear and consistent interaction hierarchy.

Study Guide reference/topics: SLDS buttons, Brand button, Neutral button, action hierarchy, modal design.

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