PMP · Question #496
A project manager has been managing a highly complex project. The project manager has ensured that all of the required tasks have been completed. During a recent external audit. The project manager wa
The correct answer is D. Ensured that all the required approvals were received per the organizational procedures. To prevent penalties and liabilities from new implementations, the project manager must ensure all required organizational approvals are obtained, as these often cover compliance, legal, and operational standards.
Question
Options
- AEnsured that all defects identified during testing were resolved before implementation
- BEnsured that all of the required tasks identified in the scope were completed successfully
- CEnsured that all documentation was completed post implementation before closing the project
- DEnsured that all the required approvals were received per the organizational procedures
How the community answered
(46 responses)- A2% (1)
- B7% (3)
- C13% (6)
- D78% (36)
Why each option
To prevent penalties and liabilities from new implementations, the project manager must ensure all required organizational approvals are obtained, as these often cover compliance, legal, and operational standards.
Resolving defects is essential for quality, but it doesn't directly address compliance with organizational procedures or external regulations that might lead to penalties even if the code is functional.
Completing tasks identified in the scope ensures scope adherence, but scope might not explicitly cover all compliance or regulatory approval steps necessary to avoid penalties.
Completing documentation post-implementation is important for project closure and maintenance, but it doesn't prevent penalties for non-compliance that should have been addressed prior to or during implementation.
Liabilities and penalties often arise from non-compliance with regulatory, legal, or organizational standards. Ensuring all required approvals are received per organizational procedures confirms that the implementation meets all necessary internal and external requirements, thus mitigating the risk of penalties. These approvals act as a formal sign-off that the implemented module complies with all relevant standards and policies.
Concept tested: Ensuring compliance and formal approvals
Source: https://www.pmi.org/pmbok-guide-standards/lexicon/project-governance
Topics
Community Discussion
6
Grace U.Jul 3, 2026D is correct here. The key word is liabilities, and the only way to protect against that is making sure the right people signed off per organizational procedures before you implemented, not just that the tasks themselves were done.
Zlatan X.Jul 5, 2026D is the answer. Why does approval per organizational procedures matter more than defect resolution for liability?
Orla P.Jun 20, 2026I first leaned toward A since unresolved defects sound like a surefire way to get penalized, but the key word in the stem is liabilities. Organizational procedures and formal approvals are what legally protect you from external penalties, so D is the move.
Grace U.Jun 21, 2026Good catch on the liability framing, and I would just add that unresolved defects get flagged as risks to monitor during transition rather than blocking the move to production.
Brenda K.Jun 28, 2026B is the right call here because the stem literally tells you all required tasks were completed, which points straight back to scope completion as the core control. This is a quick read too, maybe 45 seconds, so bank it and move on.
Orla P.Jun 29, 2026D is correct here because completed tasks means you are checking against the scope baseline to formally accept deliverables, not just confirming completion. Brenda is close but scope validation is about stakeholder acceptance, which is the control that matters once the work is done.