Free Practice Questions for CompTIA PK0-005 Exam

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 gate review is a type of meeting that evaluates the completion and quality of a project stage and decides whether the project can proceed to the next stage. A gate review is a formal governance step that involves reviewing the goals, progress, risks, deliverables, and benefits of the project, and discussing if the project is still aligned with the business strategy and stakeholder expectations. A gate review can have different outcomes, such as go, kill, hold, recycle, or conditional go, depending on the assessment of the project status and viability123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 9: Project Change Management, p. 323; Everything Project Managers Need To Know About Gate Reviews | monday.com Blog; Gate reviews: What to do and why you need them - Rebel’s Guide to Project Management; Gates and How to Operate Them - GenSight

Unit testing is a testing technique that verifies the functionality and quality of individual units or components of software, such as modules, classes, functions, etc. Unit testing can help prevent issues with preexisting capabilities by detecting and fixing errors at an early stage of development, before they affect the integration and system testing. Unit testing can also ensure that new capabilities do not break or interfere with the existing ones, by checking the compatibility and dependencies of the units. Unit testing can be performed by developers using tools and frameworks that automate the process and generate reports. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 10: Project Quality Management; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.2: Execute quality management activities.

Cultural differences are the most important aspect for the project manager to consider when assigned to a multinational project with team members from different continents. Cultural differences refer to the variations in beliefs, values, norms, behaviors, customs, and communication styles among people from different countries or regions. Cultural differences can affect how team members interact, communicate, collaborate, negotiate, make decisions, solve problems, manage conflicts, and perform tasks. The project manager should be aware of and respect the cultural differences among team members and foster a positive and inclusive team culture that leverages diversity and promotes trust and cooperation.

A burndown chart is a visual representation of the remaining work versus the time required to complete it1. It is commonly used by agile teams to track the progress of each iteration or sprint and to forecast the project completion date2. A burndown chart shows the ideal work remaining line and the actual work remaining line, which can help the team identify any deviations or impediments and adjust accordingly1. A burndown chart is different from a Pareto chart, which shows the frequency of different causes of problems; a milestone chart, which shows the key events and deliverables of a project; and a Gantt chart, which shows the dependencies and durations of tasks in a project3. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Planning Projects Part 2, page 173; Burndown Chart: What Is It & How to Use One for Agile - ProjectManager, Introduction and Components of a Burndown Chart sections; Burndown Chart: What it is, How to Use it, Example [2023] • Asana, Introduction and What is a burndown chart? sections.

To show dependencies in a schedule, the project manager should use a network diagramming technique—specifically, the Precedence Diagramming Method (PDM). PDM represents activities (nodes) and connects them with relationships (arrows/links) to show task ordering and dependency logic. CompTIA Project+ explicitly includes analyzing and using a project network diagram as a tool, and it also emphasizes understanding dependencies and successor/predecessor relationships (finish-to-start, start-to-start, etc.), which are exactly what PDM models.

The other options don’t match the requirement. Waterfall is a life-cycle methodology, not a dependency diagramming tool. Simulation is typically used for quantitative analysis (e.g., Monte Carlo) rather than directly drawing dependencies. Cost ratio analysis is financial decision support, not schedule dependency mapping.

Therefore, to build a schedule that clearly communicates task order, constraint logic, and critical sequencing, the PM should use precedence diagramming (a form of project network diagram) to visualize and manage dependencies during initiation and early planning.

The project manager should use a change control log to document the effects of the hurricane delay on the project. A change control log is a tool that records and tracks any changes that occur during the project lifecycle. It usually includes information such as change ID, description, impact, status, approval, and resolution. A change control log can help to monitor and manage the changes that affect the project scope, schedule, cost, quality, or resources and ensure that they are aligned with the project objectives and stakeholder expectations.

This is a negative risk (threat): the manufacturer may be unable to deliver due to financial trouble, which could delay the project or increase cost. The scenario already indicates the response: “the servers will be sourced from another vendor.” That is best described as risk avoidance—changing the plan to eliminate exposure to the threatened vendor failure by not depending on that manufacturer. CompTIA Project+ includes performing risk management activities such as selecting risk management strategies and executing contingency/fallback plans.

“Mitigate” would mean reducing probability/impact while still accepting some exposure (e.g., adding schedule buffer, placing partial orders early, or increasing inspections), but here the team is switching vendors, which removes the root threat from the current plan. “Share” and “exploit” are typically associated with positive risks/opportunities, not threats, and don’t fit a supplier distress scenario.

So the correct strategy is Avoid: replace the risky supplier dependency with an alternate sourcing approach to prevent the risk from materializing into a project issue (late delivery, non-delivery, or contract disruption).

Electronic document and record management systems would be the best software solutions to help an institution manage the internal flow for formally responding in writing to citizens’ complaints. Electronic document and record management systems are software systems that help organizations create, store, organize, manage, track, and distribute electronic documents and records. Electronic document and record management systems can help to improve efficiency, productivity, collaboration, compliance, and security of document and record management processes and workflows3