When identifying key customer business, technical, and system requirements for an HPE Edge- to-Cloud solution, which of the following is a key activity?

Question

Options

• ADocumenting every possible requirement, regardless of its relevance to the solution
• BGathering requirements from a single stakeholder to avoid conflicting inputs
• CPrioritizing requirements based on their potential impact on the solution outcomes
• DAvoiding any requirements that are difficult to implement

• A
  9% (3)
• B
  3% (1)
• C
  85% (29)
• D
  3% (1)

Explanation

Prioritizing requirements based on their potential impact on solution outcomes (C) is correct because effective requirements gathering isn't about volume - it's about identifying what matters most to deliver a solution that meets business goals, technical constraints, and system needs within realistic constraints.

Why the distractors fail:

• A is wrong because documenting every possible requirement wastes time and dilutes focus on what actually drives the solution - quality beats quantity.
• B is wrong because relying on a single stakeholder creates blind spots; HPE solutions typically span business, technical, and operational teams, all of whom have distinct but equally valid requirements.
• D is wrong because avoiding difficult requirements means ignoring real needs - complexity is a challenge to manage, not a reason to skip a requirement.

Memory tip: Think of requirements gathering like packing for a trip - you don't pack everything you own (A), you don't ask only one person what you need (B), you don't leave behind rain gear just because it's bulky (D) - you pack what will have the biggest impact on the trip's success (C).

No community discussion yet for this question.