PMP · Question #665
A software development project completed the initiation phase. The technical design was approved by the project steering committee. Later, it was discovered that the design will impact the company's p
The correct answer is C. Log the technical design delay as a risk in the project risk log.. The project manager must first log the newly identified design flaw and potential delay as a risk to formally capture and begin managing this significant project threat.
Question
Options
- ASet up a steering committee session to review the project delay.
- BContinue with the approved design so that the project is not delayed.
- CLog the technical design delay as a risk in the project risk log.
- DAsk the steering committee to approve a new technical design.
How the community answered
(26 responses)- A12% (3)
- B8% (2)
- C77% (20)
- D4% (1)
Why each option
The project manager must first log the newly identified design flaw and potential delay as a risk to formally capture and begin managing this significant project threat.
Setting up a steering committee session is a subsequent step after the risk has been analyzed and potential solutions or impacts are understood, not the immediate first action.
Continuing with a design known to impact the production system is irresponsible and could lead to severe operational issues, directly contravening project objectives.
When a new issue arises that could significantly impact the project (like a design flaw leading to a 3-month delay), the project manager's first step is to formally identify and log it as a risk in the project risk log. This ensures it is documented, analyzed, and managed through the project's risk management processes.
Asking for approval of a new design is premature; the problem needs to be formally documented as a risk, analyzed, and potential solutions developed before seeking approval.
Concept tested: Risk identification and logging
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
8
Nina C.Feb 5, 2026C is correct here. Before you escalate or ask for approvals on a new design, you need to log the potential three month delay as a risk in the risk register. The steering committee already approved the original design, so any change to that baseline has to go through a formal change process, and that process starts with documentation. As a teacher I learned you always write down the problem before bringing it to the principal, same idea here.
Toby R.Jan 25, 2026Took it last month, picked C since it's an identified issue now, not a future risk.
Yusuf A.Jan 27, 2026That logic tracks Toby, but worth keeping in mind that some question banks treat identified issues still without a plan as risks until they get logged as issues, so watch the exact wording.
Yusuf A.Feb 11, 2026Leaned toward A but my senior said log the risk first before escalating.
Ingrid P.Feb 13, 2026Good call by your senior because the risk register is the artifact they test on, but note that logging and escalating are often the same exam answer when the risk crosses your authority threshold, so make a card that pairs trigger equals exceeds authority with action equals escalate after logging.
Lena V.Feb 1, 2026C is correct because the exam always wants you to log newly identified issues as risks before escalating or acting. Saw this on my exam last month, nearly picked A because a 3 month delay screams escalate, but the keyword is "discovered" which means new risk first, then figure out the response.
Yusuf A.Feb 2, 2026One of the seniors on my team said the same thing, but he also mentioned to watch out if the question says the issue is already in the risk register, because then the answer flips to executing the planned response instead of logging it again.
Ingrid P.Feb 15, 2026C is correct, and I had this exact scenario on my exam last month. The key is that a potential 3 month delay is a future event, so it goes in the risk log first, then you escalate. A lot of people jump straight to D, but you cannot ask the steering committee to approve a new design before you have even documented the risk and analyzed alternatives. I made a flashcard for this one: if the impact has not happened yet, log the risk; if it has already occurred, log an issue.