CompTIA Updated PK0-005 Exam Questions and Answers by tia

A Responsibility Assignment Matrix (RAM) is the best tool for assigning and clarifying roles and responsibilities. A RAM maps project work (deliverables, work packages, or tasks) to people/roles and defines who is responsible/ accountable, and who provides input or needs to be informed (often implemented as a RACI chart). CompTIA Project+ lists RAM/RACI-style responsibility mapping under planning and resource management practices because it prevents ambiguity, reduces duplication, and supports accountability. ()

The distractors are not designed for role assignment. ERP is an enterprise resource planning system used to manage business processes; it can store resource data but isn’t the PM artifact for defining responsibilities. JAR is not a standard project management responsibility tool in this context. CCB (Change Control Board) governs change requests; it does not assign day-to-day delivery responsibilities.

Using a RAM early (initiation/planning) helps the PM establish clear ownership, streamline handoffs, and support effective communication planning. It also reduces the risk of “I thought someone else was doing that,” which is a common execution failure mode when responsibilities are not explicitly documented. ()

The project manager should approve the deliverables and monitor the performance of the outsourced structured cabling activities. These are the responsibilities of the project manager when dealing with external vendors or contractors, as they ensure that the quality standards, scope, schedule, and budget are met according to the contract terms and the project plan. The project manager should also communicate regularly with the vendor and provide feedback and guidance as needed. The other options are not correct because:

Purchasing the materials is not the responsibility of the project manager, but the vendor who is performing the structured cabling activities. The project manager should only verify that the materials are suitable and available for the project.

Assigning the resources is not the responsibility of the project manager, but the vendor who is performing the structured cabling activities. The project manager should only ensure that the vendor has the adequate and qualified resources to complete the work.

Accepting delays in the work is not a good practice for the project manager, as it can negatively affect the project schedule, scope, and quality. The project manager should proactively identify and manage the risks and issues that may cause delays, and implement contingency plans or corrective actions if necessary.

Negotiating with the vendors is not a task that the project manager should do during the execution of the structured cabling activities, as it should have been done during the planning and procurement phases of the project. The project manager should only adhere to the contract terms and conditions that have been agreed upon with the vendor, and only renegotiate if there are significant changes or disputes that require it. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Planning Projects, Part 4 (Procurement and Communication), pages 243-260; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.5: Given a scenario, plan procurement for a project; Domain 3: Project Execution, Objective 3.2: Given a scenario, execute and monitor project tasks using traditional methodologies.

A rollback plan (sometimes called a “backout plan”) defines the steps to revert a system to the last known good/operational state if an implemented change fails or creates unacceptable impacts. That is exactly what option B states: returning to the operational state before the change was applied. This aligns with IT change control practices emphasized in Project+ governance and change control contexts, where changes must include consideration for restoring service quickly if outcomes are not as expected.

Option A (“apply an alternative plan”) is closer to a general contingency/fallback plan, which may involve a different solution path rather than undoing the change. Options C and D are not standard control responses: restarting the entire project is extreme and unrelated to change backout, and repeating tasks “until they work” ignores risk control and service stability.

In project environments—especially IT—rollback planning is part of responsible change implementation because it reduces downtime, protects users, and supports controlled deployment. If validation/testing after the change shows failure, the rollback plan provides a predefined, approved path to quickly restore the prior baseline while the team reassesses or submits a revised change request.

After completing development and internal testing phases, the next step is to conduct User Acceptance Testing (UAT). UAT is performed by the end-users to ensure the system meets their requirements and is ready for deployment.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.3: Explain the importance of quality management and testing in project management, UAT is a critical phase to validate that the product meets the business needs and requirements.