Explanation:

After a project ends, the project manager must:

👥 Formally release project resources

This includes:
Reassigning team members to new work
Closing project labor codes
Updating resource allocations
Notifying functional managers

Since the team member is still charging time to the old project and cannot work on new ones, it means:
➡️ The resource release process was not completed.

❌ Why the Other Options Are Wrong

A. Remove the team member's access
Refers to system/security access
❌ Not related to time charging or resource allocation

C. Collect the stakeholders' feedback
Part of lessons learned
❌ Does not affect staffing or billing codes

D. Have the closeout report approved
Administrative closure document
❌ Not directly tied to team member reassignment

📚 References
Aligned with CompTIA Project+ (PK0-005) Objectives:
Project closure activities
Resource management
Administrative closure procedures

Also consistent with:
PMI PMBOK® Guide — Close Project or Phase

Explanation:

The scenario describes a project that was completed weeks ago, yet the quarterly financial report still shows losses from the project. This indicates that costs are still being incurred and charged against the project budget.

Why C is correct
Releasing resources includes the administrative step of closing out the project's financial accounts and ensuring that team members, contractors, and equipment are no longer charging time or costs to the project. If the project is complete but resources are still charging time, the budget will continue to show expenses (appearing as losses). The PM needs to formally release all resources and close the financial accounts to stop any further charges.

Why A is incorrect
Removing access (to systems, buildings, or data) is a security and closure step, but it does not address the financial charges. A team member could have their access removed but still have their timesheet defaulting to the old project code.

Why B is incorrect
Completing project sign-off is a formal acceptance of the deliverables by the customer or sponsor. This should have happened when the project was "completed successfully several weeks ago." Doing it now does not stop the ongoing financial charges.

Why D is incorrect
Outlining lessons learned is an important closure activity for organizational improvement, but it has no impact on the project's financial accounts or the quarterly loss report.

References
CompTIA Project+ PK0-005 Objective 4.1: Explain the importance of project closure and lessons learned. This objective includes the activity of financial closure (reconciling budgets, closing accounts) and releasing resources to ensure no further costs are incurred against the project.

Administrative Closure: A key part of administrative closure is ensuring that all project accounts are closed and that no further time or expenses can be charged to the project. This prevents exactly the situation described in the question.

Explanation:

To find the total amount that should be budgeted, we use the Expected Monetary Value (EMV) and Expected Duration formulas. This is a quantitative risk analysis technique where you multiply the probability of a risk occurring by its impact.

1. Calculating the Budget (Cost)
Base Cost: $3,000
Risk Impact: $1,000
Probability: 20% (0.20)
Contingency (Risk EMV): $1,000 × 0.20 = $200
Total Budget: $3,000 + $200 = $3,200

2. Calculating the Schedule (Time)
Base Duration: 9 days
Risk Impact: 5 days
Probability: 20% (0.20)
Contingency (Time EMV): 5 days × 0.20 = 1 day
Total Duration: 9 days + 1 day = 10 days

In project management, you do not budget for the "worst-case scenario" ($4,000) or ignore the risk entirely ($3,000); instead, you budget the statistically expected value to create a realistic contingency reserve.

Explanation of Incorrect Answers

A. 9 days and $3,000
This only accounts for the base estimate and completely ignores the identified risk. This would lead to a budget shortfall if the requirements change.

C. 12 days and $3,800
These numbers do not align with any standard calculation based on the 20% probability provided in the scenario.

D. 14 days and $4,000
This represents the Worst-Case Scenario (Base + 100% of the risk impact). Budgeting for every risk as if it is 100% likely to happen would result in an overinflated, non-competitive budget that ties up company capital unnecessarily.

References
CompTIA Project+ (PK0-005) Exam Objectives: Domain 3.0 Project Risk and Change Management (3.2 Perform risk-response techniques – Risk calculation).
PMBOK® Guide: Section on Perform Quantitative Risk Analysis (Expected Monetary Value).

Explanation:

✅ Removing access: A critical task during the project closure phase is the administrative and technical offboarding of project personnel. This includes revoking physical and logical access to systems, data repositories, and facilities. If the project manager and security team had properly removed the contractor's credentials immediately upon the project's completion, the contractor would not have had the ability to log in and steal data.

Why the other options are incorrect

B. Closing contracts
While closing a contract is a legal requirement of the closure phase, it refers to the finalization of payments and terms. A contract can be "closed" on paper while the contractor still physically holds an active badge or login credentials if those weren't manually revoked.

C. Project sign-off
This is the formal acceptance of deliverables by the sponsor or client. It signifies that the project work is complete, but it does not inherently trigger the technical removal of user permissions.

D. Project evaluation
Also known as a "post-mortem" or lessons learned session, this is a meeting to discuss what went well and what didn't. It is a retrospective analysis that happens after the fact and has no preventative security function.

Explanation:

The stakeholders require delivery of multiple milestones with proper presentation of functionalities during the project. This is best achieved using Scrum, an Agile methodology that emphasizes iterative development, frequent delivery of working increments, and regular stakeholder reviews (via sprint reviews and demos).

A. Waterfall
Linear, sequential approach. Deliverables are only presented at the end, not suitable for multiple milestone presentations.

B. SDLC (Systems Development Life Cycle)
A general framework for software development, not a specific methodology for iterative milestone delivery.

C. XP (Extreme Programming)
Agile methodology focused on engineering practices (pair programming, test-driven development), but less centered on milestone-based stakeholder presentations.

D. Scrum
✅ Correct. Scrum organizes work into sprints, each delivering functional increments. Stakeholders can review progress at each sprint review, making it ideal for milestone-based delivery.

Reference
CompTIA Project+ PK0-005 Exam Objectives, Domain 2.0 (Project Life Cycle Phases) — Scrum is an Agile methodology that emphasizes iterative delivery, stakeholder engagement, and milestone-based functionality demonstrations.

Explanation:

A network issue affects connectivity between devices and systems across an organization’s infrastructure.

Option A describes:
🌐 Multiple users
🏢 A specific location (fourth floor)
❌ No access to servers and email services

This indicates a likely:
LAN outage
Switch/router failure
Network segment problem
It’s a classic internal network connectivity failure.

❌ Why the Other Options Are Wrong

B. Cell phones served by a specific telecom company are getting a "no service" message
📡 Telecom carrier issue
❌ External cellular service problem, not the organization’s network

C. A user cannot connect to Wi-Fi because of a wrong ID or password
🔐 Authentication issue
❌ User credential error, not network failure

D. A user is receiving an automatic reply message saying that an email address does not exist
📧 Email configuration/addressing issue
❌ Messaging system error, not network connectivity

📚 References
Aligned with CompTIA Project+ (PK0-005) Objectives:
IT infrastructure awareness
Incident identification
Technical issue categorization

Explanation:

The question presents a problem: a critical shipment is delayed by two months. The project manager must follow a logical sequence to handle this issue effectively.

Why B is correct
Before making any decisions or communicating changes, the project manager must first understand the impact of this delay. The PM needs to evaluate how the two-month delay affects the project baselines (schedule, cost, scope). Which tasks are dependent on these devices? Will this push the critical path? By how much? Are there cost implications (e.g., storage fees, penalties)? This impact assessment provides the data needed for all subsequent decisions.

Why A is incorrect
Holding the project is a potential decision, but it is premature. The PM needs to know if the project can continue with other work that is not dependent on the devices. If other tasks can proceed, the project should not be completely halted.

Why C is incorrect
Requesting another supplier is a potential corrective action, but it cannot be the first step. The PM needs to know if the two-month delay is critical enough to warrant finding a new supplier, and whether a new supplier can deliver any faster. This is determined during the impact assessment.

Why D is incorrect
Updating the project timeline is a premature action. The PM does not yet know the full impact. The delay might be absorbed by project float, or the team might be able to fast-track other activities to recover some of the lost time. A new end date should only be set after a full impact analysis and consideration of corrective actions.

References
CompTIA Project+ PK0-005 Objective 3.2: Given a scenario, apply the change control process. While this is an issue (vendor delay) rather than a change request, the logical process is the same: identify the problem, analyze the impact, then determine and implement a solution.

Issue Management: The standard process for handling an issue is: 1) Identify the issue, 2) Analyze/Assess the impact, 3) Develop options/solutions, 4) Take action, and 5) Monitor the result.

Explanation:

The project closing phase focuses on finalising all activities across all process groups to formally complete the project or a project phase. Key activities include:

✅ A. Lessons learned: Conducting a lessons learned session is a critical closing task. It involves documenting what went well and what didn't to help improve future projects and update organizational process assets.

✅ C. Removing resources: This involves the administrative task of releasing personnel, equipment, and materials. It ensures that resources are available for other organizational initiatives.

✅ G. Removing access: For security and compliance, the project manager must ensure all team members have their system, physical, and logical access revoked upon project completion.

Why the other options are incorrect

❌ B. Risk analysis: This is a core activity during the planning phase (initial identification) and the monitoring and controlling phase (ongoing assessment).

❌ D. Acquiring resources: This typically occurs during the planning or execution phases when the team is being built and work is being performed.

❌ E. Statement of work (SOW) sign-off: The SOW is typically created and signed off during the initiation or procurement stages to define the work requirements before the project or a contract begins.

❌ F. Stakeholder analysis: This is a key preparation activity performed during the initiation and planning phases to identify and understand the influence and interests of those involved.

Explanation:

The question specifies an IT infrastructure change being implemented in the production environment. Production environments are live systems that users rely on, so changes carry significant risk. The most important prerequisites are those that directly address the implementation process and risk mitigation.

Why A and C are correct

C. Deployment plan: This is the step-by-step guide for actually implementing the change. It details what will be done, in what order, by whom, and when. Without a clear deployment plan, the implementation would be chaotic and prone to errors.

A. Rollback plans: This is the contingency plan that outlines how to revert the system to its previous state if the deployment fails or causes unexpected issues. In a production environment, having a rollback plan is critical for minimizing downtime and ensuring business continuity. It is the primary risk mitigation strategy for the change.

Why B is incorrect
The Project Management Plan is the overarching document that guides the entire project. While important, it is too broad to be a specific prerequisite for a single infrastructure change. The deployment plan is the relevant subset of the project management plan for this activity.

Why D is incorrect
An Asset Management Plan deals with tracking and managing assets (hardware, software licenses) throughout their lifecycle. While relevant to IT in general, it is not a prerequisite for implementing a specific change request in production.

Why E is incorrect
The Communication Plan is important for notifying stakeholders about the change and potential downtime. However, for an IT infrastructure change, the deployment and rollback plans are more immediately critical to the technical success of the implementation. Communication supports the change but does not execute it.

Why F is incorrect
The Resource Management Plan outlines how resources (people, equipment) will be acquired and managed. While resources are needed to perform the change, the deployment plan specifies which resources are needed and what they will do. The resource plan itself is not a direct prerequisite for the change implementation.

References
CompTIA Project+ PK0-005 Objective 3.3: Explain the importance of change control in project management. This objective emphasizes that a change request, especially for production environments, should include both an implementation (deployment) plan and a back-out (rollback) plan.

Change Management Best Practices: Standard IT change management procedures require that any change to a production environment must have a detailed implementation plan and a tested rollback plan before it can be approved for execution.

Explanation:

The SOW (Statement of Work) is a narrative description of the work required for the project. It defines the specific deliverables, tasks, and boundaries of the project.

When the Change Control Board (CCB) approves a customer's request for changes to a product, they are essentially approving a change to the Project Scope. Because the SOW is the foundational document that outlines what is (and is not) included in the project, it must be updated first to reflect the new requirements.

Once the SOW is updated, it serves as the legal and operational basis for updating other downstream documents, such as the project schedule, budget, and WBS (Work Breakdown Structure). Failing to update the SOW first leads to "Scope Creep," where the team is doing work that isn't officially documented in the contract or agreement.

Explanation of Incorrect Answers

A. ROI (Return on Investment): While a major change might eventually impact the project's ROI, the ROI is a financial metric used for justification in the Business Case. You don't "change" the ROI first; you update the scope of work, and the resulting cost/benefit might be recalculated later.

B. KPI (Key Performance Indicator): KPIs are used to measure how well the project is performing against its goals (e.g., "95% uptime"). While a change might require new KPIs, the primary definition of the work (SOW) must be established before you can decide how to measure it.

C. RACI (Responsible, Accountable, Consulted, Informed): A RACI matrix defines roles and responsibilities. While you may need to update the RACI if new tasks are added, you first need to define those tasks in the SOW so you know what work needs to be assigned to which people.

References
CompTIA Project+ (PK0-005) Exam Objectives: Domain 3.0 Project Risk and Change Management (3.3 Explain the operational change control process – Updating project documents).
PMBOK® Guide: Section on Control Scope and Perform Integrated Change Control.