Pass the CompTIA Project+ PK0-005 Questions and answers with CertsForce

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.

An issue log is a tool that records and tracks any issues that arise during the project. It helps the project manager to identify, prioritize, assign, monitor, and resolve the issues in a timely manner. An issue log can also include information such as the issue description, impact, status, owner, and resolution date1. An issue log is different from a defect log, which records and tracks the defects or errors in the project deliverables. A risk register is a tool that records and tracks the potential risks that may affect the project objectives. A change log is a tool that records and tracks the changes that are made to the project scope, schedule, budget, or quality2.

 The project manager should make an impact assessment after being informed that the delivery of required IT equipment will be delayed. An impact assessment is a process of analyzing and evaluating how a change or an issue may affect the scope, schedule, cost, quality, or risks of a project. An impact assessment can help to determine the severity and implications of the delay on the project objectives and deliverables and identify any possible alternatives or corrective actions to minimize or avoid its negative effects.

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 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

This work is best described as current state vs. future state analysis. The team first examined the existing process (the current state), identified areas of improvement (gaps/pain points), and then defined the desired outcomes (the future/target state). In CompTIA Project+ discovery/concept preparation activities, teams are expected to understand the problem/opportunity clearly before planning the solution; comparing the current state to the desired future state is a standard way to define what must change and what “better” looks like, and it becomes a foundation for scope definition and transition planning.

It’s not “process improvement” as the primary label here because that term typically describes the initiative type or the resulting actions, while the question is asking what the analysis itself is called. It’s also not “business objectives” (those are broader strategic goals), and it’s not “project success criteria” (the measurable conditions used to judge success). Those may come later, derived from the current-vs-future gap, but the described activity is the gap comparison between how things work now and how they should work after the project.

Mitigate is a risk strategy that involves taking actions to reduce the probability or impact of a risk. By applying new updates to a program in a sandbox environment, the software engineer is testing the changes before implementing them in the actual system, thus minimizing the chance of errors or failures that could affect the project1.

Infrastructure as a service (IaaS) offers administrators more direct control over operating systems than other cloud service models. IaaS is a type of cloud computing service that provides virtualized computing resources such as servers, storage, network, and operating systems over the internet. IaaS allows users to rent or lease infrastructure resources on demand and pay only for what they use. IaaS gives users more flexibility and control over their infrastructure resources and enables them to configure, manage, and customize their operating systems according to their needs and preferences3

Transfer is a risk management strategy that involves shifting the responsibility or impact of a risk to a third party, such as an insurance company, a vendor, or a contractor1. By buying an extended warranty for a set of servers, the project manager is transferring the risk of server failure or malfunction to the warranty provider, who will cover the cost of repair or replacement in case of a risk event. This way, the project manager reduces the exposure and liability of the project to the risk, while still retaining some level of accountability and oversight2. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 8: Planning Projects Part 4, page 245; 4 Risk Management Strategies for Successful Project Execution, Risk transferring section; How to Manage Project Risk: A 5-Step Guide, Risk treatment section.