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

The dependency between software installation and desktop installation is a mandatory dependency. A mandatory dependency is a type of dependency that is inherent in the nature or logic of the work and cannot be avoided or changed. It is also known as a hard dependency or a hard logic dependency. A mandatory dependency means that one task must be completed before another task can start or finish. For example, software installation can only start after desktop installation is finished5

The dependency between desktop installation and software installation represents a mandatory dependency. A mandatory dependency is a type of task dependency that is inherent in the nature of the work being performed. In this case, software installation cannot begin until desktops are installed and powered on, and therefore, the dependency is mandatory. References: CompTIA Project+ Study Guide, Chapter 3: Project Integration Management, Objective 3.1: Identify the project management processes and the interactions between them.

Scrum is an Agile framework that is well-suited for projects with rapidly changing requirements. It operates in iterative cycles called sprints, allowing for regular reassessment and adaptation of project goals. This flexibility makes Scrum ideal for environments where the company ' s strategy and product requirements evolve frequently, as it facilitates continuous improvement and responsiveness to change.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.2: Compare and contrast Agile vs. Waterfall concepts, Scrum is highlighted as a methodology that supports adaptability and iterative development.

The buyer faces the most risk under a cost-plus percentage of cost (CPPC) contract because the seller’s fee is a percentage of actual costs. That structure creates a perverse incentive: if costs rise, the seller’s profit rises too—so the buyer has the greatest exposure to overruns and the weakest built-in cost-control motivation on the seller side. Procurement guidance commonly flags CPPC as especially risky for buyers for exactly this reason.

By comparison, cost-plus-fixed-fee (CPFF) still leaves the buyer paying allowable costs, but the seller’s fee is fixed (less incentive to inflate costs). Cost-plus-incentive fee (CPIF) ties part of the fee to performance/cost targets, sharing risk and encouraging cost control. Finally, firm fixed-price (FFP) places the cost overrun risk primarily on the seller, because the price is set unless scope changes. PMI’s contract overview notes fixed-price provides the buyer defined cost (assuming scope is well-defined), which reduces buyer risk relative to cost-reimbursable models.

Therefore, among the options, CPPC is the clearest “highest buyer risk” contract type.

A business case provides justification for undertaking a project, programme or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution. A business case is essential for demonstrating the value of the project and securing the approval and funding from the governance. A business case is different from a scope statement, which defines the project boundaries and deliverables; a sponsor request, which initiates the project idea and seeks support; and a project charter, which authorizes the project and assigns the project manager. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 3: Initiating Projects; What is business case? | APM

An Ishikawa diagram, also known as a fishbone diagram, is a tool used to identify and analyze the root causes of a particular problem. CompTIA Project+ references this tool as essential for quality management and problem-solving.

A dashboard is the most appropriate artifact to share when a stakeholder asks for project performance data. Dashboards are designed to present key performance indicators (KPIs) and trends in a concise, visual form—such as schedule progress, scope completion, burn/burndown, budget status, risks/issues summaries, and other metrics relevant to project health. This aligns with Project+ expectations around performance monitoring and communicating status in an efficient way tailored to stakeholder needs.

An issue log is too granular and focuses only on current problems; it is part of performance, but it’s not the overall performance view stakeholders typically want. A WBS is a scope decomposition artifact used for planning and organizing work, not performance reporting. A milestone chart shows key dates and whether major points are achieved, but it does not provide comprehensive performance data (cost, trend, throughput, overall health).

Therefore, to provide performance data effectively—especially for stakeholders who want quick, up-to-date visibility—the PM should send (or grant access to) the project dashboard, ensuring it reflects the latest reporting period and includes the metrics the stakeholder cares about.

An audit conducted years after closure most commonly requires archived documentation because auditors typically need the full evidence trail of what was approved, executed, delivered, and controlled (plans, baselines, change logs, issue logs, risk registers, approvals, communications, testing evidence, acceptance/sign-off, financials, etc.). CompTIA Project+ explicitly lists “Archiving documentation” as a key project closing activity, and the CompTIA certification page also highlights project closing as including archiving documentation.

While signed contracts (A) can be part of that evidence set, they are only one subset of what an audit may request. A project closeout report (C) is useful as a summary, but auditors often need the underlying artifacts that support the report’s claims. Lessons learned (D) may be reviewed for process maturity, but it’s not usually the primary evidence package for compliance, financial, or governance verification.

Because the scenario emphasizes the long time gap (“years after”), archiving is the key: it ensures records are retained, retrievable, and complete for governance, compliance, and validation needs well beyond the project’s end date.