Free Practice Questions for CompTIA PK0-005 Exam

A rollback plan is a part of the project management plan that defines how to revert the system to its previous state or baseline if the change or migration fails or causes unacceptable impacts1. A rollback plan is different from a contingency plan, which is a plan to deal with a specific risk event that may or may not occur2. A release plan and a deployment plan are not relevant to the scenario, as they are used to plan and execute the delivery and installation of the system, not to undo them. Therefore, the correct answer is A. Rollback plan.

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.

Pll stands for personally identifiable information, which is any data that can be used to identify a specific individual. Examples of Pll include name, address, phone number, email address, social security number, passport number, driver’s license number, etc. IP address and email address are both Pll because they can be used to trace the identity and location of a person. Medical record and test result values, name and year of birth, and x-ray and blood type are not Pll by themselves, but they can become Pll if they are combined with other data that can link them to a specific individual. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Security, page 331. CompTIA Project+ Certification Exam Objectives, Domain 4: Project Security, Objective 4.1: Given a scenario, apply security best practices to a project, Sub-objective: Identify and classify Pll.

In the context of construction projects, physical injuries are a significant risk. The most effective risk response method in this scenario is mitigation, which involves taking proactive steps to reduce the likelihood or impact of the risk. Training construction workers on safety protocols and procedures is a direct way to mitigate the risk of physical injuries.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.4: Given a scenario, perform risk management activities, mitigation is a key risk response strategy. The official objectives state:

" Develop risk response plans, including mitigation strategies to reduce the likelihood or impact of risks. "

CompTIA Project+ PK0-005 Exam Objectives

By providing proper training, the project manager actively reduces the risk, aligning with best practices in risk management.

Enterprise resource planning (ERP) software is a type of software that integrates various business functions and processes, such as accounting, finance, inventory, sales, purchasing, human resources, and more. ERP software helps businesses store, organize, and manage information related to business transactions, such as invoices, payments, orders, receipts, and reports. ERP software also provides real-time data analysis, reporting, and forecasting capabilities12.

A proposal is a detailed document submitted by vendors outlining how they will meet project requirements. It helps in assessing vendor solutions and suitability, consistent with CompTIA Project+ procurement and vendor management practices.

A decision tree helps in evaluating various choices and their potential outcomes, making it suitable for comparing vendors based on costs and risks. This aligns with CompTIA Project+ methodologies for decision-making tools and analysis.

The change log should be updated first because the steering committee has decided to implement proposed suggestions, which means approved or pending changes must be formally recorded. A change log provides traceability for change requests, approvals, impacts, implementation status, owners, and dates. Updating it first ensures the project has an auditable record before related project documents are revised. The Gantt chart may need updates later if the changes affect schedule activities or milestones. The task board may also be revised if team work items change. The risk log is used for uncertain future events, not approved scope or execution changes. Proper change documentation supports governance, prevents confusion, and helps stakeholders understand why the project plan, schedule, budget, or scope may be adjusted.

================

The first priority for a PM inheriting a project midstream is to access and review the existing project artifacts—the documented “source of truth” that shows what was approved, what has changed, current status, and remaining work. CompTIA Project+ emphasizes maintaining project documentation and artifacts, and it explicitly includes “Review existing artifacts” as a key activity as a PM gets oriented to the project context.

By reviewing artifacts (charter, scope baseline/WBS or backlog, schedule, budget, risk register, issue log, change control log, stakeholder list, communication plan, testing/quality plans, and current reports), the PM can quickly understand: current phase, constraints, commitments, open risks/issues, and what decisions have already been made. That enables accurate next actions and prevents contradictory communication or rework.

A brainstorming session (B) is not the best “first” step without understanding current constraints and decisions. A kickoff meeting (C) is typically for initiation; mid-project, the PM may run a transition meeting later, but only after reviewing the facts. Establishing communication channels (D) is important, but you can’t communicate effectively until you know the baseline status and existing governance approach—information found in the artifacts.

Defining communication channels and access requirements typically occurs in the planning phase, where detailed plans for project management are established. This aligns with CompTIA Project+ standards for comprehensive project planning.