Explanation
Plan driven approaches to business analysis practices most often use the formal type of communications. This means the communication of the actual requirements is in writing, and often uses pre-defined forms requiring signatory approvals. All project documentation is normally archived as part of the project history. Face-to-face is an effective communication method, but for plan-driven approaches, formal communication is preferred in regard to requirements. Ad hoc describes the sudden, quick conversations. This is an informal approach to communication and isn't appropriate for a plan-driven business analysis approach.

In order to use the matrix documentation approach to model requirements, the identified requirements must have the uniform structure of their characteristics and identification.
Answer A is incorrect. The requirements do no need to have opposing values to use the matrix documentation approach.
Answer B is incorrect. While this choice is tempting, the best answer is the uniform structure.
Answer D is incorrect. This isn't a valid answer, as requirements don't need rated goals.

Explanation
Beth is performing the assessment of organizational readiness. This task reviews the organization's ability to accept and use the solution.
Answer A is incorrect. Stakeholder management is not an applicable business analysis task for this scenario.
Answer C is incorrect. The task of defining transition requirements describes the process of moving from one solution to another.
Answer B is incorrect. Evaluation of solution performance is the task of reviewing current solutions for improvement.

Explanation
Cost-benefits analysis is not a valid technique that a business analyst may use in the requirements verification task. The three techniques for requirements verification are acceptance and evaluation criteria definition, problem tracking, and structured walkthrough.
Answer B is incorrect. Acceptance and evaluation criteria definition is a valid technique for requirements verification.
Answer D is incorrect. Problem tracking is a valid technique for requirements verification. Answer A is incorrect. Structured walkthrough is a valid technique for requirements verification.