CompTIA Updated PK0-005 Exam Questions and Answers by rachel

The only option that can be reliably inferred in a typical project chart/diagram context (e.g., a network diagram or dependency view) is a dependency relationship—specifically that Task B must finish before Task C can start (a Finish-to-Start relationship). In CompTIA Project+ objectives, dependency management is a core scheduling concept: identifying predecessors/successors and understanding how sequencing drives the schedule. Inference about task ordering is exactly what dependency visuals are designed to communicate.

The other options require information that is not inherently inferable without additional data. “Completed on time” (A) would require schedule baseline vs. forecast/critical path analysis. “Task D must be reworked” (B) would require quality/validation results or defect/issue information. “Over budget and behind schedule” (D) would require performance metrics such as EVM or cost/schedule variance and cannot be concluded solely from a dependency relationship.

So, the best inference is the sequencing rule: B must be completed before C begins, which is a fundamental scheduling/dependency concept emphasized in Project+ planning and schedule control practices.

A Finish-to-Start dependency implies that a subsequent activity cannot start until a previous one finishes. In this scenario, the manufacturing process (subsequent activity) cannot begin until the critical raw materials (previous activity) have been delivered. This type of dependency is the most common in project schedules and is likely being affected by the global shipping slowdown, causing delays in the start of the project ' s production run.

The PM should create a project organizational chart to clarify who is who, reporting lines, and role visibility across the team. When team members are unclear about each other’s roles, the fastest way to reduce confusion is to make the project structure explicit: who leads which workstream, who approves decisions, who supports, and how to escalate. This aligns with Project+ people/resource management expectations: establish clear responsibilities and team structure to reduce duplication, gaps, and conflict caused by ambiguity.

A project plan is broader (scope/schedule/budget/governance), but it won’t necessarily provide a simple, visual map of roles. A road map is high-level sequencing of outcomes over time; it’s not meant to define roles. A milestone chart highlights key dates and deliverables, not responsibilities.

In practice, the PM often pairs the project org chart with a RAM/RACI for detailed accountability, but since the question asks which chart to create to fix role confusion, the best answer is the project organizational chart.

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