PMP · Question #1334
A project manager determines that a critical path activity is going to be delayed. The team proposes a fallback plan that could get the project back on track; however, the plan would require an additi
The correct answer is C. Evaluate the fallback plan proposed by the team and submit a change request, if required.. When a critical path activity is delayed and the team proposes a costly fallback plan, the project manager should evaluate it and follow formal change control procedures.
Question
Options
- AAdd additional resources to the project to fast track certain activities and reduce delays.
- BCommunicate the delay to stakeholders and maintain the existing budget baseline.
- CEvaluate the fallback plan proposed by the team and submit a change request, if required.
- DUse the existing budget for executing the fallback plan and update the baseline.
How the community answered
(48 responses)- A10% (5)
- B2% (1)
- C83% (40)
- D4% (2)
Why each option
When a critical path activity is delayed and the team proposes a costly fallback plan, the project manager should evaluate it and follow formal change control procedures.
Adding additional resources without proper evaluation and change control could exacerbate the budget issue and is not the first step.
While communicating delays to stakeholders is necessary, maintaining the existing budget baseline while implementing a costly plan is contradictory and not a viable solution.
When a fallback plan requires additional cost, it likely impacts the project's cost baseline and potentially other baselines. The project manager must thoroughly evaluate the plan's feasibility and impact, and if it deviates from the approved plan, a formal change request must be submitted to the Change Control Board (CCB) for review and approval.
Using existing budget for a costly fallback plan and updating the baseline without formal change request submission and CCB approval bypasses proper project governance and control.
Concept tested: Change control process for budget impacts
Source: https://learn.microsoft.com/en-us/project-management/change-management-project-plan
Topics
Community Discussion
8
Yusuf A.Jan 11, 2026C is the answer here. My senior PM always says any fallback that touches cost or schedule has to go through formal change control, you cant just spend money you didnt plan for. The team proposing the idea is great but the PM needs to evaluate it first and then submit a change request if it makes sense. D is the trap because it skips the whole Integrated Change Control process, and A assumes fast tracking will work without evaluating what the team actually proposed.
Bao N.Jan 12, 2026Agree on C but Yusuf undersells why A is the trap: fast tracking sounds proactive but the team proposed a specific fallback, not a schedule compression technique, so you evaluate their idea first not swap in your own.
Lena V.Dec 18, 2025C is correct but the stem is almost too obvious with "fallback plan" pointing you straight to change request territory. D is the trap - you cant just burn through contingency reserves and silently update the baseline without going through Integrated Change Control.
Nina C.Dec 19, 2025Agreed on C, but I would add that D also trips people up because contingency reserves are part of the cost baseline already, so spending them does not require a baseline change, whereas dipping into management reserves does.
Bao N.Jan 3, 2026C is the right call here but the wording bugs me because if the fallback plan is required then the change request is not optional. D is the trap people fall for since it sounds proactive but you cannot just burn the budget and rebaseline without going through change control.
Lena V.Jan 4, 2026Bao is right on C and correct that D skips change control, but the wording bugs me less when you remember that a fallback plan being required is exactly what makes the change request mandatory rather than optional.
Toby R.Jan 6, 2026C on my exam last month. Doesnt the fallback plan count as a reserve or a CR?
Nina C.Jan 24, 2026C is the answer here because the fallback plan means a change to cost or schedule, and any change like that goes through the change control process before you touch the budget. The PM evaluates the team's proposal first, then submits a change request if it makes sense. D is the trap because you cannot just spend money on a fallback plan and retroactively update the baseline without approval. Saw this exact scenario on my exam last month and the wording was nearly identical, the fallback plan and tight budget language is your clue that a change request is coming.