Which of the following statements best describes the purpose of the confirm elicitation results process?

Validating requirements against a proposed solution is part of solution validation or acceptance testing, which occurs later in the lifecycle and is a separate activity from confirming elicitation results.

The confirm elicitation results process is specifically designed to close the gap between what stakeholders expressed and what they truly intended, ensuring captured requirements reflect actual needs. This step involves reviewing elicitation outputs with stakeholders to confirm accuracy, completeness, and correct interpretation. Without this confirmation, misunderstandings can propagate undetected into design and development, leading to costly rework.

Comparing stated requirements to documented requirements is an internal consistency review, not the purpose of confirming elicitation results, which focuses on alignment with stakeholder intent.

Validating requirements against project scope is a scope management activity, not the purpose of the confirm elicitation results process, which centers on stakeholder intent verification.