CompTIA Updated PK0-005 Exam Questions and Answers by haadi

A rollback plan, also known as a backout plan, is a strategy designed to reverse changes made during a project in case of failure or undesired results1. A rollback plan is a form of risk response that allows the project to restore the previous state and minimize the impact of the issue. A rollback plan is usually created during the planning phase and implemented during the execution or closing phase of the project. The other options are not correct because:

A compliance check is a process that ensures that the project meets the relevant standards, regulations, and requirements. A compliance check is not a risk response, but rather a quality control or assurance activity.

A release plan is a document that outlines the scope, schedule, and resources for delivering a product or service to the customer. A release plan is not a risk response, but rather a communication or scope management tool.

A validation check is a process that verifies that the project deliverables meet the customer’s needs and expectations. A validation check is not a risk response, but rather a quality control or assurance activity. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Executing and Closing Projects, page 314; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.2: Given a scenario, execute and monitor project tasks using traditional methodologies; Backout Plan - DevX

Submit a change request to the change control board. The project manager should submit a change request to the change control board (CCB) if they realize that the project will not be completed on time due to resource constraints. A change request is a formal proposal to modify any aspect of the project, such as scope, schedule, cost, quality, or resources. A change request must be submitted to the CCB, which is a group of stakeholders who are authorized to review and approve changes. Submitting a change request can help to document the impact of the resource constraints on the project and seek approval for any corrective actions or preventive actions12

The output of this exercise where the project manager is comparing the cost of the project to the cost savings the project will produce when it is complete will produce the return on investment (ROI). ROI is a financial metric that measures the profitability or efficiency of an investment by comparing its benefits or returns to its costs. ROI can help to evaluate the value or worth of a project and support decision making and prioritization. ROI is calculated by dividing the net benefits (benefits minus costs) by the total costs and multiplying by 100 to get a percentage.

A finish-to-start dependency is a type of relationship dependency in project management, where the start of one task depends on the finish of another task12. In this case, the project manager is using a finish-to-start dependency, because testing cannot start until requirements development is finished. This implies that testing is a successor task, and requirements development is a predecessor task. A finish-to-start dependency is the most common type of dependency in project management, and it ensures that tasks are performed in a logical sequence34. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification Exam Objectives6, Understanding Dependencies in Project Management [2023] • Asana1, Dependencies in Project Management | Smartsheet2, Understanding Task Dependencies in Project Management3, What are Dependencies in Project Management? - KnowledgeHut4