PK0-005 Sample Questions Answers

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.

The WBS, or work breakdown structure, is the most helpful tool when creating the baseline schedule because it breaks the project scope into smaller deliverables and units of work. A schedule baseline is built from activities, durations, dependencies, milestones, and assigned resources. The WBS provides the foundation for identifying those activities and ensuring the schedule includes all approved project work. Without a WBS, the schedule may miss deliverables, duplicate effort, or fail to align with scope. A CMS is not a standard scheduling input in this context. A statement of work defines high-level work and contractual expectations, but it is not detailed enough by itself to build the full schedule. An RFP is used during procurement, not schedule baselining.

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

The Pareto chart should be used to identify the most important causes of issues during a quality analysis review. The Pareto chart is a graphical representation of the frequency and impact of different causes, helping to identify the most common and impactful causes. References: CompTIA Project+ Study Guide Section 3.3.3

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.

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

The team is leveraging lessons learned to create a preventive plan for avoiding issues in the upcoming project enhancement. This falls under risk management and compliance, ensuring previous failures do not repeat.

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.

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.

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

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.

Assess the impact of the request and create a change request. The project manager should assess the impact of the request and create a change request in response to the stakeholder asking to add mobile device functionality to a project that is on track to be completed under budget and ahead of schedule. A change request is a document that formally proposes and records a modification or addition to some aspect of a project, such as scope, schedule, cost, quality, or resources. A change request can help to communicate and justify the need and rationale for the change and its implications on the project objectives and deliverables. A change request also helps to initiate the change control process, which involves reviewing, approving, implementing, and monitoring the change12

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

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.

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.

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.

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.

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.

Project success criteria are the standards by which the success of a project is judged. They include specific goals, deliverables, and performance measures such as cost, time, and quality targets. Defining these criteria during the initiation phase provides a clear understanding of what constitutes project success and guides decision-making throughout the project lifecycle.

Per 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, establishing clear success criteria is fundamental for project planning and evaluation.

This is the correct order of the stages of team development according to Tuckman’s model123. The forming stage is where team members first meet and get acquainted. The storming stage is where team members experience conflicts and disagreements. The norming stage is where team members resolve their differences and establish norms and rules. The performing stage is where team members work together effectively and efficiently. The adjourning stage is where team members complete the project and celebrate their achievements. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Project Team Management, p. 197; The 5 Stages of Team Development (Including Examples) | Upwork; The 5 Stages of Team Development - Teamwork; Using the Stages of Team Development | MIT Human Resources

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.

Outsourcing the development of a system component due to a lack of internal resources is a risk response strategy known as ‘transfer.’ This approach shifts the risk to a third party who will now be responsible for managing that portion of the project. It is commonly used when an organization does not have the expertise or capacity to handle specific risks internally.

References = The answer is based on standard project management practices and the typical use of risk response strategies in the field. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

The project manager and contractor should review the vendor rules of engagement, which are the guidelines and expectations for the communication and interaction between the project team and the contractor. The vendor rules of engagement can help to prevent or resolve communication conflicts by clarifying the roles and responsibilities, the frequency and mode of communication, the escalation process, the feedback mechanism, and the performance evaluation criteria of the contractor. The vendor rules of engagement are usually part of the contract or the procurement management plan.

The vendor rules of engagement are different from the scope of work, which is the document that describes the work to be performed, the deliverables to be provided, and the acceptance criteria to be met by the contractor. The vendor rules of engagement are also different from the request for proposal, which is the document that solicits proposals from potential contractors by specifying the project requirements, evaluation criteria, and contract terms. The vendor rules of engagement are also different from the project schedule, which is the tool that displays the planned start and finish dates, durations, dependencies, and resources of the project activities and tasks. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 12: Procurement Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 12: Procurement Management2; Vendor Rules of Engagement3

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.

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

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.

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.

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.

Corporate values compliance is a consideration when determining a project’s ESG factors, because it reflects how a project aligns with the ethical standards and social responsibility of the organization. Corporate values compliance can help to enhance the reputation, trust, and loyalty of the organization among its stakeholders, as well as to avoid legal or regulatory issues that may arise from violating the values. Corporate values compliance can also influence the project scope, objectives, deliverables, and stakeholders, as well as the project management methodology, processes, and practices.

The other options are not directly related to ESG factors. Project management methodology is the approach or framework that guides how a project is planned, executed, monitored, and controlled. IT infrastructure security is the protection of the hardware, software, network, and data components of a project from unauthorized access, use, modification, or destruction. Proper accounting practices are the rules and standards that govern how financial transactions and statements are recorded, reported, and audited for a project. 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; What Is Environmental, Social, and Governance (ESG) Investing

The project manager should use the project management plan to document the input from the stakeholders on the minimum viable product that would be acceptable for the project. The project management plan is a document that describes how the project will be executed, monitored, controlled, and closed. It usually includes information such as scope statement, work breakdown structure (WBS), schedule baseline, cost baseline, quality plan, risk plan, communication plan, stakeholder plan, and change management plan. The project management plan can help to define and communicate the project requirements, deliverables, assumptions, constraints, and expectations to all stakeholders involved in the project.

The project management plan would be used to document the input obtained from stakeholders during the meeting to review the requirements and agree on the minimum viable product. The project management plan is a comprehensive document that outlines the approach, scope, schedule, budget, quality, resources, and communication for a project. The document is updated throughout the project lifecycle and serves as a guide for project execution, monitoring, and control. References: CompTIA Project+ Study Guide, Chapter 3: Project Integration Management, Objective 3.3: Identify the components of the project management plan.

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.

When analyzing the backlog to decide what to include in the next sprint, the most important aspect to consider is the impact to the project. This involves assessing which items will provide the most value and contribute significantly towards achieving the project goals. It’s crucial to prioritize work that has the highest impact on the project’s success.

References = The answer is based on standard agile project management practices, particularly in the context of sprint planning where prioritization is key. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources

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

In response to new legislation requiring the release of contractors or their conversion to full-time employees, the project manager should prioritize compliance with the law. This may involve using only full-time employees, even if it results in project delays. The focus should be on legal compliance and the ethical treatment of workers, rather than solely on project timelines.

References = The answer is based on standard project management practices and the typical response to changes in legislation affecting project staffing. For detailed information, please refer to the CompTIA Project+ Study Guide and other official CompTIA resources.

In a standard change control flow, communicating the change deployment is done last, after the change has been evaluated/approved, implemented, and validated. CompTIA Project+ explicitly frames change control as a process that includes: collecting/documenting changes, assessing impacts, determining decision makers (often the CCB), updating plans/baselines as needed, implementing the change, validating/testing implementation, and communicating deployment. The communication step is last because stakeholders need confirmation of what was deployed, when it was deployed, and any impacts—based on verified results rather than assumptions.

Option A (escalate to the CCB) happens early when approval is needed. Option B (update the project plan) occurs after approval/impact assessment so the plan reflects the authorized change. Option C (test the implemented change request) is part of validation and must occur before announcing deployment completion; otherwise, you risk communicating a change that doesn’t work as intended.

So, after the change is approved, the plan updated, the change implemented and tested, the final step is to communicate the change deployment to affected stakeholders and teams—closing the loop and maintaining governance and transparency.

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.

This answer is based on the best practice of stakeholder management, which is to identify and document the communication preferences of each stakeholder or stakeholder group12. The project manager should update the stakeholder register with the information gathered from the stakeholder analysis, which includes the preferred communication channel for each stakeholder3. The preferred reported communication channel reflects the majority preference of the stakeholders, as well as the minority preference of the face-to-face communicators. The project manager should use this information to plan and execute effective communication throughout the project life cycle4. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification Exam Objectives6, Stakeholder Register in Project Management1, What is a Stakeholder Register?2, How to Develop a Stakeholder Register3

Infrastructure as a service (IaaS) offers administrators more direct control over operating systems than other cloud service models. IaaS is a type of cloud computing service that provides virtualized computing resources such as servers, storage, network, and operating systems over the internet. IaaS allows users to rent or lease infrastructure resources on demand and pay only for what they use. IaaS gives users more flexibility and control over their infrastructure resources and enables them to configure, manage, and customize their operating systems according to their needs and preferences3

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.

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.

An Ishikawa diagram, also known as a fishbone diagram, is a tool used to identify and analyze the root causes of a particular problem. CompTIA Project+ references this tool as essential for quality management and problem-solving.

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.

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.

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.

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.

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.

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

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.

When implementing an IT infrastructure change that takes risks into consideration, the project manager should develop a rollback plan. A rollback plan is a contingency plan that outlines the steps that need to be taken in case the change does not work as expected. It includes a plan to roll back the changes and restore the system to its previous state. References: CompTIA Project+ Study Guide Section 3.3.

The project manager should develop a rollback plan when implementing an IT infrastructure change that takes risks into consideration. A rollback plan is a contingency plan that describes how to revert back to the previous state of the system in case of a failure or disruption during the change implementation. A rollback plan can help to minimize the impact of the change on the system performance and availability and ensure business continuity and data integrity.

A maintenance window is a predefined period of time during which planned changes or updates can be performed on a system or network with minimal impact on the users or business operations1. A project manager should consider the maintenance window next when deploying a new networking device into an existing production environment, as it will help to reduce the risk of downtime, disruption, or errors. A maintenance window should be scheduled in advance, communicated to the stakeholders, and aligned with the change management plan2.

The primary reason to update the budget during execution is to track and manage the project’s financial condition. As the project progresses, actual costs, commitments, and forecasts change due to procurement, labor consumption, change requests, risks/issues that materialize, and replanning. Updating the budget enables the PM and stakeholders to see whether the project is trending within the approved funding, to manage burn rate, and to take corrective actions early (cost control, scope trade-offs, re-baselining through change control).

Evaluating the communication plan (A) is not a budget purpose. Reporting risks and issues (C) is important, but that’s the role of risk/issue management artifacts and status reporting—budget updates support the financial dimension of project health. Distributing resources (D) is a resourcing activity; budget informs resourcing decisions, but the key objective of an updated budget is accurate financial control and forecasting.

In Project+ terms, this is part of performance monitoring and project controls: keeping cost information current so decision-makers can manage funding, approvals, and corrective actions with reliable data rather than outdated estimates.

Testing whether a website supports multiple concurrent users signed in at the same time is a question about system behavior under load/concurrency. Among the listed methods, stress testing is the best match because it evaluates how the system performs when pushed toward or beyond normal operating conditions—often involving high volumes of transactions or many simultaneous users/sessions. CompTIA Project+ explicitly includes stress testing as one of the testing cycles/methods candidates should understand in the context of quality and performance management.

The other choices don’t align: unit testing validates individual components/functions in isolation, not full end-to-end multi-user session handling; smoke testing is a quick confidence check that basic functionality works after a build/change; and regression testing verifies that existing features still work after changes—useful, but not primarily focused on concurrent-user capacity.

So, to answer the PM’s specific question (concurrent sign-ins), the team should run a stress test (often implemented using load-generation tools) to validate session handling, authentication, and resource utilization when many users are logged in simultaneously, and to identify bottlenecks or failure points.

Agile is a project management methodology that emphasizes customer collaboration, feedback, and adaptation throughout the project life cycle. Agile teams work in short iterations, called sprints, and deliver working increments of the product or service to the customer for review and approval. Agile teams can also respond to changing requirements and priorities by adjusting the scope, schedule, or quality of the project12. Waterfall, on the other hand, is a project management methodology that follows a linear and sequential process, where each phase of the project must be completed before moving on to the next one. Waterfall teams work with a fixed scope, schedule, and quality, and deliver the final product or service to the customer at the end of the project. Waterfall teams have less customer involvement and flexibility during the project development34.

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

The Waterfall methodology is a linear and sequential approach to project management where each phase must be completed before the next begins. It is best suited for projects with well-defined requirements and where the executive team prefers to review the product only after its completion.

As per the CompTIA Project+ PK0-005 exam objectives, under Domain 1.2: Compare and contrast Agile vs. Waterfall concepts, understanding the criteria for selecting a method, including the preference for a single final review in Waterfall, is crucial.

A rollback plan is a part of the project management plan that defines how to revert the system to its previous state or baseline if the change or migration fails or causes unacceptable impacts1. A rollback plan is different from a contingency plan, which is a plan to deal with a specific risk event that may or may not occur2. A release plan and a deployment plan are not relevant to the scenario, as they are used to plan and execute the delivery and installation of the system, not to undo them. Therefore, the correct answer is A. Rollback plan.

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.

A program is a group of related projects managed in a coordinated way to achieve benefits and control that would not be available if the projects were managed separately. Option C—a consolidation of related projects with a common goal—matches the standard program definition used across project management frameworks and aligns with CompTIA Project+ terminology that distinguishes projects (temporary endeavors producing unique outputs) from programs (coordinated management of multiple related projects).

Option A is incorrect because unrelated projects do not form a program; that is closer to a portfolio (a collection of projects/programs managed to meet strategic objectives, not necessarily related). Option B describes operational tracking, not a program definition. Option D sounds like scope decomposition or workload definition, which is not what a program is.

Programs typically have overarching governance, shared resources, interdependent timelines, and integrated risk/benefit management. The focus is on achieving strategic outcomes/benefits across the combined effort, such as rolling out a suite of capabilities or transforming an end-to-end business process via multiple projects.

Awareness of the local environment refers to the understanding of the external factors that may affect the project, such as legal, regulatory, social, cultural, economic, and environmental aspects1. In this case, the legal department applied this awareness to identify the potential risk of violating new legislation and rejected the project accordingly. This shows that the legal department was concerned about the compliance and reputation of the organization and the project in the local context. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 1: Project Management Concepts, page 17; Incorporating environmentalism into project management, Abstract and Definition of Terms sections.

The preliminary scope statement must be completed because it defines the expected deliverables, boundaries, assumptions, constraints, and high-level work needed for the project. During planning, the project manager reviews deliverables to ensure the scope is complete enough to support more detailed planning, including the work breakdown structure, schedule, budget, quality expectations, and resource needs. Project objectives are important, but they are usually established earlier during initiation and provide the reason for the project rather than a detailed description of deliverables. Access requirements may be needed for implementation or operations, but they do not validate deliverable completeness. A QA plan defines how quality will be managed and verified, but it depends on the scope and deliverables being clearly understood first.

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

When a project manager identifies stakeholders who will be impacted by the delivery of a new product, it is important to update the communication plan to reflect these findings. This ensures that all stakeholders are informed about the project’s progress and how it may affect them, fostering transparency and managing expectations.

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

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

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.

A Gap Analysis is a method used to compare the current performance or state of a product with its desired future state. It helps identify the " gaps " between the two states and determine necessary actions to bridge those gaps.

Per the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Explain the importance of activities performed during the closing phase, conducting evaluations like gap analyses is vital for assessing project outcomes and planning improvements.

Quantitative KPIs are measurable and based on numerical data. The statement about task completion time being 25% faster is quantitative, as it involves specific data that can be measured and tracked, as recommended by CompTIA Project+ for project performance evaluation.

Issue log and change log are documents that should be used to record the event where the project team has just experienced an unexpected event and implemented a work-around. An issue log is a document that tracks and records any issues or problems that arise during a project and how they are resolved. An issue log can help to monitor and control the project performance and quality and prevent any negative impacts on the project objectives and deliverables. A change log is a document that tracks and records any changes or modifications that are made to the project scope, schedule, cost, quality, or resources during a project. A change log can help to document the change request, approval, implementation, and impact of each change and ensure traceability and transparency.

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.

Real property (construction/real estate/building projects) is generally best suited to waterfall (predictive) management because the work is highly sequential, governed by physical dependencies, and often requires detailed upfront planning and permitting. For example, you typically must complete design, approvals, site preparation, foundation, framing, and inspections in a defined order. Changes later in construction can be expensive and disruptive, so strong baselining, stage gates, and formal change control align well with waterfall practices.

By contrast, research and data analytics often involve discovery and evolving understanding, making iterative/adaptive approaches more effective. Software development can be done in waterfall, but modern practice frequently benefits from Agile/iterative methods due to changing requirements, user feedback loops, and the ease of incremental delivery.

Project+ emphasizes selecting methodologies based on project characteristics (clarity of requirements, volatility, regulatory constraints, and deliverable nature). Real property projects commonly have well-defined deliverables, fixed constraints, and heavy reliance on documentation and approvals—conditions where waterfall’s structured phases and control points provide predictability and governance.

So, among the options, real property is the best candidate for waterfall management.

A rollback plan, also known as a backout plan, is a strategy designed to reverse changes made during a project in case of failure or undesired results1. A rollback plan is a form of risk response that allows the project to restore the previous state and minimize the impact of the issue. A rollback plan is usually created during the planning phase and implemented during the execution or closing phase of the project. The other options are not correct because:

A compliance check is a process that ensures that the project meets the relevant standards, regulations, and requirements. A compliance check is not a risk response, but rather a quality control or assurance activity.

A release plan is a document that outlines the scope, schedule, and resources for delivering a product or service to the customer. A release plan is not a risk response, but rather a communication or scope management tool.

A validation check is a process that verifies that the project deliverables meet the customer’s needs and expectations. A validation check is not a risk response, but rather a quality control or assurance activity. 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; Backout Plan - DevX

Multiple undefined tasks would favor using the agile methodology to manage an upcoming project. Agile methodology is a project management framework that breaks projects down into several dynamic phases, commonly known as sprints. Agile methodology is an iterative and adaptive approach that allows teams to respond to changing requirements and customer feedback quickly and effectively. Agile methodology is suitable for projects that have multiple undefined tasks, as it enables teams to prioritize and deliver the most valuable features first, and refine and improve them over time based on user input and testing12

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.

When a critical ERP system upgrade encounters a validation issue and is at risk of exceeding the allotted downtime, the project manager should begin executing the rollback plan. This action is taken to ensure that the system can be restored to its previous state without exceeding the downtime limit, thus minimizing the impact on the business operations.

This directive acknowledges local emergency policies/constraints. Hurricane season is a predictable period of elevated operational risk for a utility company, where system stability and rapid incident response are critical. By prohibiting operating-system-impacting projects during that season, the organization is recognizing that emergency preparedness and service continuity take priority, and that change activity increases outage risk when the environment is already volatile.

“National environments” (B) would relate to country-level laws, geopolitical factors, or national regulatory contexts; the directive is tied to a seasonal, location-driven emergency risk pattern rather than national policy. “Company brand value” (A) is indirectly affected, but it’s not what the directive is formally acknowledging. “Standard operating procedures” (C) is tempting because a directive could become an SOP, but the reason and driver is the emergency operating context—hurricane season—so the best match is local emergency policies.

From a Project+ perspective, this is an example of an environmental/operational constraint that should be considered in planning (schedule constraints, blackout windows, change freezes) and reflected in the project schedule and risk planning.

A task board is a visual tool that displays team progress for stand-up meetings. A task board usually consists of columns that represent different stages or statuses of tasks, such as to do, in progress, done, or blocked. Each task is represented by a card or sticky note that can be moved across the columns as the task progresses. A task board can help to facilitate communication, collaboration, and transparency among team members and stakeholders. It can also help to track and manage work flow, prioritize tasks, identify bottlenecks, and resolve issues3

This is a negative risk (threat): the manufacturer may be unable to deliver due to financial trouble, which could delay the project or increase cost. The scenario already indicates the response: “the servers will be sourced from another vendor.” That is best described as risk avoidance—changing the plan to eliminate exposure to the threatened vendor failure by not depending on that manufacturer. CompTIA Project+ includes performing risk management activities such as selecting risk management strategies and executing contingency/fallback plans.

“Mitigate” would mean reducing probability/impact while still accepting some exposure (e.g., adding schedule buffer, placing partial orders early, or increasing inspections), but here the team is switching vendors, which removes the root threat from the current plan. “Share” and “exploit” are typically associated with positive risks/opportunities, not threats, and don’t fit a supplier distress scenario.

So the correct strategy is Avoid: replace the risky supplier dependency with an alternate sourcing approach to prevent the risk from materializing into a project issue (late delivery, non-delivery, or contract disruption).

Defining the units of work should be completed before resource assignments because the project manager must know what work needs to be performed before assigning people, equipment, or other resources to it. In planning, work is decomposed into manageable activities or work packages, often through the work breakdown structure. Once the units of work are clear, the project manager can estimate durations, identify dependencies, determine required skills, and assign resources appropriately. Budget considerations are influenced by resources, but they are more accurate after the work and resource needs are known. A kickoff presentation occurs after planning information is prepared. Reviewing existing artifacts is useful early in the project, but it does not directly establish the work packages needed for resource assignment.

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

Work with the project scheduler to update the project timeline. The project manager should work with the project scheduler to update the project timeline after finding an unforeseen dependency on one of the critical project activities that will most likely cause a delay. The project scheduler is a person or a tool that helps plan, schedule, monitor, and control the project activities and resources. The project scheduler can help the project manager to assess the impact of the dependency on the project schedule and identify any possible ways to mitigate or resolve it. The project scheduler can also help to update the project timeline with the revised dates and durations of the project activities and communicate them to the relevant stakeholders.

This activity is best described as approving deliverables (often in a procurement/payment context). The PM is verifying that what the vendor invoiced—and the supporting documentation—matches what the Statement of Work (SOW) requires. That is a form of verification/acceptance: confirming the vendor has provided the contracted deliverables or services to the agreed standard before payment is approved. In Project+ procurement management, PMs are expected to manage vendor performance against contractual artifacts (SOW, acceptance criteria) and ensure work is validated before closing out payments and contracts.

“Enforcing vendor rules of engagement” is broader and might include communication protocols, escalation paths, or behavioral expectations, but the scenario is specifically about matching invoices and documentation to SOW requirements—an acceptance/verification step. “Reporting overall process” is unrelated, and “scheduling team touch points” refers to meeting cadence and coordination, not invoice/SOW reconciliation.

In practice, this check reduces financial risk (paying for unperformed work), strengthens auditability, and supports clean contract administration. It also helps detect scope misunderstandings early—before they become disputes—by tying vendor charges directly back to agreed deliverables in the SOW.

The role of a Project Manager (PM) for a Customer Relationship Management (CRM) system is to implement new features that enhance the system ' s capabilities and align with business objectives.

In the CompTIA Project+ PK0-005 exam objectives, under Domain 1.1: Compare and contrast different project management roles and responsibilities, the PM is responsible for overseeing the development and implementation of system enhancements.

Time and materials contracts are flexible and beneficial when the project scope has many unknowns. They allow costs to be adjusted based on actual time and resources used, which is consistent with CompTIA Project+ recommendations for projects with uncertain requirements.

During the project closure phase in the waterfall methodology, it is crucial to validate the deliverables to ensure that all project requirements have been met and the project outputs are complete and satisfactory. Additionally, reconciling the project budget is performed to ensure all financial records are accurate and reflect the actual project costs, which is essential for the formal closing of the project.

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

A closure meeting involving the project team and stakeholders is the most appropriate method to finalize the handoff of deliverables. This meeting ensures that all parties acknowledge the completion of project objectives and agree on the transition of deliverables.

Per the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Explain the importance of activities performed during the closing phase, conducting a closure meeting is essential for formal acceptance and documentation of project completion.

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.

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.

Option A shows a cause and effect diagram, also known as a fishbone diagram or an Ishikawa diagram1. This is a tool that helps to identify and analyze the root causes of a problem by displaying the possible causes and effects in a graphical format2. A cause and effect diagram can help the project team to determine whether the particular cause and effect are related by using a systematic and logical approach, such as asking “why” questions or using the 5 Whys technique34. A cause and effect diagram is better than the other options because:

Option B shows a Gantt chart, which is a tool that helps to plan and track the tasks, dependencies, durations, and resources of a project along a timeline5. A Gantt chart does not focus on the causes and effects of a problem, but rather on the sequence and progress of the project activities.

Option C shows a pie chart, which is a tool that helps to compare and visualize the proportions of different categories or segments of data6. A pie chart does not show the relationships between the causes and effects of a problem, but rather the distribution of the data values.

Option D shows a scatter plot, which is a tool that helps to examine the correlation or association between two variables or sets of data7. A scatter plot does not show the causes and effects of a problem, but rather the pattern or trend of the data points.

References = CompTIA Project+ Certification Study Guide8, CompTIA Project+ Certification Exam Objectives9, Cause and Effect Diagrams for PMP1, Cause and Effect Analysis: Using Fishbone Diagram and 5 Whys2, How to Create a Cause and Effect Diagram3, How to Use Cause and Effect Analysis to Solve Business Problems4, What is a Gantt Chart?5, What is a Pie Chart?6, What is a Scatter Plot?7

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

The project manager has taken a risk mitigation approach by buying the item from another vendor who can supply it immediately. Risk mitigation is a strategy that involves reducing the probability and/or impact of a negative risk to an acceptable level. By purchasing the item from another vendor, the project manager has reduced the impact of the delay on the project schedule, even though it may have increased the project cost. Risk mitigation is different from risk transfer, which involves shifting the responsibility or burden of a risk to a third party, usually through a contract or insurance. Risk acceptance is a strategy that involves acknowledging the risk and being prepared to deal with its consequences. Risk sharing is a strategy that involves allocating some or all of the ownership of a risk to another party who is willing to take on that risk, usually for some form of incentive or reward. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Risk Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 7: Risk Management2

A gantt chart is a visual representation of a project timeline that shows the tasks, durations, dependencies, and resources of a project in a horizontal bar chart format. A gantt chart can help a project manager to calculate the progress of the whole project scope by comparing the planned and actual start and finish dates of each task, as well as the percentage of completion and the critical path. A gantt chart is also a useful tool for communicating the project status and performance to the sponsor and other stakeholders. Therefore, the first document that the project manager should update to calculate the progress of the whole project scope is the gantt chart. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Schedule Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 6: Schedule Management2; What Is a Gantt Chart? 7 Examples for Project Management3

Sprint 1 shows the highest velocity because velocity measures the amount of work completed during a sprint. In a burndown chart, this is shown by how much the actual remaining work decreases from the beginning to the end of the sprint. The red actual line drops most sharply during Sprint 1, moving from about 40 user stories to the mid-20s. This indicates the team completed the largest number of user stories during that sprint compared with the other sprints. Sprint 2 and Sprint 3 show smaller decreases, meaning lower completed work. Sprint 4 and Sprint 5 also show progress, but their reductions are not as large as Sprint 1. Therefore, Sprint 1 reflects the highest team velocity.

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.

A downtime window schedule specifies a timeframe during which systems can be taken offline or changed without affecting business operations. CompTIA Project+ includes this as part of deployment planning to ensure minimal disruption to stakeholders.

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

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

When a project manager observes that the project ' s outcomes do not align with expectations, despite the vendor fulfilling all contractual obligations as per the Statement of Work (SOW), the appropriate next step is to perform a gap analysis. This analysis helps identify discrepancies between the current state (what has been delivered) and the desired state (stakeholder expectations).

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 2.5: Given a scenario, perform risk management activities, performing a gap analysis is a critical activity to assess and address such discrepancies. The gap analysis will provide insights into areas where the project may not be meeting stakeholder expectations, allowing the project manager to develop strategies to bridge these gaps.

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

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.

This answer is based on the best practice of using historical information and lessons learned from previous projects to improve the planning and execution of current projects12. By using existing artifacts, such as scope statements, project plans, risk registers, and change logs, the PM can leverage the knowledge and experience of the previous PM and avoid repeating the same mistakes or oversights. However, the PM should also accommodate the artifacts based on the current project success criteria, which may differ from the previous project in terms of scope, schedule, budget, quality, or stakeholder expectations34. The PM should not rely solely on the previous PM’s advice, the project sponsor’s report, or the project charter, as these sources may not provide enough detail or accuracy for the current project’s scope statement. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification Exam Objectives6, How to Use Historical Information in Project Management1, How to Use Lessons Learned to Improve Project Management2, How to Define Project Success Criteria3, How to Use Existing Artifacts in Project Management4

Personally identifiable information (PII) is any data that can be used to identify, contact, or locate a specific individual, either alone or combined with other sources. PII includes information such as name, address, phone number, email address, social security number, etc. Patient names are examples of PII, and therefore the data that contains them should be masked or anonymized to protect the privacy and security of the patients. Confidential information, protected health information, and security clearance are not types of data, but rather categories or levels of data sensitivity that may require different degrees of protection or access control. References = CompTIA Project+ Study Guide, Chapter 3: Project Planning, Section 3.4: Data Privacy and Security, p. 121; Patient Data: Types, Uses & Hospital Patient Databases; What is Patient Data and Why Is It Important?; Chapter 1 - Registrar Playbook

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 project manager can use the survey results as an input for performance feedback for the project team members. Performance feedback is a process of providing constructive and timely information on the performance of individuals or teams in relation to project goals and expectations. Performance feedback can help to motivate, improve, and recognize project team members345

The survey results can be used as an input for performance feedback. Performance feedback involves analyzing and evaluating the performance of the project team and project management against the project plan, including identifying areas for improvement. The survey results can help identify these areas for improvement and provide feedback to the project team on their performance. References: CompTIA Project+ Study Guide Section 4.1.1

Language barriers can significantly impact communication within a project team, especially when team members lack a common understanding of technical terminology and jargon. This can lead to misunderstandings, errors, and inefficiencies. Effective communication is critical for project success, and addressing language barriers is essential for ensuring that all team members are aligned and informed.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, recognizing and mitigating communication challenges, including language barriers, is vital for effective project management.

A dashboard is a visual tool that displays key project metrics and indicators in a single view12. A dashboard can help a project sponsor to provide the latest project status information on a weekly executive call by showing the project progress, budget, schedule, risks, issues, and milestones in a clear and concise way34. A dashboard can also facilitate communication, collaboration, and decision making among project stakeholders56. A dashboard should be reviewed and updated regularly to reflect the current state of the project7. References = CompTIA Project+ Certification Study Guide8, CompTIA Project+ Certification Exam Objectives9, Write a Project Status Report in 8 Steps + Template [2023] • Asana6, Project Status Reports: 9 Easy Steps & Examples [+ Template]7, How To Write a Project Status Report (Definition and Steps)8, How to Write a Project Status Report [Template Included] - Toggl9, What Is a Project Status? Definition and Key Terms - Indeed10

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

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

ESG stands for environmental, social, and governance, and it refers to the criteria that measure the sustainability and ethical impact of an organization. ESG concerns can affect the reputation, performance, and value of a company, as well as its stakeholders and customers. For a well-known, global company that values its brand image, hiring a vendor that has been linked to ESG concerns can be a major risk and a source of negative publicity. Therefore, the project team should consider this as a primary factor to remove a vendor from consideration12.

Confronting, also known as problem-solving or collaborating, is a method of conflict resolution that involves addressing the root cause of the conflict and finding a mutually beneficial solution that satisfies both parties. Confronting is the most effective method when the stakes are high and the relationship is important, as it can lead to increased trust, respect, and cooperation. Confronting requires open communication, active listening, empathy, and creativity from both parties. Confronting is the best method to use in this scenario, as it can help the stakeholders overcome their personal animosity, focus on their common goals, and work together to complete their tasks on time12. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Project Stakeholder Management, p. 246; What is Conflict Resolution, and How Does It Work?

The critical path of the project is the longest sequence of tasks that must be completed on time for the project to finish on schedule. It determines the shortest possible duration of the project and shows the tasks that have no slack or float. Any delay in the critical path tasks will affect the project completion date. To find the critical path, we need to calculate the earliest start (ES), earliest finish (EF), latest start (LS), latest finish (LF), and slack (S) for each task. We can use the table and the network diagram given in the question to do this. The formula for calculating the slack is S = LF - EF or S = LS - ES. A task with zero slack is on the critical path. The calculations are as follows:

Task | Duration | ES | EF | LS | LF | S A | 10 | 0 | 10 | 0 | 10 | 0 B | 15 | 10 | 25 | 10 | 25 | 0 C | 10 | 10 | 20 | 15 | 25 | 5 D | 20 | 25 | 45 | 25 | 45 | 0 E | 10 | 25 | 35 | 35 | 45 | 10 F | 15 | 20 | 35 | 30 | 45 | 10 G | 5 | 45 | 50 | 45 | 50 | 0 H | 10 | 35 | 45 | 40 | 50 | 5 I | 20 | 35 | 55 | 30 | 50 | -5 J | 5 | 50 | 55 | 50 | 55 | 0

Based on the table, we can see that the tasks with zero slack are A, B, D, G, and J. Therefore, the critical path is A-B-D-G-J, which has a total duration of 55 days. The other options are not the correct critical paths, as they either include tasks with positive slack (such as C, E, F, and H) or have a longer duration than 55 days (such as A-C-F-I-J).

If the current team lacks the necessary skills for quality assurance, the project manager should reassess the resource pool to identify whether existing team members can be trained or if additional resources with the required expertise are needed. This assessment helps in making informed decisions about resource allocation, training needs, or recruitment, ensuring that the project maintains its quality standards.

Per the CompTIA Project+ PK0-005 exam objectives, under Domain 2.3: Given a scenario, perform resource management activities, evaluating and managing resources is crucial for addressing skill gaps and maintaining project quality.

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

A burndown chart is a visual representation of the remaining work versus the time required to complete it1. It is commonly used by agile teams to track the progress of each iteration or sprint and to forecast the project completion date2. A burndown chart shows the ideal work remaining line and the actual work remaining line, which can help the team identify any deviations or impediments and adjust accordingly1. A burndown chart is different from a Pareto chart, which shows the frequency of different causes of problems; a milestone chart, which shows the key events and deliverables of a project; and a Gantt chart, which shows the dependencies and durations of tasks in a project3. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 6: Planning Projects Part 2, page 173; Burndown Chart: What Is It & How to Use One for Agile - ProjectManager, Introduction and Components of a Burndown Chart sections; Burndown Chart: What it is, How to Use it, Example [2023] • Asana, Introduction and What is a burndown chart? sections.

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

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

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

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.

When a project manager receives an escalation about a deliverable that was actually provided on time, it indicates a communication issue. The next step should be to revise the communication plan to ensure that all stakeholders are properly informed about project progress and deliverables in the future. This helps to prevent misunderstandings and ensures that everyone has the correct information.

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

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 project manager should produce a project charter first to start communication about the boundaries of the project. A project charter is a document that formally authorizes a project and defines its high-level scope, objectives, assumptions, constraints, stakeholders, roles and responsibilities, and key deliverables. A project charter can help to communicate the project vision and expectations to all stakeholders and provide a basis for future project decisions23

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

Updating the issue log is the first step in documenting the problem and determining its impact on the project. This aligns with CompTIA Project+ guidelines, which emphasize the importance of tracking issues as they arise.

The current stage of the project team is norming, which is the third stage of the five stages of team development. In this stage, the team members have resolved their conflicts and differences, and have established a sense of cohesion and collaboration. They are more productive, supportive, and cooperative, and they follow the agreed norms and rules of the team. They also communicate effectively and seek feedback and assistance from each other. The norming stage is preceded by the forming stage, where the team members get to know each other and the project goals, and the storming stage, where the team members experience disagreements and challenges. The norming stage is followed by the performing stage, where the team members work efficiently and autonomously towards the project outcomes, and the adjourning stage, where the team members complete the project and celebrate their achievements. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 11: Team Management1; CompTIA Project+ Certification Study Guide, 3rd Edition, Chapter 11: Team Management2; The 5 Stages of Team Development (Including Examples)3