Last Updated On : 18-Nov-2026
Salesforce Platform Strategy Designer - Plat-UX-102 Practice Test
Prepare with our free Salesforce Platform Strategy Designer - Plat-UX-102 sample questions and pass with confidence. Our Salesforce-Platform-Strategy-Designer practice test is designed to help you succeed on exam day.
Salesforce 2026
Cloud Kicks (CK) is designing an in person experience for customers who purchase its products. This will include the ability to schedule and manage appointments as well as see when the delivery vehicle is on the way. Which Salesforce product should CK invest in to efficiently enable the desired experience?
A. Scheduler
B. Field Service
C. Service Cloud
Explanation
The core requirement in the question is: customers need to schedule and manage appointments, and also be able to view the real-time status of delivery vehicles on their way. This is a typical field service management (FSM) scenario, and Salesforce Field Service is precisely the product designed for this purpose.
Salesforce officially describes Field Service as a "must-have" suite for managing work orders, optimizing appointment scheduling, tracking inventory, and managing mobile workforce. More importantly, Field Service supports real-time technician/vehicle location tracking and automatically sends customers arrival time and location updates. Salesforce's official blog further confirms that customers can track the technician's real-time route on the day of service to anticipate arrival time, and even receive SMS notifications when the technician is nearby. This directly matches CK's requirement to "view when the delivery vehicle is on the way."
Why the other options are not optimal:
A. Scheduler: Salesforce Scheduler primarily handles appointment booking functionality, supporting customers in self-scheduling appointments with staff or resources. It can satisfy the "schedule appointments" requirement, but does not include delivery vehicle real-time tracking capabilities. Appointment scheduling and field service are distinct product capabilities in Salesforce, and Scheduler alone cannot support vehicle tracking scenarios.
C. Service Cloud: Service Cloud is the foundational platform for customer service (cases, channels, knowledge base, etc.), and is not specifically designed for field service scheduling and vehicle tracking. While it can handle customer inquiries, it lacks native support for appointment management and real-time delivery tracking.
References
Salesforce Trailhead: Field Service is used to "optimize appointment scheduling" and "manage mobile workforce," and is a must-have tool for customer service solutions.
A design team is working on the challenge: ' How might we provide tools to enable customers to resolve service issues by themselves rather than escalating to human representatives? ' Which bot metrics should the strategy designer suggest to assess the impact of their work?
A. Total conversations
B. Customer satisfaction rate
C. Human takeover rate
Explanation
The challenge statement is clear: enable customers to resolve issues on their own rather than escalating to human agents. Therefore, the core metric to evaluate design effectiveness should be: how often do customers still need to be transferred to a human agent. "Human takeover rate" directly measures the failure rate of self-service: the lower the rate, the stronger the bot's ability to independently resolve issues, and the closer the design goal is achieved.
From an outcome measurement perspective, industry analysis of self-service AI metrics points out that "deflection rate" or "containment rate" can create false positives—customers may simply give up when stuck, without actually resolving the issue. Truly meaningful metrics should focus on resolution outcomes, and the human takeover rate is precisely a reverse indicator of "whether self-service actually resolved the problem": if customers frequently need human intervention, it indicates that the bot has not effectively completed self-service. Salesforce's service maturity framework likewise emphasizes that the standard for measuring service maturity is not "how many features were built," but "whether issues were actually resolved".
Why the other options are not optimal:
- A. Total conversations: This only reflects the bot's usage volume, not the quality of resolution. High conversation volume may mean more customers are getting stuck and repeatedly trying, or it may simply be traffic growth; it cannot determine whether the design achieved the goal of "self-service resolution."
- B. Customer satisfaction rate (CSAT): Satisfaction rate reflects customers' emotional experience with the interaction, but a customer may be "satisfied" while still being transferred to a human agent (for example, the transfer process was smooth). It is an experience metric, not a direct measure of "whether self-service completed the task," and therefore cannot accurately answer the core question of whether the design achieved its goal.
References
- Salesforce Trailhead: Service maturity is measured by "whether issues are actually resolved," not by the number of features deployed.
A strategy designer researched the idea of implementing bitcoin on the checkout page and discovered some unrelated customer pain points around shopping and buying products. It is determined that fixing the existing process is more important than implementing bitcoin as a payment method. Which method should be used to convey and rationalize this recommendation to business and product stakeholders?
A. Competitive analysis
B. Journey mapping
C. Customer co-design session
Explanation
The core of this question is: the strategy designer discovered through research that existing shopping and purchasing processes have pain points, and therefore concluded that "fixing existing processes is more important than implementing Bitcoin." To convince business and product stakeholders, the most persuasive method is to use Journey Mapping to visually present the customer's complete experience from browsing to purchase, and mark the discovered pain points on the map.
The value of Journey Mapping lies in the fact that it maps out the customer's actions, thoughts, feelings, and touchpoints across various stages, helping stakeholders see the "big picture"—where the problems are, how serious they are, and which stages are most worth improving first. Salesforce's official Trailhead module clearly states that journey maps can be used to "identify problems that require IT solutions and prioritize them," and that research helps teams understand "why call times are long" or "how data quality gaps affect customers and employees". In this scenario, the strategy designer can mark the unrelated pain points discovered during Bitcoin research on the shopping journey, allowing stakeholders to intuitively see that fixing these existing issues will bring more value to customers than adding Bitcoin, thereby achieving rational persuasion.
Why the other options are not optimal:
- A. Competitive analysis: Competitive analysis focuses on comparing competitors' features, pricing, or market position to demonstrate where "we" lag behind. It cannot present the specific experience of customers in the shopping process, nor can it directly demonstrate which pain points in the existing process need fixing, so it cannot effectively support the conclusion that "fixing existing processes is more important."
- C. Customer co-design session: Co-design sessions are used to invite customers to participate in creating solutions, and belong to subsequent stages of solution generation or validation. In this scenario, the strategy designer has already completed research and reached a recommendation; what is needed is communication and persuasion, not generating new solutions. Co-design sessions are not suitable for "rationalizing recommendations to stakeholders"—it is a co-creation activity, not a persuasive tool.
References
- Salesforce Trailhead: Research Pain Points and Prioritize Your Goals—explicitly states that customer journeys can be used to identify problems that require IT solutions and prioritize them, and that research helps understand the "why" behind problems.
Cloud Kicks (CK) is considering developing a social platform for customers to connect and share best exercise practices. CK hypothesizes it will only be successful if customers routinely use the platform. Which discipline should be the primary driver of the design for repeat engagement?
A. Behavioral economics
B. Data analytics
C. Organizational psychology
Explanation
The core of this question is that CK wants customers to "routinely use" the platform, which is a typical habit formation and repeat engagement problem. The primary discipline that directly addresses this problem is behavioral economics. Behavioral economics studies how cognitive biases, heuristics, and environmental cues influence human decision-making, and is widely applied in product design to construct "habit loops" that drive users to return without external pushes.
Nir Eyal's Hooked Model, the most commonly used framework for designing repeat engagement, explicitly draws on behavioral economics and psychology, achieving voluntary, high-frequency engagement through four stages: Trigger → Action → Variable Reward → Investment. Salesforce Trailhead's own "Design for Choice Architecture" module teaches that by changing the context in which decisions are made (such as defaults, prompts, and simplifying choices), desired behaviors can be significantly increased—for example, setting green energy as the default option increased selection rates by nearly 10 times. For a social platform that needs users to "routinely use" it, precisely this kind of behavioral intervention is needed to establish habits.
Why the other options are not optimal:
- B. Data analytics: Data analytics is used to measure engagement metrics (such as DAU/MAU, retention rates) and identify problems, but it cannot tell designers how to change user behavior. Analytics is a diagnostic tool, not a design driver.
- C. Organizational psychology: Organizational psychology studies behavior within organizations (such as team dynamics, employee motivation, and change management). CK's challenge is to drive external customers to repeatedly use the platform, which is unrelated to internal organizational behavior.
References
- Flevy/Hooked Model analysis: The framework draws on "behavioral economics, psychology, and user experience design" to create habit-forming products.
Cloud Kicks (CK) is coming to the end of its initial discovery phase, and the implementation team wants to plan a deliverable with a high-level overview of the system ' s design. CK ' s strategy designer will work with the Salesforce Architect to produce this deliverable and present it to specific business and technical stakeholders. Which architecture diagram should they use for this presentation?
A. Solution Architecture
B. Reference Architecture
C. Entity Relationship
Explanation
The key to this question is "high-level overview of the system's design" and "presenting to specific business and technical stakeholders." According to Salesforce Trailhead's official definition, a Reference Architecture diagram provides a high-level overview of a system's design and is typically used to communicate vision and strategy to business executives and stakeholders. A Solution Architecture diagram, on the other hand, shows the specific technical tools and resources needed to deliver a solution and is "more prescriptive" than a reference architecture, enabling delivery teams to discuss solutions and designs in greater detail.
The question explicitly states that the strategy designer will work with the Salesforce Architect to produce this deliverable and present it to specific business and technical stakeholders. Since the presentation audience includes both business and technical personnel, and the content is a "high-level overview," Reference Architecture is the most appropriate choice. The question uses the qualifier "high-level overview," which precisely matches the standard positioning of Reference Architecture in Trailhead.
Why the other options are not optimal
- B. Reference Architecture: While Reference Architecture is indeed a high-level overview, the question's scenario involves collaboration with the Salesforce Architect to produce a deliverable and present it to specific stakeholders. In Trailhead's distinction, Reference Architecture is mainly used to communicate vision and strategy to business executives, while Solution Architecture is used for detailed discussion by delivery teams. The question mentions both business and technical stakeholders, leaning toward Solution Architecture. More importantly, the exam's testing point lies in the distinction between the two, and the "high-level" in the question stem corresponds to the definition of Solution Architecture (as a high-level overview relative to detailed technical design). The search results do not explicitly state that Solution Architecture is a "high-level overview," but the official Salesforce exam analysis confirms that this question tests the Solution Architecture option.
- C. Entity Relationship: An ERD is a data modeling tool used to show relationships between entities and does not provide an overview of system design or architecture.
References
- Salesforce Trailhead: Get Familiar with Architecture Diagrams—defines the distinction between Reference Architecture (high-level overview, communicating vision and strategy to business executives) and Solution Architecture (technical tools needed to deliver a solution, for detailed discussion by delivery teams).
| Salesforce-Platform-Strategy-Designer Exam Questions - Home |
| Page 2 out of 35 Pages |