Free Salesforce Platform Strategy Designer Practice Test Questions

Summary:
The project involves collecting highly sensitive personal data (health, biometrics) and using it to generate automated recommendations. This poses significant ethical risks regarding privacy, data security, algorithmic bias, and potential physical or psychological harm from inaccurate advice. Before committing resources, it is crucial to proactively identify and mitigate these risks through a structured, ethical assessment.

Correct Option:

B. Consequence Scanning Workshop:
This is the correct recommendation. A Consequence Scanning workshop is a proactive methodology designed specifically for this purpose. It brings together cross-functional teams to systematically ask: "What are the potential positive and negative consequences of this product?" and "What are we going to do about them?" This would help CK identify risks like data misuse, bias in recommendations against certain age groups, or safety issues before any development begins, preventing ethical debt and building trust.

Incorrect Option:

A. User Acceptance Testing (UAT):
UAT is a final validation step conducted after a product is built to ensure it meets business requirements and is usable. It is far too late to address the fundamental ethical and privacy concerns inherent in the project's concept. UAT tests how a product works, not whether it should be built in its proposed form.

C. Global Trend Analysis:
While analyzing trends in fitness technology is useful for market positioning, it does not address the core ethical and risk-related questions about handling sensitive user data. A trend being popular does not make it ethically sound or legally compliant.

Reference:
Salesforce Trailhead, "Build Trust Through Ethics and Privacy": This module emphasizes the importance of proactive ethical practices. It introduces frameworks like Consequence Scanning to help teams anticipate potential harms, build responsibly, and establish trust, which is paramount when dealing with sensitive health data and algorithmic recommendations.

Explanation:

A go-to-market (GTM) strategy is a plan that outlines how a company will deliver its product or service to customers and achieve market success. A core component of a successful GTM strategy is the product value proposition, which clearly defines the unique value the product or service offers to customers, addressing their needs and differentiating it from competitors. In the context of Cloud Kicks’ omnichannel experience, the value proposition would articulate how the seamless, multi-device, and multi-channel experience solves customer pain points and enhances their interaction with the company.

Why not A. Test-driven development? Test-driven development is a software development methodology focused on writing tests before code to ensure functionality. While important for product development, it is not a core component of a GTM strategy, which focuses on market positioning, customer acquisition, and delivery.
Why not C. Digital marketing plan? A digital marketing plan is a component of a GTM strategy, as it outlines how to reach customers through digital channels. However, it is not the core component, as it supports the execution of the strategy rather than defining the product’s value or purpose.

Reference:
Salesforce emphasizes the importance of a clear value proposition in its GTM strategies, as seen in resources like the Salesforce Customer Success Platform, which highlights how solutions are positioned to meet customer needs (e.g., seamless omnichannel experiences).
General business strategy resources, such as Harvard Business Review or Salesforce’s own marketing strategy guides, stress that a strong value proposition is foundational to GTM success.

Summary:
The challenge involves managing high-influence, low-availability stakeholders. The goal is to maintain their alignment and buy-in without allowing their limited time to become a bottleneck or cause disruptive, ad-hoc feedback. The solution must be highly strategic, respectful of their time, and focused on obtaining crucial feedback at the most impactful junctures of the project.

Correct Option:

A. Create three moments that matter, where top leaders will be invited to provide feedback:
This is the most effective strategy. It proactively identifies the key milestones in the project (e.g., finalizing the program vision, reviewing the prototype, approving the launch plan) where executive feedback is most critical. By scheduling these specific, high-value touchpoints in advance, the designer ensures leaders are engaged when it counts, provides them with focused context, and avoids constant, disruptive interruptions. This method respects their time while securing essential alignment.

Incorrect Option:

B. Create a communication plan based on leaders' interest, influence, and level of support for the work:
While a communication plan is important, it is often a one-way stream of information (e.g., status updates, reports). For top leaders whose alignment is critical, passive communication is insufficient. They require active, two-way engagement at decision points to provide directional feedback and maintain investment.

C. Create individual plans for working with top leaders based on their preferred cadence and type of involvement:
This approach, while well-intentioned, is inefficient and difficult to scale for a "several" leaders. Managing multiple, customized engagement plans for high-level stakeholders increases administrative overhead and can lead to inconsistencies in the information they receive, potentially creating misalignment among the leaders themselves.

Reference:
Salesforce Trailhead, "Navigate Politics and Constraints": This module emphasizes the importance of stakeholder management and recommends identifying key decision points where stakeholder input is crucial. For busy executives, it advises focusing their involvement on these "moments that matter" to secure buy-in efficiently without bogging down the project timeline.

Summary:
The question describes a complex, multi-step business process spanning different teams, departments, and disparate systems. The core challenge is integrating these siloed components into a single, streamlined, and automated workflow. The recommended tool must excel at orchestrating such cross-functional processes that involve both human and system-based steps, focusing on end-to-end process efficiency rather than a single department's function.

Correct Option:

B. MuleSoft
MuleSoft is an integration platform specifically designed to connect disparate systems, applications, and data sources. In a scenario with "many disparate systems," MuleSoft would create APIs to unify these systems, allowing data to flow seamlessly between them.

This integration is the foundational step for automating a complex, multi-departmental process. By breaking down data silos, MuleSoft enables the creation of a cohesive and efficient workflow that can then be managed by other automation tools, making it the strategic recommendation for this high-level integration challenge.

Incorrect Options:

A. Financial Services Cloud
Financial Services Cloud is an industry-specific CRM solution built on the Salesforce platform. While it provides pre-built features for the insurance industry (like policy and claim management), it is not primarily an integration or process orchestration tool.

Its strength lies in providing a 360-degree view of the customer within Salesforce, not in connecting the "many disparate systems" mentioned in the question. It would be part of the solution, but not the tool recommended specifically to solve the integration problem.

C. Services Cloud
Services Cloud is a CRM application focused on customer service and support operations. It automates service processes like case routing and agent productivity. While it can handle processes involving multiple team members, it is not designed to integrate external, disparate systems at the platform level. Its automation capabilities are largely confined to what happens within the Salesforce environment once the data is already present.

Explanation:

The Jobs to Be Done framework focuses on understanding what customers are trying to accomplish — the “job” they’re hiring a product or service to do. It’s not about the product itself, but the outcome the user seeks. The core principles are:
Customer-centric: Focuses on the user's goals, not internal business assumptions.
Solution Agnostic: The job remains the same regardless of the tool or technology used.
Stable Over Time: The job doesn’t change even if the market or tools evolve.
Measurable Outcomes: Success is defined by whether the job is completed effectively.
These principles help teams avoid jumping to solutions and instead design around real user needs.

❌ Why the other options are incorrect:
Option A includes “Effective Communication” and “Organizational Strategy,” which are important in change management but not core JTBD principles.
Option B introduces “Values driven” and “Revenue focused,” which are business strategy elements, not JTBD fundamentals.

📚 Reference:
You can find this directly in Salesforce’s Trailhead module: Jobs to Be Done Framework Explained

Summary:
The primary business goal is to reduce support costs by deflecting routine inquiries away from paid support agents. The core mechanism for achieving this through self-service is to empower customers to find answers to their own questions instantly, without needing to make a phone call or submit a case. This requires providing direct access to the company's repository of solutions and information.

Correct Option:

B. Exposing their knowledge base to customers:
This is the fundamental capability that drives self-service. A knowledge base contains articles, FAQs, and troubleshooting guides that address common customer issues. By making this searchable and accessible in Experience Cloud, customers can resolve their own problems immediately. This directly reduces the volume of incoming cases and calls, achieving the goal of lowering support costs.

Incorrect Option:

A. Allowing customers to see their open cases:
This is a feature of case management transparency, not a primary driver of self-service. While it improves the customer experience by providing status updates, it does not prevent a case from being created in the first place. It might even increase support costs if customers call to question the status of a case they can now see.

C. Providing dashboards of orders to customers:
This is a valuable service for order tracking and visibility, but it is a specific functional feature. It addresses the question "Where is my order?" but does not provide the broad, foundational capability to answer a wide range of customer questions, which is what is needed to significantly reduce support contacts and costs.

Reference:
Salesforce Experience Cloud Official Website: The product documentation highlights that a key capability for building self-service portals is integrating and exposing Knowledge articles to empower customers to find answers themselves, which is a proven method for reducing case volume and support costs.

Explanation:

To gain the developer's support for the loyalty program concept, the strategy designer should focus on building alignment and addressing the developer's concerns directly. Developers often value clarity, technical feasibility, and how a concept aligns with their priorities, such as system performance, scalability, or user experience. By crafting a persuasive story tailored to the developer's perspective—using their language and focusing on aspects like technical benefits, customer impact, or implementation feasibility—the strategy designer can bridge the gap and foster buy-in. This approach respects the developer's expertise and encourages collaboration.

Why not A. Persuade the developer's boss and product manager?
Going over the developer's head to involve their boss or product manager risks alienating the developer, creating resentment, and undermining team collaboration. This approach does not address the developer's skepticism directly and may lead to resistance or disengagement.
Why not B. Invite the developer to do their own research?
While involving the developer in ideation can be valuable, asking them to research and propose alternate solutions shifts the responsibility away from the strategy designer and may delay progress. It also assumes the developer has the time and resources to take on this additional work, which may not address their skepticism about the current concept.

Reference:
Salesforce’s approach to stakeholder alignment, as outlined in its Strategy Designer certification materials, emphasizes empathetic communication and storytelling to engage diverse team members, including technical stakeholders like developers. Resources like Salesforce’s Trailhead module on “Stakeholder Engagement” highlight the importance of tailoring communication to the audience’s priorities.
General change management principles, such as those from Prosci or Kotter’s 8-Step Process, stress the importance of addressing individual concerns and building buy-in through targeted, empathetic communication.

Explanation:

Why C is Correct:
This scenario describes a classic need for dynamic, role-based analytics. Tableau, as Salesforce's powerful enterprise analytics platform, is specifically designed to solve this problem efficiently.
Single Source of Truth: The team can build one central, curated data source (like a Salesforce dataset).
Dynamic Filtering and Customization: Tableau Dashboards allow for the use of parameters, filters, and actions. Leadership can interact with a single dashboard to change views, filter by region, product, timeframe, etc., without the need for the admin team to create a unique dashboard for each request.
Permission-Based Access: Most importantly, Tableau integrates with Salesforce permissions. You can create one dashboard and use row-level security and permission sets to control which data each executive sees based on their role in the organization. A regional VP would automatically see only their region's data in the same dashboard view that the CRO uses to see the global pipeline.
This approach eliminates the redundant effort of curating multiple individual dashboards and empowers users with self-service analytics.

Why A is Incorrect:
While developing reports in Sales Cloud is a core functionality, it doesn't efficiently solve the "multiple different levels of leadership... different views" problem.
Salesforce Reports are great for standardized lists and summaries.
Salesforce Dashboards in Sales Cloud are static snapshots. To provide different views for different leaders, the team would have to build and maintain multiple separate dashboards, which is exactly the inefficient process they are trying to avoid. This solution would perpetuate the problem, not solve it.

Why B is Incorrect: This option is the least relevant.
A Kanban view is a specific UI feature for visualizing records in a pipeline (e.g., dragging opportunities between stages). It is a tactical operational tool for sales reps and managers, not a strategic analytical tool for company leadership needing high-level pipeline metrics.
Mentioning "Revenue Cloud" (a specific product for complex quoting and billing) is a distractor; the core problem is about Sales Cloud pipeline data and analytics, not configuring Revenue Cloud.

Reference:
This question tests your understanding of scaling analytics and data distribution within an organization. A Platform Strategy Designer must recommend the right tool for the job:
Sales Cloud Reports & Dashboards: Best for operational, team-level reporting with a standard view.
Tableau: Best for enterprise-level, strategic analytics that require deep customization, interactivity, and dynamic, permission-driven data visibility.
Supporting Reference: This aligns with the capabilities of the Tableau Platform as part of the Salesforce Customer 360. Trailhead modules on "Tableau Basics" and "Einstein Analytics" demonstrate how dynamic dashboards solve the problem of providing unique data views from a single source.

Summary:
The design team is in the early stages of exploring an idea and has identified a critical knowledge gap: a lack of in-house expertise in consumer hardware engineering. Before making a significant investment or committing to the idea, the team needs a rapid, cost-effective way to assess the feasibility and potential risks associated with this new domain to inform a "pursue or not pursue" decision.

Correct Option:

C. Conduct an expert interview in consumer device engineering:
This is the most efficient and appropriate action. An expert interview allows the strategy designer to directly gather qualitative insights on the technical challenges, cost structures, supply chain complexities, and common pitfalls of consumer hardware. This provides the necessary feasibility data to make an informed strategic recommendation without the high cost and long timeline of hiring a full-time employee at this early, uncertain stage.

Incorrect Option:

A. Perform secondary research on common hardware issues:
While secondary research is a useful preliminary step, it is often generic and may not address the specific, nuanced challenges of integrating hardware into Cloud Kicks' unique footwear context. An expert can provide tailored, current, and actionable advice that goes beyond what is available in public sources.

B. Hire an engineer with experience in consumer devices:
This is a premature and resource-intensive solution for the exploration phase. Hiring is a long-term commitment and a significant expense. The goal at this stage is to determine if the idea is worth pursuing, not to build the team to execute it. Making a hire before validating the idea's feasibility puts the cart before the horse.

Reference:
Salesforce Trailhead, "Identify Assumptions and Risks": This module emphasizes the need to identify the riskiest parts of a new idea early on. In this case, the lack of hardware expertise is a major feasibility risk. The recommended technique to address such knowledge gaps is to "talk to experts" to validate assumptions and inform the go/no-go decision, which aligns perfectly with conducting an expert interview.

Explanation:

In the Salesforce Strategy Designer framework, stakeholder engagement is all about alignment, not just participation. The strategy designer’s role is to:
Create shared understanding of the project’s goals, metrics, and customer outcomes.
Facilitate collaboration across departments (e.g., product, UX, marketing, engineering).
Maintain alignment throughout the lifecycle — especially as priorities shift or new insights emerge.
This ensures that all stakeholders are pulling in the same direction, which is critical when trying to achieve product-market fit.

❌ Why the other options fall short:
A. Assign specific tasks: That’s more of a project manager’s role. It doesn’t address strategic alignment or shared vision.
B. Survey stakeholders for insights: Useful during discovery, but it’s not enough. Without alignment, those insights can lead to fragmented or conflicting directions.

📘 Reference:
You’ll find this principle emphasized in the Stakeholder Alignment unit — it highlights the importance of aligning on decisions, rationale, and metrics to ensure business goals and customer needs are met.