CompTIA Updated PK0-005 Exam Questions and Answers by halima

An Informative meeting is designed to share information, such as presenting new software features to stakeholders. This type of meeting ensures that all participants are informed about the software's capabilities and how it will impact their work.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, recognizing different meeting types, including informative meetings, is essential for effective communication management.

A burndown chart is a visual representation of the remaining work versus the time required to complete it1. It is commonly used by agile teams to track the progress of each iteration or sprint and to forecast the project completion date2. A burndown chart shows the ideal work remaining line and the actual work remaining line, which can help the team identify any deviations or impediments and adjust accordingly1. A burndown chart is different from a Pareto chart, which shows the frequency of different causes of problems; a milestone chart, which shows the key events and deliverables of a project; and a Gantt chart, which shows the dependencies and durations of tasks in a project3. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Planning Projects Part 2, page 173; Burndown Chart: What Is It & How to Use One for Agile - ProjectManager, Introduction and Components of a Burndown Chart sections; Burndown Chart: What it is, How to Use it, Example [2023] • Asana, Introduction and What is a burndown chart? sections.

A rollback plan is a contingency plan that describes how to revert the system to its previous state in case the change fails or causes problems. A rollback plan is important to minimize the impact of a failed change and ensure the system’s availability and functionality12.

A deployment plan is a document that outlines the steps and procedures for implementing the change in the production environment. A deployment plan is important to ensure the change is executed smoothly, efficiently, and securely, and that the system meets the expected performance and quality standards34.

A dashboard is the most appropriate artifact to share when a stakeholder asks for project performance data. Dashboards are designed to present key performance indicators (KPIs) and trends in a concise, visual form—such as schedule progress, scope completion, burn/burndown, budget status, risks/issues summaries, and other metrics relevant to project health. This aligns with Project+ expectations around performance monitoring and communicating status in an efficient way tailored to stakeholder needs.

An issue log is too granular and focuses only on current problems; it is part of performance, but it’s not the overall performance view stakeholders typically want. A WBS is a scope decomposition artifact used for planning and organizing work, not performance reporting. A milestone chart shows key dates and whether major points are achieved, but it does not provide comprehensive performance data (cost, trend, throughput, overall health).

Therefore, to provide performance data effectively—especially for stakeholders who want quick, up-to-date visibility—the PM should send (or grant access to) the project dashboard, ensuring it reflects the latest reporting period and includes the metrics the stakeholder cares about.