CompTIA Project+ PK0-005 (PK0-005) — Questions 826–900

CPI = EV/AC, SPI = EV/PV. So EV, AC, and PV are required.

The project charter includes high-level scope, objectives, assumptions, and constraints, but detailed work packages are developed during planning.

Purchasing insurance transfers the financial risk of a potential loss to a third party (the insurer). This is the defining characteristic of the Transfer risk response strategy, where the ownership and impact of the risk are shifted, but the risk itself is not eliminated. In project management, this is distinct from Mitigate, which reduces probability or impact through direct action.

A Gantt chart with dependency links is correct because it visually represents task sequences and dependencies, allowing project managers to trace the longest path of dependent tasks, which defines the critical path. The Critical Path Method (CPM) is a mathematical algorithm that calculates the longest path through the project network by determining early start, early finish, late start, and late finish dates for each activity, directly identifying the critical path.

According to the PMBOK Guide, the triple constraint (also known as the iron triangle) traditionally includes scope, time, and cost (budget). Scope defines the work required to deliver the project's deliverables, and any change to scope directly impacts time and cost. Therefore, Scope (D) is a core project constraint.

The project charter is a key document created during project initiation that formally authorizes the project and provides the project manager with the authority to apply organizational resources to project activities. The stakeholder register is also created during initiation to identify all individuals, groups, or organizations that may impact or be impacted by the project, capturing their interests, expectations, and influence levels.

The sponsor provides resources and champions the project; the PM does planning and execution.

In project quality management, Quality Assurance focuses on process adherence, Quality Control on product verification, and Continuous Improvement on iterative enhancements. Common confusions include swapping QA/QC definitions or misattributing Cost of Quality to Continuous Improvement.

When a project is delayed due to an external factor like regulatory changes, the project manager must follow the formal change control process. Submitting a change request with the revised schedule and impact analysis ensures that the sponsor and change control board (CCB) can formally approve the new baseline, maintaining governance and traceability. This aligns with the PMBOK Guide's guidance on managing changes to the project management plan.

The risk register is the correct document because it is the central repository for recording identified risks, their impact, probability, and planned response strategies. The project manager uses the risk register to track and communicate risk details to stakeholders, making it the appropriate source for the report described.

The process of collecting feedback on what went well and what could be improved is the essence of creating a lessons learned document. In project management, this document captures insights and recommendations to improve future project performance, and it is a key output during project closure.

Upon identifying a delay that impacts the critical path, the project manager must first analyze the full impact on schedule and cost before formally documenting the change. Submitting a change request initiates the formal change control process, ensuring that all stakeholders review and approve adjustments before any plan updates or actions are taken. This aligns with the PMBOK Guide's integrated change control process, which requires impact analysis as the first step after identifying a potential change.

A program is a group of related projects managed together to achieve benefits. A project is a single initiative. A portfolio is a collection of projects and programs aligned to strategy.

Version control systems (VCS) like Git, SVN, or document management platforms (e.g., SharePoint) maintain a complete history of changes. When a file is overwritten, the previous correct version can be restored by reverting to an earlier commit or revision in the version history, preserving all metadata and audit trails. This is the most reliable and efficient recovery method, avoiding data loss or manual reconstruction.

The first step in change control is to submit a change request, which then undergoes impact analysis.

In agile, the product backlog is a prioritized list of all desired work for the project. Sprint backlog is for a single sprint.

If cost performance continues, EAC = BAC / CPI = BAC / (EV/AC) = 200000 / (120000/130000) = 200000 / 0.9231 ≈ $216,667.

Jira is a widely used Agile project management tool that supports Scrum and Kanban boards, epics, stories, and sprints.

Follows the standard user story format: 'As a [user role], I want [goal], so that [benefit].' This structure is prescribed by agile methodologies like Scrum and XP to ensure requirements are user-centric, testable, and value-driven. The 'so that' clause provides the business rationale, which is critical for prioritization and acceptance criteria definition.

The project charter must identify the project sponsor, who provides authority and funding. The exhibit lists the project manager, business case, and high-level scope but omits the sponsor, making option D correct.

In a fixed-price contract, the seller bears the risk of cost overruns because the price is fixed.

A Kanban board is the most appropriate tool for managing user stories, sprints, and backlog items in an Agile project because it visualizes workflow, limits work-in-progress, and allows the team to track tasks across columns (e.g., To Do, In Progress, Done). Unlike Gantt or PERT charts, Kanban boards are designed for iterative, continuous delivery and real-time collaboration, making them ideal for Agile frameworks like Scrum or Kanban.

In the norming stage, team members begin to work together and share ideas openly.

The team should discuss the reasoning behind the high estimates to uncover hidden assumptions or risks, leading to a shared understanding.

Parametric estimation uses a statistical relationship between historical data and other variables (e.g., cost per function point) to calculate an estimate. In this scenario, the project manager derives a cost per function point from a similar project and multiplies it by the expected number of function points. This is a classic example of parametric estimation because it applies a unit rate to a quantity.

When an issue cannot be resolved at the project manager level, it should be escalated to the appropriate level of management (e.g., program manager, sponsor) using the predefined escalation path. Updating the issue log is a good practice, but escalation is the required action when resolution is not possible.

The Pareto chart is based on the 80/20 rule, helping prioritize the most impactful issues.

The project charter formally authorizes the project and includes the project purpose, objectives, high-level scope, budget, schedule, assumptions, constraints, and the authority of the project manager. The other options are developed later in the planning or executing phases.

After approval, the project manager must update the relevant project baselines (e.g., scope, schedule, cost), implement the change, and then monitor its effect. Communication is also key, but updating baselines and implementing are primary.

A matrix organizational structure is common because it blends functional and projectized elements, allowing team members to report to both a functional manager and a project manager. This structure balances resource sharing with project focus, making it widely used in organizations that handle multiple concurrent projects.

Velocity is the average story points completed per sprint. With a consistent velocity of 30 points per sprint, over two sprints the team can complete approximately 60 points.

In a regulated medical device project, noncompliance with the quality management plan (QMP) must be addressed immediately to avoid regulatory penalties, product recalls, or legal liability. Stopping work on affected tasks ensures that no further noncompliant work is performed, and the design documents can be properly reviewed and approved before proceeding, which is a fundamental requirement of ISO 13485 and FDA 21 CFR Part 820. This action also protects the project from cascading defects that would be far more costly to fix later.

A project status report is a communication tool that provides stakeholders with a snapshot of project progress. 'Accomplishments since last report' is a standard section that summarizes completed tasks and achieved milestones, allowing stakeholders to see what has been delivered since the previous update. This aligns with the PMBOK Guide's guidance on performance reporting, which focuses on work performance data and information.

Gold plating is adding extra features beyond specified requirements. Scope creep is uncontrolled changes to scope, but gold plating is specifically adding extras without approval.

The project charter is the document that formally authorizes the project and assigns the project manager.

The work breakdown structure is the primary tool for ensuring all work is identified and organized.

Analogous estimation uses historical data from similar projects, adjusted for differences.

The project manager should first reestimate the remaining work based on the actual velocity (30% lower than planned) and then adjust the release plan accordingly. This aligns with agile principles of data-driven planning and transparency, addressing the root cause (unforeseen technical debt) by incorporating the team's actual capacity into future sprints.

The Gantt chart is the correct tool because it visually displays task dependencies, durations, and the critical path. By reviewing the Gantt chart, the project manager can immediately see which tasks are on the critical path and how the delayed deliverable's dependency affects the overall project timeline, enabling an accurate impact assessment before updating the schedule.

The stakeholder list is a foundational component of the stakeholder engagement plan because it identifies all individuals, groups, or organizations that may be affected by or have an influence on the project. Without a complete and accurate stakeholder list, the project manager cannot effectively tailor engagement strategies or communication requirements. This list typically includes names, roles, influence levels, and interest levels, which directly inform the subsequent planning activities.

The project charter is a high-level document that authorizes the project and provides the project manager with the authority to apply organizational resources. It must include the business case and a high-level project description to justify the project and define its scope at a strategic level, as specified in the PMBOK Guide.

The WBS process starts with identifying major deliverables, decomposing them, assigning codes, verifying completeness, and documenting details.

The project manager should perform a trade-off analysis and present options to the sponsor because no single option clearly meets all constraints (budget, schedule, quality, and business criticality) without further evaluation. A trade-off analysis quantifies the impact of each alternative on scope, cost, time, and risk, enabling an informed decision aligned with organizational priorities. This aligns with the PMBOK process of performing integrated change control and ensures the sponsor understands the implications before committing resources.

Analogous estimation relies on historical data from similar projects.

Story points are a relative measure of effort; the exact values are less important than the relative comparison. Planning poker facilitates consensus.

After submitting a change request, the project manager should communicate the potential impact to stakeholders to manage expectations. Updating the risk register is important but not the immediate next step; fast tracking and requesting resources may be considered after approval.

Risk priority is determined by the product of probability and impact (P × I). For R1, probability is 0.8 and impact is 5, yielding a risk score of 4.0, which is the highest among all risks in the register. This makes R1 the highest priority risk.

Following the change control process, the first step is to submit a formal change request, which will then be evaluated by the change control board.

Net Present Value (NPV) is the sum of present values of future cash flows. A higher NPV indicates greater profitability. Payback period is secondary.

If acceptance criteria are not met, the project manager should document the issue and initiate the change control process to address the discrepancy.

The Pareto principle states that roughly 80% of effects come from 20% of causes, used to prioritize issues.

The lessons learned register is the correct document for capturing knowledge gained during a project to benefit future projects. It systematically records what went well, what went wrong, and recommendations for improvement, directly supporting organizational process assets. The project manager uses this register to document insights that can be applied to subsequent projects, aligning with PMI's knowledge management practices.

Hypervisor memory overcommitment allows a hypervisor to allocate more virtual machine (VM) memory to VMs than the physical RAM available on the host, relying on the fact that VMs rarely use their full allocated memory simultaneously. This directly improves resource utilization by enabling higher VM density per physical host, which is the core inefficiency in resource pooling. Technologies like VMware ESXi's transparent page sharing or KSM (Kernel Same-page Merging) further optimize this by deduplicating identical memory pages.

Resource leveling is a technique to address resource overallocation by delaying tasks within their float.

The project charter is the document that formally authorizes the project and defines high-level information such as objectives, key stakeholders, high-level requirements, and the initial budget. This aligns with the PMBOK Guide definition, where the charter provides the project manager with the authority to apply organizational resources to project activities.

Predictive (waterfall) methodology is suitable when requirements are stable and well-defined, as it follows sequential phases with fixed scope.

A Gantt chart is a bar chart that displays project tasks against a calendar, showing start and end dates, dependencies, and progress. This matches the description in the question, making option B correct.

A CPI of 0.8 means the project is earning only $0.80 for every $1.00 spent, indicating it is over budget. An SPI of 0.9 means the project is progressing at 90% of the planned rate, indicating it is behind schedule. Therefore, the project is both over budget and behind schedule, making option D correct.

A project is defined by the creation of a unique product, service, or result. This uniqueness distinguishes a project from routine operations, as the output is not a repeat of a previous effort. The PMBOK Guide and the PK0-005 exam emphasize that uniqueness is a core characteristic of any project.

A Storage Area Network (SAN) is a dedicated, high-speed network that provides block-level storage access to servers. For a new software deployment, the project manager must ensure that the SAN has sufficient capacity, IOPS, and connectivity to support the application's storage requirements, making it a critical infrastructure component.

Mandatory dependencies, also known as hard logic, are inherent in the nature of the work and cannot be changed.

In project management, any change that impacts the budget must follow the formal change control process. The project manager should submit the change request to the change control board (CCB) for evaluation and approval, as the CCB has the authority to approve or reject changes that affect cost, scope, or schedule. This ensures that all impacts are assessed and that the project remains aligned with its baseline.

A WBS decomposes the project scope into manageable work packages, forming the basis for estimating, scheduling, and controlling work.

Escalation procedures are a required element of a communication plan because they define the structured path for raising issues, risks, or decisions that cannot be resolved at the current level. Without documented escalation procedures, project communications lack a clear authority chain, leading to delays and misalignment. This ensures that critical information reaches the appropriate decision-maker efficiently.

Analogous estimation uses historical data from similar projects to estimate costs. It is often used when limited information is available about the current project.

The first step in any project selection decision, especially with constrained resources, is to conduct a feasibility study. This study assesses whether the firm has the necessary resource availability (e.g., the senior developer is occupied for four months) and identifies risks (e.g., overextension) before committing to the fixed-price, six-month deadline. Without this analysis, the owner cannot make an informed decision about hiring, negotiating, or accepting the project.

The Work Breakdown Structure (WBS) is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team. It organizes and defines the total scope of the project, with each level providing more detail.

When an issue cannot be resolved at the project manager's level, it should be escalated to higher management or the appropriate authority.

A version control system like Git or SharePoint provides change tracking, branching, and merge conflict resolution, which prevents accidental overwrites by maintaining a complete history of file changes. Unlike a shared network drive, these tools allow multiple users to work on the same document simultaneously without losing data, as changes are committed and reconciled systematically.