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

Objectives and success criteria are core elements of the project charter, which formally authorizes the project and establishes the high-level direction for what success looks like. During initiation, the PM works with stakeholders to define the project’s purpose, objectives, high-level scope, key stakeholders, assumptions/constraints, and success criteria. That aligns to CompTIA Project+ initiation artifacts and the practice of establishing alignment before detailed planning begins.

A requirements traceability matrix is used later to map detailed requirements through design/build/test to ensure nothing is missed; it’s not the primary artifact for initial objectives and success criteria. A communications plan defines audiences, channels, frequency, and message types; it’s informed by objectives but isn’t where objectives are defined. A risk register captures uncertainties and responses; it’s created/expanded as risks are identified but is not the main artifact for defining objectives and success measures.

So, when the PM is meeting stakeholders to define objectives and success criteria, they are primarily working on the project charter (or charter-level initiation documentation) that anchors the project’s “why” and how success will be evaluated.

A velocity chart is a tool used in agile project management to track the progress and performance of a project team over time. It shows the number of features or user stories completed in each iteration or sprint. The planned timeline line represents the expected or ideal velocity, while the actual effort line shows the actual or achieved velocity. By comparing the two lines, the Scrum master can identify any gaps, trends, or issues in the project delivery.

Based on the image, the most likely update that the Scrum master can provide to the senior management team is D. The project is trending ahead of schedule. This is because the actual effort line is above the planned timeline line for most of the time, indicating that the project team is completing more features than expected in each sprint. This means that the project is ahead of schedule and has a positive velocity variance. 

A milestone chart is the best chart to use to show major accomplishments for key events, because it displays the important deliverables or outcomes of a project along a timeline12. A milestone chart can provide a high-level overview of the project progress and achievements, without showing the details of each task or activity34. A milestone chart can also help communicate the project status and expectations to the stakeholders, and identify any potential risks or delays that may affect the project completion56. References = CompTIA Project+ Certification Study Guide7, CompTIA Project+ Certification Exam Objectives8, What is a Milestone Chart?1, How to Create a Milestone Chart in Excel in 3 Steps2, Milestone Chart: The Easiest Way to Track Project Milestones3, How to Use Milestones in Project Management4

A Request for Proposal (RFP) is a document issued by an organization to solicit proposals from potential vendors for a specific solution or service. It outlines the organization ' s requirements and criteria for evaluation, allowing vendors to propose how they would meet those needs. An RFP is appropriate when the company seeks detailed proposals for a solution to its specific needs.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 3.4: Explain important project procurement and vendor selection concepts, understanding the use of RFPs is essential for effective procurement management.

Stress testing is a type of performance testing that evaluates how a system behaves under extreme load conditions, such as high volume of data, concurrent users, or transactions12. Stress testing can help to identify the system’s breaking point, bottlenecks, and resource limitations, and to ensure that the system can recover from failures and maintain its functionality34. In this case, the team performed stress testing to validate that system performance will not be impacted by migrating all data to a single system following the merger of two companies. This implies that the team simulated a high amount of data transfer and processing, and measured the system’s response time, throughput, availability, and reliability under such load. Stress testing is better than the other options because:

Regression testing is a type of functional testing that verifies that a system’s existing features and functionality are not affected by a change or an update56. Regression testing does not focus on system performance or load conditions, but rather on system correctness and quality.

Smoke testing is a type of functional testing that checks the basic functionality and stability of a system before performing more detailed and comprehensive testing78. Smoke testing does not measure system performance or load conditions, but rather ensures that the system is ready for further testing.

Automation testing is a technique of using software tools or scripts to execute test cases and compare the actual results with the expected results910. Automation testing is not a specific type of testing, but rather a way of performing testing. Automation testing can be applied to various types of testing, including stress testing, regression testing, and smoke testing.

References = CompTIA Project+ Certification Study Guide, CompTIA Project+ Certification Exam Objectives, What is Stress Testing?1, Stress Testing: A Complete Guide2, What is Regression Testing?3, Regression Testing: A Complete Guide4, What is Smoke Testing?5, Smoke Testing: A Complete Guide6, What is Automation Testing?7, Automation Testing: A Complete Guide8

Encryption is the process of transforming data into an unreadable format that can only be accessed by authorized parties who have the decryption key. Encryption is the best approach for the project manager to keep the PII confidential, as it protects the data from unauthorized access during storage and transmission12.

Post-implementation support is the best answer because it occurs after the project solution has been transitioned to operations or the business team. In the closing and transition stages, the project team ensures deliverables are accepted, documentation is handed over, resources are released, and support arrangements are available so the production team can operate the solution successfully. User acceptance testing and performance testing normally occur before final deployment or acceptance, not after project closure. Audits and inspections may occur during or after a project, but they are not the normal operational service available once the solution is in production. Post-implementation support helps address defects, user questions, stabilization issues, and knowledge-transfer gaps after handoff.

================

Control objectives are the desired outcomes or goals of implementing security controls to mitigate risks and protect information assets. Control objectives should be the primary basis for establishing metrics that measure the effectiveness of an information security program, as they align with the business objectives, requirements, and expectations of the organization and its stakeholders. Metrics based on control objectives can help to evaluate the performance, efficiency, and maturity of the security program, and to identify gaps, issues, and areas for improvement. The other options are not correct because:

Residual risk is the remaining risk after applying security controls. Residual risk is not a basis for establishing metrics, but rather a result of measuring the effectiveness of security controls. Residual risk should be monitored and reported, but it does not define the desired outcomes or goals of the security program.

Regulatory requirements are the external standards, laws, and regulations that the organization must comply with to avoid legal or financial penalties. Regulatory requirements are not a basis for establishing metrics, but rather a constraint or a driver for the security program. Metrics based on regulatory requirements can help to demonstrate compliance, but they may not reflect the actual effectiveness or efficiency of the security program.

Risk tolerance is the level of risk that the organization is willing to accept or bear. Risk tolerance is not a basis for establishing metrics, but rather a factor or an input for the security program. Metrics based on risk tolerance can help to prioritize and allocate resources, but they may not measure the actual outcomes or goals of the security program. References = Key Performance Indicators for Security Governance, Part 1; 14 Cybersecurity Metrics + KPIs You Must Track in 2023; KPIs in Information Security: The 10 Most Important Security Metrics; Why metrics are crucial to proving cybersecurity programs’ value; Implementing and Maintaining Security Program Metrics

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.

Agile is a methodology that emphasizes iterative and incremental development, customer collaboration, and responsiveness to change. Agile is suitable for developing a minimum viable product (MVP), which is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development. Agile allows the project sponsor to deliver an MVP quickly and test it with real users, and then adapt the product based on the feedback and changing requirements. Agile also reduces the risk of wasting time and resources on a product that does not meet the customer’s needs or expectations123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 2: Project Methodologies, p. 55; What is a Minimum Viable Product (MVP)? | Agile Alliance; Minimum Viable Product (MVP): What is it & Why it Matters - Atlassian