When collecting customer requirements for an HPE Edge-to-Cloud solution, which of the following is a key consideration?

Question

Options

• ADocumenting requirements in a way that is easy to understand for technical experts only
• BGathering requirements from a single stakeholder to avoid conflicting inputs
• CAsking open-ended questions to gather as much information as possible
• DAvoiding any requirements that are difficult to implement

• A
  3% (1)
• B
  3% (1)
• C
  87% (33)
• D
  8% (3)

Explanation

Asking open-ended questions (C) is the foundational technique for effective requirements gathering because it allows stakeholders to share context, priorities, and constraints in their own words - uncovering needs you wouldn't find with yes/no questions or a predefined checklist.

Why the distractors are wrong:

• A is wrong because requirements documentation must be accessible to all stakeholders, including business owners and non-technical decision-makers, not just technical experts.
• B is wrong because limiting input to a single stakeholder creates blind spots; effective discovery pulls from multiple perspectives (business, IT, operations) to surface conflicting priorities early.
• D is wrong because avoiding difficult requirements ignores legitimate business needs - the role of the solution architect is to find a path to meet those needs, not filter them out upfront.

Memory tip: Think of open-ended questions as "opening the door" - they let the customer walk through and show you the whole room, rather than you guessing what's inside. In HPE solution selling, the acronym SPIN (Situation, Problem, Implication, Need-Payoff) is a classic open-ended questioning framework worth remembering for exam scenarios involving discovery and requirements.

No community discussion yet for this question.