Salesforce Plat-UX-101 Practice Test Questions Answers

The correct answer is C. Lead, Contact, and Opportunity, as keyed by the uploaded study guide.

These three standard objects correspond to different parts of the realty customer's sales lifecycle. A Lead can represent a prospective home buyer before that person becomes an established customer relationship. A Contact represents the individual once that relationship is maintained within Salesforce, while an Opportunity represents the potential sales transaction being pursued.

That combination fits the scenario because brokers need to track people who begin by shopping for homes, establish contact with the real estate company, and potentially progress toward a transaction.

Option A includes Address and Property, which are not the three standard objects identified by the study guide for this lifecycle.

Option B includes Account, Person Account, and Contact, but this combination does not represent the prospect-to-sales-opportunity progression the guide is testing.

The UX significance is that the underlying object model should reflect the business stages users actually work with. Brokers need to distinguish prospective buyers, known individuals, and active sales opportunities rather than treating all information as one undifferentiated customer record.

Study Guide reference/topics: Lead, Contact, Opportunity, Salesforce standard objects, customer lifecycle, Declarative Design.

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

The correct answer is A. Component Blueprints, exactly as identified in the study guide. The key phrases are accessible HTML and CSS and implementation guidelines. Component Blueprints are the SLDS resource the study guide associates with these needs. They provide the structural patterns required to build components that visually and semantically align with the Salesforce Lightning Design System.

This is especially important when a UX Designer and developer are implementing a custom Lightning Web Component rather than relying entirely on an existing base component. Starting from a documented blueprint helps maintain consistency with established Salesforce component structure.

Option B, Design Tokens, serves another purpose. Tokens represent reusable design values such as spacing, sizing, or color. They support visual consistency but do not provide complete component markup and implementation patterns.

Option C, Development Tools, may support implementation workflow, but it does not represent the specific SLDS location described in the question.

The study-guide distinction is therefore precise: when a designer requires the HTML/CSS structure and implementation guidance for an SLDS component, the appropriate reference is the Component Blueprint.

This also reinforces the design-system objective of reducing custom reinvention and promoting consistent, accessible interface construction.

Study Guide reference/topics: SLDS Component Blueprints, accessible markup, component implementation, LWC, Salesforce Lightning Design System.

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

The correct answer is A. In-App Guidance, as explicitly stated in the study guide.

The question contains two direct indicators: users need Floating or Docked Prompts, and administrators want to evaluate adoption through Salesforce reporting capabilities. The study guide associates those requirements with the out-of-the-box In-App Guidance feature.

In-App Guidance is used to provide contextual assistance directly within the Salesforce experience. The prompts can support users as they learn a new process without requiring them to leave their workflow for separate training material.

Option B introduces an AppExchange solution even though the requirement specifically asks for an out-of-the-box feature.

Option C, Screen Flow, can guide users through a business process, but it is not the feature identified by the guide for Floating and Docked Prompts.

The distinction is important: Screen Flow guides users through a structured transactional workflow, whereas In-App Guidance provides contextual adoption and learning assistance around the interface and process.

Because the administrative team also wants to assess adoption of the guidance, the study guide's answer fits both the instructional and measurement aspects of the requirement.

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

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

The correct answer is C. Key fields to complete before next Path stage, which the uploaded study guide confirms. Salesforce Path provides stage-oriented guidance for processes such as opportunities. Its major UX value comes from showing users where they are within the process and surfacing the information most relevant to each stage. Salesforce documentation states that a Path can expose up to five key fields per step, helping users focus on important information, together with contextual Guidance for Success. This makes key fields especially useful for onboarding. A new sales representative does not need to memorize every field or requirement associated with the opportunity lifecycle. Instead, the interface progressively surfaces the important information at the relevant stage, reducing cognitive load and reinforcing the intended business process.

Option A is not a standard defining capability of Path. Path does not primarily exist to supply integrated approval-automation buttons. Option B refers to a separate component and does not represent the core stage-specific onboarding functionality being tested.

One nuance is important: Path highlights key fields but does not inherently make those fields mandatory solely because they appear there; validation rules may be required when true enforcement is needed.

Study Guide reference/topics: Salesforce Path, key fields, onboarding, Guidance for Success, process guidance.

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

The correct answer is A. Observing user behavior, as explicitly identified by the uploaded study guide.

Human-centered design begins with understanding the people for whom a product, service, or process is being designed. Observing actual user behavior allows designers to understand what users really do, including their workflows, difficulties, workarounds, and environmental constraints. This provides evidence that may not emerge if the team relies only on assumptions or internal business objectives.

Option B places company OKRs at the center of requirements definition. Business objectives are important constraints, but they do not substitute for understanding users when adopting a human-centered approach.

Option C places rapid prototyping before ideation. Prototyping is useful for making ideas tangible and testing them, but the team first needs to understand users and generate potential solutions.

The study-guide distinction is therefore between evidence about people and organization-centered or prematurely solution-centered activities. Observing users gives the organization direct insight into needs and behavior and helps ensure subsequent design decisions are grounded in real experiences rather than assumptions.

Study Guide reference/topics: Human-Centered Design, user observation, behavioral research, user needs.

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