PMP · Question #543
In a global project, the main definitions were developed in country A, and the delivery of the project will be completed in phases in countries B, C, and D. Country B discovers that one of the legal…
The correct answer is D. Identified the regulatory differences among the countries. To prevent overlooking legal requirements in a global project, the project manager should have proactively identified and documented the specific regulatory differences across all involved countries.
Question
In a global project, the main definitions were developed in country A, and the delivery of the project will be completed in phases in countries B, C, and D. Country B discovers that one of the legal requirements was not addressed. What should the project manager have done to avoid this situation?
Options
- AManaged risk mitigation strategies specific to each country.
- BAsked procurement to assign resources located in each country.
- CSelected countries that had similar regulatory requirements.
- DIdentified the regulatory differences among the countries.
How the community answered
(38 responses)- A8% (3)
- B16% (6)
- C3% (1)
- D74% (28)
Why each option
To prevent overlooking legal requirements in a global project, the project manager should have proactively identified and documented the specific regulatory differences across all involved countries.
While managing risk mitigation strategies is important, simply managing them without first identifying the specific risks (like regulatory differences) is insufficient for prevention.
Assigning local resources is a valuable strategy for understanding local nuances, but it's a resource management decision and doesn't explicitly guarantee that all regulatory differences will be identified and addressed without a dedicated process.
Selecting countries with similar regulatory requirements is a strategic business decision made before project initiation and is often not within the project manager's control once the project is underway.
In a global project spanning multiple countries, legal and regulatory environments can vary significantly. To prevent overlooking specific requirements in countries like B, C, or D, the project manager should have proactively identified and documented the regulatory differences among all involved countries during the planning phase. This ensures that the main definitions and project deliverables are compliant with all applicable local laws and regulations from the outset.
Concept tested: Global project risk management and regulatory compliance
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok/plan-risk-management
Topics
Community Discussion
5D is the correct answer here. The key phrase in the stem is "legal requirements," which in PMI-speak maps directly to Enterprise Environmental Factors and regulatory differences. If you're running a global project across four countries, identifying those regulatory gaps upfront during planning is what prevents a country from discovering a missed legal requirement mid-delivery. A is tempting because it sounds responsible, but you can't mitigate a risk you never identified in the first place. D comes first in the logical sequence, which is exactly how PMI wants you to think about it.
D is the giveaway: Different countries = Discover the Differences. Does anyone have a sticky hook for scope vs compliance gaps?
D is the right call here, though honestly A is tempting because it sounds more action-oriented. The giveaway is that the whole problem started during definitions in country A, so the root failure was never mapping the regulatory landscape across B, C, and D before work began.
Going with B here. The clue is the global, multi-country delivery setup, which screams "resource gap" rather than a pure planning omission. If procurement had assigned local resources in each country from the start, those in-country team members would have flagged the legal requirement in country B before it ever became a discovery. Option D sounds nice on paper, but identification alone does not fix the execution problem when the work is happening thousands of miles from where the definitions were built. Local resources are your frontline defense against missed compliance items, and that maps directly to the "manage project resources" domain.
Actually it is D, because the question is testing what went wrong in the planning phase, not execution. Sara is describing a solid mitigation for a gap that should never have existed in the first place.