PK0-005 CompTIA Project+ Certification (2026) Questions and Answers

The environmental factor would be impacted the most by requirements for a project to implement an air quality control system at a coal plant. This is because coal combustion produces various air pollutants, such as particulate matter (PM), sulfur dioxide (SO2), nitrogen oxides (NOx), carbon dioxide (CO2), and mercury, that can harm human health and the environment12. An air quality control system can reduce the emissions of these pollutants by using different technologies, such as low NOx burners, flue gas desulfurization, electrostatic precipitators, and carbon capture and storage23. However, these technologies also have environmental impacts, such as water consumption, waste generation, energy consumption, and greenhouse gas emissions4. Therefore, the project manager should consider the environmental factor in terms of the project scope, objectives, constraints, risks, and stakeholders, and evaluate the trade-offs and benefits of different air quality control options5. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 3: Project Scope Management, p. 97; Update on air pollution control strategies for coal-fired power plants; AQCS Air Quality Control Systems; NOx control for high-ash coal-fired power plants in India; Coal Dust Control

Applying the contingency plan is the immediate response to mitigate a security risk. CompTIA Project+ emphasizes the importance of having pre-established contingency plans to handle potential risks promptly and effectively.

Meeting minutes should be prepared to ensure team members who are absent remain informed about assignments. Meeting minutes document what was discussed, decisions made, and assignments given during a meeting, providing a record of the team's progress and ensuring absent members are up-to-date. References: CompTIA Project+ Study Guide Section 4.2.2

The project manager should prepare meeting minutes to ensure team members who are absent remain informed about assignments. Meeting minutes are a written record of what was discussed and decided in a meeting. They usually include information such as attendees, agenda items, action items, decisions made, issues raised, and deadlines assigned. Meeting minutes can help to communicate important information to team members who could not attend the meeting and provide a reference for future follow-up.

Scrum is an agile methodology well-suited for projects that require frequent milestone deliveries and functionality demonstrations. It emphasizes iterative development, with regular presentations to stakeholders, which aligns with CompTIA Project+ principles for agile project management.

The Scrum team should break the stories into workable items that can be completed within one sprint, which is a time-boxed period of 7 to 30 days, during which the team delivers a potentially releasable product increment. Breaking the stories into smaller and more manageable items can help the team to estimate them more accurately, plan them more effectively, and deliver them more reliably. Breaking the stories also aligns with the agile principle of delivering working software frequently and satisfying the customer through early and continuous delivery of valuable software.

The other options are not the best steps for the Scrum team to take next. Assigning more resources to complete similar stories in the future may not solve the problem of underestimation, and may introduce additional complexity and communication overhead. Extending the sprint duration when required with the approval of the product owner may compromise the consistency and predictability of the Scrum process, and may delay the feedback and validation from the stakeholders. Releasing the current progress into production and carrying over the rest of the code for the next sprint may result in an incomplete or unstable product increment, and may violate the definition of done, which is a shared understanding of the quality criteria that the product increment must meet. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 5: Project Scope Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 5: Project Scope Management2; The 3 Scrum Roles and Responsibilities Explained3; Implementation of Scrum - 7 Steps for an Effective Process4

Reviewing the Gantt chart weekly with the team would be the most effective step for the project manager to take to ensure clarity within the team after receiving feedback from the project sponsor that the resources involved in the project are unsure of their daily activities. A Gantt chart is a graphical tool that shows the schedule of a project, including the start and end dates, durations, dependencies, milestones, and progress of each task or activity. Reviewing the Gantt chart weekly with the team can help to clarify their roles and responsibilities, assign tasks and deadlines, track and report their status and performance, identify and resolve any issues or risks, and keep them aligned and engaged with the project goals.VVVVVVVVVVVVVV

An Informative meeting is designed to share information, such as presenting new software features to stakeholders. This type of meeting ensures that all participants are informed about the software's capabilities and how it will impact their work.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, recognizing different meeting types, including informative meetings, is essential for effective communication management.

This answer is based on the understanding that outsourcing is a form of procurement, which is one of the knowledge areas in project management. Procurement involves acquiring goods and services from external sources to support the project objectives. According to the CompTIA Project+ Study Guide1, procurement activities occur mainly in the planning phase of the project, where the project manager identifies the project needs, defines the scope of work, evaluates the potential vendors, and prepares the procurement documents. The other options are not correct because:

Initiating is the phase where the project manager defines the project purpose, objectives, and deliverables, and obtains the project charter and stakeholder approval. Initiating does not involve procurement activities, although it may involve some preliminary research on the feasibility and availability of external resources.

Controlling is the phase where the project manager monitors and measures the project performance, compares it with the baseline, and implements corrective actions if needed. Controlling does involve some procurement activities, such as reviewing the vendor deliverables, managing the changes, and resolving the issues, but these are not the main tasks of procurement.

Executing is the phase where the project manager leads and directs the project team and other resources to complete the project work according to the plan. Executing does involve some procurement activities, such as selecting the vendor, signing the contract, and managing the relationship, but these are not the main tasks of procurement. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Planning Projects, Part 4 (Procurement and Communication), pages 243-260; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.5: Given a scenario, plan procurement for a project.

If a project manager continues to receive project-related work after the project has been released into production, it suggests that the project closure phase was not completed properly. The project closure phase involves several activities, including ensuring that all project deliverables are accepted, documenting the lessons learned, releasing project resources, and formally closing the project. If these activities are not completed, the project can remain ‘open’ in a sense, leading to continued work and inquiries.

References = The answer is based on standard project management practices and the importance of the project closure phase as described in project management literature. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources. Specific references to the closure phase can be found in the CompTIA Project+ PK0-005 Cert Guide1 and the CompTIA Project+ Certification Exam Objectives2.

The communication plan defines the meeting cadence, frequency, participants, formats, and methods of communication. If participation is low, the project manager refers to this plan for validation and adjustment. This is part of governance and compliance to ensure the right stakeholders are engaged appropriately.

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.

Scrum is an Agile framework that is well-suited for projects with rapidly changing requirements. It operates in iterative cycles called sprints, allowing for regular reassessment and adaptation of project goals. This flexibility makes Scrum ideal for environments where the company's strategy and product requirements evolve frequently, as it facilitates continuous improvement and responsiveness to change.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.2: Compare and contrast Agile vs. Waterfall concepts, Scrum is highlighted as a methodology that supports adaptability and iterative development.

For teams distributed across different regions, effective collaboration tools are essential. A wiki knowledge base allows team members to access and contribute to shared information asynchronously, while real-time, multi-authoring editing software enables simultaneous collaboration on documents.

The CompTIA Project+ PK0-005 exam objectives, under Domain 3.1: Given a scenario, use the appropriate tools throughout the project life cycle, highlight the importance of collaboration tools:

"Collaboration tools: Real-time, multi-authoring editing software; Wiki knowledge base."

CompTIA Project+ PK0-005 Exam Objectives

These tools facilitate seamless collaboration, knowledge sharing, and document management among geographically dispersed team members.

A transition plan is a document that outlines how the project deliverables will be transferred to the operations team or the end users, and how the project team will disengage from the project. It typically includes details such as operational training, go-live date, support arrangements, roles and responsibilities, and acceptance criteria. A transition plan is different from a project closeout report, which summarizes the project performance, lessons learned, and final status. A handover to operations is a process of transferring the project deliverables to the operations team, but it is not a document. A phase-gate review documentation is a set of documents that are used to evaluate the project progress and readiness to move to the next phase, but it is not related to the operational handoff. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 14: Closing the Project, p. 409-410; [CompTIA Project+ Certification Exam Objectives], Domain 4: Project Closure, Objective 4.1: Compare and contrast various project closure activities.

An RFP (request for proposal) is a document that solicits proposals from potential vendors for a specific project or service. An RFP typically describes the project scope, requirements, evaluation criteria, and instructions for submitting proposals. An RFP is the best document for the company to use to obtain and compare information on cabling services and costs from various vendors, as it allows the company to evaluate the vendors’ qualifications, experience, approach, and pricing12.

Risk transfer means shifting ownership and impact of a risk to a third party—commonly via contracts, insurance, warranties, or outsourcing. Moving procurement under the general contractor transfers the procurement responsibility (and much of the delivery-delay risk) to that contractor, who is then contractually accountable for sourcing and timely delivery. This matches CompTIA Project+ risk strategy concepts where transfer is used when another party is better positioned to manage the risk and can accept it contractually.

The other options are mitigation, not transfer. Determining alternative supplies (A) and sourcing locally (B) reduce the probability/impact of delays by creating backup options—classic mitigation. Scheduling deliveries earlier (D) is also mitigation via schedule/procurement adjustments and buffering. None of those shift the risk to another party; they keep the risk with the project team while reducing exposure.

Therefore, the action that best represents transferring the risk is moving procurement under the general contractor, assuming the contract terms make them responsible for procurement performance and delivery timing.

Assessing the resource pool is the process of identifying and evaluating the availability, skills, and costs of the resources needed for the project. The PM reviews the SOW from the contractor to understand the scope and requirements of the project, grades the full-time equivalents’ resumes to determine their qualifications and suitability for the project, evaluates the titles and salaries to estimate the budget and allocation of the resources, and estimates the number of hours for each milestone by full-time equivalents to plan the schedule and workload of the project12.

RACI is a tool that best illustrates how team members with different roles should interact on the team. RACI is an acronym that stands for responsible, accountable, consulted, and informed. RACI is a type of responsibility assignment matrix (RAM) that defines and clarifies the roles and responsibilities of each team member for each task or activity in a project. RACI can help to improve communication, collaboration, and accountability among team members and avoid confusion, duplication, or conflicts3

The system is lacking proper access controls if a third-party vendor was able to see secured project information in a recently implemented system that resulted in a fine for the organization. Access controls are security mechanisms that regulate who or what can view, use, or modify data or resources in a system or network. Access controls typically involve authentication and authorization processes that verify the identity and permissions of users or devices before granting them access. Access controls can help to protect data confidentiality, integrity, and availability and prevent unauthorized access, misuse, or theft12

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.

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.

When a project involves new or unfamiliar technologies, it's essential to ensure that the project team has the necessary knowledge and skills. Providing training to team members helps bridge knowledge gaps and prepares them to handle project tasks effectively. Simultaneously, developing a detailed scope statement clarifies the project's objectives, deliverables, and boundaries, which is crucial for guiding the team's efforts and setting stakeholder expectations.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.2: Given a scenario, determine the appropriate scope management activities, training and scope definition are key activities in managing project scope and ensuring team readiness.

The project manager should have identified and assessed the building owner as a key stakeholder in the initiation phase, and understood their expectations and requirements for the application. This would have helped to avoid the conflict over the corporate colors and the delay in testing. Stakeholder identification and assessment is an important process in the initiation phase, as it helps to define the project scope, objectives, and success criteria, and to establish a communication plan12. References = CompTIA Project+ PK0-005 Certification Study Guide,

Platform as a Service (PaaS) is designed to accelerate software delivery by providing a managed platform that typically includes the operating system layer, runtime, middleware, databases, and developer tooling—so teams can focus on building the service rather than provisioning and maintaining infrastructure and OS components. This directly supports the goal of speeding development and delivery while integrating closely with OS-level services provided by the platform (e.g., runtime services, identity, logging, scaling, patching). CompTIA Project+ includes understanding cloud models as part of IT concepts that affect project delivery choices.

By comparison, SaaS is a finished application you consume (not a development platform). IaaS provides raw compute/storage/networking; you still manage the OS and much of the stack, which is slower for development acceleration. DaaS generally refers to delivering desktops or data services depending on context, but it is not the standard model for speeding application development via an integrated platform stack.

Therefore, PaaS best matches the scenario: it reduces setup/maintenance work, standardizes environments, and helps teams deliver software faster and more reliably.

This work is best described as current state vs. future state analysis. The team first examined the existing process (the current state), identified areas of improvement (gaps/pain points), and then defined the desired outcomes (the future/target state). In CompTIA Project+ discovery/concept preparation activities, teams are expected to understand the problem/opportunity clearly before planning the solution; comparing the current state to the desired future state is a standard way to define what must change and what “better” looks like, and it becomes a foundation for scope definition and transition planning.

It’s not “process improvement” as the primary label here because that term typically describes the initiative type or the resulting actions, while the question is asking what the analysis itself is called. It’s also not “business objectives” (those are broader strategic goals), and it’s not “project success criteria” (the measurable conditions used to judge success). Those may come later, derived from the current-vs-future gap, but the described activity is the gap comparison between how things work now and how they should work after the project.

If team members are confused about which meetings to attend, this indicates a flaw in the communication plan. Revising the plan ensures clear expectations on who participates in which communication events. Scope or schedule changes don’t automatically require altering the communication plan.

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

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.

After identifying logical dependencies in schedule planning, the next practical step is to determine the resources required to complete the tasks. Dependencies define task order; resource planning then identifies who/what is needed (people, equipment, materials) and informs realistic duration estimates, resource leveling, and schedule feasibility. In Project+ planning practices, schedule development is tightly linked with resource planning—because you can’t finalize a reliable schedule without understanding capacity constraints and resource availability.

Option A (stakeholders positively impacted) is a stakeholder analysis activity, but it does not directly progress schedule planning after dependencies are defined. Option B (escalation reporting tool) is governance/communication planning, not the next scheduling step. Option D (total cost incurred) is an execution-phase cost tracking activity and cannot be determined during schedule planning.

So, once sequencing is known, the PM should identify and assign the resources needed for each activity, check availability, and adjust the schedule accordingly (including potential resource leveling or trade-offs). This creates a schedule that is not only logically correct but also executable with the available capacity.

The project manager should have considered environmental, social, and governance (ESG) factors during initial planning to prevent the situation of receiving a penalty for disposing of some computers improperly. ESG factors are criteria that measure the sustainability and ethical impact of an organization’s activities. They include aspects such as environmental protection, social responsibility, human rights, diversity, and corporate governance. Considering ESG factors can help to reduce risks, improve reputation, and enhance performance of an organization12

A decision tree helps in evaluating various choices and their potential outcomes, making it suitable for comparing vendors based on costs and risks. This aligns with CompTIA Project+ methodologies for decision-making tools and analysis.

Operational security is the process of identifying, protecting, and controlling sensitive information and activities from unauthorized access or disclosure. Operational security includes background screenings for personnel who need to access classified or restricted information or resources, as well as implementing policies and procedures to prevent leaks, breaches, or espionage. Operational security is essential for government projects that involve national security, defense, intelligence, or law enforcement.

Operational security is different from data security, which is the process of safeguarding data from unauthorized access, use, modification, or destruction. Data security includes encryption, authentication, authorization, backup, and recovery of data. Operational security is also different from physical security, which is the process of securing physical assets, such as equipment, data, or personnel, from unauthorized access or damage. Physical security includes locks, alarms, cameras, guards, and fences. Operational security is also different from digital security, which is the process of protecting digital devices, networks, and systems from cyberattacks, malware, or hacking. Digital security includes firewalls, antivirus, VPN, and passwords. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 9: Security Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 9: Security Management2; What is Operational Security (OPSEC)?3

Electronic document and record management systems would be the best software solutions to help an institution manage the internal flow for formally responding in writing to citizens’ complaints. Electronic document and record management systems are software systems that help organizations create, store, organize, manage, track, and distribute electronic documents and records. Electronic document and record management systems can help to improve efficiency, productivity, collaboration, compliance, and security of document and record management processes and workflows3

Evaluating the impact to baselines (such as schedule and budget) helps determine the delay’s effect on the project. This aligns with CompTIA Project+ guidance on project control, which emphasizes analyzing impacts before taking corrective actions.

When a project manager achieves a compromise, it often means that stakeholders may not be entirely satisfied with the outcome. However, compromise is sometimes necessary to balance differing needs, consistent with CompTIA Project+ principles on stakeholder management and negotiation.

Zero-based budgeting involves starting from a “zero base” and justifying each expense without reference to previous budgets. This budgeting method promotes financial discipline and aligns with CompTIA Project+ guidelines on budget control and justification.

DevOps architecture integrates development and operations to enhance the software development lifecycle. It emphasizes continuous integration and delivery, automation, and collaboration, ensuring that factors like reliability, scalability, security, and cost-effectiveness are integral to project goals and objectives. By adopting DevOps practices, organizations can achieve faster deployment times, improved system stability, and efficient resource utilization.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Explain the basic characteristics of a project and various methodologies and frameworks used in IT projects, DevOps is recognized as a methodology that supports these critical factors.

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 backlog is commonly used in agile project management to list deliverables and tasks that have not yet been completed. It allows the project manager to prioritize and organize the workload, especially for complex projects. This aligns with agile principles as outlined in CompTIA Project+.

An issue log is a document that records and tracks any issues that arise during a project and how they are resolved1. It is different from a risk register, which records and tracks potential risks that may or may not occur during a project2. When a risk becomes an issue, it means that it has occurred and has a negative impact on the project. Therefore, the project manager should update the issue log next to document the compliance issue, its cause, its impact, its priority, its owner, and its resolution status3. Updating the issue log will help the project manager communicate the issue to the stakeholders, monitor the progress of the mitigation plan, and prevent similar issues from happening again4. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 11: Executing Projects Part 2, page 331; Project Risk Mitigation Guide + Starter Kit | Smartsheet, Risk Register section; How to Make a Risk Management Plan (Template Included) - ProjectManager, Risk Register section; Issue Log - Project Management Knowledge, Introduction section; Issue Log Template: Free Download | ProjectManager, Introduction and How to Use an Issue Log sections.

The project manager should address the issue of damage to the monitor first because it has the highest percentage (40%) among the issues observed. This means that it is the most frequent and severe issue that affects the quality and functionality of the refurbished desktops. Addressing this issue first can help to improve customer satisfaction, reduce rework, and avoid waste1

The project manager should consult a Gantt chart after the sponsor states that the project is taking too long to complete. A Gantt chart is a graphical tool that shows the schedule of a project, including the start and end dates, durations, dependencies, milestones, and progress of each task or activity. A Gantt chart can help to monitor and control the project timeline and identify any delays, variances, or issues that may affect the project completion.

 The project manager should exploit the risk after an opportunity emerged in the middle of a project life cycle. Exploit is a risk response strategy that aims to increase the probability and/or impact of a positive risk or opportunity. Exploit can involve actions such as allocating more resources, changing the scope or schedule, or adding more features or benefits to the project deliverables. Exploit can help to ensure that the opportunity is realized and that the project gains more value or advantage from it3

Using a corporate virtual private network (VPN) over a secure home internet connection is the most secure method for remote access. A VPN encrypts the data transmitted between the user's device and the company's network, protecting sensitive information from potential interception.

In the CompTIA Project+ PK0-005 exam objectives, under Domain 4.3: Explain the importance of risk strategies and activities, understanding secure methods for remote access is emphasized .

By connecting through the corporate VPN, the team member ensures that the emergency update is performed securely, maintaining the integrity and confidentiality of the company's systems and data.

The project manager should approve the deliverables and monitor the performance of the outsourced structured cabling activities. These are the responsibilities of the project manager when dealing with external vendors or contractors, as they ensure that the quality standards, scope, schedule, and budget are met according to the contract terms and the project plan. The project manager should also communicate regularly with the vendor and provide feedback and guidance as needed. The other options are not correct because:

Purchasing the materials is not the responsibility of the project manager, but the vendor who is performing the structured cabling activities. The project manager should only verify that the materials are suitable and available for the project.

Assigning the resources is not the responsibility of the project manager, but the vendor who is performing the structured cabling activities. The project manager should only ensure that the vendor has the adequate and qualified resources to complete the work.

Accepting delays in the work is not a good practice for the project manager, as it can negatively affect the project schedule, scope, and quality. The project manager should proactively identify and manage the risks and issues that may cause delays, and implement contingency plans or corrective actions if necessary.

Negotiating with the vendors is not a task that the project manager should do during the execution of the structured cabling activities, as it should have been done during the planning and procurement phases of the project. The project manager should only adhere to the contract terms and conditions that have been agreed upon with the vendor, and only renegotiate if there are significant changes or disputes that require it. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Planning Projects, Part 4 (Procurement and Communication), pages 243-260; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.5: Given a scenario, plan procurement for a project; Domain 3: Project Execution, Objective 3.2: Given a scenario, execute and monitor project tasks using traditional methodologies.

ERP (Enterprise Resource Planning) systems are designed to integrate and manage all core functions of a business, such as finance, HR, and supply chain management. This aligns with CompTIA Project+ guidelines on selecting appropriate systems for organizational needs.

Adding contingency buffers to the critical path is a method to account for potential delays, increasing project certainty. This technique is part of risk management and schedule management, as recommended by CompTIA Project+.

Archiving project documentation is an important process to ensure that the project information is stored, retrieved, and updated in a consistent and efficient manner1. It also helps to meet legal requirements, enable long-term analysis, and support new projects and team members1. If the documentation was not archived as per the PMO standards, it would be difficult for the current project manager to find the relevant documents and learn from the previous project. This would cause the current project manager to keep asking questions to the previous project manager, who may not have all the answers or may not be available. Therefore, the most likely cause of this situation is that the documentation was not archived as per the PMO standards. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing the Project, page 403; How to Archive a Completed Project: A Guide for PMOs, Introduction and Benefits sections.

A business collaboration tool is a software that enables teams to communicate, share, and create together online. A business collaboration tool can help project teams across multiple time zones to overcome the challenges of distance, time differences, and cultural diversity. A business collaboration tool can provide features such as instant messaging, video conferencing, file sharing, document editing, project management, and more. A business collaboration tool can also integrate with other applications and platforms that the project team uses. A business collaboration tool can improve the efficiency, productivity, and quality of the project team’s work12. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Communications, p. 137; The 15 best collaboration tools for productive teams - Workable; 17 Best Business Collaboration Tools for Teams - Venngage

Option C shows a graph that most likely represents the observed relationship in this scenario. The graph shows a learning curve, which is a graphical representation of the relationship between a learner’s performance on a task and the number of attempts or time required to complete the task. The learning curve theory proposes that a learner’s efficiency in a task improves over time the more the learner performs the task. In this case, the IT intern was able to complete more set-ups in less time as they gained more experience and proficiency over the two-week rotation12

The project charter is a foundational document that formally authorizes a project and provides the project manager with the authority to apply organizational resources to project activities. Reviewing the project charter is essential at the outset to understand the project's objectives, scope, stakeholders, and any constraints or assumptions. This understanding is crucial, especially for large, complex projects with regulatory and environmental considerations, as it sets the direction for detailed planning and stakeholder engagement.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.1: Explain the value of artifacts in the discovery/concept preparation phase for a project, the project charter is a key artifact that guides the initiation and planning phases.

The client provided a statement of work (SOW) to the project manager and suggested that the project manager and team just need to execute the plan. 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.

The next step after defining tasks, durations, resources, and costs is to establish baselines. A baseline is an approved version of a project plan that serves as a reference point for measuring progress and performance throughout the project lifecycle. A baseline typically includes scope, schedule, cost, quality, and risk parameters. Establishing baselines involves presenting the project plan to key stakeholders and obtaining their formal agreement on the project objectives and deliverables. Baseline approval can help to establish clear expectations, avoid scope creep, and facilitate change control during project execution34

A collaboration tool best prevents confusion from multiple file copies because it typically provides a single source of truth with centralized storage, access control, and version management (e.g., one authoritative document link rather than many emailed attachments). CompTIA Project+ highlights the importance of maintaining project documentation and also references document/record management capabilities (e.g., electronic document and record management systems and content management systems), which support controlled storage and retrieval of artifacts—exactly what reduces duplicate-copy confusion.

A knowledge base can store guidance and finalized information, but it may not fully solve “multiple copies” if teams still circulate separate versions outside the system. A ticketing system is best for tracking requests, defects, and work items; it can link to documents, but it’s not primarily designed for document version control. Print media is the worst option because it creates even more uncontrolled copies and can go out of date immediately.

Using a collaboration tool (or integrated document management within it) lets the PM enforce conventions like: “share links, not files,” require check-in/check-out or tracked changes where needed, and maintain clear naming/version rules—reducing rework and misalignment.

The critical path is the sequence of tasks that determines the minimum project duration. It is the longest path through the network diagram and has the least amount of slack or float. Based on the provided network diagram, the critical path is A-C-G-K-M, which has the longest total duration when adding up the individual task durations. References = The concept of the critical path is covered in the CompTIA Project+ Certification Study Guide1. For more detailed information on how to calculate and identify the critical path in project management, you can refer to the study guide and other project management resources2.

The PM should create a project organizational chart to clarify who is who, reporting lines, and role visibility across the team. When team members are unclear about each other’s roles, the fastest way to reduce confusion is to make the project structure explicit: who leads which workstream, who approves decisions, who supports, and how to escalate. This aligns with Project+ people/resource management expectations: establish clear responsibilities and team structure to reduce duplication, gaps, and conflict caused by ambiguity.

A project plan is broader (scope/schedule/budget/governance), but it won’t necessarily provide a simple, visual map of roles. A road map is high-level sequencing of outcomes over time; it’s not meant to define roles. A milestone chart highlights key dates and deliverables, not responsibilities.

In practice, the PM often pairs the project org chart with a RAM/RACI for detailed accountability, but since the question asks which chart to create to fix role confusion, the best answer is the project organizational chart.

Chat messaging services are particularly effective for teams that are distributed globally across different time zones. These tools facilitate asynchronous communication, allowing team members to send and receive messages at their convenience, which is crucial when real-time communication is challenging due to time differences. This ensures continuous collaboration and information sharing without the constraints of synchronous meetings.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 3.2: Compare and contrast various project management productivity tools, chat messaging is highlighted as a key communication tool for distributed teams.

A Responsibility Assignment Matrix (RAM) is the best tool for assigning and clarifying roles and responsibilities. A RAM maps project work (deliverables, work packages, or tasks) to people/roles and defines who is responsible/ accountable, and who provides input or needs to be informed (often implemented as a RACI chart). CompTIA Project+ lists RAM/RACI-style responsibility mapping under planning and resource management practices because it prevents ambiguity, reduces duplication, and supports accountability. ()

The distractors are not designed for role assignment. ERP is an enterprise resource planning system used to manage business processes; it can store resource data but isn’t the PM artifact for defining responsibilities. JAR is not a standard project management responsibility tool in this context. CCB (Change Control Board) governs change requests; it does not assign day-to-day delivery responsibilities.

Using a RAM early (initiation/planning) helps the PM establish clear ownership, streamline handoffs, and support effective communication planning. It also reduces the risk of “I thought someone else was doing that,” which is a common execution failure mode when responsibilities are not explicitly documented. ()

The kickoff meeting is held at the beginning of a project to set direction and expectations. The most important activity is to review the project objectives and overall timeline so everyone understands the project’s scope and goals. Detailed assignments and communication planning are handled afterward in the execution and planning phases.

A milestone chart is a tool that shows the key events or deliverables of a project along a timeline12. A milestone chart is useful for tracking the progress of a project that has technical tasks and requires a SME’s knowledge, because it can provide a high-level overview of the project status, without getting into the details of each task or activity34. A milestone chart can help the PM and the project lead communicate the project achievements, challenges, and expectations to the stakeholders, and also identify any potential risks or delays that may affect the project completion56. A milestone chart is better than the other options because:

A Gantt chart is a tool that shows the tasks, dependencies, durations, and resources of a project along a timeline7. A Gantt chart is more detailed and complex than a milestone chart, and may not be suitable for providing high-level updates to the stakeholders8.

A project organization chart is a tool that shows the roles, responsibilities, and reporting relationships of the project team members and other stakeholders9. A project organization chart is not a tool for tracking project data, but rather for defining the project structure and authority10.

A Program Evaluation Review Technique (PERT) chart is a tool that shows the tasks, dependencies, and critical path of a project along a network diagram. A PERT chart is more focused on the sequence and timing of the project tasks, and may not capture the key milestones or deliverables of the project.

References = CompTIA Project+ Certification Study Guide, CompTIA Project+ Certification Exam Objectives, 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, What is a Gantt Chart?5, Gantt Chart vs Milestone Chart: What’s the Difference?6, What is a Project Organization Chart?7, How to Create a Project Organization Chart8, What is a PERT Chart?9, PERT Chart vs Gantt Chart: What’s the Difference?10

A warranty period is the time during which a manufacturer or seller agrees to repair or replace a product that is defective or does not meet the specified standards. A warranty period can be expressed in terms of duration (e.g., one year) or usage (e.g., 10,000 miles). A warranty period is a form of consumer protection that obliges the manufacturer or seller to bear the costs of repairing or changing any part of the product that is not functioning properly1.

The project manager should communicate with the affected stakeholders first after realizing that the sign-off for the project scope baseline is delayed due to multiple changes and that the budget for this project is restricted by the project sponsor. The affected stakeholders are those who have an interest or influence on the project and may be impacted by any changes or delays. Communicating with them can help to explain the situation, assess the impact, seek feedback, and manage expectations.

A risk register is used to document potential risks, including causes and impacts. This tool is essential for tracking and communicating project risks to stakeholders, as recommended by CompTIA Project+ for risk management.

This answer is based on the best practice of choosing a project management methodology that suits the project characteristics and environment12. Scrum is an agile framework that is designed to handle complex and uncertain projects with frequent changes and tight deadlines34. Scrum involves a small, cross-functional team that works in short iterations called sprints, delivering incremental and potentially shippable products at the end of each sprint5. Scrum also allows for continuous feedback and improvement through daily stand-up meetings, sprint reviews, and retrospectives6. Scrum is suitable for this project because it can accommodate the high uncertainty, the risk of requirement changes, and the tight deadlines, while also enabling the two developers to collaborate effectively and deliver value to the customer. References = CompTIA Project+ Certification Study Guide7, CompTIA Project+ Certification Exam Objectives8, Project Management Methodologies Comparison (11 PM Methods)6, Project Management Methodologies: 12 Best Frameworks [2023]7, What is Scrum?5, Scrum Methodology: The Ultimate Guide6

Before starting a new project that involves personal data, the project manager should first understand the relevant privacy regulations that apply to the data subjects, the data controllers, and the data processors. These regulations may vary depending on the location, industry, and nature of the data. For example, GDPR applies to any project that processes the personal data of individuals in the European Union, regardless of where the project is based or executed. Understanding the applicable privacy regulations will help the project manager to identify the legal obligations, risks, and compliance requirements for the project data. References = CompTIA Project+ Study Guide, Chapter 3: Project Planning, Section 3.4: Data Privacy and Security, p. 121-122; A Project Management Approach to Data Protection Compliance; 10 Data Protection Considerations Before Starting a New Project; Project Teams Must Manage Risk and New Requirements to Ensure Data Privacy

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.

A Preliminary Scope Statement outlines the initial project objectives, high-level requirements, and milestones. It serves as a foundational document during the initiation phase and is refined as the project progresses.

As per the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Compare and contrast different project management roles and responsibilities, developing a preliminary scope statement is a key activity in defining the project's direction and scope.

A proposal is a detailed document submitted by vendors outlining how they will meet project requirements. It helps in assessing vendor solutions and suitability, consistent with CompTIA Project+ procurement and vendor management practices.

The project manager should contact the project management office (PMO) for assistance after learning that a similarly time-consuming project was executed previously in the organization. A PMO is a department or group within an organization that provides centralized guidance, governance, standards, best practices, resources, and oversight for project management activities. A PMO can help the project manager by providing access to historical data, lessons learned, templates, tools, methodologies, and expertise from previous projects that can be useful for planning and executing the current project.

A wiki knowledge base is a tool that allows the project team to store, organize, and share information that is captured throughout the life cycle of a project. A wiki knowledge base is stored in a centralized location that is easily accessible to all stakeholders via a web browser. A wiki knowledge base also provides search functionality that enables the users to find the information they need quickly and easily. A wiki knowledge base can help the project team to document the project requirements, scope, schedule, budget, quality, risks, issues, lessons learned, and best practices.

A wiki knowledge base is different from a secure folder, which is a tool that protects the files and folders from unauthorized access or modification. A secure folder may not be easily accessible to all stakeholders, and may not provide search functionality or collaboration features. A wiki knowledge base is also different from a real-time, multiauthoring editing software, which is a tool that allows the project team to create and edit documents simultaneously and synchronously. A real-time, multiauthoring editing software may not be suitable for storing large amounts of information, and may not provide the same level of organization and structure as a wiki knowledge base. A wiki knowledge base is also different from a digital whiteboard, which is a tool that allows the project team to brainstorm, visualize, and communicate ideas. A digital whiteboard is not designed for storing information, and may not provide the same level of search functionality or security as a wiki knowledge base. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 3: Project Communications Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 3: Project Communications Management2; The 15 best collaboration tools for productive teams3

A burndown chart tracks how much work remains over time in an iteration (or release). The most direct inputs are the remaining work and the work completed (often expressed as tasks, story points, or hours). Therefore, to obtain burndown data efficiently, the PM should analyze remaining and completed tasks. This aligns with CompTIA Project+ Agile metrics concepts, where burn charts are used to visualize progress and forecast completion based on work remaining versus time.

The other options are not primary burndown inputs. “Number of people available” affects capacity and can influence how fast work burns down, but it is not what the chart directly measures. “Cost variance” is an earned value / financial control concept (more predictive/traditional) and not what burndown charts are built from. “Number of issues registered” is useful for quality and risk/issue tracking but does not represent the work remaining in the sprint backlog unless issues are explicitly counted as backlog items—and even then, the chart is still fundamentally about remaining work, not raw issue counts.

So, for efficient burndown extraction, the PM should use the team’s work tracking (sprint backlog/task board) to calculate remaining vs. completed tasks/work, which is exactly what the burndown visualizes.

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.

Kanban is a visual workflow management method that aims to maximize efficiency and promote continuous improvement by visualizing work, limiting work in progress, and enhancing flow.

The CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Explain the basic characteristics of a project and various methodologies and frameworks used in IT projects, include Kanban as a methodology:

"Methodologies and frameworks: Kanban."

CompTIA Project+ PK0-005 Exam Objectives

Kanban helps teams manage work by visualizing tasks and optimizing the flow from start to finish, aligning with the principles of efficiency and continuous improvement.

Defining communication channels and access requirements typically occurs in the planning phase, where detailed plans for project management are established. This aligns with CompTIA Project+ standards for comprehensive project planning.

Using the chat and plain language can help overcome the communication barriers caused by accents and background noises. Chat allows team members to write down their ideas and questions, which can be easier to understand than spoken words. Plain language reduces the ambiguity and complexity of the messages, making them more clear and concise. These techniques can also enhance the participation and engagement of the team members, as they can express their thoughts and opinions more comfortably and confidently. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Communication and Change Management, p. 97-98.

The project manager should use synchronous communication methods if they prefer to have immediate contact with team members. Synchronous communication is a type of communication that occurs in real time and allows for faster response times and more interactive discussions. Examples of synchronous communication methods include phone calls, video conferences, instant messaging, and face-to-face meetings. Synchronous communication can help to build rapport, clarify doubts, and resolve issues quickly among team members.

Synchronous communication should be used when the project manager prefers to have immediate contact with team members. Synchronous communication allows for real-time interaction and feedback, enabling faster response times and more interactive discussions. References: CompTIA Project+ Study Guide Section 3.1.3

A self-organized team is a typical characteristic of Scrum, which is an agile framework for managing complex projects. A self-organized team is a group of motivated and skilled individuals who have the autonomy and authority to make decisions and collaborate on how to deliver the project goals. A self-organized team does not rely on a manager or a leader to assign tasks, monitor progress, or resolve issues. Instead, a self-organized team uses Scrum events, such as daily stand-ups, sprint planning, sprint review, and sprint retrospective, to coordinate their work, communicate with each other, and inspect and adapt their process and product123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 2: Project Methodologies, p. 55; Scrum Characteristics - Scrumversity; What is Scrum? | Scrum.org; Characteristics of a Great Scrum Team | Scrum.org

Sharing a resource like an API between projects to leverage each project's strengths and reduce duplicated efforts is a risk-sharing strategy. CompTIA Project+ outlines risk-sharing as a way to capitalize on opportunities or mitigate project constraints.

Once a work-around is in place, the next best step is root cause analysis (RCA) to identify and remove the underlying cause so the defect does not recur and so the permanent fix can be designed correctly. CompTIA Project+ explicitly includes issue management activities such as handling work-arounds and performing root cause analysis, indicating that RCA is a standard follow-on control after stabilizing the situation.

Submitting a change to the CCB (A) may be necessary later if the permanent fix requires a formal change request, but RCA should come first so the team knows what change is actually needed and can accurately assess impact/risk. Escalating to a steering committee (C) is reserved for high-severity governance decisions (e.g., major budget/scope shifts), and may not be required if the team can resolve within existing authority. Updating the risk register (D) can be appropriate (e.g., record the risk of recurrence), but this is secondary to diagnosing and eliminating the defect’s cause.

So, after implementing a temporary work-around, the correct next action is to perform root cause analysis.

Enterprise resource planning (ERP) software is a type of software that integrates various business functions and processes, such as accounting, finance, inventory, sales, purchasing, human resources, and more. ERP software helps businesses store, organize, and manage information related to business transactions, such as invoices, payments, orders, receipts, and reports. ERP software also provides real-time data analysis, reporting, and forecasting capabilities12.

Escalating to the Change Control Board (CCB) is necessary when a change request impacts the project’s timeline or budget. The CCB reviews and approves changes, ensuring that they align with project objectives. CompTIA Project+ highlights the role of the CCB in change management processes.

The project manager and team should review assumptions and constraints for input to the risk register during the planning phase of a project. Assumptions are statements that are considered to be true for the purpose of planning, but may or may not be valid in reality. Constraints are factors that limit the project scope, time, cost, quality, or resources. Both assumptions and constraints can introduce risks to the project, which are uncertain events or conditions that can have a positive or negative impact on the project objectives. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, owners, and status. Reviewing assumptions and constraints can help the project manager and team identify, analyze, prioritize, and plan for the potential risks that may affect the project12.

The other options are not the correct activities that the team should do during the planning phase of a project. Identifying and assessing stakeholders (option A) is an activity that is done during the initiating phase of a project, not the planning phase. Stakeholders are individuals or groups that have an interest or influence in the project, and their identification and assessment is important to define the project scope, objectives, and success criteria, and to establish a communication plan12. Holding daily status meetings (option B) is an activity that is done during the executing and monitoring and controlling phases of a project, not the planning phase. Daily status meetings are short and frequent meetings where the project team members report on their progress, issues, and plans for the next day. Daily status meetings can help the project manager track the project performance, resolve problems, and communicate updates12. Removing access and planning the project sign-off (option C) is an activity that is done during the closing phase of a project, not the planning phase. Removing access is a security measure to ensure that the project resources do not have access to the project systems, data, or assets after the project is completed. Planning the project sign-off is a process to obtain the formal acceptance and approval of the project deliverables from the stakeholders and customers12.

A contingency plan is a risk mitigation strategy that involves preparing alternative courses of action in case the original plan fails or encounters unexpected problems. A contingency plan can help reduce the impact of negative risks and ensure the project continuity and success. In this case, the project manager should develop a contingency plan to mitigate the risk of hurricanes affecting the implementation of the new radar system. For example, the contingency plan could include backup resources, alternative locations, emergency procedures, and communication channels in case of a hurricane. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Risk Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 7: Risk Management

Removing access means revoking the contractor’s permissions to access the project data, systems, and devices after the project is closed. This is a crucial security measure to prevent unauthorized access, misuse, or theft of sensitive data by external parties. Closing contracts, project sign-off, and project evaluation are important steps in the project closure process, but they do not necessarily prevent data theft by themselves. They may involve formal agreements, documentation, and feedback, but they do not address the technical aspects of data security. References = CompTIA Project+ Study Guide: Exam PK0-005, Third Edition, Chapter 14: Closing the Project, page 3771; 9 Ways to Prevent Third-Party Data Breaches in 20232; 3 Ways to Prevent Data Theft by Contractors3

Avoiding is a conflict resolution technique that involves postponing or withdrawing from a conflict situation. The project manager is using this technique by taking a break and continuing the meeting on another day, hoping that the conflict will resolve itself or become less important over time. This technique may be appropriate when the conflict is trivial, the potential damage is greater than the benefits, or more information is needed before making a decision. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Executing and Closing Projects, page 287; [CompTIA Project+ Certification Exam Objectives], Domain 3: Project Execution, Objective 3.2: Given a scenario, apply appropriate conflict resolution techniques.

Closing contracts involves finalizing any remaining contractual obligations and formally closing out the relationship with the vendor. CompTIA Project+ emphasizes this as part of the project closure phase to ensure all legal and financial aspects are complete.

Quantitative risk analysis involves numerically analyzing the effect of identified risks on overall project objectives. It often includes assigning monetary values to risks to understand their impact in financial terms, helping in prioritizing risks based on their potential cost or impact on the project. This contrasts with qualitative risk analysis, which assesses risks based on their probability and impact but does not assign numerical values.

The waterfall methodology is a project management framework that follows a linear and sequential process, where each stage of the project must be completed before moving on to the next one. The stages of the waterfall model are initiation, planning, execution, and closure, as described in the question12.

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

The Project Gantt chart is a scheduling tool used to track task progress and timelines. When tasks are completed ahead of schedule, updating the Gantt chart ensures accurate tracking. This aligns with CompTIA Project+ recommendations on project scheduling and monitoring.

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.

This answer is based on the best practice of issue management in project management, which is to identify, analyze, prioritize, and resolve issues that affect the project performance, scope, schedule, quality, or budget12. The first step in this process is to rate the severity of the impact the issue has on the project, which involves assessing the likelihood and consequences of the issue, and assigning a rating or score to the issue based on a predefined scale or criteria34. By rating the severity of the impact, the project manager can determine the urgency and importance of the issue, and decide the appropriate course of action to address the issue56. Rating the severity of the impact is better than the other options because:

Buying a replacement for the faulty equipment may not be feasible, cost-effective, or timely, depending on the availability, price, and delivery time of the equipment. It may also require approval from the project sponsor or other stakeholders, and may affect the project budget or scope7.

Getting the maintenance team to resolve the issue may not be possible, depending on the nature and extent of the malfunction, the skills and availability of the maintenance team, and the warranty or service contract of the equipment. It may also take time and resources to diagnose and fix the problem, and may cause further delays or disruptions to the project8.

Escalating the issue to the project sponsor may not be necessary, depending on the severity and complexity of the issue, and the authority and responsibility of the project manager. It may also create unnecessary alarm or confusion among the project stakeholders, and may undermine the project manager’s credibility or autonomy9.

References = CompTIA Project+ Certification Study Guide, CompTIA Project+ Certification Exam Objectives, What is Issue Management?1, Issue Management Process2, How to Assess the Severity of Project Issues3, How to Prioritize Project Issues4, How to Replace Faulty Equipment in Project Management5, How to Manage Equipment Maintenance in Project Management6, How to Escalate Issues in Project Management7

A RACI chart would be the most useful option for the project manager to illustrate roles for major project activities for an upcoming project kickoff. A RACI chart is a visual representation of a RACI matrix that shows who is responsible, accountable, consulted, and informed for each task or activity in a project using a table format. A RACI chart can help to communicate and document the roles and expectations of each team member and stakeholder for the project and ensure alignment and agreement.

Obtaining project sign-off is crucial in the closure phase, as it signifies formal acceptance of the project deliverables by the stakeholders. According to CompTIA Project+, project sign-off is a key milestone in officially closing the project.

A project evaluation review is a tool that helps a project manager assess the activities performed, work effort applied, and the productivity of a project. It involves collecting and analyzing data on the project’s performance, outcomes, and impacts. It also provides feedback and recommendations for improvement and learning. A project evaluation review can be done at different stages of the project life cycle, such as during or after completion. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 14: Project Evaluation and Assessment; CompTIA Project+ Certification Exam Objectives, Domain 4: Project Closure, Objective 4.1: Conduct project closure activities.

An issue log is a tool that records and tracks any issues that arise during the project. It helps the project manager to identify, prioritize, assign, monitor, and resolve the issues in a timely manner. An issue log can also include information such as the issue description, impact, status, owner, and resolution date1. An issue log is different from a defect log, which records and tracks the defects or errors in the project deliverables. A risk register is a tool that records and tracks the potential risks that may affect the project objectives. A change log is a tool that records and tracks the changes that are made to the project scope, schedule, budget, or quality2.

An Ishikawa diagram is a tool that the project team should use to find the cause of the defects associated with project deliverables. An Ishikawa diagram, also known as a fishbone diagram or a cause-and-effect diagram, is a graphical tool that shows the possible causes of a problem or effect using a fishbone-like structure. An Ishikawa diagram can help to identify and analyze the root causes of defects or issues and find solutions to prevent or eliminate them.

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 real-time survey is a tool that allows the project manager to collect feedback from the project team members in an interactive and timely manner. A real-time survey can measure the level of engagement, satisfaction, motivation, and performance of the team members, as well as identify any issues, challenges, or opportunities for improvement. A real-time survey can also increase the participation and collaboration of the team members, as they can see the results and comments of their peers instantly. A real-time survey is more effective than a meeting chat, an email, or a whiteboard, as it can reach a larger and more diverse audience, provide more structured and quantitative data, and avoid distractions and interruptions. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Closure, p. 367; The 9 best online survey apps in 2023 | Zapier

 The project manager is creating a quality assurance plan when identifying multiple techniques that will help the project team ensure confidence and alignment with the project scope and goals during a brainstorming meeting. A quality assurance plan is a plan that defines and documents the standards, criteria, methods, activities, and tools for ensuring and verifying that the quality requirements and expectations of a project are met. A quality assurance plan can help to improve the quality of the project processes and deliverables and prevent or reduce defects or errors.

A project closure meeting is a formal gathering held at the end of a project timeline. Its chief purpose is to evaluate the project’s performance, identify and discuss the achieved outcomes, successes, and challenges, and confirm that all predefined tasks and objectives have been completed successfully1. The project closure meeting also involves obtaining project sign-off from all necessary parties, such as the project sponsor, the client, the stakeholders, and the team members. Project sign-off is the official approval that the project has met the agreed-upon criteria and quality standards, and that the project is formally closed2.

The results are best described as a positive correlation: as extra hours worked increase, the number of defects also increases. A positive correlation means the variables move in the same direction (higher X is associated with higher Y). This is consistent with the common quality-management interpretation that sustained overtime can correlate with higher error rates due to fatigue, reduced review quality, and rushed work—an important insight for a PM balancing schedule pressure with quality outcomes.

Within Project+ quality and performance monitoring concepts, interpreting basic analytical outputs (such as charts/diagrams that show relationships) supports better decisions about staffing approaches, sustainable pacing, and corrective actions (e.g., limiting overtime, increasing peer review, adding automated tests, or re-planning). The distractors represent other possible patterns: “no correlation” would show scattered results without a trend; “negative correlation” would show defects decreasing as hours rise (unlikely for overtime/fatigue scenarios); and “non-linear” would require evidence of a curved pattern rather than a straight trend. Based on the stated results interpretation for this scenario, the correct description is positive correlation.

A Sprint Review involves reviewing the completed backlog items and presenting the work to stakeholders. This aligns with CompTIA Project+ agile practices, where a Sprint Review focuses on completed tasks and feedback.

The project manager should communicate the change deployment next after updating the project plan with the newest project end date as a result of an approved change. Communicating the change deployment involves informing all relevant parties about when and how the change will be implemented and what are the expected outcomes and benefits. Communicating the change deployment can help to ensure alignment, readiness, and support for the change and avoid any confusion or resistance.

Operational security (OPSEC) is a process that prevents sensitive information from getting into the wrong hands by viewing operations from the perspective of an adversary1. Facility access is a form of OPSEC that controls who can enter and exit a physical location where sensitive data or equipment is stored or processed. Facility access can include measures such as locks, alarms, badges, biometrics, guards, and cameras. The other options are not correct because:

Mobile device compliance is a policy that ensures that mobile devices used by employees or contractors meet certain security standards and requirements, such as encryption, password protection, antivirus, and remote wipe. Mobile device compliance is not a form of OPSEC, but rather a form of data security or device management.

Background screening is a process that checks the criminal, financial, and employment history of a potential employee or contractor before hiring them. Background screening is not a form of OPSEC, but rather a form of human resource management or risk mitigation.

Multifactor authentication is a method that requires users to provide two or more pieces of evidence to verify their identity before accessing a system or service, such as a password, a code, a token, or a biometric. Multifactor authentication is not a form of OPSEC, but rather a form of access control or identity management. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Executing and Closing Projects, page 314; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.2: Given a scenario, execute and monitor project tasks using traditional methodologies; What is Operational Security? The Five-Step Process, Best Practices, and More

The first step in planning maintenance windows is to understand the organization's production cycle. This knowledge ensures that maintenance activities are scheduled during periods that minimize impact on operations.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.4: Explain the importance of change control and maintenance, understanding operational cycles is essential for effective maintenance planning.

Unit testing is a testing technique that verifies the functionality and quality of individual units or components of software, such as modules, classes, functions, etc. Unit testing can help prevent issues with preexisting capabilities by detecting and fixing errors at an early stage of development, before they affect the integration and system testing. Unit testing can also ensure that new capabilities do not break or interfere with the existing ones, by checking the compatibility and dependencies of the units. Unit testing can be performed by developers using tools and frameworks that automate the process and generate reports. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 10: Project Quality Management; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.2: Execute quality management activities.

IaaS (Infrastructure as a Service) provides virtualized computing resources, such as storage and servers, necessary for hosting a development environment. According to CompTIA Project+, IaaS is ideal for environments requiring infrastructure control without hardware management.

This describes a transition plan (also called a release plan) because it focuses on moving a deliverable into production/go-live, defining the target audiences/users, and identifying operational training needs. The CompTIA Project+ objectives explicitly list “Develop a transition plan/release plan” and include example components such as operational training, go live, operational handoff, and identifying internal vs. external audience—all of which match the scenario.

A contingency plan is for responding to risks/issues if something goes wrong, not the standard production handover approach. A scope statement defines what work/deliverables are included and excluded, but it doesn’t detail production cutover, operational ownership, or training. A communication plan defines how information is shared (who, what, when, and through what channels), but it is not specifically the go-live and operational handoff blueprint.

So, because the team is planning deployment/move to production plus user identification and training, they are developing the transition plan.

The PM is building a Work Breakdown Structure (WBS). A WBS is the structured decomposition of the project’s deliverables and scope into progressively smaller pieces until you reach the lowest practical level of detail (often called work packages), which can then be scheduled, estimated, assigned, and tracked. In the CompTIA Project+ objectives, the WBS is explicitly listed as a planning artifact used to break down the work during initiation/planning activities.

The other options don’t fit the “smallest activity components” description. A milestone chart highlights key checkpoints/dates, not the granular decomposition of work. A task board visualizes workflow status (e.g., to-do/in-progress/done) but doesn’t inherently define the decomposition structure. A detailed project plan is broader and would include schedule, resources, budget, and governance—often informed by the WBS rather than being the decomposition itself.

By creating the smallest components list, the PM is effectively decomposing scope into manageable units, which is precisely the purpose of a WBS in Project+ planning and control.

Timeboxing is a time management technique that involves allocating a fixed, maximum unit of time for an activity and completing the activity within that time frame. In the context of meetings, timeboxing helps ensure that discussions stay within the allotted time, preventing overruns.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, timeboxing is listed as a meeting management technique to control the duration of meetings and keep them focused .

By implementing timeboxing, the project manager can structure the status calls to adhere strictly to the scheduled one-hour duration, improving efficiency and respecting participants' time.

By negotiating a middle ground, the PM used compromise as a conflict resolution technique. Force and avoid do not build consensus, while smoothing minimizes issues but does not resolve them. Compromise achieves agreement acceptable to both sides.

A wiki knowledge base is a collaborative online platform that allows users to create, edit, and share information about a specific topic or domain1. A wiki knowledge base is best to use for storing lessons learned because it enables easy access, retrieval, and update of the lessons learned by project teams and stakeholders2. A wiki knowledge base can also support keyword search, version control, and linking of related documents3. A wiki knowledge base is different from a whiteboard, which is a physical or digital board that can be used for brainstorming, sketching, or presenting ideas; a content management system, which is a software application that allows users to create, manage, and publish digital content; and a workflow platform, which is a software tool that automates and streamlines business processes4. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing the Project, page 403; Capturing Lessons Learned in Project Management [2023] • Asana, Different types of lessons learned sessions and Lessons Learned Process in Project Management sections; Project Management Lessons Learned | Smartsheet, What Are Lessons Learned in Project Management? and Lessons Learned Process in Project Management sections; How to Do Lessons Learned in Project Management, Store and Retrieve sections.

When an organization lacks the internal resources or expertise to develop a specific feature, subcontracting is an effective procurement method. This involves hiring an external entity to perform the work, thereby filling the skill gap.

The CompTIA Project+ PK0-005 exam objectives, under Domain 1.11: Explain important project procurement and vendor selection concepts, list subcontracting as a procurement method:

"Resource procurement methods: Build, Buy, Lease, Subscription/pay-as-you-go."

CompTIA Project+ PK0-005 Exam Objectives

Subcontracting falls under the 'Buy' category, where services are procured externally to meet project requirements.

The project manager should review existing artifacts to get an understanding of the purpose of the project. Existing artifacts are documents or records that provide information about the project background, context, scope, objectives, requirements, stakeholders, and deliverables. They may include documents such as project proposal, project charter, business case, feasibility study, statement of work (SOW), or contract. Reviewing existing artifacts can help to clarify the project vision and expectations and provide a basis for planning and executing the project.

A dashboard is a tool that the project manager will most likely use to update the project sponsor and senior stakeholders about the progress of a project. A dashboard is a graphical tool that displays key performance indicators (KPIs), metrics, and data related to a project using charts, graphs, tables, or other visual elements. A dashboard can help to provide a quick and easy overview of the project status and performance and highlight any issues or risks that need attention.

The project manager should hold sessions to understand user challenges and track system usage and report user activity. These steps will help the project manager to identify the root causes of the adoption issues and monitor the progress of the system utilization. They will also help to communicate with the sales organization and provide feedback and support12

Phishing is a scenario where someone claiming to be from a legitimate organization sends an email or other message to a target person asking for sensitive information or access to a system or account. Phishing is a type of cyberattack that aims to trick the target into revealing personal or financial data or installing malware on their device. Phishing can compromise the security and privacy of the target and expose them to identity theft, fraud, or other malicious activities.

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.

A rollback plan (sometimes called a “backout plan”) defines the steps to revert a system to the last known good/operational state if an implemented change fails or creates unacceptable impacts. That is exactly what option B states: returning to the operational state before the change was applied. This aligns with IT change control practices emphasized in Project+ governance and change control contexts, where changes must include consideration for restoring service quickly if outcomes are not as expected.

Option A (“apply an alternative plan”) is closer to a general contingency/fallback plan, which may involve a different solution path rather than undoing the change. Options C and D are not standard control responses: restarting the entire project is extreme and unrelated to change backout, and repeating tasks “until they work” ignores risk control and service stability.

In project environments—especially IT—rollback planning is part of responsible change implementation because it reduces downtime, protects users, and supports controlled deployment. If validation/testing after the change shows failure, the rollback plan provides a predefined, approved path to quickly restore the prior baseline while the team reassesses or submits a revised change request.

The scatter diagram shows a clear negative correlation between time (days) and output (pages), meaning as time progresses, the number of pages completed decreases. This is evident from the downward trend of the plotted points on the graph. References = CompTIA Project+ Certification Study Guide, Chapter 3: Project Execution, page 130; CompTIA Project+ Certification Exam Objectives, Domain 3.0: Project Execution, Objective 3.3: Analyze project performance by using appropriate tools and techniques, Sub-objective 3.3.2: Given a scenario, interpret the results of data analysis using appropriate tools and techniques, Knowledge of: Scatter diagrams.

The best choice is cadence because it establishes a repeatable rhythm for ceremonies, work sequencing, and deliverables across iterations (e.g., sprint planning → daily touchpoints → review → retrospective), which is exactly what the scenario is asking for: a “consistent flow of tasks and deliverables after each iteration.” CompTIA Project+ explicitly includes “Establish cadences” and “Meeting cadence and methodologies” as planning activities, and it also calls out “Impacts to cadence” as something to manage during schedule development/maintenance—showing cadence is a recognized control lever for iteration-based delivery.

A task log tracks tasks but doesn’t create a repeatable time pattern. Milestones mark significant points in time, but they don’t inherently standardize the iteration routine. A work breakdown structure (WBS) decomposes scope into work packages; it helps organize work, but it won’t by itself create a stable sprint-to-sprint operating rhythm. By establishing a cadence, the team reduces iteration variability, improves predictability, and makes it easier to forecast and coordinate dependencies—aligning directly with Project+ schedule management and Agile/iteration practices.

An intellectual property (IP) breach occurs when proprietary information, such as software, designs, or trade secrets, is used without authorization. In this scenario, a service provider reusing developed software for another customer constitutes an IP breach, as the software is typically owned by the company that commissioned its development.

The CompTIA Project+ PK0-005 exam objectives, under Domain 3.4: Explain the importance of project compliance, emphasize the significance of protecting intellectual property and ensuring that all project outputs are used in accordance with contractual agreements and legal standards.