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.

175 Questions
Salesforce 2026

A project team at Cloud Kicks framed this design challenge: " How might we help our customers amidst supply chain interruptions? " What information is missing that belongs in all well-written challenge statements?

A. The persona being designed for

B. The desired outcome

C. The hypothesis for the solution

B.   The desired outcome

Explanation

In the challenge statement "How might we help our customers amidst supply chain interruptions?", what is missing is the desired outcome—that is, what specific result we hope to achieve by "helping customers." According to Salesforce Trailhead's official guidance, a well-written How Might We (HMW) statement must contain a clear desired outcome, enabling the team to understand what success looks like based on the statement. In the Trailhead framework, a good HMW should answer the question: "If we solve this problem, the impact will be ____". The current statement only defines the target audience (customers) and the context (supply chain interruptions), but does not specify what state the customers should ultimately achieve—for example, "maintain trust during delays" or "reduce uncertainty while waiting for deliveries."

Why the other options are not optimal:

- A. The persona being designed for: The statement already explicitly mentions "our customers," so the target audience is not missing. Although more granular persona information (such as a specific customer segment) can enhance precision, Salesforce's definition of a "good HMW" does not require the persona to be written into the statement itself; what is required is a clear outcome.

- C. The hypothesis for the solution: HMW statements should be "solution-agnostic" and should not contain any solution hypotheses. Salesforce explicitly points out that a common pitfall is that the statement is too narrow and "the solution has already been stated in the framework," which prevents the discovery of multiple solution paths. Therefore, solution hypotheses should not appear in challenge statements, and their absence is not a flaw.

References

- Salesforce Trailhead: Create Effective How Might We Statements—When evaluating whether a HMW is well-written, one of the key criteria is "Does it contain a desired outcome? Can you understand what success would look like based on the statement?".

Cloud Kicks is excited about a new customer self service initiative. Within the stakeholder team, a support manager has shared features they want to recreate from their previous system; a product manager wants to implement new features that were not available in their previous system. There is a concern that conflicting demands may lead to organizational paralysis on the project. What should the strategy designer recommend to stakeholders to remediate risks?

A. Advise executive leadership to make the decision about priorities.

B. Revisit customer research to inform internal prioritization.

C. Map features between the two systems and let stakeholders prioritize.

B.   Revisit customer research to inform internal prioritization.

Explanation

The core of this question is that stakeholders each have their own agenda (the support manager wants to replicate old system features, the product manager wants to add new features), creating a risk of "organizational paralysis." The strategy designer's responsibility is not to adjudicate who is right, but to guide the team back to a shared decision-making foundation. Salesforce's official alignment methodology explicitly states that when a group begins to fragment into individual positions, the approach should be to "back up and remind everyone about the premises they already agree on," reviewing key insights from research first, then checking whether goals are still correct, and thereby restoring alignment . Customer research provides objective evidence of user needs, helping stakeholders shift from "I want" to "users need," using a shared factual foundation to resolve disagreements.

Why the other options are not optimal:

- A. Advise executive leadership to make the decision about priorities: Escalating to leadership is a last resort. It bypasses the team's collaborative decision-making process and can undermine stakeholders' sense of ownership and responsibility for the project. The strategy designer should first attempt to build consensus internally rather than rely on top-down arbitration.

- C. Map features between the two systems and let stakeholders prioritize: This approach merely visualizes the conflict and does not provide an objective basis for resolving it. If stakeholders prioritize based on their own positions, the support manager and product manager will still each cling to their own views, and mapping itself will not change the underlying logic of the disagreement.

References

- Salesforce Trailhead, Make Decisions and Resolve Conflicts: When a group fragments, it is recommended to "back up and remind everyone about the premises they already agree on," starting with key insights from research, checking alignment layer by layer, and restoring a shared perspective .

Cloud Kicks (CK) is working on enhanced functionality for an existing sales application. What should CK do to ensure the proposed design is compatible with the current data model?

A. Create high fidelity prototypes.

B. Perform end user testing.

C. Run a technical design critique.

C.   Run a technical design critique.

Explanation

The core of this question is to ensure that the proposed design is compatible with the existing data model. A technical design critique is a method specifically designed for this purpose: it invites technical experts (such as developers or architects) to review the design solution and identify potential conflicts between the design and the current data model, integration dependencies, or technical constraints, and propose improvements or alternatives . This step is an important checkpoint for validating technical feasibility before design implementation, and directly addresses the risk of "design not matching the data model."

Why the other options are not optimal:

- A. Create high fidelity prototypes: High-fidelity prototypes focus on the presentation of user experience and interface interaction, and do not address the technical compatibility of the underlying data model. They cannot proactively expose issues such as field types, object relationships, or data constraints.

- B. Perform end user testing: End user testing is used to verify whether the product meets user needs and is typically conducted at a later stage of the project. It cannot provide professional technical feedback on the compatibility of the data model.

References

- Salesforce Strategy Designer Certification Preparation materials explicitly state that a technical design critique ensures that the proposed design is compatible with the current data model through technical expert feedback .

A large professional services organization is starting to re-design its intranet platform. In the early stages of the project, the strategy designer plans on bringing a low-fidelity prototype to a co-creation session. What should the designer aim to achieve with the prototype?

A. Assess the feasibility for all features from participants.

B. Help participants articulate their needs, motivations, and expectations.

C. Get validation from participants on the features and content.

B.   Help participants articulate their needs, motivations, and expectations.

Explanation

The key to this question lies in "early stages" and "low-fidelity prototype." The value of low-fidelity prototypes (such as sketches and paper interfaces) lies in their "unfinished" nature, which precisely encourages participants to express their true thoughts without being constrained by specific interface details. In the early stages of project reconstruction, the strategy designer's goal is not to verify the correctness of features, but to use rough prototypes as "conversation catalysts" to help participants articulate their real needs, motivations, and expectations. The Salesforce Trailhead module clearly points out that low-fidelity prototypes are "great for ideation level questions," and their role is to present ideas for team and stakeholder discussion and divergent thinking . A prototype is a learning tool, not a preview of the final interface; it should be used to test the assumptions with the greatest risk and to obtain evidence at low cost .

Why the other options are not optimal:

- A. Assess the feasibility for all features from participants: Assessing technical or implementation feasibility requires the participation of technical experts, and low-fidelity prototypes do not contain sufficient technical information to support such assessment. Even more, it is impossible to assess "all features" in the early stages.

- C. Get validation from participants on the features and content: Validation is a task for later stages. The purpose of low-fidelity prototypes is to generate ideas and stimulate discussion, not to confirm the final form of features and content. Validation of features and content typically requires higher-fidelity prototypes and is conducted in more mature phases of the project .

References

- Salesforce Trailhead: Low-fidelity prototypes are suitable for ideation-level questions, with the goal of presenting ideas for discussion and divergent thinking .

A start-up company that develops machine learning-based tools which track the performance of carbon offsets wants to reinforce the positive perception of the validity of its data. The company starts by developing a need statement and a challenge statement. What is the commonality between the two statements?

A. Both are solution-free statements.

B. Both explain the scope of the possible solution.

C. Both are tactics intended to solve a problem.

A.   Both are solution-free statements.

Explanation

The commonality between a need statement and a challenge statement is that both are solution-agnostic—they define the problem or opportunity space without prescribing or implying any specific solution. A need statement articulates the user's unmet need (what outcome is desired), while a challenge statement (typically framed as a "How Might We" question) reframes that need into an open-ended provocation to inspire ideation. Neither embeds a predetermined answer, which keeps the solution space broad and prevents premature convergence on a single approach.

Why the other options are not optimal:

- B. Both explain the scope of the possible solution: Scope-setting is a separate activity. Challenge framing informs scoping, but the statements themselves do not define the boundaries of a solution—they define the problem to be solved .

- C. Both are tactics intended to solve a problem: A tactic is a specific action used to execute a solution. Need and challenge statements precede solution generation; they frame the problem, not solve it.

References

- Salesforce Trailhead, Create Effective How Might We Statements: HMW statements use "might" to "imagine or explore possibilities without committing to them," keeping the framing solution-agnostic .

Salesforce-Platform-Strategy-Designer Exam Questions - Home Previous
Page 3 out of 35 Pages