PMP · Question #1020
A compliance strategy was created during the planning phase of a project. During execution, the project manager left the organization and another project manager was assigned to the team. What…
The correct answer is C. Review the compliance strategy and version history. A new project manager is assigned to an ongoing project and needs to ensure its compliance.
Question
A compliance strategy was created during the planning phase of a project. During execution, the project manager left the organization and another project manager was assigned to the team. What should the project manager do first to ensure the project is compliant?
Options
- AReview the organizational process assets (OPAs) for compliance topics.
- BMeet with the team to discuss compliance concerns.
- CReview the compliance strategy and version history.
- DMeet with the project sponsor to discuss their compliance concerns.
How the community answered
(33 responses)- A9% (3)
- B6% (2)
- C82% (27)
- D3% (1)
Why each option
A new project manager is assigned to an ongoing project and needs to ensure its compliance.
While organizational process assets (OPAs) contain general compliance policies, the project's specific compliance strategy document is the most relevant and detailed source for understanding its unique requirements.
Meeting with the team is important for understanding current practices, but the project manager should first independently review the documented strategy to gain a foundational understanding before discussing it with the team.
For a new project manager taking over an ongoing project, the immediate priority to ensure compliance is to thoroughly understand the project's specific compliance requirements and its history. Reviewing the previously created compliance strategy and its version history provides the most direct and accurate information regarding the project's agreed-upon compliance standards, implementation plans, and any past changes or issues.
The project sponsor can offer high-level insights into compliance priorities, but the detailed requirements and implementation plans are contained within the project's compliance strategy document.
Concept tested: Project handover and compliance documentation review
Topics
Community Discussion
6
Mei-Ling H.Jul 5, 2026C is correct here. The key word in the stem is "first", and since a compliance strategy was already created during planning, the new project manager must review that existing artifact before doing anything else. Checking the version history is also critical because it shows what changes occurred and gives context on why decisions were made before the previous manager left. Option A is a trap because it skips the project-specific strategy that already exists, while B and D are good steps but only come after you understand the current plan.
Samuel O.Jul 5, 2026Took over a project last year, first thing I did was read the existing compliance strategy. C.
Luis F.Jul 5, 2026C is the right call here. The new PM needs to review the existing compliance strategy and its version history first before doing anything else, since that document was already created during planning and shows how the approach evolved. Jumping straight to meetings with the team or sponsor without understanding what was already decided would waste time and maybe cause confusion. I actually got this exact scenario on my PMP attempt last spring and almost picked B because it felt like the collaborative move. Then I remembered the PMBOK emphasis on reviewing existing project artifacts before taking action, so I went with C and it was correct.
Nina C.Jul 5, 2026C is right. Review what was already created before reinventing the wheel.
Wei W.Jul 5, 2026Leaned toward B first but a strategy already exists so review it first, C.
Nina C.Jul 7, 2026Agreed, C makes sense since you always evaluate the existing strategy before creating a new one, but watch out if the question says the current strategy is outdated or noncompliant because then the answer shifts to B.