CompTIA Project+ PK0-005 (PK0-005) — Questions 1–75

The project manager plans, executes, and controls the project, manages the team, and communicates with stakeholders. The sponsor provides resources, and the steering committee provides governance.

Crash cost per day = (crash cost - normal cost) / (normal duration - crash duration). Assuming normal cost is zero incremental, crash cost per day = $3,000 / (10-7) = $1,000 per day.

The communication management plan defines how communications are handled; the stakeholder register identifies stakeholders and their needs; the issue log tracks current problems. The risk register lists risks, not communication issues. The WBS is for scope.

A burndown chart shows remaining work (e.g., story points) over time in a sprint, helping visualize whether the team is on track.

Executing is one of the five standard project management process groups defined by the Project Management Institute (PMI) in the PMBOK Guide. This process group involves coordinating people and resources to carry out the project management plan, producing the deliverables of the project. It is a core phase where the planned work is actually performed.

If exit criteria are not met, the project is typically required to complete the remaining work and then be re-reviewed before proceeding to the next phase.

Crashing adds resources to critical path tasks, typically increasing cost.

In a predictive (waterfall) life cycle, the project scope is defined and baselined early in the project, and changes are tightly controlled through a formal change control process. This approach is suitable for software development projects where requirements are well-understood and unlikely to change significantly, such as when building a system with fixed regulatory or contractual specifications.

The project sponsor is the executive-level stakeholder who provides the financial resources, high-level support, and organizational authority necessary for project initiation and success. In the PK0-005 framework, the sponsor champions the project, secures budget approval, and removes escalated obstacles, distinct from the project manager who handles day-to-day execution.

The control schedule process focuses on managing changes to the schedule baseline. Since the project manager has exhausted the management reserve and the delay is due to unforeseen compatibility issues, the only formal way to extend the schedule is through a change request that updates the schedule baseline. Option D directly aligns with this process by formally documenting and approving the schedule extension.

In a Work Breakdown Structure (WBS), the highest level of decomposition is the top-level element that encompasses all deliverables. Option C (1.0) represents the entire project or major deliverable, which is the root of the hierarchy, while the other options are sub-elements at lower levels. This aligns with the PMBOK Guide's WBS principle that the highest level is the project itself or the first level of decomposition.

Scope creep refers to uncontrolled changes or continuous growth in a project's scope. This directly impacts the scope constraint, and typically affects cost and schedule as well. However, scope is the primary constraint impacted.

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

When a defect report indicates that a new requirement necessitates updating a configuration item (CI-103), the first step in the configuration management process is to submit a change request to the change control board (CCB). This ensures that any modification to a baselined CI is formally evaluated, approved, and tracked before implementation, preventing unauthorized changes that could destabilize the project.

A version control system (VCS) is specifically designed to track changes to files—such as requirements, design documents, and source code—by recording every modification with the author and timestamp. It ensures all team members can access the latest versions through branching, merging, and centralized or distributed repositories (e.g., Git, SVN). This directly meets the need for change logging and access control.

Newly identified risks are added to the risk register for assessment and response planning.

Escalate further, document in issue log, and involve stakeholders for resolution.

The procurement management plan includes documents related to procurement, such as SOW (scope of work) and contract terms. The other documents are not procurement-specific.

The project charter and stakeholder register are created during initiating. The WBS and risk register are planning outputs; the status report is from monitoring and controlling.

A Gantt chart is the correct project management tool because it visually maps project tasks along a horizontal timeline, with bars representing task duration and arrows or lines indicating dependencies between tasks. This allows project managers to see the sequence of work, identify critical paths, and track progress against scheduled dates, which is exactly what the question describes.

In a matrix organization, the project manager shares authority over resources with functional managers. The first step should be to negotiate directly with the functional manager to retain the key team member, as this aligns with the principle of collaborative conflict resolution and resource management. This approach preserves the relationship and allows for a mutually agreeable solution before escalating or making reactive adjustments.

The Close Project or Phase process formally completes the project or phase and produces the final product, service, or result transition as a key output. This output documents the handover of deliverables to the customer or operations, ensuring acceptance and closure. It is the definitive artifact that signals the end of project work.

The correct sequence for procurement management is Plan, Conduct, Select, Administer, and Close. This order ensures that procurement is well-defined before market engagement, vendors are evaluated after solicitation, contracts are managed after selection, and all activities are formally closed.

A proper WBS is deliverable-oriented, decomposed to manageable work packages, and follows the 100% rule.

The schedule baseline (B) is a component of the project management plan because it is an approved version of the schedule model that is used as a basis for comparison to actual results. The PMBOK Guide defines the project management plan as including baselines such as the schedule, cost, and scope baselines, which are used to measure project performance.

The scope management plan defines the process for managing scope changes, including how change requests are submitted, reviewed, and approved. Since the project manager needs to ensure proper review and approval of all changes, this is the correct document to reference. It outlines the specific roles, responsibilities, and procedures for scope change control, which directly addresses the issue of frequent scope changes.

It directly addresses the root cause: unauthorized scope changes. The burndown chart's steady increase indicates unapproved tasks inflating the sprint backlog. By holding a meeting with the product owner and team, you can review Jira's sprint backlog, remove unauthorized tasks, and reinforce Agile scope management—ensuring the product owner controls the backlog and the burndown chart accurately reflects progress.

CPI < 1 means over budget; SPI > 1 means ahead of schedule.

In a RACI matrix, 'Responsible' is the role that actually performs the work or task. This is the person or team who does the hands-on effort to complete the deliverable, such as configuring a router or writing code. The 'Responsible' role is distinct from 'Accountable,' who ultimately answers for the outcome.

The project manager should first discuss the issue with the team member to understand the root cause of the delays. This aligns with the PMI's principle of addressing performance issues through direct communication before taking corrective actions that affect the schedule or team composition. Only after understanding the reason (e.g., unclear requirements, resource constraints, or personal issues) should the PM consider schedule updates or escalation.

Cause-and-effect diagram (fishbone) helps identify root causes; Pareto chart applies 80/20 rule to prioritize; control chart monitors process variation. Scatter diagram shows relationships but not root cause; run chart shows trends over time.

Voice quality over VoIP is highly sensitive to latency, jitter, and packet loss. Switch QoS settings (e.g., 802.1p/DSCP marking, strict priority queuing) ensure that voice traffic is prioritized over data traffic, preventing delays and dropped packets that degrade call quality. Without proper QoS, even high-bandwidth links will suffer from poor Mean Opinion Scores (MOS).

Adding features without adjusting time or cost increases scope, leading to scope creep. This directly affects the scope constraint.

A burnup chart shows completed work over time and total work; a burndown chart shows remaining work. Both together give a complete picture.

In a control chart, 8 consecutive points on one side of the mean (a 'run' of 8) indicates a special cause variation, even if points are within control limits. This rule is a common test for special causes.

Implementing change control processes (A) is a best practice because IT infrastructure projects often involve complex, interdependent systems where unapproved changes can cause cascading failures, security vulnerabilities, or downtime. Formal change control ensures that all modifications are reviewed, tested, and documented before deployment, maintaining stability and compliance.

A feasibility study assesses whether the project is viable and worth doing.

The project manager must first assess the impact of the co-location provider's consistent delays and the two servers' hardware incompatibility before deciding on corrective actions. A risk assessment evaluates the probability and impact of these issues on the critical path to the December 31 deadline, enabling data-driven decisions rather than reactive measures. This aligns with the PMBOK risk management process, where identifying and analyzing risks precedes response planning.

In a functional structure, team members report to functional managers who control resources. Project managers have limited or no authority.

The project manager must balance the triple constraint (cost, schedule, scope) when an unplanned security vulnerability emerges. Escalating to the sponsor with a trade-off analysis allows informed decision-making, as the fixed budget and strict deadline mean any change requires stakeholder approval. This aligns with PMI's best practices for managing change requests in a constrained environment.

In a balanced matrix, the PM and functional manager share authority equally. Weak matrix has more functional authority, strong matrix has more PM authority.

The project manager should evaluate the impact on the triple constraint and follow the formal change control process to prevent scope creep.

NPV indicates long-term profitability; a high NPV is favorable. However, a long payback period increases risk of uncertainty. Both factors should be balanced.

Decomposition is the process of breaking down deliverables into smaller components for the WBS. Option D is correct. Rolling wave is for progressive elaboration; bottom-up and analogous are estimating techniques.

A Pareto chart is based on the 80/20 rule and is used to highlight the most significant factors causing defects.

The Responsibility Assignment Matrix (RAM) is the correct document because it explicitly maps project work packages or activities to team members, showing who is responsible, accountable, consulted, and informed (RACI). This directly resolves conflicts arising from unclear roles and responsibilities by providing a clear, documented assignment of duties.

The critical path has the longest duration and zero float. Any delay on the critical path delays the project.

Analogous estimation uses historical data from similar projects as a basis.

Payback period: Project A = $100,000/$30,000 = 3.33 years. Project B = $50,000/$20,000 = 2.5 years. Shorter payback is better, so Project B is selected.

The responsibility assignment matrix (RAM), often in the form of a RACI chart, explicitly maps each work package or task to the specific team members who are responsible, accountable, consulted, or informed. This directly answers the project manager's need to track which team members are assigned to each task in the software development project.

SharePoint provides centralized document storage with built-in version control, allowing team members to check in/out files, track changes, and revert to previous versions. This eliminates the confusion caused by multiple email attachments with different filenames and revisions.

An issue log is used to document current problems that have occurred, as opposed to risks which are uncertain future events.

The scope statement formally documents all these elements to define the project scope.

Agile methodologies are adaptive and welcome changing requirements, even late in development.

Stakeholders with high power and high interest are key players who require close management to keep them engaged and satisfied.

CPI less than 1 indicates over budget; SPI greater than 1 indicates ahead of schedule. Therefore the project is over budget but ahead of schedule.

In a RACI matrix, 'A' stands for Accountable, meaning the person who has ultimate ownership and sign-off authority for the task. This individual is answerable for the successful completion of the deliverable and cannot delegate that responsibility. The correct answer is D because the RACI acronym explicitly defines 'A' as Accountable.

Scope creep refers to uncontrolled changes or continuous growth in a project's scope, often without proper authorization.

Payback period calculates the time to recover the investment.

The best approach because it allows each region to use its own methodology while establishing integration points to ensure compatibility and coordination. This balances flexibility with the need for a unified project outcome, addressing the European team's integration concerns without forcing a single methodology that may not suit all regions.

The requirements traceability matrix (RTM) is the correct document because it links each requirement to its origin, design, testing, and delivery status. When a stakeholder asks for the project's requirements documentation, the RTM provides a structured view of all requirements and their lifecycle, which is the authoritative source for requirement status and traceability.

Common risk register fields include risk ID, description, owner, probability, impact, risk score, response strategy, residual risk, and trigger. Budget and resource names are not standard fields in the risk register; they may be in other project documents.

The Communications Management Plan is the correct document because it defines all project communications, including which documents will be created, maintained, and distributed throughout the project lifecycle. This plan specifies the types of documents, their format, frequency, and stakeholders, directly addressing the project manager's need to identify all project documents.

A Pareto chart is based on the 80/20 rule where 80% of problems come from 20% of causes. It helps prioritize which issues to address first.

An RFP includes a statement of work (SOW) describing the work, technical specifications, and evaluation criteria for selecting the vendor. Payment terms are part of the contract, not typically in RFP, and company financial data is not required.

After the customer has accepted deliverables and the final project report is complete, the next step is to conduct a lessons learned session with the project team. This aligns with the closing process group in the PMBOK Guide, where capturing knowledge and process improvements is a key activity before administrative closure. In a CRM system project, this session would review integration challenges, data migration issues, and user adoption strategies to inform future projects.

The change log is the primary document for recording all change requests, their status, and approval decisions throughout the project. The issue log tracks problems that arise during the project, which often lead to changes, making it a secondary source for tracking changes. Both documents are essential for maintaining a clear audit trail of project modifications.

The project scope statement formally documents the project's scope, including acceptance criteria and deliverables, serving as the baseline for what must be completed. The project closure report formally communicates the final deliverables and confirms that acceptance criteria have been met, marking the official end of the project. Both documents are key outputs in the PMI framework for PK0-005.

A network diagram (activity-on-node) shows the sequence and dependencies of activities, allowing identification of the critical path.