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

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

Obtaining approval for changes to software is crucial to ensure that the changes do not negatively impact other functionalities of the software. Approval processes typically involve a review that assesses the potential impacts of the change, which helps in mitigating risks associated with the change.

References = The answer is based on standard project management practices and the typical use of change control processes in software development. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

A Gantt chart is a visual tool used in project management to represent the timing of tasks required to complete a project. It is particularly useful for showing the start and finish dates of elements of a project, dependencies between tasks, and the current schedule status. This makes it an ideal choice for a project manager to discern overlapping tasks and allocate resources efficiently.

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

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.

After completing development and internal testing phases, the next step is to conduct User Acceptance Testing (UAT). UAT is performed by the end-users to ensure the system meets their requirements and is ready for deployment.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.3: Explain the importance of quality management and testing in project management, UAT is a critical phase to validate that the product meets the business needs and requirements.

The program manager should schedule a call with the vendor PM and vendor executive to review the statement of work (SOW), which is a document that defines the scope, deliverables, timeline, quality, and payment terms of the project. The program manager should clarify the expectations and criteria for user acceptance testing (UAT), which is a process of verifying that the system meets the user’s requirements and expectations. The program manager should also discuss the reasons for the UAT failure and the corrective actions needed to resolve the issues. The program manager should not approve the invoice until the UAT is successfully completed, as this would compromise the quality and value of the project. The program manager should also not escalate the issue or work on a compromise without first reviewing the SOW and communicating with the vendor12.

When the team is confused about what must be accomplished, the best method is formal written communication so expectations are clear, consistent, and unambiguous, and there is a single reference point everyone can review. Formal written communication (e.g., documented assignments, acceptance criteria, task descriptions, action items with owners and due dates) reduces interpretation differences that often happen in scattered individual messages. CompTIA Project+ covers communication methods and emphasizes selecting the right channel based on complexity and the need for clarity, traceability, and shared understanding. ()

Informal internal messages can be fast, but they are more likely to create inconsistent interpretation, especially if people receive different versions or lack context. Asynchronous verbal methods (like voicemail) are harder to reference and can increase misunderstanding. “Synchronous external” is the wrong audience and doesn’t solve internal task clarity.

A practical implementation is: publish tasks in the team’s system of record (ticketing tool/task board), write clear “definition of done” and acceptance criteria, capture decisions and action items in meeting notes, and ensure each task has a single owner. That approach aligns with Project+ expectations for structured communication, documentation, and accountability. ()

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.

KPIs (Key Performance Indicators) are measurable values tied to project goals. If KPIs are being met, the PM can confirm that the project outcomes align with objectives. Audit reports verify compliance, while lessons learned capture knowledge at project closure.

When a project relies on legacy applications, a primary and often heightened risk is a major cybersecurity event. Legacy systems frequently have older architectures, limited vendor support, weaker security controls, outdated dependencies, and delayed patching capabilities—factors that increase vulnerability exposure. From a Project+ perspective, risk management requires identifying threats with the highest potential impact; a cybersecurity incident can create severe consequences across confidentiality, integrity, and availability, leading to service outages, regulatory exposure (especially if PII is involved), reputational damage, and unplanned cost/schedule impacts.

“Infrastructure end of life” (A) is also a legitimate legacy-related risk, but it is typically a more predictable lifecycle risk that can be planned around (replacement schedules, support contracts). A “company reorganization” (B) is a general organizational risk not specific to legacy applications. “Digital transformation” (C) is more of a strategic initiative context than a discrete risk event.

Because the question asks for the main concern when using legacy apps, the most critical, high-impact threat that legacy systems exacerbate is a major cybersecurity event—the kind of risk that can derail timelines and budgets and force emergency scope changes and remediation work.

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.

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

Multifactor authentication (MFA) is a security method that requires users to provide two or more pieces of evidence to verify their identity before accessing a system. MFA can use different types of factors, such as something the user knows (e.g., password, PIN, security question), something the user has (e.g., token, smart card, mobile device), or something the user is (e.g., fingerprint, face, voice). MFA provides a layered approach to logging in to systems that contain an organization’s most valuable intellectual property, as it makes it harder for unauthorized users to gain access by compromising one factor alone. MFA can also prevent phishing, brute force, and credential theft attacks12. References = CompTIA Project+ PK0-005 Certification Study Guide,

This answer is based on the best practice of conflict resolution in project management, which is to use a collaborative or problem-solving approach that seeks a win-win outcome for all parties involved12. By facilitating a meeting, the project manager can help the team members communicate effectively, understand each other’s perspectives, and find a mutually acceptable solution that meets the project requirements. This way, the project manager can also maintain team morale and cohesion, and avoid imposing a decision that may cause resentment or dissatisfaction among the team members3. References = CompTIA Project+ Certification Study Guide4, CompTIA Project+ Certification Exam Objectives5, How Do You Handle Conflict in Project Management?1, 7 Strategies for Conflict Resolution in Project Management2, The Conflict Resolution Skills Every Project Manager Needs3

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

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

Smoothing is a conflict resolution technique that involves minimizing or ignoring the differences between the parties and focusing on the common interests or goals1. It is often used when the conflict is not very important or when there is a need to maintain harmony and relationships2. By using smoothing, the project manager can reduce the tension and stress caused by the disagreement and encourage the team members to cooperate and work together. Smoothing is different from compromising, which involves finding a middle ground or a trade-off that partially satisfies both parties; forcing, which involves imposing one’s own solution or decision on the other party; and collaborating, which involves finding a win-win solution that fully satisfies both parties3. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 10: Executing Projects Part 1, page 297; A Quick Guide to Resource Smoothing: Definition, Benefits, and Process, Conflict Resolution Techniques section; Resource Smoothing: How To Use In Project Management | Hive, Smoothing section.

If a team member is still able (or forced) to charge time to a project months after it ended, the most likely missed closure activity is releasing project resources. In CompTIA Project+ closing activities, resource release/offboarding is a key step: it ensures people are formally transitioned off the project, their assignments are ended in the resourcing/timekeeping system, and they become available to be allocated to new work. If the PM neglects this, the organization’s resource management system may keep the person tied to the closed project code, preventing accurate time charging and creating both reporting and utilization problems.

“Removing access” (A) is a security/offboarding step and might be relevant for systems or repositories, but it doesn’t directly control time code availability or project assignment in resource planning. “Collecting stakeholder feedback” (C) supports lessons learned and continuous improvement, not time charging. “Having the closeout report approved” (D) is important for formal closure, but the specific symptom—charging time incorrectly and being blocked from new projects—points most directly to failing to release resources in the organization’s administrative systems.

So the PM neglected to complete the operational closure step of releasing the project resources, ensuring staffing and timekeeping are correctly transitioned to new work.

A videoconference is the best channel for delivering weekly presentations to geographically dispersed stakeholders because it supports real-time, synchronous communication while enabling visual content sharing (slides, dashboards, demos) and interactive Q & A. CompTIA Project+ emphasizes selecting communication methods appropriate to the audience and purpose; presentations generally benefit from richer media than text-only channels, especially when alignment and decision-making are needed.

“In-person meetings” (A) are impractical “across the country” on a weekly cadence due to travel cost, time, and logistics. “Email” (B) can distribute slide decks, but it’s asynchronous and often results in misunderstandings, delayed feedback, and lower engagement—weak for a presentation format requiring discussion. “Telephone” (C) is synchronous but lacks visuals, making it harder to present complex status, plans, or demonstrations effectively.

Using videoconferencing also supports meeting best practices: agenda and timeboxing, screen sharing for consistent messaging, and easy recording (where appropriate) to help absent stakeholders catch up—aligning with Project+ meeting and communication management expectations.

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 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 number of items in the backlog can be determined by looking at the “Commitment” column for each sprint in the provided chart. For Sprint 5, there is a commitment of completing 23 items, which is the highest among all sprints. This indicates that there are at least 23 items in the backlog to be worked on. This is consistent with the concept of agile project management, which allows for changes and additions to the project scope based on customer feedback and changing requirements. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 14: Agile Project Management, page 321. CompTIA Project+ Cert Guide: Exam PK0-005, Chapter 9: Agile Project Management, page 287

Cultural differences are the most important aspect for the project manager to consider when assigned to a multinational project with team members from different continents. Cultural differences refer to the variations in beliefs, values, norms, behaviors, customs, and communication styles among people from different countries or regions. Cultural differences can affect how team members interact, communicate, collaborate, negotiate, make decisions, solve problems, manage conflicts, and perform tasks. The project manager should be aware of and respect the cultural differences among team members and foster a positive and inclusive team culture that leverages diversity and promotes trust and cooperation.

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.

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

The project manager should review the requested change first to assess its impact, feasibility, and alignment with the project objectives and scope. Reviewing the change will help the project manager to determine if the change is necessary, beneficial, and acceptable to the stakeholders. The project manager should also consider the risks, costs, and quality implications of the change before proceeding to the next steps of the change management process123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 9: Project Change Management, p. 323; 5 Steps in the Change Management Process | HBS Online; 8 Steps for an Effective Change Management Process - Smartsheet

The buyer faces the most risk under a cost-plus percentage of cost (CPPC) contract because the seller’s fee is a percentage of actual costs. That structure creates a perverse incentive: if costs rise, the seller’s profit rises too—so the buyer has the greatest exposure to overruns and the weakest built-in cost-control motivation on the seller side. Procurement guidance commonly flags CPPC as especially risky for buyers for exactly this reason.

By comparison, cost-plus-fixed-fee (CPFF) still leaves the buyer paying allowable costs, but the seller’s fee is fixed (less incentive to inflate costs). Cost-plus-incentive fee (CPIF) ties part of the fee to performance/cost targets, sharing risk and encouraging cost control. Finally, firm fixed-price (FFP) places the cost overrun risk primarily on the seller, because the price is set unless scope changes. PMI’s contract overview notes fixed-price provides the buyer defined cost (assuming scope is well-defined), which reduces buyer risk relative to cost-reimbursable models.

Therefore, among the options, CPPC is the clearest “highest buyer risk” contract type.

The BEST way to coordinate management of multiple related projects is to establish a program. A program is a group of related projects that are managed together to achieve specific strategic business objectives. References: CompTIA Project+ Study Guide Section 2.2.1

The organization should establish a program to coordinate management of multiple related projects. A program is a group of related projects, subprograms, and program activities that are managed in a coordinated way to obtain benefits and control not available from managing them individually. A program can help to align multiple projects with strategic goals, optimize resources and risks, and deliver value to stakeholders.

SaaS, or software as a service, is a cloud model that provides on-demand access to ready-to-use, cloud-hosted application software. SaaS is the best solution for the global franchise, because it can unify its operation worldwide by using the same software platform across different locations and devices. Additionally, SaaS can provide operation reports in real time without asking the country franchise manager for these reports, because the cloud service provider manages the data collection, analysis, and presentation in the cloud. SaaS also offers the benefits of scalability, reliability, security, and cost-effectiveness for the global franchise.

SaaS is different from IaaS, or infrastructure as a service, which provides on-demand access to cloud-hosted computing infrastructure, such as servers, storage, and networking. IaaS is not suitable for the global franchise, because it requires the franchise to manage and maintain its own software applications and data on the cloud infrastructure. IaaS also does not provide operation reports in real time, unless the franchise develops its own reporting tools and processes. SaaS is also different from XaaS, or anything as a service, which is a generic term that encompasses various types of cloud services, such as IaaS, PaaS, SaaS, and others. XaaS is not a specific cloud model that the company can suggest to the global franchise, but rather a broad category of cloud offerings. SaaS is also different from PaaS, or platform as a service, which provides on-demand access to a complete, ready-to-use, cloud-hosted platform for developing, running, maintaining, and managing applications. PaaS is not ideal for the global franchise, because it requires the franchise to develop and deploy its own software applications on the cloud platform, which may be more complex and time-consuming than using a ready-made SaaS solution. 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; IaaS vs. PaaS vs. SaaS3

Forcing is a conflict resolution technique where the project manager makes a decision unilaterally, without seeking consensus. According to CompTIA Project+, forcing may be used when time is critical, and decisions need to be made promptly.

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

 Review the resource pool and review the project objectives are activities that the project manager should undertake after accepting a new project. Reviewing the resource pool involves identifying and evaluating the availability, skills, and competencies of the human and material resources that are needed for the project. Reviewing the project objectives involves understanding and clarifying the expected outcomes and benefits of the project and how they align with the organizational strategy and stakeholder expectations. These activities can help to plan and execute the project effectively and efficiently.

The project manager should have generated a contingency plan first to alleviate the impact of this issue prior to deployment where a major malfunction resulted in an inoperative product condition during a code implementation. A contingency plan is a plan that outlines alternative courses of action or strategies to deal with potential problems or risks that may occur during a project. A contingency plan can help to prevent or minimize the negative impacts of unforeseen events or issues on the project objectives and deliverables and ensure business continuity and stability.

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.

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.

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.

A Finish-to-Start dependency implies that a subsequent activity cannot start until a previous one finishes. In this scenario, the manufacturing process (subsequent activity) cannot begin until the critical raw materials (previous activity) have been delivered. This type of dependency is the most common in project schedules and is likely being affected by the global shipping slowdown, causing delays in the start of the project ' s production run.

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.

To show sequencing between all tasks (i.e., predecessor/successor relationships and dependency flow), the PM should provide a project network diagram. A summary Gantt chart is great for high-level timelines and major bars, but it can hide the detailed dependency logic that explains why tasks occur in a particular order and how delays propagate. In the CompTIA Project+ objectives, “Project network diagram” is explicitly listed among the key tracking charts/diagrams used to inform project decisions (alongside Gantt and milestone charts).

The other choices don’t match the need. A fishbone (Ishikawa) diagram is a root-cause analysis tool for quality issues, not for schedule dependencies. A burndown chart is used mainly in Agile to show remaining work over time, not task-to-task sequencing. A milestone chart highlights key dates, but it doesn’t show the detailed dependency chain between tasks.

So, to satisfy the team’s request for full sequencing visibility, the PM should share a project network diagram.

A time and materials contract is a type of contract where the buyer pays the seller for the actual time and materials used during the project. This type of contract is suitable when the scope of work is uncertain or likely to change, and the vendor cannot provide accurate estimates. The document also specifies the resources involved and the rates the vendor will charge for the work12.

The percentage of risk investments with defined business cases is a metric that measures how well the information security program aligns with the operational objectives of the organization. It indicates how many of the security-related investments are justified by a clear analysis of the expected benefits, costs, and risks, and how they support the business goals and priorities. This metric can help the organization optimize its security spending, demonstrate the value of security to the stakeholders, and align the security strategy with the business strategy1. References = Performance Measurement Guide for Information Security, Section 3.2.3, page 16; Key Performance Indicators for Security Governance, Part 1, Section 3, page 3.

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.

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.

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

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.

Country legal regulations. Country legal regulations are impacting the rest of the team that did not receive the equipment for testing. Country legal regulations are rules and laws that govern how businesses operate in different countries. They may include aspects such as customs, tariffs, taxes, import and export restrictions, data protection, intellectual property rights, and environmental standards. Country legal regulations can affect the delivery and use of equipment for a global project team and may require compliance with different procedures and documentation3

A formal contract is a legal document that defines the terms and conditions of the agreement between the project parties, such as the scope, schedule, budget, quality, deliverables, roles and responsibilities, payment methods, and dispute resolution mechanisms. A formal contract is essential for external projects, especially when there is an exchange of money involved, to protect the interests and rights of both parties and to ensure mutual understanding and compliance. A formal contract is different from a business requirement, which is a statement of the needs and expectations of the customer or stakeholder for the project outcome. A formal contract is also different from a client statement of work, which is a document that describes the work to be performed, the deliverables to be provided, and the acceptance criteria to be met by the project vendor or contractor. A formal contract is also different from a project charter, which is a document that authorizes the project and provides the high-level information about the project objectives, scope, stakeholders, and project manager. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Integration Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 4: Project Integration Management2; 11 Essential Documents To Use as a Project Manager3

In agile methodology, an epic is a large user story or body of work that can be broken down into smaller backlog items deliverable within iteration cycles. This enables large projects to be incrementally deployed while maintaining predictable iteration lengths.

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.

This meeting should identify (and re-confirm) the project scope because repeated “additional changes” are classic drivers of scope change/scope creep, and scope is the primary input for setting a realistic delivery date. In CompTIA Project+ objectives, scope is explicitly treated as a planning-phase activity—e.g., creating a detailed scope statement and defining units of work—which then enables reliable scheduling and estimating.

When stakeholders keep adding changes, the project manager must use the change control process (collect the change requests, assess impacts, determine decision makers/CCB involvement, update the project plan, implement and validate changes, and communicate deployment). Agreeing on an “expected delivery date” requires stakeholders to align on what work is actually included (scope boundaries) so impacts to the schedule can be calculated and accepted.

While budget, objectives, and communication are important, they don’t directly resolve the problem created by ongoing additions: without a clarified, agreed scope baseline (what’s in vs. out), any delivery date becomes unstable and will continue to slip as new work is introduced.

When managing vendor contracts, the PM must validate vendor status reports to confirm progress and monitor vendor performance against agreed service levels. Approving deliverables occurs less frequently, and creating charters/baselining schedules are initiation tasks, not recurring vendor management tasks.

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.

Infrastructure as a service (IaaS) is a cloud model that provides on-demand access to cloud-hosted physical and virtual servers, storage, and networking resources. IaaS customers can provision, configure, and use these resources as they would use on-premises hardware, but without the hassle of purchasing, installing, managing, and maintaining them. The cloud service provider owns, manages, and maintains the hardware and computing resources in its own data centers, and charges the customers based on their usage. IaaS is suitable for customers who need flexibility, scalability, and control over their IT infrastructure, and who want to avoid the high costs and complexity of owning and operating their own hardware. The other options are not correct because:

Software as a service (SaaS) is a cloud model that provides on-demand access to ready-to-use, cloud-hosted application software. SaaS customers do not need to install, update, or maintain the software, as the cloud service provider handles all the technical aspects. SaaS is suitable for customers who need to access common applications, such as email, office productivity, or customer relationship management, without worrying about the underlying infrastructure or platform.

Data as a service (DaaS) is a cloud model that provides on-demand access to cloud-hosted data sources, such as databases, data warehouses, or data lakes. DaaS customers can query, analyze, and visualize the data, as well as integrate it with other applications or services, using APIs or web interfaces. DaaS is suitable for customers who need to leverage data from various sources, such as social media, IoT devices, or third-party providers, without having to store, manage, or process the data themselves.

Platform as a service (PaaS) is a cloud model that provides on-demand access to a complete, ready-to-use, cloud-hosted platform for developing, running, maintaining, and managing applications. PaaS customers can use the platform’s tools, frameworks, libraries, and services to create and deploy applications, without having to worry about the underlying infrastructure or software. PaaS is suitable for customers who need to develop, test, and deploy applications quickly and efficiently, and who want to take advantage of the cloud’s scalability, reliability, and security features. References = IaaS vs. PaaS vs. SaaS; AWS Fundamentals: Understanding Compute, Storage, Database, Networking & Security; What are the different types of cloud computing?; What is Cloud Storage and How to Use It

Informal communication is a type of communication that is casual, spontaneous, and unstructured. It does not follow any predefined rules, protocols, or formats. Examples of informal communication include email, phone calls, conversations in the hallway, and impromptu meetings12. The sponsor is using informal communication to communicate with the team, as these methods are convenient, flexible, and personal. However, informal communication may also have some drawbacks, such as lack of documentation, inconsistency, and potential for misunderstanding3. Therefore, the sponsor should also use formal communication when necessary, such as for official reports, contracts, and presentations4.

 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

The change log should be updated first because the steering committee has decided to implement proposed suggestions, which means approved or pending changes must be formally recorded. A change log provides traceability for change requests, approvals, impacts, implementation status, owners, and dates. Updating it first ensures the project has an auditable record before related project documents are revised. The Gantt chart may need updates later if the changes affect schedule activities or milestones. The task board may also be revised if team work items change. The risk log is used for uncertain future events, not approved scope or execution changes. Proper change documentation supports governance, prevents confusion, and helps stakeholders understand why the project plan, schedule, budget, or scope may be adjusted.

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

The output of this exercise where the project manager is comparing the cost of the project to the cost savings the project will produce when it is complete will produce the return on investment (ROI). ROI is a financial metric that measures the profitability or efficiency of an investment by comparing its benefits or returns to its costs. ROI can help to evaluate the value or worth of a project and support decision making and prioritization. ROI is calculated by dividing the net benefits (benefits minus costs) by the total costs and multiplying by 100 to get a percentage.

This is compromising because the PM negotiates a middle-ground solution: the end users reduce/simplify what they originally wanted, and the project can implement a version of the change without increasing the constrained budget. Compromising is characterized by each side giving up something to reach an agreement that is acceptable and achievable within constraints (scope/cost/time). This matches Project+ objectives that include applying appropriate communication and people-management techniques (including handling disagreements and stakeholder expectations) to keep delivery feasible.

It is not collaborating, which aims for a true win-win by addressing root needs and often requires more time or resources (for example, securing more budget, changing constraints, or redesigning to meet all requirements). It is not smoothing (downplaying differences and emphasizing agreement) because the PM is actively changing the request content to fit constraints. It is not avoiding, because the PM is directly engaging and resolving the conflict rather than postponing or sidestepping it.

So the PM used compromising to maintain stakeholder buy-in while protecting the budget constraint and still achieving an implementable change outcome.

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 project charter is a foundational document that outlines the project ' s objectives, scope, stakeholders, and overall goals. It serves as a reference point throughout the project lifecycle.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Compare and contrast different project management roles and responsibilities, the project charter is critical for defining the project ' s purpose and success criteria .

By consulting the project charter during the closure meeting, the project manager can verify whether the project ' s outcomes align with the initially agreed-upon objectives, facilitating resolution of stakeholder disagreements.

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

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

The project manager can use the burn up chart to analyze the current status of the project based on its scope (value delivered), budget (cost), and schedule (time). A burn up chart is a graphical tool that shows how much work has been completed (burned up) versus how much work remains (scope) over time. It also shows how much budget has been spent (burned up) versus how much budget remains (budget) over time. A burn up chart can help to monitor and control the project progress and performance and identify any variances or deviations from the plan. The chart given shows that both scope and budget lines are above their respective target lines at any given time point. This means that less work has been completed than planned (scope variance) and more money has been spent than planned (budget variance) at any given time point. Therefore, the project is behind schedule and over budget.

Project sign-off is the activity most likely to have avoided the discrepancy because formal sign-off (especially at closure) confirms that key project outcomes—including final reporting—are reviewed, agreed, and approved by the appropriate authority (sponsor/customer/PMO/finance stakeholders). In CompTIA Project+ closing activities, sign-off is part of ensuring the project is properly closed, deliverables are accepted, and records are accurate and complete for governance and auditability. A formal sign-off step typically includes reconciling final cost/schedule performance, confirming financials match the system of record, and documenting approvals.

“Closing contracts” relates to procurement and vendor obligations and might influence final costs, but it doesn’t directly guarantee reconciliation between financial reporting sources. “Validation of deliverables” focuses on product acceptance/quality, not financial reporting alignment. “Removing access” is an offboarding/security step and doesn’t address financial discrepancies.

So, the best preventive control among the options is project sign-off, because it provides a structured checkpoint to reconcile and confirm closure information (including final financials) with stakeholders and records—reducing the chance of inconsistent reporting that later triggers audit findings.

To account for potential risks, project managers use Expected Monetary Value (EMV) analysis. EMV is calculated by multiplying the probability of a risk event by its potential impact and adding this to the base estimate.

Base estimate: 9 days, $3,000

Risk impact: 5 additional days, $1,000 extra cost

Probability of risk: 20% (0.2)

Calculations:

Time: 9 days + (0.2 * 5 days) = 9 + 1 = 10 days

Cost: $3,000 + (0.2 * $1,000) = $3,000 + $200 = $3,200

However, to ensure sufficient contingency, it ' s prudent to budget for the full potential impact:

Time: 9 days + 5 days = 14 days

Cost: $3,000 + $1,000 = $4,000

But since the risk has only a 20% chance of occurring, the EMV approach provides a balanced estimate:

Time: 9 days + 1 day (20% of 5 days) = 10 days

Cost: $3,000 + $200 (20% of $1,000) = $3,200

Therefore, the most accurate budget considering the risk is 10 days and $3,200.

This aligns with the CompTIA Project+ PK0-005 exam objectives under Domain 1.4: Given a scenario, perform risk management activities, which includes understanding and applying EMV analysis.

Resolution time is a standard component of a Service Level Agreement (SLA), defining the maximum time for addressing issues. SLAs are essential for managing client expectations and service performance, in line with CompTIA Project+ concepts of contract management.

A wiki is the best tool to record retrospective results for a distributed/virtual team because it provides a shared, persistent, easily editable knowledge base where outcomes can be documented and revisited. Retrospectives produce actionable items such as what went well, what didn’t, root causes/themes (e.g., production issues), and improvement experiments with owners and due dates. A wiki supports this by enabling structured pages, version history, links to incident records, and ongoing updates—helping the team track whether morale and operational stability improve over time. CompTIA Project+ includes meeting management and documentation practices (agendas, notes, action items) and recognizes collaboration tools used to capture and share project knowledge.

A presentation is typically one-way and not ideal for ongoing collaborative updates. Chat is transient and hard to curate as a long-term record; key decisions and actions get buried. Polling is useful for quick sentiment checks (which can help measure morale), but it doesn’t serve as the primary system to document discussion, decisions, and actions from the retrospective.

Therefore, to record retrospective results clearly and durably for a virtual team, the PM should use a wiki.

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.

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.

According to Four agile ceremonies, demystified, one of the Scrum ceremonies is the daily stand-up, which is a short meeting to discuss progress and identify blockers. Blockers are any issues or impediments that prevent the team from completing their tasks or achieving their goals. Reviewing project blockers during the daily stand-up helps the team to resolve them quickly, collaborate effectively, and stay on track1. The other options are not likely to take place during a Scrum ceremony, as they are either part of the initial project planning or outside the scope of Scrum.

Multitier architecture is a type of software architecture that is suitable to support enterprise-level client-server solutions. Multitier architecture divides an application into logical layers or tiers that are distributed among different servers or machines. Each tier performs a specific function or role and communicates with other tiers through well-defined interfaces. Multitier architecture can provide benefits such as scalability, performance, security, maintainability, and reusability for complex and large-scale applications.

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.

Identifying business needs and product descriptions is a crucial first step in project initiation, as it defines the project ' s purpose and scope. This step is in line with CompTIA Project+ practices for understanding and documenting project requirements.

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

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.

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.

When a change request is rejected due to a code freeze, the project manager should communicate to the stakeholders to inform them of the situation. Transparent communication ensures that all parties are aware of the project ' s current status and any limitations affecting progress. This step is crucial for managing expectations and maintaining stakeholder trust.

This approach is supported by the CompTIA Project+ PK0-005 exam objectives, specifically under Domain 1.3: Given a scenario, apply the change control process throughout the project life cycle, which emphasizes the importance of communication in change management.

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

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

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

Regression testing is a type of testing that is done on an existing system to ensure that the previous functionality still works after a change has been made. Regression testing is a process of retesting or verifying that a software system or application still performs as expected after it has been modified or updated with new features, bug fixes, patches, etc. Regression testing can help to detect any errors or defects that may have been introduced by the change and ensure that no functionality has been broken or degraded.

A project schedule is an artifact that shows the sequence, duration, and dependencies of the project activities, as well as the resources assigned to each activity. A project schedule helps the project team understand what needs to be done, who needs to complete the tasks, and when the tasks need to be completed. A project schedule can also help monitor and control the project progress and performance1.

A cost-plus contract is a type of contract where the buyer agrees to reimburse the seller for the actual costs of the work plus a fee, which can be fixed, percentage, incentive, or award based. This type of contract has the highest risk for the buyer because the buyer has no control over the cost or quantity of the work and the seller has little incentive to control the costs or complete the work efficiently. The seller may inflate the costs or prolong the work to increase the fee. The buyer may end up paying much more than the estimated budget or the market value of the work. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 9: Project Procurement Management; CompTIA Project+ Certification Exam Objectives, Domain 3: Project Execution, Objective 3.3: Execute procurement activities.

The total amount that should be budgeted for the task is calculated by adding the expected value of the risk to the original estimate. The expected value of the risk is the product of the probability and the impact of the risk. In this case, the expected value of the risk is 0.2 x (5 days and $1,000) = 1 day and $200. Therefore, the total amount that should be budgeted for the task is 9 days and $3,000 + 1 day and $200 = 10 days and $3,2001.

Background screening is an operational security control: it helps organizations reduce the risk of insider threats, fraud, and inappropriate access by verifying identity, employment history, and other relevant checks before granting trust, credentials, and system access. This aligns with security governance practices that protect organizational assets (data, systems, finances, customers) by ensuring personnel are vetted according to policy and role sensitivity.

Option A (“increase access restrictions”) is related but incomplete—screening doesn’t restrict access by itself; it supports decisions about whether access should be granted at all, and at what level. Option B (define KPIs) is performance management, not security. Option C (evaluate PHI) is healthcare-data specific and not the purpose of background checks.

In project environments, especially those handling sensitive data (PII/financial/customer records) or regulated work, background screening supports compliance and reduces risk exposure. It’s part of broader operational security controls alongside least privilege, need-to-know, MFA, monitoring, and offboarding. Therefore, the best explanation is to apply operational security.

Preliminary procurement involves identifying and evaluating potential vendors based on their qualifications and capabilities. This step is essential for project procurement and aligns with CompTIA Project+ best practices for vendor selection.

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

A project manager did not release the resources. A project manager not releasing the resources could most likely be the cause of this issue where several employees’ allocations from the past month appear to be 200% even though they are only assigned to a particular project. Releasing resources is a process of freeing up or reallocating any human or material resources that were used for a project after its completion or closure. Releasing resources can help to update the resource availability and utilization records and avoid any conflicts or errors in resource allocation or reporting.

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

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.

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.

To determine the best description of the team ' s performance, we analyze the chart showing:

Committed work (orange bars): what the team planned to do.

Actual work completed (blue bars): what the team actually accomplished.

Key Observations:

In most sprints (e.g., 1, 3, 4, 5, 6, 8, 10), the actual work is slightly less than the committed work.

In Sprints 9 and 10, the actual work exceeds the committed work.

There ' s inconsistency in how much work is completed compared to what ' s committed.

Interpretation:

The team frequently overestimates its capacity. This suggests a misalignment between planning and execution, which indicates that their velocity is not yet well-understood or accurately reflected in sprint planning.

According to the CompTIA Project+ PK0-005 Exam Objectives:

Under Domain 1.2: Compare and contrast Agile vs. Waterfall concepts, understanding team velocity, iteration planning, and the ability to plan based on past performance is key to Agile success.

" Agile teams should use velocity as a guide to improve predictability. Sprint commitments should align with the team’s proven delivery capacity. "

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

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.

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

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.

Submit a change request to the change control board. The project manager should submit a change request to the change control board (CCB) if they realize that the project will not be completed on time due to resource constraints. A change request is a formal proposal to modify any aspect of the project, such as scope, schedule, cost, quality, or resources. A change request must be submitted to the CCB, which is a group of stakeholders who are authorized to review and approve changes. Submitting a change request can help to document the impact of the resource constraints on the project and seek approval for any corrective actions or preventive actions12

A RACI matrix clarifies roles and responsibilities for tasks, reducing confusion and disagreements among team members. Missing or incomplete information in the RACI matrix could lead to disputes, as it is a key tool for accountability in project management per CompTIA Project+.

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.

The first priority for a PM inheriting a project midstream is to access and review the existing project artifacts—the documented “source of truth” that shows what was approved, what has changed, current status, and remaining work. CompTIA Project+ emphasizes maintaining project documentation and artifacts, and it explicitly includes “Review existing artifacts” as a key activity as a PM gets oriented to the project context.

By reviewing artifacts (charter, scope baseline/WBS or backlog, schedule, budget, risk register, issue log, change control log, stakeholder list, communication plan, testing/quality plans, and current reports), the PM can quickly understand: current phase, constraints, commitments, open risks/issues, and what decisions have already been made. That enables accurate next actions and prevents contradictory communication or rework.

A brainstorming session (B) is not the best “first” step without understanding current constraints and decisions. A kickoff meeting (C) is typically for initiation; mid-project, the PM may run a transition meeting later, but only after reviewing the facts. Establishing communication channels (D) is important, but you can’t communicate effectively until you know the baseline status and existing governance approach—information found in the artifacts.

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.

During the stabilization phase of recently deployed software, the project manager will most likely use a defect log to track and manage reported bugs. A defect log is a document that contains information about the defects or issues identified during testing or after the deployment of software. It includes the severity of the defect, the steps to reproduce the problem, and the actions taken to resolve the defect. References: CompTIA Project+ Study Guide Section 4.1.

The project manager will most likely use a defect log during the stabilization phase for recently deployed software to record a bug that is compromising data integrity. A defect log is a tool that tracks and documents any errors or flaws found in a software product or system during testing or operation. It usually includes information such as defect ID, description, severity, priority, status, resolution, and responsible person. A defect log can help to monitor and manage the quality of the software product or system and ensure that all defects are identified and resolved before delivery or release.

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.

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.

The project sponsor is the person who provides the authority, funding, and support for the project. The project sponsor can also help to influence and engage the key stakeholders who are essential for the success of the project. If several stakeholders have declined the invitation for the kickoff meeting, which is an important event to establish the vision, scope, and expectations of the project, the project manager should escalate this issue to the project sponsor and seek their assistance to ensure the participation of the stakeholders1, p. 47

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

According to PRINCE2, a project management methodology, the process of initiating a project includes creating the project plan, which is a high-level plan that covers the whole project scope, schedule, budget, quality, and risks. The project plan is based on the project brief, the business case, and the product descriptions. The project plan is used to obtain the authorization from the project board to initiate and execute the project. The project plan is also refined and updated throughout the project life cycle as more information becomes available.

The other processes are not directly involved in creating the project plan. Starting up a project is a pre-project process that ensures the project is viable and worthwhile, and produces the project brief and the initiation stage plan. Managing product delivery is a process that coordinates the delivery of products from the team managers to the project manager, and ensures that the work conforms to the quality criteria and the project plan. Directing a project is a process that enables the project board to oversee and control the project, and make key decisions and approvals. 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; PRINCE2 Processes - 7 Processes Of PRINCE2 Explained3; Initiating a Project Process – This process is the procedure which defines the product quality, Project Product, project timeline, costs, the commitment of resources, risk analysis, and assembles the Project Initiation Documentation (PID)4

The closing phase is when the project manager and the team finalize the project, deliver the outcomes to the customer, obtain formal acceptance, conduct lessons learned, and hand over the project to the operations team. Identifying the baseline go-live date, the operational training, and the handoff procedures are part of the closing activities that ensure a smooth transition and closure of the project. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 14: Closing Projects, p. 333-334.

Project quality assurance is the process of ensuring that the project meets the quality standards and requirements defined by the stakeholders and the organization. It involves planning, implementing, and monitoring quality activities throughout the project life cycle. Project quality assurance is different from project quality control, which is the process of inspecting and testing the project deliverables and outputs to identify and correct defects. Project quality assurance is also different from project transition, which is the process of transferring the project deliverables and outputs to the end users or customers. Project management is the application of knowledge, skills, tools, and techniques to project activities to meet the project objectives. Project communications is the process of planning, creating, distributing, and managing information among the project stakeholders. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 8: Quality Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 8: Quality Management2

Identifying and assessing stakeholders is an action item that will benefit from the analysis of the objectives, the high-level requirements, the success criteria, and the budget resources in the initiation phase. By reviewing these elements, the PM can determine who are the key individuals or groups that have an interest or influence in the project, what are their expectations and needs, and how to engage them effectively throughout the project life cycle12.

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

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

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.

The project manager should first document the change request in the change log because an additional feature represents a potential change to the approved scope described in the SOW. In project change control, requested changes must be formally captured before they are evaluated, approved, rejected, or communicated as accepted work. The change log provides traceability by recording the request, requester, date, description, status, impact, and decision. Validating the request and determining decision makers may occur after documentation, but the project manager should not skip the formal record. Communicating the change broadly before review could create confusion or expectations that the feature is already approved. Proper logging supports governance, prevents scope creep, and ensures the change follows the approved control process.

To keep the client informed about project needs and budget compliance, the project manager should send a weekly status report by email. This report provides a structured and documented update on project progress, budget status, and any actions required from the client.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, regular status reporting is a key component of effective communication management. It ensures that stakeholders are kept informed and engaged throughout the project lifecycle.

The project scope is the document that defines and describes the project objectives, deliverables, requirements, boundaries, assumptions, and constraints. It also includes the success criteria that should be fulfilled by the product or service to meet the stakeholder expectations and the business case. The success criteria are the measurable standards that indicate whether the project has achieved its intended results. The other options are not correct because:

A quality plan is the document that defines and describes the quality standards, policies, procedures, tools, and techniques that will be applied to the project to ensure that the deliverables meet the requirements and the success criteria.

Contract obligations are the terms and conditions that bind the parties involved in a contractual agreement, such as the project manager, the customer, the sponsor, and the vendor. Contract obligations specify the roles, responsibilities, deliverables, payments, and penalties of each party.

A work breakdown structure (WBS) is a graphical representation of the project scope that breaks down the deliverables into smaller and manageable components. A WBS shows the hierarchy and relationship of the project elements, but does not include the success criteria. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Planning Projects, Part 2 (Scope, Quality, and Risk), pages 175-179; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.1: Given a scenario, create a project charter and project management plan.

A project manager who makes a company-wide announcement about the successful completion of a project and thanks team members is doing the following:

Celebrating the team’s hard work: This is the correct answer, as the project manager is acknowledging the efforts and contributions of the team members and showing appreciation and recognition for their performance12.

Bringing attention to the project sponsor: This is not the correct answer, as the project manager is not highlighting the role or involvement of the project sponsor, who is the person who provides the resources and authority for the project.

Sharing lessons learned: This is not the correct answer, as the project manager is not discussing the successes, challenges, or best practices of the project, which are part of the lessons learned process.

Collecting feedback: This is not the correct answer, as the project manager is not soliciting any input or opinions from the team members or other stakeholders, which are part of the feedback process.

Milestones are activities with zero duration that are added to a project schedule by a project manager. Milestones are significant events or achievements in a project that mark the completion of a phase, deliverable, or task. Milestones can help to track and measure the progress and performance of a project and communicate it to stakeholders.

A rollback plan is a contingency plan that describes how to revert the system to its previous state in case the change fails or causes problems. A rollback plan is important to minimize the impact of a failed change and ensure the system’s availability and functionality12.

A deployment plan is a document that outlines the steps and procedures for implementing the change in the production environment. A deployment plan is important to ensure the change is executed smoothly, efficiently, and securely, and that the system meets the expected performance and quality standards34.

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.

The RACI (Responsible, Accountable, Consulted, Informed) matrix is used to document which resources are responsible for which tasks. The RACI matrix is a tool that helps to clarify roles and responsibilities on a project. It assigns a level of responsibility to each resource involved in the project. References: CompTIA Project+ Study Guide Section 3.4.

The project manager should use a RACI matrix to document which resources are responsible for which tasks. A RACI matrix is a type of responsibility assignment matrix (RAM) that plots the roles and responsibilities of resources on a project team. RACI stands for Responsible, Accountable, Consulted, and Informed. A RACI matrix can help to clarify who does what on a project, avoid confusion and duplication of work, and improve communication and collaboration among team members.

A rollback plan is used when an issue is identified during testing or implementation. It allows the team to revert to the previous state, removing the new package. This aligns with CompTIA Project+ guidance on implementing fallback strategies for risk management.