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

Agile methodologies emphasize flexibility and iterative progress, so strict deadlines can be a concern. They may limit the team’s ability to adapt and respond to change, as emphasized by CompTIA Project+ in agile project management principles.

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 scrum master helps the team achieve its sprint objective by facilitating Scrum practices, removing impediments, encouraging collaboration, and protecting the team from unnecessary distractions. In an agile environment, the sprint objective guides what the team intends to accomplish during the sprint. The scrum master does not usually assign work or control the team like a traditional manager; instead, this role supports self-organization, coaches the team, and ensures ceremonies such as sprint planning, daily stand-ups, reviews, and retrospectives are effective. The product owner is responsible for backlog priority and maximizing product value, but the scrum master focuses on enabling the team to deliver the sprint goal. A project manager and business analyst may support projects, but they are not the primary Scrum role for this purpose.

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

Benchmarking is a quality technique that compares results, processes, or best practices from similar activities or organizations. It helps set realistic performance standards and identify improvement opportunities. Unlike cost-benefit analysis (financial), benchmarking focuses on performance comparison.

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 statement of work (SOW) is a formal document that defines the entire scope of work involved for a vendor and clarifies deliverables, costs, and timeline1. It serves as a contractual agreement between a vendor and a client, providing a comprehensive description of the work to be performed2. A reason to use a SOW on a project is to ensure the team stays within the scope of the contract, as it outlines what the team will and won’t do on a project, saving from painful client negotiations and protecting the timeline and the bottom line3. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 3: Initiating Projects Part 1, page 63; What Is a Statement of Work? Definition & Examples, Introduction and What Is a Statement of Work (SOW) In Project Management? sections; Statement Of Work Ultimate Guide: Simple Definition & Template, Introduction and What is a Statement of Work? sections; What Is a Statement of Work (SOW)? - Coursera, Introduction section.

Smoke testing is the best fit because it is a quick, high-level validation that a new build’s most critical functions work and the build is stable enough to proceed to deeper testing. The scenario specifically says “ready for the next testing phase,” which is exactly the gate smoke testing supports: confirm the build is not “broken” and that core paths execute without major failures. CompTIA Project+ includes smoke testing as one of the testing cycles/methods candidates should recognize in project quality activities. ()

The other options are not the best match. Unit testing is low-level testing of individual components (often done by developers) and doesn’t validate that the integrated build’s critical workflows function end-to-end. Regression testing is broader and verifies existing features weren’t broken by changes; it typically takes more time and is usually run after the build passes smoke checks. Performance testing evaluates responsiveness, throughput, and resource usage—important, but not the initial readiness check for a new build entering the next test stage.

So, to quickly confirm essential functionality and determine readiness to proceed, the PM should ensure a smoke test is performed.

The project charter is a high-level authorization document that outlines the purpose, objectives, and identifies key stakeholders. It does not contain detailed schedules, risk management plans, or resource allocation — those come later in the planning process.

A fixed-price contract is suitable when the scope is well defined and stable. This shifts cost risk to the vendor, as they must deliver within the agreed-upon price. NDAs, requirements volume, or logistics do not determine contract type as strongly as scope clarity does.

The data type most directly associated with compliance controls for websites is credit card (payment card) data. Payment card information is regulated by strict industry security requirements (commonly aligned with PCI DSS) and is a prime example of sensitive data that must be protected through confidentiality, access controls, encryption, logging, and secure handling procedures. PCI DSS is specifically focused on securing payment card data.

CompTIA Project+ includes compliance and privacy considerations and information security concepts that impact projects, including data confidentiality and data security, as well as awareness of applicable privacy regulations and organizational compliance concerns. When a designer confirms “controls are in place,” the primary intent is that regulated/sensitive data is protected by those controls.

The distractors are less fitting: mission statements are public-facing strategic content; trademarks relate to intellectual property/branding; and site certificates are security assets used to enable encrypted communication, but they are not the same as the customer data type being protected for compliance. The question is asking which data type would be protected by compliance controls—credit card data is the clearest, most regulated choice.