Pass the Salesforce Salesforce Designers Plat-UX-101 Questions and answers with CertsForce

The correct answer is A. App Builder property, as keyed in the uploaded Master Study Guide.

The key requirement is that administrators, rather than developers, should be able to change the component's functionality or styling depending on the page where the component is placed. An App Builder property provides the configuration surface identified by the guide for exposing component-level settings to administrators.

This enables a reusable custom Lightning Web Component to behave differently according to the configuration selected in Lightning App Builder. Instead of creating separate components for every page context, the component can expose configurable properties.

Option B, Styling hooks, addresses styling customization but does not satisfy the broader requirement to allow an administrator to change both functionality or styling through page-specific component configuration.

Option C, Audience page variations, concerns delivering page variations according to different audiences rather than configuring reusable properties of the component itself.

The design principle is configurable reuse: a well-designed custom component can expose meaningful settings so administrators can adapt it to multiple page contexts without modifying source code or duplicating the component.

Study Guide reference/topics: App Builder properties, Lightning Web Components, configurable components, administrator customization, Declarative Design.

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

The study guide identifies A. Troubleshooting customer issues and logging activities as the correct activity set for the Case Solver persona.

Persona-based UX design requires the designer to align the interface with the user's primary responsibilities rather than with every activity that may exist somewhere within the organization. The name “Case Solver” itself points toward users whose principal work centers on resolving customer cases.

Option A directly reflects that operational role. Troubleshooting addresses the core problem-resolution responsibility, while logging activities supports documentation of the work performed while handling the customer issue. Those tasks therefore belong at the center of the Case Solver experience.

Option B shifts toward coaching, administration, or knowledge-management responsibilities. Those activities may exist within a service organization, but they are not the primary activities the study guide associates with the Case Solver persona.

Option C combines case-status visibility with campaign metrics. Campaign analysis belongs to a different business context and therefore does not form a coherent task set for this Service Cloud persona.

The design implication is that pages, actions, information hierarchy, and workflows should prioritize the activities users perform most frequently. For the Case Solver, the guide centers that experience on customer troubleshooting and activity logging.

Study Guide reference/topics: Personas, Case Solver, Service Cloud, task analysis, Discovery.

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

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. Expand the first section by default, exactly as keyed in the uploaded study guide.

An accordion is intended to reduce vertical complexity by grouping content into expandable and collapsible sections. On a mobile screen, however, presenting every section collapsed can introduce an additional interaction before users see any substantive content. Expanding the first section by default gives users an immediate entry point and demonstrates how the accordion behaves.

Option A is unsuitable because the browser Back control normally represents navigation history. Using it as the primary mechanism for collapsing accordion content would conflict with users' established expectations about browser behavior.

Option B would cause the interface to reposition content whenever a section is expanded. That can produce unexpected movement and interfere with the user's spatial understanding of the page.

Within the study guide's framing, option C provides the most predictable mobile experience: the user immediately sees useful content while retaining the ability to expand other sections when required.

This reflects a broader UX principle of minimizing unnecessary interaction while keeping content organized through progressive disclosure.

Study Guide reference/topics: Accordion usability, mobile UX, progressive disclosure, content organization, UX Fundamentals.

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

The correct solution is C. Enablement Site to build and assign custom modules, exactly as specified in the uploaded study guide. An Enablement Site is appropriate because the requirement is broader than simply showing users contextual assistance. Cloud Kicks requires structured, custom product training that can be delivered as learning content to internal users and leadership. Salesforce's Enablement functionality supports publishing modules and assigning relevant learning content to users. Salesforce documentation specifically explains that administrators can assign modules published on an enablement site and that users can complete assigned content from within Salesforce. Option A addresses a narrower use case. In-App Guidance prompts are effective for contextual onboarding, feature announcements, and short instructional interventions within the user's workflow, but they are not a replacement for a structured custom learning curriculum.

Option B provides an environment where users can experiment, but a sandbox does not inherently provide organized learning modules, assignments, learning progression, or formal enablement content.

The UX requirement here is therefore solved by selecting the platform capability that supports repeatable, organized, assignable learning experiences, rather than merely contextual assistance or an experimentation environment.

Study Guide reference/topics: Enablement Sites, custom learning modules, onboarding, internal user education, 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 correct answer is C. Account, Contact, Opportunity, according to the uploaded study guide.

The question tests the Salesforce data-model transition associated with converting a Lead. The study guide identifies the resulting business records as Account, Contact, and Opportunity.

Conceptually, each record represents a different part of the emerging customer relationship. The Account represents the customer or organization context, the Contact represents the individual person involved, and the Opportunity represents potential sales business being pursued.

Option A includes an Order. An Order represents a later transactional concept and is not one of the three records identified by the guide as the typical outcome of lead conversion.

Option B refers to a “Converted Lead” and Activity, but the guide does not identify those as the three resulting records in the standard lead-to-opportunity flow being tested.

For a UX Designer, understanding this record lifecycle matters because a user interface should align with what happens to users' data as they advance a sales process. Navigation, record context, and process guidance all depend on understanding how a Lead transitions into the customer and opportunity records sales users subsequently work with.

Study Guide reference/topics: Lead Conversion, Account, Contact, Opportunity, Sales process, Declarative Design.

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

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 correct answer is C. Sketch Plugin. The study guide explicitly associates this tool with the requirement to rapidly create Salesforce-oriented designs and prototypes using SLDS resources such as components, tokens, and patterns.

The key phrase is “quickly mock up Salesforce User Interface experiences.” The designer needs a design-oriented resource rather than an implementation or validation mechanism. According to the guide, the Sketch Plugin provides the appropriate design workflow for working with reusable SLDS assets while creating prototypes.

Option A, the Lightning Design System Unmanaged Package, is not the design-tool solution keyed for this mockup requirement.

Option B, SLDS Validator, is oriented toward checking or validating implementation rather than providing the prebuilt design resources the UX Designer needs to compose a visual prototype.

The question reinforces the distinction between design tooling and development tooling. At the prototyping stage, the designer needs assets that can be quickly assembled into Salesforce-consistent screens without recreating base interface patterns from scratch.

Using a plugin built around SLDS resources also improves consistency between proposed designs and Salesforce visual conventions. Therefore, the study guide selects the Sketch Plugin as the tool best suited to rapid SLDS-based mockup creation.

Study Guide reference/topics: SLDS resources, Sketch Plugin, prototypes, prebuilt components, design patterns.

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

The correct answer is C. Tabs, as identified in the study guide. Tabs are used to divide related information into logical sections within the same interface. For a content-rich record page, they allow the UX team to consolidate substantial amounts of information without displaying every section simultaneously. This supports information hierarchy and reduces visual overload. Users can focus on the currently relevant category while retaining easy access to other related information through clearly labeled tab controls. Option A, Data Tables, is appropriate for presenting structured records in rows and columns. A table does not solve the broader requirement to organize several categories of record-page content. Option B, Modals, temporarily display focused information or actions above the current interface. They are useful for confirmation, short forms, or specific interactions, but they are not intended as the primary architecture for persistent record-page organization. The underlying UX principle is progressive disclosure: present the information required for the current task while keeping secondary content readily accessible. Tabs accomplish this without forcing users to leave the record page. Accordingly, for consolidating a content-heavy Salesforce record experience, the SLDS Tabs component offers the most appropriate structural pattern.

Study Guide reference/topics: SLDS Tabs, content organization, progressive disclosure, information hierarchy, component design.

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