Its A because they studied the impact and they need to submit a change request ( in the execution phase )

As long as it’s a traditional approach, you can’t make any changes to the scope without a change request.

You can change the scope now in execution phase and you don't kame a change request to avoid in the future. Look your register

Updating the scope of work cannot avoid the future delay, change request does.

Looks like D. as per similar questions before.

In this situation, the project manager should submit a change request (option A). The missing deliverable that impacts the critical path represents a change to the project's scope. By submitting a change request, the project manager can initiate the formal process of documenting, reviewing, and approving scope changes. This helps ensure that the impact of the missing deliverable is properly assessed, and necessary adjustments are made to the project plan to avoid future delays.

A. Submit a change request

You should submit change request forms any time they want to make changes that are likely to affect the scope, budget, or schedule of a project. Team members should fill out change request forms if they need additional resources or want to propose a change to the project plan.

For example you create a social network website . And you forget login page . After some deliverable completed you see key deliverable missed. I think Update the scope of work is good choice. no need go to CCB. it is key deliverable and you forgot or missed.

Adding a new scope element, even if it's a missing deliverable, can indeed have ripple effects on various aspects of the project. Analyzing the impact of scope changes is crucial to ensure that the changes are feasible, and their consequences are understood. In situations where a missing deliverable impacts the critical path and potential scope changes could have cascading effects, submitting a change request (Option A) is a more comprehensive and structured approach.

How can a project manager update the scope without a change request????! The scope is defined beginning of a project stage .and what is the risk management plan ?!! the potential risk affecting the project ! Is scope change a risk ?!!!! not its not. Only aswer "A" is the right choice

Is it a change request that would authorize change of scope.

Option C. The key here is: “ do to avoid future delays” update the project scope. Change request is to handle the situation now.

it says what should he do to avoid that is to manage risk if the qn was what should he do next, then ill choose A to extend the dateline due to change in cp

"A" makes more sense to me. The second best option is the risk management plan. Risk management plan helps you identify and manage identified and unidentified risks. This situation is an unidentified risk, the risk management plan will help you with how to manage unidentified risks. But since this is a key deliverable and we already know the impact on the critical path, the best path is to just submit the change request as soon as possible and then discuss it with the CCB.

C seems correct, as in the context of the question change request is probably referring to adding the missing deliverable, but it does not guarantee avoidance in future delays, revising the scope will.

To Avoid this in the future, a change request should have been initiated to update the scope of work.