PMP · Question #382
During a documentation audit of an international company, it was identified that the last version of the project schedule was from one month ago even though the project manager knew it was recently up
The correct answer is D. Kept documentation in the project management information system (PMIS), and shared it with. To ensure accurate and current documentation, the project manager should have kept the project schedule and other documentation in a Project Management Information System (PMIS) and ensured its timely sharing.
Question
Options
- AUpdated the project management plan regularly and had it securely shared with all stakeholders
- BAssigned a project team member to ensure all project documentation was updated
- CReviewed the risk register to identify a response plan for the audit
- DKept documentation in the project management information system (PMIS), and shared it with
How the community answered
(22 responses)- A5% (1)
- B9% (2)
- C5% (1)
- D82% (18)
Why each option
To ensure accurate and current documentation, the project manager should have kept the project schedule and other documentation in a Project Management Information System (PMIS) and ensured its timely sharing.
While regular updates are important, simply sharing updated plans doesn't guarantee the *latest* version is easily accessible or identifiable for an audit without a proper system.
Assigning a team member is a task delegation, but it doesn't specify *how* documentation is managed and made accessible to ensure auditors find the correct version.
Reviewing the risk register for an audit response plan addresses the *symptom* of the audit finding, not the underlying *cause* of outdated accessible documentation.
A Project Management Information System (PMIS) is designed to centralize, manage, and make readily available the latest versions of all project documentation, including schedules. Utilizing a PMIS ensures that audits find the most current and approved information, preventing discrepancies.
Concept tested: Project documentation management and PMIS utilization
Source: https://learn.microsoft.com/en-us/project/project-management-information-system
Topics
Community Discussion
8D is the answer here. One of the senior PMs at my company told me the PMIS is basically your single source of truth, and if documents are not stored and shared from there, people end up looking at stale versions. The question points to a version control problem since the schedule was actually updated but the audit found an old copy. Option A sounds okay but the PMIS is the specific tool the exam wants for managing and distributing project records.
D is correct but that trailing comma in the text is sloppy exam writing. A is the tempting distractor because regular PM plan updates sound right, but the scenario is about schedule version control and single source of truth, which is the PMIS.
Agreed on D and the PMIS angle, though I would push back slightly on calling A a distractor since our group felt it was less about PMIS being the only right answer and more about A being wrong because it describes a generic process instead of the tool that actually enforces version control.
Saw this one on my exam last month and a bunch of us in the study group landed on D because the PMIS is the single source of truth for project docs, which explains why the latest schedule was not accessible to the auditors. A few folks in our group went with B at first since delegating doc updates sounds practical, but the real issue is where the documentation lives and how it gets shared, not who updates it. Anyone else run into this one recently and want to weigh in?
One of the seniors on my team said the same thing, that PMIS as the single source of truth is the fix here, though he also mentioned the question sometimes throws in language about version control to trip you up, so watch for that angle too.
Leaned toward A first but PMIS is the keyword for version control here.
PMIS is the right call but the deeper giveaway is that version control implies a system of record for artifacts, not just a communication channel.
D is the right call here, though the option cuts off mid-sentence on most versions of this question. The PMIS is your single source of truth, so if people are looking at stale schedules, that is a version control and access problem, not a documentation quantity problem. A is tempting because regular updates sound responsible, but updates mean nothing if stakeholders cannot find the current version.