PK0-005 Exam Dumps : CompTIA Project+ Certification (2026)

A gantt chart is a visual representation of a project timeline that shows the tasks, durations, dependencies, and resources of a project in a horizontal bar chart format. A gantt chart can help a project manager to calculate the progress of the whole project scope by comparing the planned and actual start and finish dates of each task, as well as the percentage of completion and the critical path. A gantt chart is also a useful tool for communicating the project status and performance to the sponsor and other stakeholders. Therefore, the first document that the project manager should update to calculate the progress of the whole project scope is the gantt chart. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Schedule Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 6: Schedule Management2; What Is a Gantt Chart? 7 Examples for Project Management3

Because the regulatory change is anticipated (“coming in the next month”) and has not yet impacted the project, it should be treated as a risk (a potential future event) rather than an issue (a current problem). The correct next step is to add the risk to the risk register so it can be assessed for probability/impact, assigned an owner, and have response actions planned (avoid/mitigate/transfer/accept and contingency plans). This aligns with CompTIA Project+ risk management expectations: using the risk register to capture and manage upcoming threats that could affect scope, schedule, cost, or compliance obligations.

The other options don’t fit “next.” An issue log is for something that is already occurring and needs resolution now. A CCB is used when a specific change request is ready to be evaluated/approved, but at this point the PM needs to first understand the regulatory impact and options (which begins with risk capture and analysis). A work-around is a temporary fix for an active problem, which does not apply to an upcoming regulatory change. The PM should document the risk, analyze impact, and then—if needed—raise change requests once requirements and compliance impacts are clear.

A change log is a document that records and tracks the changes that are made to the project scope, schedule, budget, or quality. It helps the project manager to monitor and control the project performance and ensure that the changes are aligned with the project objectives and stakeholders’ expectations. A change log can also include information such as the change description, impact, status, approval, and date. A change log is the best source for the PM to use to confirm the assertion that the functionality request was rejected during the planning phase, as it would show the details and reasons for the rejection12.