Free Salesforce Plat-UX-101 Practice Exam with Questions & Answers | Set: 3

The uploaded study guide identifies B. Only the body, footer, and header helper components can be styled using styling hooks as the correct answer.

The item tests an implementation constraint that matters when a UX Designer is attempting to align a Lightning modal with organizational branding. The guide distinguishes between the primary modal framework and its associated helper components.

According to the answer key, the relevant styling-hook support applies to the body, footer, and header helper components, rather than to the primary Lightning Modal component as described in option A.

Option C is too broad because the study guide does identify supported styling-hook usage within the modal's helper-component structure.

The UX implication is that brand requirements must be evaluated against the styling capabilities Salesforce actually exposes. A designer should not assume that every visual property of every base component can be overridden freely. Design-system components deliberately constrain customization so that accessibility, structure, and platform consistency can be maintained.

Therefore, when preparing specifications for a custom modal experience, the designer must account for the specific styling surfaces supported by the Lightning modal architecture rather than designing treatments that cannot be implemented through the available hooks.

Study Guide reference/topics: Lightning Modal, styling hooks, LWC, branding constraints, SLDS.

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

The correct answer is B. 44 pixels wide x 44 pixels tall, which is the minimum target size identified by the study guide for interactive mobile elements. Touch interfaces require larger interaction targets than pointer-based desktop interfaces because users interact with them using fingers rather than a precise mouse cursor. A sufficiently large target makes buttons, links, icons, and other controls easier to activate accurately while reducing accidental selection of neighboring elements. The 44 × 44 pixel minimum therefore supports both usability and accessibility. The requirement is particularly important for users with limited dexterity, motor impairments, tremors, or users interacting with a mobile device while moving. Small targets can create repeated selection errors even for users without disabilities. Option A, 24 × 24 pixels, can be visually appropriate for some icons, but an icon's visual dimensions do not necessarily represent an adequate interactive touch area. Option C, 64 × 64 pixels, would certainly provide a large target but exceeds the minimum being tested. A UX Designer should distinguish between the visual size of an icon and its effective clickable or tappable area. A small-looking icon can still be enclosed within a larger interactive target.

Study Guide reference/topics: Mobile UX, touch targets, accessibility, interactive controls, UX Fundamentals.

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

The correct answer is C. Allows the user to share a raw stream of thought, as explicitly identified in the uploaded study guide.

The think-aloud technique asks users to verbalize what they are thinking while they interact with an interface or attempt a task. The value described by the study guide is that this provides researchers with access to the participant's immediate thought process.

Rather than observing only whether the user succeeds or fails, the researcher can hear what the user expects, what they find confusing, what assumptions they are making, and why they choose a particular path.

Option A is incorrect because asking someone to continuously verbalize thoughts does not necessarily create a more natural situation. It is a deliberate research technique.

Option B is also incorrect. Think-aloud does not eliminate bias from user behavior; instead, it provides additional qualitative information about the user's reasoning.

The important distinction is between observable behavior and expressed reasoning. A user may hesitate or select the wrong option, but the think-aloud stream can reveal why that behavior occurred.

The study guide therefore treats think-aloud as a way to obtain richer qualitative evidence during user testing.

Study Guide reference/topics: Think-Aloud Protocol, user testing, qualitative research, user reasoning, Testing.

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

A wireframe is the appropriate artifact when the primary requirement is to quickly establish and communicate page structure, information hierarchy, content placement, navigation areas, and functional relationships without spending unnecessary time on polished visual treatment. The uploaded study guide specifically identifies Wireframes (C) as the correct answer. This choice reflects an important UX principle: artifact fidelity should correspond to the design question currently being answered. During early structural planning, typography, branding, detailed imagery, animation, and production-quality interactions can distract stakeholders from the underlying information architecture.

A UI mockup generally introduces greater visual detail, such as typography, colors, spacing, imagery, and brand treatment. A high-fidelity prototype goes further by representing realistic interactions and application behavior, making it more appropriate for later validation or usability testing.

Salesforce's UX artifact guidance distinguishes mapping artifacts from screen-design artifacts and emphasizes progressing toward increasingly detailed screens after the designer has established user needs, hierarchy, and the structure of the solution. Therefore, when the objective is to quickly plan and communicate intended layouts, wireframes provide the required speed, flexibility, and structural clarity.

Study Guide reference/topics: Wireframes, UX artifacts, information hierarchy, fidelity levels, early-stage interface 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 A. Cross-Functional Map, as stated in the uploaded study guide.

The requirement is not simply to document the sequence of a process. Cloud Kicks specifically wants to explain the relationship between process steps and the business teams responsible for or involved in those steps.

A Cross-Functional Map is suited to that requirement because it organizes process activities according to the different roles, groups, or organizational functions involved. This allows stakeholders to see both the sequence of work and how responsibility moves across functional boundaries.

Option B, a Detailed Process Map, can document individual steps in significant depth, but the question emphasizes the relationship between those steps and different teams.

Option C, a Journey Map, represents an experience from the user's perspective, typically emphasizing stages, touchpoints, pain points, and opportunities. That is valuable for understanding the user's experience but does not primarily map organizational ownership across business functions.

The Discovery value of a cross-functional representation is that it can reveal handoffs, dependencies, duplicated effort, and organizational boundaries that may contribute to friction in the process.

Study Guide reference/topics: Cross-Functional Map, process mapping, business teams, responsibilities, Discovery.

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

The correct answer is B. In-App Feedback, as stated in the uploaded UX Designer study guide.

The scenario contains three important requirements: feedback is needed at scale, from a specific set of users, and while those users are in the flow of their work. The study guide identifies In-App Feedback as the approach that best fits that combination.

Because the feedback mechanism appears within the application context, users can respond while the newly released feature and their interaction with it are still immediately relevant. This reduces the separation between the experience being evaluated and the moment when feedback is collected.

Option A, User Interviews, can provide detailed qualitative insight, but interviews are typically more resource-intensive and do not satisfy the at-scale requirement as directly.

Option C, Survey, can collect responses from many users, but the study-guide answer emphasizes gathering feedback directly within the working context rather than through a separate feedback channel.

The Discovery principle being tested is contextual research. When the objective is to understand a recently released feature from selected users while they are actively using the product, collecting feedback inside the experience preserves useful context and supports broader participation.

Study Guide reference/topics: In-App Feedback, contextual research, feedback at scale, feature evaluation, Discovery.

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

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 study guide identifies B. Use Salesforce Flow to help complete fields required for case closure as the correct answer.

The support agents must work with information distributed across several Salesforce objects while resolving and closing cases. The study-guide solution is to use Salesforce Flow to guide the agent through the required information and process steps.

This approach reduces the amount of information the agent has to locate manually. Instead of expecting agents to navigate independently between records and remember every required field, a Flow can structure the activity around the case-closing task described in the question.

Option A would increase navigation overhead by opening additional windows. That approach can fragment the user's context instead of simplifying it.

Option C focuses on components completed by the customer, while the scenario is specifically concerned with making the support agent's experience more efficient.

The UX principle is task-oriented simplification. When users must collect or update information across multiple parts of Salesforce to complete a defined business process, a guided declarative experience can reduce cognitive load and unnecessary navigation.

The guide therefore favors Salesforce Flow as the mechanism for streamlining the case-closure process.

Study Guide reference/topics: Salesforce Flow, support-agent productivity, case closure, guided processes, Declarative Design.

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

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.

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