CompTIA Updated PK0-005 Exam Questions and Answers by genevieve

The project manager should inform the project sponsor about the issue and seek their guidance and support. The project sponsor is the person who provides the resources and authority for the project, and who can help resolve any conflicts or problems that may arise. The project manager should not withdraw the offer, ignore the lawsuit, or use a third-party company without consulting the project sponsor first, as these actions may have legal, ethical, or financial implications for the project and the organization12.

The best choice is cadence because it establishes a repeatable rhythm for ceremonies, work sequencing, and deliverables across iterations (e.g., sprint planning → daily touchpoints → review → retrospective), which is exactly what the scenario is asking for: a “consistent flow of tasks and deliverables after each iteration.” CompTIA Project+ explicitly includes “Establish cadences” and “Meeting cadence and methodologies” as planning activities, and it also calls out “Impacts to cadence” as something to manage during schedule development/maintenance—showing cadence is a recognized control lever for iteration-based delivery.

A task log tracks tasks but doesn’t create a repeatable time pattern. Milestones mark significant points in time, but they don’t inherently standardize the iteration routine. A work breakdown structure (WBS) decomposes scope into work packages; it helps organize work, but it won’t by itself create a stable sprint-to-sprint operating rhythm. By establishing a cadence, the team reduces iteration variability, improves predictability, and makes it easier to forecast and coordinate dependencies—aligning directly with Project+ schedule management and Agile/iteration practices.

The correct document is meeting minutes. Minutes capture what was discussed, key decisions/agreements made, action items/next steps (often with owners and due dates), and any follow-up items. CompTIA Project+ includes meeting management practices and emphasizes documenting outcomes and action items so the team has a shared, traceable record—especially important in recurring status meetings where decisions and commitments accumulate over time. ()

A project presentation is typically used to brief stakeholders visually and isn’t the standard artifact for recording agreements and action items from a weekly meeting. A memorandum can communicate information formally, but it is not the specific document type for “summary of topics discussed, agreements, and next steps” in a meeting context. An issue log is for tracking issues (problems that have occurred), not for documenting the full meeting discussion and decisions.

Well-written minutes reduce confusion, align stakeholders, and create accountability. They also support change control and escalation because they document what was agreed and when. Therefore, for a weekly status meeting summary including agreements and next steps, the PM should prepare and distribute minutes. ()