When validating that a final solution design meets updated customer requirements, which of the following is necessary?

Question

Options

• APlanning the solution design
• BQualifying the customer requirements
• CDocumenting customer intent
• DSelecting the right HPE and 3rd party products and services

• A
  5% (1)
• B
  5% (1)
• C
  89% (17)

Explanation

Documenting customer intent (C) is necessary when validating a final solution design against updated requirements because intent captures why the customer wants something, not just what they asked for. When requirements change, you need to confirm the documented intent still aligns with the evolved design - without it, you have no stable reference point for validation.

• A (Planning the solution design) is wrong because planning is an earlier-phase activity; by the validation stage, the design already exists.
• B (Qualifying the customer requirements) is wrong because qualification happens before design to confirm requirements are feasible - not during final validation.
• D (Selecting HPE and 3rd party products) is wrong because product selection also precedes validation; you validate after products are selected and the solution is built.

Memory tip: Think of intent as the "north star" - requirements can shift, but the documented why behind them keeps your validation grounded. When in doubt, ask: "What was the customer actually trying to achieve?" That's intent, and it's what you check against.

No community discussion yet for this question.