Free Practice Questions for CompTIA PK0-005 Exam

Pll stands for personally identifiable information, which is any data that can be used to identify a specific individual. Examples of Pll include name, address, phone number, email address, social security number, passport number, driver’s license number, etc. IP address and email address are both Pll because they can be used to trace the identity and location of a person. Medical record and test result values, name and year of birth, and x-ray and blood type are not Pll by themselves, but they can become Pll if they are combined with other data that can link them to a specific individual. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Security, page 331. CompTIA Project+ Certification Exam Objectives, Domain 4: Project Security, Objective 4.1: Given a scenario, apply security best practices to a project, Sub-objective: Identify and classify Pll.

The best action is to assign training so the developer can close the skills gap and return to expected performance. Project+ emphasizes team and resource management—including managing team performance and addressing resource gaps—and also highlights organizational change management activities such as training to ensure adoption of new ways of working.

Option C is the most constructive and sustainable response: it improves capability, reduces rework/defects, and helps the project maintain velocity without creating new staffing or morale issues. Requesting an additional developer (A) may be appropriate if capacity is truly insufficient, but it increases cost and onboarding time and doesn’t solve the original skill deficiency. Giving only non-critical tasks (B) can temporarily reduce risk, but it can also delay critical work and still leaves the underlying competency problem unaddressed. Removing the developer (D) is a last resort typically reserved for persistent performance issues after coaching/training or for role mismatch that cannot be corrected within project constraints.

A practical PM approach is to pair training with short-term support (mentoring, pairing, code reviews) and then monitor performance metrics and deliverables—consistent with Project+ execution-phase management and performance monitoring expectations.

A time and materials (T&M) contract is the best fit when you need temporary, specialized resources for a limited period (here, only during the testing phase) and the exact effort/hours are not fully predictable. With T&M, the buyer pays for the actual labor time (often at an agreed hourly/daily rate) and any approved materials/expenses. This aligns to CompTIA Project+ procurement objectives around selecting appropriate contract considerations and types, where time and material is a standard option used when work is phase-specific or scope is not fully defined to a fixed deliverable.

By contrast, fixed-price is most appropriate when the scope and deliverables are clearly defined upfront (less suitable for staff augmentation). Cost-plus reimburses allowable costs plus a fee and is typically used for broader, less-defined deliverables—often creating higher buyer cost risk than T&M for a small, contained staffing need. A warranty is not a primary contract type for acquiring temporary engineers; it’s usually a contract provision related to quality/defects after delivery.

The Requirements Traceability Matrix (RTM) is the best document for the PM to check when a stakeholder believes a key functionality might be missing. The RTM links requirements → design/work items → test cases → deliverables/acceptance, allowing the PM to confirm whether the functionality is already included and where it is implemented and validated. This aligns to CompTIA Project+ objectives around maintaining project artifacts and using tools that ensure requirements are tracked through delivery and verification (i.e., ensuring what was requested is what gets built and tested).

A detailed scope statement can confirm what is in/out at a high level, but it typically won’t provide the same end-to-end mapping to implementation and testing evidence that gives a PM confidence about a specific feature’s presence. A task board shows current work status, not requirement coverage. A risk register is for threats/opportunities and responses, not for proving whether functionality exists in scope and has been built/tested.

So, to avoid unnecessary change requests and to respond with evidence, the PM most likely checked the RTM to confirm the feature is already included and traceable to completed or planned work and validation.

A finish-to-start dependency is a type of relationship dependency in project management, where the start of one task depends on the finish of another task12. In this case, the project manager is using a finish-to-start dependency, because testing cannot start until requirements development is finished. This implies that testing is a successor task, and requirements development is a predecessor task. A finish-to-start dependency is the most common type of dependency in project management, and it ensures that tasks are performed in a logical sequence34. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification Exam Objectives6, Understanding Dependencies in Project Management [2023] • Asana1, Dependencies in Project Management | Smartsheet2, Understanding Task Dependencies in Project Management3, What are Dependencies in Project Management? - KnowledgeHut4

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. ()

A finish-to-start relationship is a type of logical dependency between two tasks, in which the first task must be completed before the second task can start. In this scenario, the document containing information about how the new system will interact with other systems within the organization is a prerequisite for the configuration of the system in development. Therefore, the document writing task must finish before the configuration task can start, which is a finish-to-start relationship. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Schedule Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 6: Schedule Management2

A positive correlation means that as the number of worked hours increases, so does the number of mistakes. According to CompTIA Project+, understanding such correlations is crucial for effective resource and quality management.

Customer notification should be added to the issue log after receiving an escalation from an executive about the extension of the downtime after the scheduled window. Customer notification is a communication activity that informs the customers about any issues or changes that may affect their satisfaction or expectations. Customer notification can help to maintain trust, transparency, and goodwill with the customers and prevent any negative impacts on their business operations or experience.