PMP · Question #569
A major public-transportation construction project is aimed at significantly reducing emissions. The project has been severely delayed due to noncompliance with environmental codes and bylaws. What sh
The correct answer is D. Mapped environmental compliance requirements, identified risks to achieving them, and prepared. To prevent delays from non-compliance with environmental codes, the project manager should have proactively identified all compliance requirements, assessed associated risks, and prepared mitigation strategies.
Question
Options
- AAppointed a senior environmental compliance officer to report directly to the project manager.
- BApproached the regulator for a partial waiver in light of the environmental importance of the
- CIncorporated sufficient schedule reserves based on similar delays in past projects.
- DMapped environmental compliance requirements, identified risks to achieving them, and prepared
How the community answered
(42 responses)- A2% (1)
- B12% (5)
- C7% (3)
- D79% (33)
Why each option
To prevent delays from non-compliance with environmental codes, the project manager should have proactively identified all compliance requirements, assessed associated risks, and prepared mitigation strategies.
While appointing a compliance officer is a good step, simply having an officer doesn't guarantee prevention unless a systematic process for mapping requirements, identifying risks, and preparing strategies is also in place.
Approaching a regulator for a waiver is a reactive measure and depends on external approval; it does not represent proactive prevention of non-compliance.
Incorporating schedule reserves addresses the symptom (delay) by adding buffer time, but it does not prevent the root cause of the delay, which is the non-compliance itself.
Mapping environmental compliance requirements, identifying risks to achieving them, and preparing mitigation strategies is a proactive risk management approach that directly addresses potential non-compliance issues before they cause delays. This involves understanding legal obligations, potential obstacles, and developing plans to ensure adherence or address deviations effectively.
Concept tested: Proactive risk management and compliance
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/project-risk-management
Topics
Community Discussion
6D is the right call here. Mapping compliance requirements and tying them to identified risks is exactly what risk management in the Planning process group is all about, and that proactive step is what keeps you from getting blindsided by code violations later.
Agreed on D, and I would add that the group also flagged how the word "identified" in the stem is the real giveaway, since it tells you the risks already exist and just need mapping rather than discovery.
D is correct. Compliance requirements are constraints you map as risks before they sink your schedule.
Agreed on D, and the flip side is that compliance constraints can also drive positive risk opportunities like fast-tracking approvals if you engage auditors early in planning.
Our group landed on A because someone needed to own environmental compliance directly and flag issues early, not wait for delays to surface. A few folks argued for D saying the PM should map requirements and risks proactively, but the core failure here is accountability, not planning, so weigh in if you see it differently.
D is correct because the PM owns mapping requirements and risks proactively across the project, and the compliance failure here stems from nobody doing that upstream work, not from a missing role assignment. Assigning an owner in A treats the symptom after the fact when the PMBOK expectation is that the PM identifies regulatory requirements and their associated risks during planning.