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

A Preliminary Scope Statement outlines the initial project objectives, high-level requirements, and milestones. It serves as a foundational document during the initiation phase and is refined as the project progresses.

As per the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Compare and contrast different project management roles and responsibilities, developing a preliminary scope statement is a key activity in defining the project's direction and scope.

Zero-based budgeting involves starting from a “zero base” and justifying each expense without reference to previous budgets. This budgeting method promotes financial discipline and aligns with CompTIA Project+ guidelines on budget control and justification.

A burndown chart tracks how much work remains over time in an iteration (or release). The most direct inputs are the remaining work and the work completed (often expressed as tasks, story points, or hours). Therefore, to obtain burndown data efficiently, the PM should analyze remaining and completed tasks. This aligns with CompTIA Project+ Agile metrics concepts, where burn charts are used to visualize progress and forecast completion based on work remaining versus time.

The other options are not primary burndown inputs. “Number of people available” affects capacity and can influence how fast work burns down, but it is not what the chart directly measures. “Cost variance” is an earned value / financial control concept (more predictive/traditional) and not what burndown charts are built from. “Number of issues registered” is useful for quality and risk/issue tracking but does not represent the work remaining in the sprint backlog unless issues are explicitly counted as backlog items—and even then, the chart is still fundamentally about remaining work, not raw issue counts.

So, for efficient burndown extraction, the PM should use the team’s work tracking (sprint backlog/task board) to calculate remaining vs. completed tasks/work, which is exactly what the burndown visualizes.

The project manager should distribute an agenda before a call to ensure all meeting items are addressed and the correct participants attend. An agenda is a document that outlines the purpose, topics, and objectives of a meeting. It also includes information such as date, time, duration, location, attendees, and roles. Distributing an agenda can help to prepare the participants for the meeting, set clear expectations, and facilitate a productive and focused discussion12

When implementing an IT infrastructure change that takes risks into consideration, the project manager should develop a rollback plan. A rollback plan is a contingency plan that outlines the steps that need to be taken in case the change does not work as expected. It includes a plan to roll back the changes and restore the system to its previous state. References: CompTIA Project+ Study Guide Section 3.3.

The project manager should develop a rollback plan when implementing an IT infrastructure change that takes risks into consideration. A rollback plan is a contingency plan that describes how to revert back to the previous state of the system in case of a failure or disruption during the change implementation. A rollback plan can help to minimize the impact of the change on the system performance and availability and ensure business continuity and data integrity.

CI/CD (Continuous Integration/Continuous Deployment) allows faster and more reliable delivery by automating builds, tests, and deployments. It ensures rapid delivery without compromising quality. Updates are frequent but not necessarily tied to sprint cycles.