The number and impact of change requests often increase towards the end of the project, as this is the stage where the solution is tested, validated, and deployed, and the stakeholders may discover new or changing needs, expectations, or issues that require modifications to the solution12. Change requests are formal proposals for altering the requirements, deliverables, or processes of the project or the solution3. Change requests can have positive or negative effects on the project scope, schedule, budget, quality, or benefits, and they need to be managed and controlled effectively4. The other options are not stages where the number and impact of change requests often increase, as they either occur earlier in the project life cycle, where the changes are less likely or less costly, such as during project planning (A), once the project scope is reviewed (B), or at the launch of the project (D), or they are not relevant to the CCBA certification, which is based on the BABOK® Guide, which does not mention change requests as a technique or a task. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™ (CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, The Ultimate Guide to Business Capability Analysis, [A GUIDE TO THE BUSINESS ANALYSIS BODY OF KNOWLEDGE]