Free Salesforce Plat-UX-101 Practice Exam with Questions & Answers

The uploaded study guide identifies C. Heroku, Visualforce, Android as the correct set of platforms on which SLDS resources can be used.

The question is testing the portability of the Salesforce Lightning Design System beyond a single Salesforce interface. SLDS provides design resources that can help designers create visual and interaction consistency across different environments associated with Salesforce solutions.

The study guide specifically selects Heroku, Visualforce, and Android. This illustrates the broader purpose of a design system: reusable design principles, patterns, component guidance, and styling resources can support consistency across multiple implementation contexts.

Option A includes Azure, Visual Studio, and .NET, which are not the combination identified by the guide.

Option B includes AWS, Aura, and iOS. Although Aura is part of the Salesforce ecosystem, the complete three-item set is not the answer specified by the study guide.

The important UX lesson is that a design system is not merely a collection of styles for one page type. It provides a common design language that can be applied across experiences so that users encounter recognizable patterns, visual hierarchy, interaction behavior, and brand treatment.

Study Guide reference/topics: SLDS resources, cross-platform consistency, Heroku, Visualforce, Android, Salesforce Lightning Design System.

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

The correct answer is A. Be specific about the issues testers encountered, as stated in the uploaded study guide.

Usability findings become actionable when stakeholders understand exactly what happened, where it happened, and how it affected the participant's ability to complete the task. Specific descriptions therefore provide a stronger basis for design and development decisions than vague observations such as “users found the page confusing.”

Option B recommends excluding issues merely because they were already known. Existing problems encountered again during testing can still be meaningful evidence about their impact on users, so selectively omitting them would weaken the representation of the session.

Option C proposes identifying participants by name. The study guide does not support that approach; participant identities are not necessary for communicating the usability problem itself.

The broader testing principle is to translate observations into precise findings that the product team can understand and act upon. A specific finding connects the observed problem to the relevant part of the experience rather than leaving stakeholders to interpret ambiguous research notes.

Accordingly, the study guide prioritizes clear, concrete reporting of encountered issues.

Study Guide reference/topics: Usability Testing, reporting findings, research observations, actionable UX findings, Testing.

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

The correct answer is C. Import Lightning stylesheets in Visualforce, according to the uploaded study guide.

The scenario is specifically about an organization that has not yet migrated to Lightning Experience but still wants custom Salesforce applications to present a Lightning-consistent visual appearance.

Within the study-guide framing, importing Lightning stylesheets into Visualforce provides the appropriate bridge between legacy Visualforce applications and the visual language associated with Lightning Experience.

Option A references an SLDS package, but the question is not asking how to build an independent front-end application using package-managed CSS resources. It asks for the Salesforce-based solution appropriate to the existing Visualforce context.

Option B, importing standard design tokens into a stylesheet, would not by itself reproduce the broader Lightning component styling required to give the application a consistent Lightning appearance.

The essential UX objective is visual consistency across platform generations. Users should encounter familiar spacing, typography, control treatments, and general presentation even when some applications remain on older Salesforce technology.

The study guide therefore points to Visualforce's ability to use Lightning styling as the appropriate way to achieve this transition-oriented design requirement.

Study Guide reference/topics: SLDS, Visualforce, Lightning Experience styling, legacy application consistency, Salesforce Lightning Design System.

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

The correct answer is C. Brand color and loading page logo, which is explicitly identified in the study guide. Salesforce provides native branding controls for the Salesforce mobile application. Official Salesforce Help states that administrators can customize the application's brand color, loading-page background color, and loading-page logo to align the mobile experience with company identity. The brand color influences important user-interface elements such as the header, buttons, and search bar. Salesforce can also derive contrasting colors for supporting interface elements based on the selected brand color. The loading-page logo gives organizations a recognizable branded identity during the application startup experience.

Option A is incorrect because although branding can influence the color treatment of interface elements, Salesforce does not provide branding configuration for redesigning the search bar layout itself. Option B similarly describes settings that are not the standard mobile-branding controls specified by Salesforce.

This distinction is important for a UX Designer because declarative Salesforce configuration should be used before custom development. When the requirement can be satisfied through Salesforce's supported branding settings, those controls provide greater maintainability and platform consistency.

Thus, brand color and loading-page logo are valid customizable elements for CK's mobile branding.

Study Guide reference/topics: Salesforce mobile branding, brand color, loading-page logo, Declarative Design.

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

The correct answer is C. Desirable, Feasible, Viable, exactly as identified in the study guide. These three criteria represent a foundational human-centered design framework. Salesforce Trailhead explains that human-centered design historically seeks solutions that are desirable, feasible, and viable. A desirable solution addresses something people genuinely need; a feasible solution can realistically be created with available technology and capabilities; and a viable solution fits the organization's business model and objectives. Successful UX design therefore requires more than satisfying the user in isolation. A proposed Salesforce experience could be highly desirable to sales representatives but technologically impractical. Likewise, a technically feasible solution that users do not need provides little value. A solution can satisfy both users and technology constraints yet still fail if it cannot support organizational objectives or sustainable operations.

V2MOM is Salesforce's organizational alignment framework covering Vision, Values, Methods, Obstacles, and Measures; it is not the conceptual product-design balance described here. Agile is an iterative delivery methodology rather than the three-dimensional HCD evaluation model.

For the redesigned sales processes, Cloud Kicks should therefore seek the intersection where user needs, implementation capability, and business sustainability are simultaneously satisfied.

Study Guide reference/topics: Human-Centered Design, desirability, feasibility, viability, design thinking.

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

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 A. Trailhead modules. The study guide explicitly identifies Trailhead modules as the content that can be assigned to learners through Learning Paths in this onboarding scenario.

The question is testing the distinction between Salesforce learning content that can be incorporated directly into an employee learning assignment and other forms of Trailhead achievement or assessment. Within the guide's framing, Learning Paths is being used as an onboarding mechanism, so the appropriate assigned resource is a structured Trailhead module.

Modules are suited to an onboarding context because they represent defined learning content around a subject area. The requirement is not merely to give employees an environment in which to experiment or to require a larger credential-oriented achievement. Instead, Cloud Kicks wants to assign learning material as part of a managed learning experience.

Option B, hands-on challenges, describes a specific assessment/activity format rather than the assignment type selected by the guide. Option C, Superbadges, represents a broader accomplishment and is not the answer keyed for Learning Paths here.

Therefore, when the objective is to assign structured onboarding learning through Learning Paths, the study guide points to Trailhead modules.

Study Guide reference/topics: Learning Paths, employee onboarding, Trailhead modules, assigned learning, Declarative Design.

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

The correct answer is B. Compact Display Density, as explicitly stated in the study guide. Display density controls how much spacing Salesforce places around interface elements. When users work primarily on laptops with restricted screen dimensions and the organization needs to expose a large amount of textual information, Compact Display Density reduces whitespace and allows more content to fit within the visible viewport.

The requirement is global rather than page-specific. That is important because the question asks for a global user interface setting. Compact density addresses this directly.

Option A, Comfy Display Density, introduces more spacing around fields and UI elements. Although it may increase visual separation and improve readability in some circumstances, it consumes more screen area and therefore works against the stated requirement. Option C, Enable Collapsible Sections, can reduce visible content in particular layouts, but it is not the global density setting being tested. From a UX standpoint, density should be selected according to task context. High-information, productivity-focused environments often benefit from compact presentation because users can scan more data without excessive scrolling. The study guide therefore favors Compact Display Density for this laptop-centric, information-rich scenario.

Study Guide reference/topics: Display Density, Compact Density, screen-space optimization, Salesforce UI configuration, Declarative Design.

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

The study guide identifies A. Master-Detail as the correct relationship type.

The decisive requirement is that a Container Bid must be tightly dependent on its associated Container. The question provides a specific behavior: if the parent Container is deleted, the related Container Bids should also be deleted automatically. That dependency aligns with the relationship behavior the study guide associates with Master-Detail.

A many-to-one Lookup would create an association between records, but the scenario explicitly calls for a stronger dependency rather than a loose reference. The UX Designer therefore needs to consider the underlying data model, not merely how related records appear on the page.

A Hierarchical Lookup is also not appropriate for this general object-to-object relationship. The question is centered on two business objects—Container and Container Bids—and on enforcing dependent lifecycle behavior between them.

The study-guide answer illustrates that data architecture affects usability. If dependent child records remain after their parent is deleted, users can encounter orphaned or misleading information. A correctly modeled Master-Detail relationship keeps the related data aligned with the business relationship represented in the interface.

Study Guide reference/topics: Master-Detail relationships, dependent records, Salesforce data modeling, related objects, Declarative Design.

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

The correct answer is B. Exhaust the list of available base Lightning components in the Component Library. This is the best practice explicitly selected in the uploaded study guide.

The scenario begins with a proposed custom Lightning component, but the guide indicates that customization should not be the first assumption. Before developing something new, the designer and implementation team should first determine whether an existing base Lightning component already satisfies the requirement.

This approach promotes consistency with the standard Salesforce user experience and avoids unnecessary duplication. Existing components already embody Salesforce interaction and presentation conventions, making them the logical starting point for a Lightning-based solution.

Option A immediately moves toward custom HTML and separately linked styling resources. That bypasses the study guide's preferred sequence of first checking whether established Salesforce functionality already exists.

Option C is too absolute. SLDS blueprints are useful resources for component construction, but the guide does not recommend choosing blueprint markup over existing base Lightning components in every case.

The principle being tested is reuse before customization. Custom development should be justified by a genuine gap in standard functionality, not merely by the existence of a specialized business requirement.

Study Guide reference/topics: Base Lightning Components, Component Library, custom components, SLDS, reuse before customization.

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