PMP · Question #1077
During a project gate review meeting, it is identified that one of the project deliverables will require corrective actions to meet the project quality requirements. What should the project manager…
The correct answer is B. Update the issue log. identify the involved stakeholders, and assign resources to the corrective. During a gate review, a project deliverable is found to require corrective actions to meet quality requirements.
Question
During a project gate review meeting, it is identified that one of the project deliverables will require corrective actions to meet the project quality requirements. What should the project manager do first?
Options
- ASubmit a change request to update the project quality requirements for the involved project
- BUpdate the issue log. identify the involved stakeholders, and assign resources to the corrective
- CUpdate the risk register and implement the approved risk response plan for quality deviations.
- DIdentify the resources that were responsible for the deliverable and request a team development
How the community answered
(33 responses)- A9% (3)
- B73% (24)
- C15% (5)
- D3% (1)
Why each option
During a gate review, a project deliverable is found to require corrective actions to meet quality requirements.
Submitting a change request to *update* quality requirements would be an attempt to lower standards, which is generally not the appropriate first response to a quality deviation; the goal should be to meet the existing quality requirements.
When a deliverable fails to meet quality requirements, it becomes an identified issue that needs tracking and resolution. Updating the issue log is the immediate first step to formally record the problem, followed by identifying relevant stakeholders and assigning resources to initiate the corrective actions necessary to bring the deliverable up to standard.
While quality deviations can sometimes stem from risks, this is an *identified issue* with a deliverable, not a potential future event (risk). Implementing a risk response plan is for *unrealized* risks, not *realized* issues that have already occurred.
Identifying responsible resources and requesting team development may be a longer-term solution if a skill gap is found to be the root cause, but the immediate priority is to address the specific deliverable and its quality defect.
Concept tested: Quality management, issue management, corrective action
Topics
Community Discussion
5
Wei W.Mar 22, 2026B is correct because a deliverable failing quality requirements at a gate review is an issue, and the first move is always to log it, figure out who is impacted, and get the right people on the fix. The other options either paper over the problem by lowering the bar, jump ahead to risk responses when the issue is already here, or look backward for someone to blame instead of forward toward a working increment.
Nina C.Mar 30, 2026Going with B. Does anyone know if corrective actions always require a change request first?
Mei-Ling H.Mar 16, 2026First leaned toward A but corrective actions always need a change request, so B.
Bao N.Mar 26, 2026Going with D here. Corrective actions during a gate review mean someone missed the quality bar, so root cause starts with the team that produced the deliverable and addressing their gaps is the logical first move before touching logs or registers.
Mei-Ling H.Mar 28, 2026B is correct because the question asks about what the project manager does during the gate review itself, and documenting the corrective actions in the issue log or change register is the immediate step, not investigating root cause which comes after. The qualifier word here is 'during', which points to the documentation action, while D describes a follow-up activity that happens later.