CompTIA Project+ PK0-005 (PK0-005) — Questions 676–750

The change log is updated to record the approval, implementation details, and closure of the change request, providing an audit trail. The project baseline (e.g., scope, schedule, cost) must be updated to reflect the approved change, ensuring all future work and variance analysis are measured against the revised baseline.

The typical project life cycle phases are initiating, planning, executing, monitoring and controlling, and closing. Executing follows planning.

A negative NPV means the project's costs exceed its benefits, indicating it is not financially viable.

Option A is correct because lessons learned documents are forward-looking artifacts that capture actionable insights to improve future project execution. Recommendations for future projects are a standard component, as they translate past experiences into specific guidance for planning, risk management, and process adjustments in subsequent initiatives.

The project charter is the formal document that authorizes the project's existence and provides the project manager with the authority to apply organizational resources to project activities. It is issued by the project sponsor or initiator and establishes a partnership between the performing and requesting organizations. Without a signed charter, the project manager lacks the official mandate to commit resources or make binding decisions.

The critical path is Path 1 (14 days). Task D is on Path 2 with a duration of 13 days. Total float = critical path duration - non-critical path duration = 14 - 13 = 1 day.

In a weak matrix, the project manager has limited authority and resources are controlled by functional managers. Strong matrix gives PM more authority; balanced is in between; functional is not a matrix.

Approved changes must be reflected in the project management plan and baselines (scope, schedule, cost) to maintain accurate control.

Option C is correct because the waterfall methodology enforces distinct phase gates (e.g., requirements, design, implementation, testing, deployment) where each phase must be fully completed and formally reviewed before the next phase begins. This gate-based approach ensures that deliverables are approved at each stage, preventing overlapping or concurrent work.

A risk is an uncertain event that may or may not occur. An issue is a current problem that has already occurred.

Option C is correct because separating the web server and database onto two VMs eliminates resource contention between IIS and SQL Server Express, which is the root cause of the CPU and I/O spikes. Replacing the HDD with SSDs reduces disk I/O latency from 50 ms to under 1 ms, directly addressing the performance bottleneck. This solution is cost-effective and can be implemented within two weeks using existing on-premises hardware, without requiring cloud migration or VPN setup.

Adding extra resources to the critical path to reduce the impact of a potential two-week delay is a classic example of the Mitigate risk response strategy. Mitigation aims to reduce the probability or impact of a risk, and here the project manager is proactively reducing the impact by increasing capacity on the critical path. This is not accepting the risk, avoiding it, or transferring it to a third party.

CPI = EV / AC = $120,000 / $110,000 = 1.09.

Lessons learned capture knowledge and experience from the project to improve future projects. While they may inform the final report, their main value is for continuous improvement.

The RACI matrix (Responsible, Accountable, Consulted, Informed) is the definitive project document for clarifying roles and responsibilities for specific tasks or deliverables. When team members disagree on task ownership, the project manager should consult the RACI matrix to identify who is designated as 'Responsible' for performing the work, thereby resolving the ambiguity and preventing further delays.

A milestone chart displays key events (milestones) along a timeline. Gantt charts show all tasks, network diagrams show dependencies, and burndown charts track remaining work over time.

The error 'connection refused' indicates that the application's TCP SYN packet to the database server was met with a TCP RST or no response, which typically occurs when a firewall drops or rejects the traffic. Since the database server is on a separate subnet, a network-layer access control list (ACL) or firewall rule is the most common cause of blocking the specific database port (e.g., 3306 for MySQL, 5432 for PostgreSQL, 1433 for SQL Server). This prevents the three-way handshake from completing, resulting in the connection refused error.

Option C is correct because introducing a demonstration after the coding phase constitutes a scope change that could impact the project schedule, resources, and testing timeline. The project manager must follow formal change control procedures by submitting a change request to the change control board (CCB) for approval, ensuring that all impacts are assessed and authorized before proceeding.

A cause-and-effect diagram (also known as fishbone or Ishikawa) is used to identify root causes by organizing potential causes into categories.

Fast-tracking involves overlapping sequential activities to compress the schedule, but it increases risk of rework.

Analogous estimation uses historical data from similar projects to estimate current project costs, adjusting for differences.

Change control applies to any change that affects the project baselines, including scope, schedule, cost, and quality.

The change log records all change requests and their disposition.

In RACI, 'Responsible' does the work (security lead), 'Accountable' answers for the work (project manager), and 'Informed' receives updates (compliance officer).

A network diagram (e.g., activity-on-node or PERT chart) is the best complement to a Gantt chart because it explicitly maps task dependencies (finish-to-start, start-to-start, etc.) and calculates the critical path using forward and backward pass methods. While a Gantt chart shows progress over time, it does not inherently display the logical relationships between tasks or the float/slack values needed to identify the critical path.

A retention policy is essential because it defines how long backup copies are kept, ensuring compliance with legal or operational requirements and enabling recovery to specific points in time. Without a retention policy, backups may be deleted too early (causing data loss) or retained indefinitely (wasting storage). It directly governs the lifecycle of backup data, which is a core component of any comprehensive backup strategy.

Obtaining formal acceptance of deliverables is a key responsibility during project closure because it ensures that the customer or stakeholder has signed off that all project requirements have been met. This formal acceptance triggers the transition to operations and closes the contractual or service obligations. Without it, the project cannot be considered officially complete, and any remaining disputes would remain unresolved.

The risk register should include risk ID, description, owner, probability, impact, risk score, response strategy, residual risk, and trigger. These are standard fields.

Risk R4 has the highest risk score (Probability 0.8 × Impact 5 = 4.0), making it the most critical risk in the register. The project manager should prioritize risks with the highest product of probability and impact for immediate response, as this represents the greatest potential threat to project objectives.

When a change request is submitted, an impact analysis is performed to evaluate the effects on scope, schedule, cost, and quality. This analysis is then presented to the Change Control Board for decision.

In a weak matrix, the functional manager has more authority than the project manager.

An issue is a current problem that has occurred, as opposed to a risk which is a future uncertain event. Issues are documented in the issue log.

Recording meetings and sharing minutes ensures that all team members, regardless of time zone, have access to the same information asynchronously. This approach compensates for the lack of real-time attendance and provides a permanent reference that reduces misunderstandings. It is the most effective method for maintaining clear communication in a distributed, multi-timezone environment.

The most likely cause is a missing route on the database server's routing table. Even with correct firewall rules and an active database service, the database server may not have a return route to the application server's subnet, causing packets to be dropped. This is a common Layer 3 issue where the destination server can receive traffic but cannot reply because it lacks a route back to the source.

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

Option B is correct because a PMO is justified when an organization faces inconsistent processes and low project success rates across multiple projects. The PMO provides standardization, governance, and best practices to improve consistency and success rates, directly addressing the root cause of poor performance.

CPI = EV/AC = 50,000/60,000 = 0.83. A CPI less than 1 indicates the project is over budget.

Option B is correct because both the Cost Performance Index (CPI) of 0.92 and the Schedule Performance Index (SPI) of 0.80 are less than 1.0, indicating the project is over budget and behind schedule. A CPI below 1 means the project is earning less value for each dollar spent (cost overrun), while an SPI below 1 means the project is progressing slower than planned (schedule delay). This is the only option where both indices are under 1.0, which is a common realistic scenario in troubled projects.

Work packages are the lowest level of the WBS. Here, 1.1.2 (Design) is a leaf node, representing a work package. 1.0 is the top level, 1.1 is a higher level, and 1.3 is a control account, not a work package.

The 100% rule states that the WBS must include 100% of the work defined by the project scope and capture all deliverables, both internal and external. The sum of the work at the lower levels must equal 100% of the work at the parent level.

The 100% rule in WBS creation requires that the WBS captures all deliverables and work defined in the project scope, and nothing outside that scope. Decomposition is the process of breaking down work, but the 100% rule specifically ensures completeness.

In agile methodology, the sprint is a time-boxed iteration with a fixed scope of work committed by the team. When the product owner frequently changes priorities mid-sprint, it disrupts the team's focus and capacity, making it highly likely that the original sprint goals will not be completed. This directly leads to missed sprint goals, as the team cannot deliver the planned work within the sprint's fixed duration.

Gold plating is when the team adds extra features beyond what was required, which can increase cost and risk without customer approval.

The project charter is the document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It is issued by a sponsor or initiator external to the project and establishes a partnership between the performing organization and the requesting organization. Without a signed charter, the project manager lacks the official mandate to allocate budget, personnel, or equipment.

The communication plan outlines the communication management approach, including stakeholders, information needs, and methods.

The Delphi technique uses anonymous rounds of questionnaires with a facilitator to achieve consensus among experts. It avoids group bias.

CPI = EV/AC = 50000/55000 ≈ 0.91. A CPI less than 1 indicates the project is over budget.

The product backlog is a prioritized list of all features, enhancements, and fixes needed for the product.

Task C has a negative float of -2 days, indicating that it is behind schedule by 2 days. Since Task C is on the critical path (float = 0 in the original schedule), any delay directly extends the project completion date. The project is therefore behind schedule due to Task C.

Option B is correct because the root cause of the delays is the junior members' lack of skills, leading to errors that require rework. Providing targeted training and mentoring directly addresses this skill gap, enabling junior members to produce higher-quality work independently, which reduces rework and improves overall efficiency. This approach aligns with the project management principle of investing in team development to enhance performance under tight deadlines.

The project charter includes high-level scope, which defines the boundaries of the project. Assumptions and constraints are also included, but the high-level scope specifically sets the boundaries.

On a critical path, all activities have zero total float.

PERT expected duration = (Optimistic + 4*Most Likely + Pessimistic) / 6 = (5 + 4*8 + 13)/6 = (5+32+13)/6 = 50/6 ≈ 8.33 days.

Option C is correct because implementing configuration management directly reduces the likelihood of a server misconfiguration, which is the root cause of the potential data breach. This is a classic risk mitigation strategy that proactively addresses the risk's probability by enforcing standardized, auditable server configurations (e.g., using tools like Ansible or Puppet with CIS benchmarks).

Activity A finishes at day 3. Activity B starts at day 4 (FS+1? Actually FS means B starts after A finishes, so B starts day 4). With SS+2 lag, C can start 2 days after B starts, i.e., day 6.

The project charter is the formal authorization document that establishes the project and provides the project manager with the authority to apply organizational resources. It must include the high-level scope to define the boundaries of the project without going into detailed decomposition, which is why option A is correct.

A trigger (or risk trigger) is an event or condition that indicates a risk is imminent or about to occur.

Functional and matrix organizational structures are two of the three classic organizational structures (functional, matrix, and projectized) that directly influence how projects are managed, including authority levels, resource allocation, and communication paths. In a functional structure, team members report to a functional manager, and the project manager has limited authority. In a matrix structure, authority is shared between functional and project managers, creating a dual-reporting system that requires careful coordination.

An external dependency is one outside the project's control.

The parallel deployment strategy is recommended because it allows the old and new ERP systems to run concurrently during cutover, enabling users to validate the new system while maintaining operations on the legacy system. This minimizes downtime by providing a fallback option if issues arise, ensuring business continuity during the migration.

NPV is a primary indicator of profitability. Higher NPV is better, regardless of payback period.

A project is defined by its temporary nature and unique outcome. Option B is correct because a project creates a unique product, service, or result, distinguishing it from ongoing operations. This uniqueness is a core characteristic per the PMBOK Guide, which defines a project as a temporary endeavor undertaken to create a unique deliverable.

A Pareto chart is based on the 80/20 rule and prioritizes the most significant factors.

The correct first step is to update the risk register and assess the impact because the departure of a key developer is a known risk that should have been identified during planning. By documenting the event and evaluating its effect on the schedule, the project manager can make informed decisions about mitigation strategies. This aligns with the PMBOK risk management process, where risk response planning follows risk assessment.

Archiving project documents and lessons learned (Option A) is a key closing-phase activity because it preserves project knowledge for future reference and organizational process assets. Formal acceptance of deliverables from stakeholders (Option C) ensures that all project outputs have been reviewed and approved, formally closing the project scope. Both activities are explicitly part of the closing process group in the CompTIA PK0-005 exam objectives.

Project status reports are designed to provide a snapshot of progress and health. 'Accomplishments since last report' (B) is a standard section that tracks completed milestones and tasks, enabling stakeholders to see forward momentum. 'Budget spent to date' (E) is a core financial metric that compares actual costs against the planned budget, which is essential for cost control and forecasting.

The Recovery Time Objective (RTO) defines the maximum acceptable downtime after a disaster, directly dictating the speed of failover to the secondary data center. In a replication-based DR plan, the RTO determines whether synchronous or asynchronous replication is used and how quickly systems must be brought online. The project manager must prioritize this metric to align recovery speed with business continuity requirements.

Gold plating is when the team adds extra features beyond requirements without approval. Scope creep is uncontrolled changes to scope; change control is the process to manage changes; value engineering improves value without extra cost.