PDF Plat-UX-101 Study Guide

The uploaded study guide identifies C. Account Object as the correct answer.

The scenario requires Salesforce to represent existing individual customers in a way that allows financial advisors to open a customer record and see associated business opportunities. The study guide therefore selects the Account object rather than Case or Lead.

A Case represents a support or service issue rather than the customer entity itself, so it would not provide the correct foundation for representing the person whose opportunities need to be viewed. A Lead represents a prospective individual or organization before that prospect is converted into the established Salesforce customer structure. The scenario, however, refers to customers whose business opportunities must already be associated with their records.

The fact that the bank currently serves individuals rather than corporate customers does not change the study guide's selected Salesforce object. The essential UX and data-model requirement is to represent the customer using the object intended to anchor the relationship and associated opportunities.

Correct object selection directly affects the quality of the user experience because advisors need a coherent customer record from which related sales activity can be viewed.

Study Guide reference/topics: Salesforce objects, customer representation, Account records, Sales Cloud, Declarative Design.

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

The study guide identifies A. Formula Field, Static Resource, and Object Page Layout as the correct combination. The scenario requires the record detail page to show a custom visual indicator that changes according to the current membership level. The tools selected in the guide support that requirement declaratively.

A Static Resource can hold the image assets required for the membership indicators. A Formula Field can determine which visual representation should be shown according to the data stored on the record. The resulting field can then be positioned on the relevant Object Page Layout so that users see the membership indicator as part of the record experience.

Option B refers to an Image Field and Dynamic Forms, but that combination is not the platform approach selected by the study guide for deriving the displayed image from membership-level logic.

Option C introduces Lightning components and SLDS icons. That could imply a more customized implementation, while the guide favors the simpler declarative combination of formula, resource, and layout configuration.

The UX value is immediate recognition: a visual membership indicator can communicate status faster than requiring users to interpret raw field values.

Study Guide reference/topics: Formula Fields, Static Resources, page layouts, visual status indicators, Declarative Design.

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

The correct answer is B. Community Manager. The uploaded study guide explicitly associates a user who moderates forums, enforces community standards, and supports members with the Community Manager persona. Persona identification is important during UX discovery because different user archetypes have different goals, responsibilities, pain points, and workflow expectations. A Community Manager typically focuses on maintaining the health and quality of an online community. Their activities commonly include monitoring member participation, moderating discussions, responding to inappropriate content, applying community policies, encouraging engagement, and assisting members.

A Site Admin is more closely associated with administration and configuration responsibilities, such as site settings, access, technical configuration, or platform maintenance. Although a Site Admin can support an Experience Cloud environment, the activities described in the question are primarily community-governance activities rather than system-administration activities.

A Support Manager would normally focus on support operations, service teams, escalations, case management, agent performance, or customer-service delivery rather than ongoing forum moderation and community-policy enforcement.

From a UX perspective, correctly identifying the persona helps the designer build navigation, moderation tools, dashboards, workflows, and information architecture around the user's real operational responsibilities.

Study Guide reference/topics: Personas, user research, Experience Cloud users, role identification, Discovery.

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

The study guide identifies C. Configure a pre-filtered opportunity list view for each key attribute with the partner group as the correct answer. The requirement is for partners to quickly browse opportunities according to predetermined business criteria. The guide's selected solution is therefore a declarative one: create list views that are already filtered for the relevant opportunity attributes and expose those views to the appropriate partner audience.

This approach directly addresses both conditions stated in the scenario. One view can focus on opportunities closing within two weeks, while another can focus on opportunities valued above $100,000. Partners do not need to repeatedly construct their own filters or understand the underlying filtering logic.

Option A introduces a custom Lightning Web Component even though the requirement can be addressed using standard list-view functionality. That adds unnecessary implementation complexity.

Option B delegates filter creation to each partner, which conflicts with the requirement for a quick, standardized browsing experience.

The design principle reflected by the study guide is to prefer configured, reusable Salesforce functionality when it satisfies the user need. Pre-filtered list views reduce interaction effort and provide consistent segmentation across the partner experience.

Study Guide reference/topics: Experience Builder, opportunity list views, partner experience, filtering, Declarative Design.

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