CompTIA PK0-005 - CompTIA Project+ Certification (2026)

When a project team lacks hands-on experience and decides to involve a third-party vendor for product development, the first document to expedite is a Request for Proposal (RFP). An RFP outlines the project requirements and asks potential vendors to submit proposals detailing how they would meet those requirements and at what cost. This allows the project manager to evaluate the capabilities and offerings of different vendors before making a decision.

References = CompTIA Project+ Certification Study Guide (PK0-005)

The project sponsor typically defines the success criteria and overall goals of the project. This alignment ensures the project meets organizational objectives, as outlined in CompTIA Project+ guidance on roles and responsibilities.

First name, last name, and address are Personally Identifiable Information (PII) because they can identify (directly or when combined with other data) a specific individual. CompTIA Project+ includes compliance/privacy and information handling considerations relevant to projects, and knowing common sensitive data categories is part of applying appropriate controls.

The other options don’t fit: PCI refers to payment card information standards/data (e.g., card numbers, CVV) rather than general identity details. PHI is Protected Health Information, tied to healthcare/medical data and regulated in healthcare contexts. CMS typically refers to a content management system, which is a technology platform, not a data classification category.

Correctly identifying data as PII matters because it drives project requirements for security and privacy: access control (need-to-know/least privilege), encryption in transit/at rest, retention rules, logging, and potentially regulatory obligations depending on jurisdiction. As the PM coordinates database design decisions with stakeholders, labeling these fields as PII ensures the team applies the correct controls and avoids accidental exposure—like overly broad access or insecure storage—throughout development, testing, and production deployment.

A ticketing system is a tool that allows the project manager to assign, track, and manage tasks for the testing phase. A ticketing system can help the resources to remain at their desks and only react when needed, because they can receive notifications, updates, and feedback on their tickets through email or other channels. A ticketing system can also help the project manager to monitor the progress, quality, and issues of the testing phase, and to generate reports and metrics. A ticketing system is different from a videoconference, which is a tool that allows the project team to communicate and collaborate in real time through audio and video. A videoconference is not suitable for allowing the resources to remain at their desks and only react when needed, because it requires their active participation and attention. A ticketing system is also different from a simple messaging system, which is a tool that allows the project team to exchange text messages and files. A simple messaging system is not effective for assigning, tracking, and managing tasks for the testing phase, because it lacks the features and functions of a ticketing system, such as prioritization, categorization, status, and history. A ticketing system is also different from a corporate social media, which is a tool that allows the project team to share information and ideas through online platforms. A corporate social media is not appropriate for allowing the resources to remain at their desks and only react when needed, because it may not be secure, reliable, or professional for the testing phase. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Execution1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 10: Project Execution2; The 15 best collaboration tools for productive teams3

The statement of work (SOW) would be the next document that a project manager should update once the need to procure goods and/or services is identified. A SOW is a document that defines the scope, deliverables, schedule, and terms and conditions of a project or contract. A SOW typically includes information such as purpose, scope of work, location of work, period of performance, deliverables schedule, applicable standards, acceptance criteria, special requirements, and payment schedule. A SOW can help to establish a common understanding and agreement between the client and the service provider on what needs to be done and how it will be done.

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

A strategy to store records must include data management and document management as two essential elements. Data management is the process of ensuring that the data collected, stored, and used by the project is accurate, complete, consistent, secure, and accessible. Data management helps to maintain the quality and integrity of the project data and supports the analysis and reporting of the project outcomes1, p. 4

Document management is the process of creating, organizing, storing, retrieving, and disposing of project documents in a systematic and controlled way. Document management helps to ensure that the project documents are available, reliable, usable, and authentic throughout the project life cycle and beyond. Document management also helps to comply with the legal, regulatory, and organizational requirements for records retention and disposition2, p. 3

A control chart is a graphical tool that displays the variation of a process over time and compares it to predetermined control limits. It can be used to determine whether a sample product is within an acceptable range by checking if the sample values fall within the upper and lower control limits, which indicate the expected variation of the process. If the sample values are outside the control limits or show a non-random pattern, it indicates that the process is out of control and there may be some assignable causes of variation that need to be investigated and corrected. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Quality Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 8: Quality Management2

Conducting lessons learned sessions is a critical part of the project closing phase. The primary purpose is to document what went right and wrong during the project, as well as to identify possible improvements for future projects. This process helps in capturing valuable insights and experiences, which can be used to enhance the effectiveness and efficiency of future projects.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Explain the importance of activities performed during the closing phase, one of the key activities is:

Collecting feedback from stakeholders

This includes conducting lessons learned sessions to gather insights on project performance, challenges faced, and areas of improvement.

Furthermore, the CompTIA Project+ PK0-005 Certification Study Guide emphasizes the importance of lessons learned sessions in the project closure process. It states that these sessions are conducted to:

Review what went well and what did not

Document lessons learned

Provide recommendations for future projects

By systematically analyzing the project ' s successes and shortcomings, organizations can build a repository of knowledge that serves as a reference for future projects, thereby fostering continuous improvement.

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.