CompTIA Project+ (PK0-005) Practice Exam

Correct: A — clarify and communicate roles. Unclear responsibilities are the stated root cause, so defining them — often via a responsibility assignment matrix (RAM/RACI) — and communicating them directly addresses the problem and restores accountability.

Why not the others: more budget (B) or a shorter timeline (C) does not resolve role confusion; eliminating meetings (D) removes a coordination channel and would likely make things worse.

Correct: A — evaluate impact, then update the plan. Any scope change must be assessed for its effect on schedule, cost, quality, and risk before it is accepted, then folded into the plan through change control. Assessment comes first.

Why not the others: ignoring the changes (B) abandons the client’s need; implementing them immediately (C) bypasses impact analysis and breaks the baseline; reassigning everyone (D) reacts before the impact is even known.

Correct: A — record and assess in the risk register. Newly identified risks are logged in the risk register and evaluated for probability and impact so a response can be planned. Formal capture is the disciplined first move.

Why not the others: delaying the project (B) reacts before the risk is even understood; removing the team member (C) punishes good risk identification; skipping analysis (D) ignores a known threat.

Correct: A — a project status report. Status reports are the standard vehicle for communicating overall progress, milestones, and health to stakeholders on a regular cadence.

Why not the others: the risk register (B) tracks risks, the change control log (C) tracks change requests, and the escalation matrix (D) defines who handles escalated issues — each is narrower than a general progress update.

Correct: A — engage the vendor and adjust the schedule. A vendor delay is managed through direct communication to understand the new timeline, then updating the schedule and stakeholders accordingly — addressing the constraint at its source.

Why not the others: ignoring it (B) lets the slip cascade; replacing the team (C) targets the wrong party; more meetings (D) adds overhead without resolving the supply problem.

Correct: A — objectives and quality. Success is defined by delivering the agreed scope to the required quality, not by how much budget was consumed. Missed deliverables are the real problem to solve.

Why not the others: spending down the budget (B) is waste, not value; hiring without a defined need (C) may not address the gap; changing scope (D) without analysis can mask the missed objectives rather than fix them.

Correct: A — provide training or resources. A skills gap is closed by developing the team member, which addresses the root cause and retains institutional knowledge — the resource-management response Project+ expects.

Why not the others: replacing the member (B) is costly and skips the fixable cause; ignoring it (C) leaves the gap; eliminating meetings (D) is unrelated to a training need.

Correct: A — route it through change control for formal approval. A change affecting cost and schedule must go through the documented change-control process — impact assessment, then a decision from the change control board or sponsor — before any work begins. Authorization protects the baseline.

Why not the others: implementing immediately (B) skips approval and breaks the baseline; rejecting all requests (C) ignores legitimate change; compressing the schedule elsewhere (D) commits to the change before it is even approved and risks new problems.

Correct: A — facilitate a collaborative resolution. Bringing the parties together to surface priorities and reach consensus is the constructive conflict-management approach, preserving the team and the work.

Why not the others: dumping all tasks on one person (B) creates a bottleneck and resentment; ignoring the conflict (C) lets it fester; delaying the project (D) avoids the issue rather than resolving it.

Correct: A — lessons learned plus address the feedback. Proper closing captures lessons learned and resolves outstanding client concerns, both improving the relationship and feeding future projects — the disciplined closeout Project+ expects.

Why not the others: closing without action (B) leaves a dissatisfied client and no learning; blaming the team (C) is unproductive and inaccurate; adding budget after completion (D) does not fix the deliverable.