Explanation
Requirements allocation typically begins early in the project lifecycle (as soon as the solution approach is determined) and will continue to be performed until all valid requirements are allocated. Allocation typically continues through design and construction of a solution.
Answer C is incorrect. Requirements allocation doesn't have to wait until the project has been chartered.
Answer B is incorrect. Approval of the requirements is good, but the solution scope for the requirements
needs to be created to begin allocating the requirements.
Answer A is incorrect. The budget creation isn't linked to the requirements allocation process.

Explanation
According to the BABOK® Guide, requirements allocation is "the process of assigning stakeholder and solution requirements to solution components in order to provide a common understanding of the scope and value of each component" (p. 36). The business analyst and the organization should start requirements allocation as soon as the solution approach is determined, which is the output of the Define Future State task in the Strategy Analysis knowledge area. The solution approach defines the "overall direction for how the organization will achieve the desired future state" (p. 30). By allocating requirements to solution components based on the solution approach, the business analyst and the organization can ensure that the requirements are aligned with the business objectives and deliver value to stakeholders. References:
CCBA® Handbook, p. 11
BABOK® Guide, p. 30, 36

An interview is a systematic approach. It is used for eliciting information from a person or a group of people in an informal or formal setting by talking to an interviewee, asking relevant Questions, and documenting the responses. Interviewees are also able to identify other stakeholders.
Answer C is incorrect. Acceptance and evaluation criteria are useful for identifying who has the authority to accept or reject solutions.
Answer D is incorrect. Risk analysis is the study of the probability, impact, and scoring of identified risk events. Risk analysis is the science of risks and their probability and evaluation in a business or a process. It is an important factor in security enhancement and prevention in a system. Risk analysis should be performed as part of the risk management process for each project. The outcome of the risk analysis would be the creation or review of the risk register to identify and quantify risk elements to the project and their potential impact.
Answer B is incorrect. User stories are useful to capture requirements, stakeholder attitudes, and for identifying actors and roles.

Explanation
Voice mails are not a valid method for documenting elicitation because they are not reliable, consistent, or traceable. Voice mails can be easily deleted, distorted, or misunderstood. They do not provide a clear record of the elicitation results, nor do they allow for verification, validation, or feedback from the stakeholders. The other methods, such as whiteboards, audio recordings, and written documentation, are valid methods for documenting elicitation because they can capture the information, insights, and agreements from the elicitation activities in a more structured, accessible, and transparent way12. References:
1: BABOK® Guide, Version 3.0, p. 39
2: Business Analysis Elicitation and Collaboration (IIBA -ECBA)