CompTIA Project+ PK0-005 (PK0-005) — Questions 301–375

The project has a negative NPV (-$10,000) and an IRR (4%) that is lower than the company's required rate of return (6%). Both of these financial criteria indicate the project will destroy value rather than create it. Therefore, the project manager should recommend rejecting the project based on standard capital budgeting principles.

Scope and cost are classic project constraints (triple constraint). Team morale and customer satisfaction are not typically considered constraints in the traditional sense.

The root cause is that the MX records in DNS still point to the old on-premises mail server, so sending mail servers cannot route messages to the new cloud service. Updating the MX records to point to the new service and waiting for DNS propagation (typically 1–48 hours depending on TTL) is the correct first step because it restores proper email routing at the DNS level. No server-side errors exist, so the issue is purely a DNS configuration problem.

Fast-tracking and crashing are the two primary schedule compression techniques.

Mitigation involves reducing the probability or impact of a risk to an acceptable level.

The Agile Manifesto prioritizes customer collaboration over contract negotiation, meaning the project team works closely with the customer to refine requirements and deliver value iteratively. In an agile project with daily stand-ups and iterative development, this principle ensures continuous feedback and adaptation rather than rigid adherence to a contract.

Common risk identification techniques include brainstorming, Delphi technique, SWOT analysis, and assumptions analysis.

The scope statement is the document that defines the project scope, including deliverables, boundaries, and acceptance criteria. The WBS is derived from the scope statement, and the charter provides high-level scope.

Formal acceptance is documented, often through a sign-off, to confirm that deliverables meet requirements and the project is complete.

The Work Breakdown Structure (WBS) is the correct document because it provides a hierarchical decomposition of the total scope of work into manageable work packages. Each work package represents a deliverable or task that can be assigned, estimated, and tracked, making it the definitive source for task assignment details.

The stakeholder register is an output of the project initiation phase because it identifies all individuals or organizations impacted by the project and documents their interests, influence, and expectations. This register is created during initiation to ensure stakeholder engagement strategies are defined early, aligning with PMI's process of identifying stakeholders as part of the Initiating process group.

Fast-tracking overlaps sequential activities, which increases risk but may compress schedule.

The WBS is a hierarchical decomposition of the total scope into work packages, forming the scope baseline.

In a matrix structure, authority is shared between functional and project managers; the project manager typically has limited authority compared to a projectized organization.

During closure, obtaining formal acceptance from the sponsor and archiving project documents are key activities. Releasing resources and contract closure are also part of closure, but the question asks for two. The correct answers are formal acceptance and archiving documents.

PMI defines a project as 'a temporary endeavor undertaken to create a unique product, service, or result,' and progressive elaboration is a key characteristic where details are refined through iterative cycles as more information becomes available. This means the project scope and deliverables are developed in successive steps, not fully defined upfront, which aligns with the adaptive planning approach in project management.

Total float is calculated as Late Start minus Early Start (or Late Finish minus Early Finish). Here, Late Start (10) minus Early Start (5) equals 5 days. This represents the amount of time the activity can be delayed without affecting the project's overall completion date.

SPI = EV / PV = 40,000 / 50,000 = 0.8. An SPI less than 1 indicates the project is behind schedule.

Cost-benefit analysis (A) directly compares the total expected costs against the total expected benefits of a project, quantifying the net financial return. Payback period (B) calculates the time required to recoup the initial investment, which is a straightforward measure of financial return. Both methods are explicitly used to evaluate the monetary profitability of IT infrastructure projects.

The correct order for initiating a project is: create the project charter, identify stakeholders, obtain project charter approval, and then hold the kick-off meeting. Scope definition occurs during the planning phase, not initiation. Option A lists these initiation steps in the proper sequence without including any extraneous scope-definition activities.

Setting up a VPN connection with two-factor authentication is the best practice because it creates an encrypted tunnel over the internet, ensuring data confidentiality and integrity, while two-factor authentication adds an extra layer of security beyond just a password. This approach allows the vendor to access only the internal network resources necessary for installation and configuration, without exposing the entire network to unauthenticated or unencrypted access.

The project charter authorizes the project and assigns the project manager.

Communication starts with identifying stakeholders, analyzing, planning, distributing, and adjusting based on feedback.

The WBS, risk register, and schedule baseline are all created during planning.

Planning poker is a consensus-based estimation technique that uses story points to achieve team agreement on effort.

A Request for Proposal (RFP) is used to solicit proposals from vendors.

The risk management plan describes how risk management will be performed, while the risk register captures the actual risks.

EMV = Probability × Impact = 0.20 × 0.10 = 0.02, or 2% of the project cost.

The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team. It organizes and defines the total scope, with work packages at the lowest level representing deliverables that can be assigned, estimated, and managed.

The Cost Performance Index (CPI) is calculated as EV/AC = $80,000/$90,000 = 0.89, indicating cost overrun. The Schedule Performance Index (SPI) is EV/PV = $80,000/$100,000 = 0.80, indicating schedule delay. Option B correctly matches these values.

In a strong matrix, the PM has high authority, often more than functional managers, and controls project resources.

In project management, when a change request impacts scope, cost, or schedule, the project manager must follow the formal change control process. The first action is to submit the change request to the change control board (CCB) for review and approval, as the project manager does not have unilateral authority to approve or reject changes that affect the project baseline. This ensures proper governance and stakeholder alignment.

After the project charter is approved, the next step is to develop the project management plan. This plan defines how the project is executed, monitored, controlled, and closed, and it integrates all subsidiary plans (e.g., scope, schedule, cost). The PMBOK Guide and the PK0-005 exam follow the sequence: charter approval → develop project management plan → then detailed planning activities like risk assessment, budget determination, and WBS creation.

The project sponsor is the executive champion who provides resources and supports the project.

The exhibit shows that the connection string in the application configuration explicitly references the 'SalesDB' database and uses the 'app_user' account. The error message indicates a login failure for user 'app_user', which in SQL Server typically means the login succeeded at the server level but the user lacks a mapped database user or the CONNECT permission on the specified database. Since the database name and server are correctly specified, the most likely cause is that 'app_user' does not have permission to access 'SalesDB'.

Risk identification and planning occur during the planning phase.

The scope statement documents the project's scope including deliverables, acceptance criteria, exclusions, assumptions, and constraints.

The final project report provides the basis for the sponsor or customer to formally accept the project deliverables.

A burndown chart shows remaining work over time in a sprint, making it easy to spot deviations from the plan.

Once an issue is added to the issue log, the next step is to assign an owner and a target resolution date. This ensures accountability and provides a clear deadline for resolving the problem, which is essential for tracking progress and minimizing further impact on the project schedule.

Closing activities include obtaining formal acceptance from the sponsor and archiving project documents. Releasing resources and lessons learned are also part of closing, but the question asks for exactly two.

Low power, high interest stakeholders should be kept informed, so regular email updates are appropriate.

The correct matches are: Project Charter (authorization), Stakeholder Register (stakeholders), and Lessons Learned (knowledge). Common confusions involve swapping definitions of Project Management Plan and Risk Register.

The triple constraint is scope, time, and cost. Quality is sometimes added as a fourth constraint.

The most likely cause of the issue is that the actual finish dates for completed tasks (like Task 3) have not been entered in Microsoft Project. Without actual finish dates, the scheduling engine cannot calculate the successor task's start date, even if dependencies are correctly set. Recalculating the schedule after verifying and entering actual dates forces the tool to update the forward pass and reflect the true project status.

The 100% rule states that the WBS includes all work defined by the scope and that the sum of lower-level work equals the total work at higher levels.

Hybrid combines predictive planning for fixed elements (like deadline) with agile iterations for evolving requirements.

The project management plan integrates all subsidiary plans for managing the project.

In a hybrid project combining waterfall planning with iterative execution, the key challenge is balancing scope changes (which are natural in iterative cycles) with baseline control (which is rigidly defined in waterfall planning). This tension requires careful change management to prevent scope creep while still allowing adaptive adjustments, making option A correct.

Redundant network paths ensure that if one link or switch fails, traffic can immediately fail over to an alternate path, providing high availability. They also reduce latency by enabling load balancing across multiple links, which is critical for real-time applications. This directly addresses the requirement for both high availability and low latency in a data center build.

A project is temporary and creates a unique product, service, or result. Ongoing operations and repetitive tasks are not project characteristics.

The project charter is the document that formally authorizes the project and defines high-level success criteria, including measurable project objectives and key stakeholder expectations. According to the PMBOK Guide, the project charter is created during the Initiating process group and must contain the business case, high-level risks, and the criteria that will be used to determine whether the project is successful. Without these criteria defined in the charter, there is no agreed-upon baseline for evaluating project performance or closure.

Documenting the change and updating the change log is performed when the change request is first submitted and logged. This is the 'Change Request Documentation and Logging' step of integrated change control, which occurs prior to CCB review and approval.

The project manager must follow the formal change control process when the client requests work outside the signed scope baseline. Since the defects are not in the original scope, the only way to proceed legitimately is to submit a change request to modify the scope baseline, which will trigger a review of cost, schedule, and resource impacts. This aligns with PMI's integrated change control and ensures the project does not proceed without proper authorization, especially given the exhausted budget and lack of schedule buffer.

Quantitative risk analysis techniques include expected monetary value (EMV), sensitivity analysis, and Monte Carlo simulation. Probability/impact matrix is qualitative, and SWOT analysis is a qualitative technique.

Reviewing historical data and lessons learned from similar projects (Option A) directly addresses the root cause of inaccurate estimates by leveraging empirical evidence from past work. This aligns with the PMI's iterative estimation approach, where actual performance data (e.g., velocity from previous sprints) is used to calibrate future estimates, improving accuracy over time. In software development, this is analogous to using historical cycle times or story point completion rates to refine planning poker sessions.

Addressing performance issues in a private, respectful manner aligns with project management best practices for maintaining team morale while ensuring accountability. The project manager should first gather specific data on missed deadlines and quality metrics, then schedule a one-on-one meeting to discuss root causes and collaboratively develop an improvement plan. This approach preserves trust and avoids public embarrassment, which could further demotivate the team member.

Monte Carlo simulation uses repeated random sampling to model the probability of different outcomes, commonly used for schedule and cost risk analysis.

According to PMI best practices, after the project charter is approved, the next step is to develop the project management plan. This plan defines how the project will be executed, monitored, and controlled, and it serves as the baseline for all subsequent planning activities, including scope, schedule, cost, risk, and quality. The project manager must create this comprehensive plan before building the team or creating detailed deliverables like the WBS.

Fast-tracking involves performing tasks in parallel that were originally planned sequentially, which increases risk but can compress the schedule.

The correct matches are: Avoid - eliminate threat; Mitigate - reduce probability/impact; Transfer - shift to third party; Accept - no proactive action. Common confusions include confusing Avoid with Mitigate and Transfer with Avoid.

The risk with the highest risk score (0.30) is R2 (Staff turnover). Risk score is typically used to prioritize risks for response planning.

SWOT stands for Strengths, Weaknesses, Opportunities, and Threats. These four categories are examined. Assumptions and constraints are not part of SWOT; they are elements of the scope statement.

Scope creep is best prevented by implementing a formal change control process that requires all changes to be reviewed and approved before integration. This ensures that every additional feature is evaluated for impact on scope, schedule, budget, and quality, aligning with the project management plan and preventing uncontrolled expansion of project deliverables.

The critical path is the longest path through the project network diagram, determining the shortest possible project duration. By summing the durations of all activities on the critical path (e.g., A→C→E→G→I), the total duration is 50 days. This is calculated by adding the individual task durations along the path with zero total float.

According to the integrated change control process, after evaluating the impact, the change request should be submitted to the change control board for review and decision. The project manager does not approve changes alone.

The project manager has identified a risk (vendor may not deliver on time) and decided to document it and monitor it without taking any proactive action. This is the definition of an 'Accept' risk response, where the risk is acknowledged and a contingency plan may be in place, but no active steps are taken to reduce the probability or impact beforehand. In the context of the PK0-005 exam, this is a passive acceptance strategy, often used when the cost of mitigation exceeds the potential impact or when the risk is low enough to be tolerated.

CPI > 1 means under budget; SPI < 1 means behind schedule.

In the Norming stage, team members start to resolve differences, develop consensus, and establish norms and roles.

Cost Performance Index (CPI) and Cost Variance (CV) are metrics that measure cost efficiency. CPI = EV/AC, CV = EV - AC.