Pass the CompTIA Project+ PK0-005 Questions and answers with CertsForce

A milestone chart is a tool that shows the key events or deliverables of a project along a timeline12. A milestone chart is useful for tracking the progress of a project that has technical tasks and requires a SME’s knowledge, because it can provide a high-level overview of the project status, without getting into the details of each task or activity34. A milestone chart can help the PM and the project lead communicate the project achievements, challenges, and expectations to the stakeholders, and also identify any potential risks or delays that may affect the project completion56. A milestone chart is better than the other options because:

A Gantt chart is a tool that shows the tasks, dependencies, durations, and resources of a project along a timeline7. A Gantt chart is more detailed and complex than a milestone chart, and may not be suitable for providing high-level updates to the stakeholders8.

A project organization chart is a tool that shows the roles, responsibilities, and reporting relationships of the project team members and other stakeholders9. A project organization chart is not a tool for tracking project data, but rather for defining the project structure and authority10.

A Program Evaluation Review Technique (PERT) chart is a tool that shows the tasks, dependencies, and critical path of a project along a network diagram. A PERT chart is more focused on the sequence and timing of the project tasks, and may not capture the key milestones or deliverables of the project.

References = CompTIA Project+ Certification Study Guide, CompTIA Project+ Certification Exam Objectives, What is a Milestone Chart?1, How to Create a Milestone Chart in Excel in 3 Steps2, Milestone Chart: The Easiest Way to Track Project Milestones3, How to Use Milestones in Project Management4, What is a Gantt Chart?5, Gantt Chart vs Milestone Chart: What’s the Difference?6, What is a Project Organization Chart?7, How to Create a Project Organization Chart8, What is a PERT Chart?9, PERT Chart vs Gantt Chart: What’s the Difference?10

The velocity chart typically shows the amount of work completed over time. If the “Actual Effort” line is below the “Planned Timeline,” it indicates that the project is not progressing as fast as planned, hence it is behind schedule. This is inferred by comparing the actual work completed against what was scheduled.

References = The answer is based on standard project management practices and the typical interpretation of velocity charts in project management. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

Evaluating the project is an activity that should be used in the closing phase of a project to support the project triple constraint. This involves reviewing the project plan, deliverables, and outcomes to ensure they meet the project objectives and requirements. References: CompTIA Project+ Study Guide Section 4.4.4

An audit conducted years after closure most commonly requires archived documentation because auditors typically need the full evidence trail of what was approved, executed, delivered, and controlled (plans, baselines, change logs, issue logs, risk registers, approvals, communications, testing evidence, acceptance/sign-off, financials, etc.). CompTIA Project+ explicitly lists “Archiving documentation” as a key project closing activity, and the CompTIA certification page also highlights project closing as including archiving documentation.

While signed contracts (A) can be part of that evidence set, they are only one subset of what an audit may request. A project closeout report (C) is useful as a summary, but auditors often need the underlying artifacts that support the report’s claims. Lessons learned (D) may be reviewed for process maturity, but it’s not usually the primary evidence package for compliance, financial, or governance verification.

Because the scenario emphasizes the long time gap (“years after”), archiving is the key: it ensures records are retained, retrievable, and complete for governance, compliance, and validation needs well beyond the project’s end date.

A rollback plan is used when an issue is identified during testing or implementation. It allows the team to revert to the previous state, removing the new package. This aligns with CompTIA Project+ guidance on implementing fallback strategies for risk management.

Using the chat and plain language can help overcome the communication barriers caused by accents and background noises. Chat allows team members to write down their ideas and questions, which can be easier to understand than spoken words. Plain language reduces the ambiguity and complexity of the messages, making them more clear and concise. These techniques can also enhance the participation and engagement of the team members, as they can express their thoughts and opinions more comfortably and confidently. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Communication and Change Management, p. 97-98.

Sharing a resource like an API between projects to leverage each project's strengths and reduce duplicated efforts is a risk-sharing strategy. CompTIA Project+ outlines risk-sharing as a way to capitalize on opportunities or mitigate project constraints.

Assess the impact of the request and create a change request. The project manager should assess the impact of the request and create a change request in response to the stakeholder asking to add mobile device functionality to a project that is on track to be completed under budget and ahead of schedule. A change request is a document that formally proposes and records a modification or addition to some aspect of a project, such as scope, schedule, cost, quality, or resources. A change request can help to communicate and justify the need and rationale for the change and its implications on the project objectives and deliverables. A change request also helps to initiate the change control process, which involves reviewing, approving, implementing, and monitoring the change12

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.