CompTIA Updated PK0-005 Exam Questions and Answers by ashley

When the team is confused about what must be accomplished, the best method is formal written communication so expectations are clear, consistent, and unambiguous, and there is a single reference point everyone can review. Formal written communication (e.g., documented assignments, acceptance criteria, task descriptions, action items with owners and due dates) reduces interpretation differences that often happen in scattered individual messages. CompTIA Project+ covers communication methods and emphasizes selecting the right channel based on complexity and the need for clarity, traceability, and shared understanding. ()

Informal internal messages can be fast, but they are more likely to create inconsistent interpretation, especially if people receive different versions or lack context. Asynchronous verbal methods (like voicemail) are harder to reference and can increase misunderstanding. “Synchronous external” is the wrong audience and doesn’t solve internal task clarity.

A practical implementation is: publish tasks in the team’s system of record (ticketing tool/task board), write clear “definition of done” and acceptance criteria, capture decisions and action items in meeting notes, and ensure each task has a single owner. That approach aligns with Project+ expectations for structured communication, documentation, and accountability. ()

The WBS, or work breakdown structure, is the most helpful tool when creating the baseline schedule because it breaks the project scope into smaller deliverables and units of work. A schedule baseline is built from activities, durations, dependencies, milestones, and assigned resources. The WBS provides the foundation for identifying those activities and ensuring the schedule includes all approved project work. Without a WBS, the schedule may miss deliverables, duplicate effort, or fail to align with scope. A CMS is not a standard scheduling input in this context. A statement of work defines high-level work and contractual expectations, but it is not detailed enough by itself to build the full schedule. An RFP is used during procurement, not schedule baselining.

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

The project manager should distribute an agenda before a call to ensure all meeting items are addressed and the correct participants attend. An agenda is a document that outlines the purpose, topics, and objectives of a meeting. It also includes information such as date, time, duration, location, attendees, and roles. Distributing an agenda can help to prepare the participants for the meeting, set clear expectations, and facilitate a productive and focused discussion12

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.