PK0-005 Sample Questions Answers

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.

A weak matrix organizational structure is one where the project manager has low authority and the functional manager has high authority. The project manager is considered to be a coordinator or an escalator, and the team members are primarily loyal to their functional units. This can cause issues with team motivation, communication, and performance1

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.

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

A common disadvantage of cloud models is higher dependency on the vendor—often described as vendor lock-in. When solutions rely on a provider’s proprietary services, APIs, data formats, or managed offerings, switching providers (or moving back on-premises) can become costly and complex. This dependency can reduce portability and negotiating leverage over time, and it can increase switching costs if pricing, service levels, or strategic needs change.

Options A and B are generally the opposite of typical cloud benefits: cloud platforms usually provide elastic scaling and abundant capacity relative to on-prem constraints (assuming budget allows). Latency (C) can be a disadvantage in some architectures, but it isn’t as consistently defining as vendor dependence—latency can be mitigated through region selection, edge services, and network design, and many workloads experience acceptable performance. Vendor dependency/lock-in, however, is a well-known structural risk of adopting cloud-native services.

From a project management lens, this matters in planning and governance: procurement strategy, architectural choices, and exit/migration planning help manage the risk of over-dependence on a single provider.

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

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

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

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

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.

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

A business case exists to justify why the project should be done—what problem/opportunity it addresses and what benefits/value it provides relative to cost. In CompTIA Project+ objectives, the business case is part of discovery/concept and initiation, linked to business objectives and ROI, and is used to support approval decisions. The first, foundational element of that justification is clearly stating the problem being solved (or the opportunity being captured). ()

Option D best captures that intent: specify what problem is being solved by the project. Once the problem is defined, the business case typically expands to include expected benefits, costs, assumptions, constraints, and high-level risks—but those are supporting elements, not the primary objective.

Option A is more aligned to risk management artifacts (risk register, issue log). Option B (timeline and budget) is more aligned to the project plan and estimating/scheduling. Option C (specific tasks) aligns to a WBS or backlog planning. The sponsor is asking for the “why” and justification for investment before committing effort—so the business case objective is to articulate the problem and the value of solving it. ()

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

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

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

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

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

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

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

Monthly feedback and training sessions are the best approach to ensure that the deliverables of a critical business initiative are increasingly adopted and leveraged by the organization over time. Feedback and training sessions are communication and learning activities that provide information and guidance on how to use and benefit from the new processes and technology introduced by the initiative. Feedback and training sessions can help to increase awareness, understanding, acceptance, and adoption of the deliverables among the organization’s employees and stakeholders. They can also help to identify and address any issues or challenges that may arise during the implementation and transition phases.

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.

The project manager should validate against the scope statement and ask for sign-off after a system was implemented and testing was successfully completed. The scope statement is a document that defines and documents the project scope, objectives, deliverables, requirements, assumptions, and constraints. The scope statement can help to establish a common understanding and agreement between the project manager and the stakeholders on what the project aims to achieve and deliver. Validating against the scope statement means checking whether the project deliverables meet the agreed-upon scope criteria and quality standards. Asking for sign-off means requesting formal acceptance and approval of the project deliverables from the stakeholders.

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

In project management, understanding the difference between the current state and the desired future state is essential for identifying gaps and planning improvements. The current state refers to the organization's existing conditions, processes, or performance levels. The desired future state represents the target conditions or performance levels the organization aims to achieve through the project. This comparison is fundamental in conducting a gap analysis, which helps in planning the necessary steps to transition from the current to the desired state.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.3: Given a scenario, apply the change control process throughout the project life cycle, understanding the current and desired states is crucial for effective change management and project planning.

A kickoff meeting is the best fit because it is used at the start of a project (or phase) to align stakeholders and the team on core fundamentals such as scope, objectives, roles, high-level schedule/timeline, budget constraints, risks, and ways of working. If the PM is unclear about budget and timeline before work begins, a kickoff (often preceded by initiation artifacts like the charter) is where those expectations are clarified, confirmed, and communicated broadly.

A “demo” is used to show working product increments. A “stand-up” is a short Agile daily coordination meeting focused on immediate work, blockers, and next steps—not initial budget/timeline clarity. A “status call” is a recurring execution-phase update meeting; it assumes the project already has an agreed baseline.

Therefore, to establish shared understanding and confirm budget and timeline expectations prior to start, the PM should hold a kickoff meeting (or kickoff-style alignment session) to confirm baselines and ensure everyone begins execution with the same commitments and constraints.

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

To show dependencies in a schedule, the project manager should use a network diagramming technique—specifically, the Precedence Diagramming Method (PDM). PDM represents activities (nodes) and connects them with relationships (arrows/links) to show task ordering and dependency logic. CompTIA Project+ explicitly includes analyzing and using a project network diagram as a tool, and it also emphasizes understanding dependencies and successor/predecessor relationships (finish-to-start, start-to-start, etc.), which are exactly what PDM models.

The other options don’t match the requirement. Waterfall is a life-cycle methodology, not a dependency diagramming tool. Simulation is typically used for quantitative analysis (e.g., Monte Carlo) rather than directly drawing dependencies. Cost ratio analysis is financial decision support, not schedule dependency mapping.

Therefore, to build a schedule that clearly communicates task order, constraint logic, and critical sequencing, the PM should use precedence diagramming (a form of project network diagram) to visualize and manage dependencies during initiation and early planning.

An ERP (Enterprise Resource Planning) system integrates financial management, HR, and operations. In this case, ERP can handle time tracking and cost reporting together. EDRMS manages documents, CRM handles customer relationships, and CMS manages content—not project costs.

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 plan, monitor, and control the project progress, scope, and quality. A gantt chart is different from a milestone chart, which only shows the key events or deliverables of a project without the details of the tasks. A gantt chart is also different from a PERT chart, which is a network diagram that shows the logical relationships and sequence of tasks in a project. A gantt chart is also different from a WBS, which is a hierarchical breakdown of the project scope into smaller and manageable components. 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; 3 types of visual project management: Timelines, calendars, and boards (with examples)4

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

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

Pll stands for personally identifiable information, which is any data that can be used to identify a specific individual. Examples of Pll include name, address, phone number, email address, social security number, passport number, driver’s license number, etc. IP address and email address are both Pll because they can be used to trace the identity and location of a person. Medical record and test result values, name and year of birth, and x-ray and blood type are not Pll by themselves, but they can become Pll if they are combined with other data that can link them to a specific individual. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 10: Project Security, page 331. CompTIA Project+ Certification Exam Objectives, Domain 4: Project Security, Objective 4.1: Given a scenario, apply security best practices to a project, Sub-objective: Identify and classify Pll.

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.

Archival involves preserving project records and communications so that they are accessible for future reference. This helps ensure important information is not lost over time, consistent with best practices in project documentation as per CompTIA Project+.

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

Identifying the root cause analysis. Identifying the root cause analysis is a quality assurance tool that can help to find and eliminate the underlying causes of quality problems or defects. Root cause analysis is a systematic process of asking why a problem occurred and tracing it back to its source. Root cause analysis can help to prevent recurrence of the same or similar problems, improve quality performance, and reduce costs and risks12

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.

A capital expense is the cost of acquiring or making improvements to fixed assets that have a useful life of more than one year1. A building purchase is an example of a capital expense, as it is a long-term investment that increases the value of the company’s assets2. Building lease, maintenance, and insurance are not capital expenses, as they are recurring or short-term costs that do not increase the value of the company’s assets3.

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

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

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

Validating deliverables involves ensuring that the project's outputs meet the defined requirements and objectives. The first step in this process is to review the project objectives to confirm that the deliverables align with the intended goals. This review provides a benchmark against which the deliverables can be assessed, ensuring that they fulfill the project's purpose before seeking stakeholder feedback or assessing documentation.

This aligns with the CompTIA Project+ PK0-005 exam objectives, particularly under Domain 2.1: Explain the value of artifacts in the discovery/concept preparation phase for a project, which emphasizes the importance of aligning deliverables with project objectives.

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

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.

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

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

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 positive correlation means that as the number of worked hours increases, so does the number of mistakes. According to CompTIA Project+, understanding such correlations is crucial for effective resource and quality management.

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

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

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

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.

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 risk log or risk register is used to document potential risks to the project, including the loss of team members due to high stress. CompTIA Project+ recommends this log as a tool for identifying and managing risks throughout the project lifecycle.

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.

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 gate review is a type of meeting that evaluates the completion and quality of a project stage and decides whether the project can proceed to the next stage. A gate review is a formal governance step that involves reviewing the goals, progress, risks, deliverables, and benefits of the project, and discussing if the project is still aligned with the business strategy and stakeholder expectations. A gate review can have different outcomes, such as go, kill, hold, recycle, or conditional go, depending on the assessment of the project status and viability123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 9: Project Change Management, p. 323; Everything Project Managers Need To Know About Gate Reviews | monday.com Blog; Gate reviews: What to do and why you need them - Rebel’s Guide to Project Management; Gates and How to Operate Them - GenSight

The process is out of control and should be revised. The project manager can use the rule of seven to determine the status of the process based on the control chart. The rule of seven states that if seven or more consecutive measurements fall on one side of the mean that there’s an assignable cause that needs investigation. In this case, the last seven data points are all below the mean, which indicates that the process is out of control and in need of adjustment12

A dashboard is the most appropriate artifact to share when a stakeholder asks for project performance data. Dashboards are designed to present key performance indicators (KPIs) and trends in a concise, visual form—such as schedule progress, scope completion, burn/burndown, budget status, risks/issues summaries, and other metrics relevant to project health. This aligns with Project+ expectations around performance monitoring and communicating status in an efficient way tailored to stakeholder needs.

An issue log is too granular and focuses only on current problems; it is part of performance, but it’s not the overall performance view stakeholders typically want. A WBS is a scope decomposition artifact used for planning and organizing work, not performance reporting. A milestone chart shows key dates and whether major points are achieved, but it does not provide comprehensive performance data (cost, trend, throughput, overall health).

Therefore, to provide performance data effectively—especially for stakeholders who want quick, up-to-date visibility—the PM should send (or grant access to) the project dashboard, ensuring it reflects the latest reporting period and includes the metrics the stakeholder cares about.

A postmortem (often synonymous with a structured “lessons learned”/retrospective at the end of a project) is specifically intended to identify what worked, what didn’t, and what to improve next time. It creates actionable improvements for future projects—process changes, tooling updates, training needs, better estimation approaches, risk triggers, and governance refinements. CompTIA Project+ closing-phase expectations include evaluating the project and collecting feedback, which is the exact purpose of a postmortem-style activity.

A contract review is valuable for procurement performance and compliance, but it’s narrower than overall delivery improvement. Archived documents are essential for auditability and reference, but archiving is primarily record retention; it doesn’t inherently analyze improvement opportunities unless paired with a review session. Project rewards support morale and recognition (also called out as part of closure activities), but they don’t generate systematic improvement insights.

A strong postmortem typically produces: a short list of top improvement themes, owners, due dates, and where to embed changes (templates, playbooks, onboarding, QA practices). That turns closure learning into measurable organizational improvement—exactly what the question is asking for.

The project manager is using multiauthoring software to maintain the version control for the documentation of requirements. Multiauthoring software is a type of software that allows multiple users to create, edit, and collaborate on documents simultaneously. It also provides features such as tracking changes, commenting, reviewing, and merging versions. Multiauthoring software can help to improve the quality, accuracy, and consistency of documents and facilitate communication and feedback among stakeholders. Examples of multiauthoring software include Google Docs, Microsoft Word Online, and Confluence34

Because the issues are already occurring and are expected to negatively impact schedule and cost, the most direct mitigation action is to use contingency reserves/buffers that were planned for uncertainty. CompTIA Project+ explicitly includes both determining contingency reserves/buffers during planning and contingency reserve/buffer utilization during execution/controls as part of schedule and project control activities.

Updating the issue log is important for tracking, ownership, escalation, and outcomes, but it is primarily a documentation/control step, not the immediate mitigation that protects the timeline and budget. Communicating with stakeholders is also essential (especially if reserves will affect commitments), but communication alone doesn’t reduce the impact—reserves do. Reviewing the risk register can help connect issues back to known risks and validate whether contingency plans exist, but the question asks what is best to do to mitigate the schedule/cost impact now; that is exactly what contingency reserves are designed for.

In practice, the PM would typically: document the issues, apply the reserve/buffer, update schedule/budget baselines as needed, and then communicate the revised forecast—however, the mitigation action among the options is using contingency reserves.

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

This answer is based on the best practice of defining access requirements in project management, which is to identify the roles, responsibilities, and permissions of the project team members and other stakeholders who need to access the project information, resources, and deliverables12. The first step in this process is to assess the resource pool, which is the availability and capability of the human resources that can be assigned to the project34. By assessing the resource pool, the project manager can determine the skills, experience, and security clearance of the potential project team members, as well as their reporting relationships, communication preferences, and expectations56. This information can help the project manager to define the access requirements for each role and stakeholder group, and to assign the appropriate level of access to the project data, documents, tools, and systems78. References = CompTIA Project+ Certification Study Guide9, CompTIA Project+ Certification Exam Objectives10, What is Requirements Management?, How to Write Project Requirements, A Guide to Functional Requirements, Project Requirements Management: A Quick Guide, Creating clear project requirements, How to Define Project Roles and Responsibilities

Assigning a scribe allows the project manager to focus on hosting and facilitating the meeting effectively without being distracted by note-taking. This approach is consistent with best practices in meeting management and aligns with CompTIA Project+ guidelines, which emphasize the importance of efficient meeting roles and responsibilities.

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.

To validate that a project has been successfully completed. The intent and purpose of a project closeout report is to validate that a project has been successfully completed and to summarize the goals, objectives, and outcomes of the project, as well as the lessons learned and the feedback from stakeholders. A project closeout report is a document that is submitted at the end of a project to officially conclude it and release the resources and contracts involved. It is useful for evaluating the project’s success and improving the performance of future projects12

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.

The project manager should put in place a time and materials contract before work begins for a third party that needs to perform a short-term task for which the duration cannot be accurately estimated and the cost cannot be calculated in advance. A time and materials contract is a type of contract where the buyer pays the seller based on the actual time spent and materials used during the project. A time and materials contract is suitable for projects that have uncertain or variable scope, duration, or cost. A time and materials contract can provide flexibility and adaptability for both parties and allow them to adjust to changing requirements or circumstances.

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

When a risk trigger is detected, the risk hasn’t yet turned into an issue, but the conditions indicate it may happen. At this stage, the project team should execute the contingency plan that was pre-developed during risk planning. Assigning a risk owner happens earlier in the planning stage, and work-arounds are used only for unplanned risks. Escalation is only needed if the contingency cannot address the risk.

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

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

The rules of engagement are the guidelines and expectations that define the relationship between the contractor and the company. They may include topics such as communication, confidentiality, access, security, performance, and compliance. The project manager should reinforce the rules of engagement with the contractor to ensure that they understand and respect the boundaries and protocols of the company. This will help to avoid any potential conflicts, misunderstandings, or breaches of contract. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 7: Project Stakeholder Management, p. 239; Contractor Rules of Engagement - Cox Enterprises, p. 1; Legal Considerations for Engaging Contractors | LegalVision

The product owner is the person who is responsible for managing the product backlog, which includes adding, removing, or changing items based on stakeholder feedback and business value. The product owner is also the one who can collaborate with the development team and the scrum master to decide if a change can be accommodated in the current sprint or deferred to a future sprint. Therefore, the stakeholder should have asked the product owner to request the change instead of the team member, who is not authorized to make changes to the sprint backlog12.

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

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

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

CompTIA Project+ PK0-005 Exam Objectives

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

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

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

Continuous Integration and Continuous Delivery (CI/CD) aim to accelerate software delivery while maintaining high quality through frequent automated testing and deployment. This practice is endorsed by CompTIA Project+ as part of modern project methodologies for improving efficiency and quality.

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

The diagram shows that the customer added requests for previously unrequested features during execution and the change control process was not followed. That combination most strongly points to scope creep as the root cause of the missed deadline: additional scope entered the workstream without proper evaluation, approval, replanning, and schedule/budget adjustment. CompTIA Project+ emphasizes controlling scope through defined requirements, scope baselines/artifacts, and a formal change control process; when that process is bypassed, uncontrolled scope growth commonly drives schedule slippage and cost overruns.

Gold plating (building “unnecessary features”) is also present, but in the diagram it appears as a downstream effect of weak requirements discipline and poor change control—teams often overbuild when requirements are incomplete or shifting. The initiating problem highlighted is that the customer did not provide all requirements early, which increases later change requests; when those changes are not properly controlled, the project experiences scope creep and deadline impact.

Team conflicts and unvalidated deliverables are not supported by the causal chain shown. The best root-cause label among the options is scope creep.

CI/CD (Continuous Integration/Continuous Deployment) allows faster and more reliable delivery by automating builds, tests, and deployments. It ensures rapid delivery without compromising quality. Updates are frequent but not necessarily tied to sprint cycles.

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

Home address and date of birth must be protected as personally identifiable information (PII). PII is any information that can be used to identify, contact, or locate an individual person, either alone or in combination with other sources. PII can include information such as name, email address, phone number, social security number, passport number, driver’s license number, bank account number, credit card number, biometric data, medical records, etc. PII must be protected from unauthorized access, use, disclosure, modification, or destruction to prevent identity theft, fraud, or other malicious activities that may harm the individual’s privacy or security.

An audit conducted years after closure most commonly requires archived documentation because auditors typically need the full evidence trail of what was approved, executed, delivered, and controlled (plans, baselines, change logs, issue logs, risk registers, approvals, communications, testing evidence, acceptance/sign-off, financials, etc.). CompTIA Project+ explicitly lists “Archiving documentation” as a key project closing activity, and the CompTIA certification page also highlights project closing as including archiving documentation.

While signed contracts (A) can be part of that evidence set, they are only one subset of what an audit may request. A project closeout report (C) is useful as a summary, but auditors often need the underlying artifacts that support the report’s claims. Lessons learned (D) may be reviewed for process maturity, but it’s not usually the primary evidence package for compliance, financial, or governance verification.

Because the scenario emphasizes the long time gap (“years after”), archiving is the key: it ensures records are retained, retrievable, and complete for governance, compliance, and validation needs well beyond the project’s end date.

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

A Scrum daily stand-up (daily Scrum) focuses on short, tactical coordination: what was completed since the last meeting, what will be done next, and what blockers/impediments are in the way. Option D matches that format: yesterday’s progress, today’s plan, and issues that may interfere. This aligns with Agile meeting practices emphasized in Project+ where meeting cadence and purpose are tailored to keep delivery flowing and expose impediments early.

Option A describes risk analysis and response planning (risk register work), not the daily Scrum. Option B describes a retrospective (stop/continue/start improvements) which typically happens at the end of a sprint, not daily. Option C describes schedule compression/resource coordination concepts common in predictive planning (buffers, critical path convergence), not a Scrum stand-up.

Daily stand-ups are timeboxed, typically 15 minutes, and are intended to help the team synchronize and adjust the plan for the next 24 hours. The key output is clarity on what’s moving, what’s blocked, and who needs follow-up conversations after the stand-up to resolve impediments.

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

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

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

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

A request for proposal (RFP) is the best document for the company to use in this scenario, because it is the most detailed and personalized type of request document. An RFP allows the company to specify the project scope, requirements, deliverables, evaluation criteria, and budget for the structured cabling installation, and to solicit proposals from various vendors that can meet those needs. An RFP also enables the company to compare the vendors based on their qualifications, experience, methodology, and pricing, and to select the best one for the project. An RFP is more suitable than an RFB, RFQ, or RFI, because those documents are less comprehensive and more generic, and they do not provide enough information for the company to make an informed decision. References = CompTIA Project+ Study Guide: Exam PK0-005, Third Edition, Chapter 5: Initiating the Project, page 1131; RFI, RFP, RFQ: Understanding the Differences2; Data Center Structured Cabling RFP Template3

DevSecOps integrates security controls early in the development lifecycle. Its focus is to develop, secure, and test continuously, ensuring that vulnerabilities are identified and addressed before deployment. Security is not bolted on later but woven into development and testing workflows.

The SOW (statement of work) is a document that defines the scope, deliverables, schedule, and resources of a project. It is a contractual agreement between the buyer and the seller that should be changed first when there are approved changes to the product. Changing the SOW will ensure that the project expectations and requirements are updated and aligned with the customer’s requests. The other options are not documents that need to be changed first, but rather metrics or tools that can be used to measure or manage the project. References = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 3: Initiating Projects; CompTIA Project+ Certification Exam Objectives, Domain 2: Project Planning, Objective 2.1: Develop a project scope document.

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

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

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

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

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

Meeting with the team to emphasize the importance of following change management procedures is the best approach to prevent future unauthorized changes. CompTIA Project+ highlights the importance of adhering to formal change control processes to ensure project alignment and accountability.

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

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

According to 6 Techniques for Running Project Management Meetings, one of the best practices for effective project meetings is to assign meeting roles to stay focused. By delegating the roles and responsibilities of facilitator, timekeeper, scribe, and presenter, the project manager can ensure that the meeting agenda is followed, the action items are recorded, and the outcomes are communicated. This can also increase the engagement and accountability of the project team members, and reduce the frustration of the project manager.

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

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

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

Notifying the CCB that an approved change “failed” is consistent with logging and escalating an issue/incident arising from change implementation. In CompTIA Project+ objectives, the change control process includes not only approval and implementation, but also validating the change implementation and communicating change deployment. If validation shows the change did not achieve the expected outcome, that result must be documented and escalated through the same governance path (often the CCB) so the project can decide whether to roll back, revise, or raise a new change request.

CompTIA also separates risk management (responses to potential future events) from issue management (handling problems that have already occurred), including issue tracking, escalation path, ownership, and a resolution plan, and it highlights “connections between issues and changes.” A failed implemented change is an issue now, so an incident report (documenting what happened, impact, and next steps) best matches the control process being followed.

“Scope creep” is unauthorized scope growth, “risk response” is for anticipated risks, and “recovery plan” could be a next action, but the process described is the reporting/documentation and escalation of the incident.

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

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

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

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

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 core Kanban concept is managing flow by limiting work in progress (WIP). Kanban uses visual workflow boards and explicit WIP limits to prevent overloading the system, expose bottlenecks, and improve throughput and predictability. By limiting how many items can be “in progress” at once, teams finish work faster, reduce context switching, and stabilize cycle time—key goals of flow-based delivery. CompTIA Project+ includes Agile and adaptive concepts, and Kanban is commonly distinguished by its focus on continuous flow and WIP limits rather than timeboxed iterations.

Option A describes iteration-based alignment (more associated with Scrum’s sprint cadence). Option B (color-coding tasks) can be a visual technique but is not a defining Kanban principle. Option C (allocating resources to high-priority tasks) is a general management practice; Kanban does include prioritization, but its hallmark control is WIP limitation to optimize flow.

Therefore, the correct Kanban concept is limiting WIP to manage flow—a fundamental mechanism used to improve delivery efficiency and quality while keeping the system from becoming congested.

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.

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

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.

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.

The scenario indicates a breakdown in communication between the project team and the project sponsor. The sponsor was unaware of the issues and could not provide guidance on the next steps, highlighting a deficiency in the project's communication processes.

According to the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, it is essential to:

Develop communication platforms/modalities

Manage project communication

Control project communication

One of the key aspects of controlling project communication is:

Revising the communication plan

The communication plan outlines how information is disseminated among stakeholders, including the frequency, methods, and responsible parties. If a sponsor is uninformed about project issues, it suggests that the communication plan is either inadequate or not being followed correctly.

The CompTIA Project+ PK0-005 Certification Study Guide further elaborates on this by stating that:

The communication plan should be reviewed and updated regularly to ensure effective information flow among stakeholders.

In this case, revising the communication plan would address the communication gaps, ensuring that the sponsor and other stakeholders receive timely and accurate information about project issues and developments.

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

Data security involves classifying information based on sensitivity and ensuring that it is protected accordingly. This approach is key in project management to protect sensitive data, as emphasized by CompTIA Project+.

When a project team lacks hands-on experience and decides to involve a third-party vendor for product development, the first document to expedite is a Request for Proposal (RFP). An RFP outlines the project requirements and asks potential vendors to submit proposals detailing how they would meet those requirements and at what cost. This allows the project manager to evaluate the capabilities and offerings of different vendors before making a decision.

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

In Tuckman’s team development model (forming, storming, norming, performing, adjourning), the storming phase is characterized by conflict, tension, and disagreement as members challenge ideas, roles, and ways of working. Option A describes this best: conflict that affects relationships. CompTIA Project+ includes people management concepts such as team dynamics and the need for PMs to apply leadership, conflict resolution, and motivation techniques as the team develops. ()

Option C describes forming (meeting and learning about the project). Option B describes performing (high-functioning, well-organized execution). Option D aligns with adjourning (closing/disbanding after work completion).

In storming, the PM’s role is to help the team move toward norming by clarifying goals and roles, setting working agreements, reinforcing communication norms, and addressing conflicts early and constructively. For a tax application (high accuracy/compliance needs), stabilizing team collaboration is crucial to reduce defects and rework. Therefore, the life-cycle description that matches storming is conflict affecting relationships. ()

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

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

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

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

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

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.

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

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

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

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

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

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.

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.

In a software development project with an external customer, the project manager (PM) is responsible for coordinating and managing the project—including building, maintaining, and controlling the schedule. CompTIA Project+ specifically identifies schedule management as a core skill area (e.g., maintaining schedules and related activities), which aligns directly with option A.

The other options describe responsibilities typically owned by other roles or governance functions. Defining functional requirements is usually led by a business analyst and/or product owner/customer stakeholders, with the PM facilitating requirements activities and ensuring traceability and impact awareness—not owning definition outright. Developing software components is a developer/engineer responsibility, not the PM’s. And assessing/authorizing security policies is commonly handled by security/compliance leadership (or a governance authority), while the PM ensures the project aligns with required policies and coordinates related work.

Therefore, the clearest PM responsibility in this scenario is managing the project schedule (along with integrating scope, resources, risks, stakeholders, and communications).

One of the primary purposes of a stand-up meeting is to identify blocking tasks that hinder progress. This allows the team to address issues promptly and maintain momentum.

In the CompTIA Project+ PK0-005 exam objectives, under Domain 1.8: Compare and contrast communication management concepts, stand-up meetings are highlighted as a tool for daily communication to surface impediments and coordinate efforts.

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