Free Practice Questions for Salesforce Plat-UX-101 Exam

The study guide identifies C. Menu tabs can be Visualforce and Lightning pages as the correct administrative capability for Salesforce mobile navigation setup.

The question is testing what administrators can include when configuring the navigation experience available to mobile Salesforce users. According to the answer key, navigation entries can include supported Visualforce and Lightning pages, giving administrators a mechanism to expose relevant application destinations through the mobile navigation structure.

Option A states that menu tabs can be based on different user types. Although user access can influence what users ultimately see within Salesforce, that is not the navigation capability selected by the study guide in this question.

Option B claims visibility can be based on user location. The guide does not identify geographic location as the relevant administrative mechanism for setting up mobile navigation tabs.

The broader declarative-design principle is that mobile users should have direct navigation to the Salesforce resources relevant to their workflows. Administrators can configure supported page types as destinations without requiring users to reach them through indirect navigation paths.

This allows the Salesforce mobile experience to incorporate both Lightning-based and Visualforce-based functionality where appropriate.

Study Guide reference/topics: Salesforce mobile navigation, menu tabs, Visualforce pages, Lightning pages, Declarative 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 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 correct answer is A. Design tokens prefixed with "brand", exactly as identified in the uploaded UX Designer study guide.

The question is testing how a design system propagates theme-level design decisions across multiple components. Rather than hard-coding individual color values into every button, icon, or component, SLDS uses named design values represented through design tokens.

The guide specifically identifies tokens prefixed with “brand” as the mechanism used to align components with a custom theme.

This approach improves both consistency and maintainability. If a theme changes, components referencing the appropriate brand token can inherit the updated design value instead of requiring developers to locate and replace numerous hard-coded values.

Option B, JavaScript libraries loaded from a static resource, is not the design-value mechanism described in the question.

Option C, CSS hexadecimal values, represents the opposite of a scalable design-system approach. Hard-coded values make global design changes harder and can cause components to become visually inconsistent over time.

The study-guide principle is that theme-driven interfaces should rely on reusable named design entities rather than duplicated literal values.

Study Guide reference/topics: Design Tokens, brand tokens, themes, component consistency, Salesforce Lightning Design System.

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

The study guide selects B. Economic growth, greater market share, and less employee turnover as the business outcomes representing the value of diversity, inclusion, and equality in design.

The option is internally consistent because each listed outcome is positive from an organizational perspective: business growth, broader market reach, and improved employee retention.

Option A includes lower market share, which conflicts with the positive business-value framing of the question. Even though inclusive recruitment is itself presented positively, the overall combination is not the one identified by the study guide.

Option C includes more employee turnover, which similarly represents an undesirable organizational outcome and therefore does not align with the intended value proposition.

The question is not asking only about ethical design principles; it is asking how those principles can be framed in terms of business outcomes. The guide therefore connects diversity, inclusion, and equality with both organizational sustainability and market performance.

For the UX Designer, the implication is that inclusive design considerations can be communicated to stakeholders not only as design responsibilities but also through outcomes meaningful to the organization.

Study Guide reference/topics: Diversity, inclusion, equality, business outcomes, inclusive design, Human-Centered Design.

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

The uploaded study guide identifies B. Grid as the correct SLDS utility.

The requirement describes a responsive layout in which content must adapt as available screen width changes. Elements may occupy multiple columns on wider screens and then wrap into additional rows when horizontal space becomes constrained.

A Grid system is designed precisely for this type of flexible page structure. It allows designers and developers to organize content into responsive rows and columns rather than relying on fixed positioning.

Option A, Float, can affect how individual elements position themselves relative to surrounding content, but it does not provide the structured, flexible responsive-layout system required by the scenario.

Option C, Alignment, controls positioning or distribution of content but does not itself define the responsive column-and-row layout architecture described.

The underlying UX principle is that responsive design should adapt the interface to varying screen sizes without requiring a completely separate page for each device. A grid gives the layout a systematic structure for resizing, wrapping, and repositioning content while retaining hierarchy.

Therefore, when the design requirement explicitly describes columns that can expand and wrap into new rows, the SLDS Grid utility is the appropriate solution.

Study Guide reference/topics: SLDS Grid, responsive design, flexible layouts, columns and rows, Salesforce Lightning Design System.

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

The uploaded study guide identifies C. Specify prompt scheduling as the available In-App Guidance customization.

The requirement is specifically about delivering an appropriate onboarding experience to new Salesforce users. Scheduling is relevant because onboarding guidance is most useful when it appears at an intentional point in the user's adoption journey rather than indiscriminately.

Within the answer choices, the guide distinguishes scheduling from presentation-level customization and permission concepts. Option B, selecting a prompt font, is not identified as the supported customization. Visual styling of individual prompt typography is therefore not the feature being tested.

Option A, setting prompt permissions, is likewise not the customization keyed by the guide in this scenario.

The important UX concept is timing. Guidance can be technically correct yet ineffective if users encounter it too early, too late, or repeatedly without regard to onboarding stage. The availability of prompt scheduling gives the designer or administrator a mechanism for controlling when that assistance is presented.

This is consistent with the role of In-App Guidance as contextual onboarding support. The study guide therefore identifies prompt scheduling as the configuration capability that can be used to shape the new-user experience.

Study Guide reference/topics: In-App Guidance, onboarding, prompt scheduling, user adoption, Declarative Design.

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

The study guide identifies A. Traits similar to customer personas as the correct criterion when recruiting users for testing.

A usability study is valuable only when the participants meaningfully represent the users for whom the feature is being designed. Customer personas summarize relevant user characteristics, behaviors, goals, needs, and task patterns. Recruiting participants with similar traits therefore makes the test findings more relevant to the intended experience.

Option B, friends and family, is convenient but does not ensure that participants share the behaviors or needs represented by the actual target audience. Their feedback could reflect personal preference rather than the experience of representative customers.

Option C narrows recruitment to the most common demographic and ability. That approach could exclude important user groups and does not necessarily correspond to the personas the solution is meant to serve. A representative study should be guided by the relevant user characteristics established through UX research rather than by selecting only the statistical majority.

The study-guide principle is therefore representative participant recruitment. Testing should be performed with people whose characteristics align with the intended users so that observed usability issues and responses are meaningful to the design team.

Study Guide reference/topics: User testing, participant recruitment, personas, representative users, 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 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.

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