PK0-005 Exam Preparation Material | CompTIA Project+Certification

Explanation:
To validate that a project has been successfully completed. The intent and purpose of a project closeout report is to validate that a project has been successfully completed and to summarize the goals, objectives, and outcomes of the project, as well as the lessons learned and the feedback from stakeholders. A project closeout report is a document that is submitted at the end of a project to officially conclude it and release the resources and contracts involved. It is useful for evaluating the project’s success and improving the performance of future projects12

Explanation:
This violates the need-to-know principle because employees in the sales department should only
have access to information required to perform their job responsibilities. Granting broad access to project files―especially files containing employee personal information―is an access control failure: permissions are too open and not aligned to role-based necessity. CompTIA Project+ emphasizes compliance and information security considerations that affect projects, including the expectation that sensitive information is protected through appropriate controls and access restrictions.
“Intellectual property” (B) concerns ownership and protection of creations (designs, trademarks, code, patents), not role-based access to personal data. “Multifactor authentication” (C) is an authentication mechanism that strengthens login security, but the scenario is about authorization/permissions (who is allowed to access what) rather than proving identity. “Facility access” (D) relates to physical security of locations, not digital file permissions.
In practice, the PM would coordinate with security/IT to correct access groups, implement least-privilege and role-based access control, and ensure sensitive data (like employee PII) is stored and shared with stricter controls―consistent with Project+ governance expectations around handling sensitive information appropriately.

Explanation:
Videoconference is the best tool to use when conducting project meetings across time zones, as it allows real-time communication, visual cues, screen sharing, and collaboration among the participants. Videoconference can also help build rapport and trust among the team members, and reduce the risk of misunderstandings or miscommunication. Videoconference tools such as Zoom, Skype, or Google Meet can also accommodate different time zones by showing the local time of each participant and allowing them to schedule meetings in advance12.

Explanation:
A kickoff meeting is the best fit because it is used at the start of a project (or phase) to align stakeholders and the team on core fundamentals such as scope, objectives, roles, high-level schedule/timeline, budget constraints, risks, and ways of working. If the PM is unclear about budget and timeline before work begins, a kickoff (often preceded by initiation artifacts like the charter) is where those expectations are clarified, confirmed, and communicated broadly.
A “demo” is used to show working product increments. A “stand-up” is a short Agile daily coordination meeting focused on immediate work, blockers, and next steps―not initial budget/timeline clarity. A “status call” is a recurring execution-phase update meeting; it assumes the project already has an agreed baseline.
Therefore, to establish shared understanding and confirm budget and timeline expectations prior to start, the PM should hold a kickoff meeting (or kickoff-style alignment session) to confirm baselines and ensure everyone begins execution with the same commitments and constraints.