CompTIA Project+ (PK0-005) — All Questions

A stakeholder asks the project manager to add a major new feature after the schedule and budget are already fixed. Increasing scope without adjusting time or cost most directly threatens which project fundamental?

• a.The communication plan
• b.The lessons-learned register
• c.The triple constraint (scope, schedule, cost)✓
• d.The procurement contract type

The triple constraint describes the balance among scope, schedule, and cost, where changing one usually forces a change in another. Expanding scope while holding time and budget fixed pressures quality and is the classic constraint conflict a project manager must manage through change control.

During risk planning, a team decides to purchase insurance to shift the financial impact of a potential event to a third party. Which risk response strategy is this?

• a.Transfer✓
• b.Avoid
• c.Mitigate
• d.Accept

Transferring a risk shifts its impact or ownership to a third party, for example through insurance or a warranty. Avoiding eliminates the risk by changing the plan, mitigating reduces its probability or impact, and accepting takes no proactive action.

Which statement best distinguishes a project from ongoing operations?

• a.A project runs indefinitely with no defined end
• b.A project is temporary and produces a unique result✓
• c.A project never has a budget or schedule
• d.A project cannot involve more than one person

A project is a temporary endeavor with a defined beginning and end that creates a unique product, service, or result. Operations, by contrast, are ongoing and repetitive. Projects still have budgets, schedules, and can involve many people.

A project uses fixed-length iterations, delivers working increments frequently, and welcomes changing requirements throughout. Which delivery approach is being used?

• a.Pure waterfall
• b.Predictive-only
• c.Phase-gate with no iteration
• d.Agile✓

Agile approaches deliver work in short iterations, produce frequent increments, and embrace change even late in development. Waterfall and predictive approaches plan extensively up front and resist late changes, making them the opposite of the described behavior.

Who typically provides the funding and high-level support for a project and champions it within the organization?

• a.The project sponsor✓
• b.The end user
• c.The vendor's delivery driver
• d.The quality auditor

The project sponsor authorizes funding, provides high-level direction, and champions the project to remove organizational obstacles. End users benefit from the product, and auditors and vendors play supporting roles but do not fund or champion the effort.

Which document, produced during initiation, formally authorizes the project and names the project manager and high-level objectives?

• a.The work breakdown structure
• b.The project charter✓
• c.The final lessons-learned report
• d.The risk register

The project charter is created during initiation to formally authorize the project, appoint the project manager, and record high-level objectives and constraints. The WBS and risk register come later in planning, and lessons learned are captured at closure.

A planner decomposes the total project work into progressively smaller, manageable deliverables and work packages. Which tool is being created?

• a.A stakeholder register
• b.A responsibility assignment matrix
• c.A communication plan
• d.A work breakdown structure (WBS)✓

A work breakdown structure decomposes the full scope into progressively smaller deliverables and work packages, forming the basis for estimating, scheduling, and assigning work. The other documents address stakeholders, responsibilities, and communication rather than scope decomposition.

In which project life-cycle phase does the team primarily measure performance against the plan and manage change requests to keep the project on track?

• a.Initiating
• b.Closing
• c.Monitoring and controlling✓
• d.Planning

Monitoring and controlling runs alongside execution to compare actual performance to the plan, address variances, and process change requests through change control. Initiating authorizes the project, planning defines how to do the work, and closing finalizes it.

Which activities are characteristic of the project closing phase?

• a.Obtaining final acceptance, releasing resources, and documenting lessons learned✓
• b.Drafting the project charter and appointing the project manager
• c.Building the detailed schedule and budget for the first time
• d.Identifying stakeholders for the very first time

Closing involves obtaining formal acceptance of deliverables, releasing the team and resources, closing contracts, and documenting lessons learned for future projects. Chartering, initial scheduling, and initial stakeholder identification occur in earlier phases.

A change request has been submitted to alter an approved deliverable. What is the correct next step before any work begins on the change?

• a.Immediately implement the change to save time
• b.Evaluate the change through the formal change control process✓
• c.Ignore the request unless the sponsor calls
• d.Delete the original project plan

Approved baselines are protected by change control, so a change request must be evaluated for its impact on scope, schedule, cost, and risk, then formally approved or rejected before work starts. Implementing changes without review causes scope creep and uncontrolled impacts.

A RACI chart lists a team member as "Accountable" for a deliverable. What does this designation mean?

• a.They perform the hands-on work of the task
• b.They are simply kept informed of progress
• c.They are ultimately answerable for the deliverable and there is only one such person✓
• d.They provide input as a subject-matter expert when consulted

In a RACI matrix, Accountable is the single person ultimately answerable for the outcome. Responsible parties do the work, Consulted parties provide input, and Informed parties are kept up to date. There should be exactly one Accountable per task to preserve clear ownership.

A geographically dispersed team needs to review a lengthy design document at their own pace and leave written comments over several days. Which communication method is most appropriate?

• a.Asynchronous written communication such as a shared document with comments✓
• b.An unscheduled live phone call to each person
• c.A synchronous all-hands meeting at a single fixed time
• d.A verbal hallway conversation

Asynchronous communication lets participants contribute on their own schedule, which suits detailed review across time zones and preserves a written record. Synchronous methods require everyone to be available at once, which is impractical for lengthy, distributed review.

Two team members disagree strongly about a technical approach, and the conflict is delaying the project. Which is generally the most constructive first approach for the project manager?

• a.Force one side to comply immediately without discussion
• b.Withdraw and let the conflict resolve itself over time
• c.Smooth over the issue by ignoring the substantive disagreement
• d.Facilitate a collaborative discussion to find a solution addressing both concerns✓

Collaborating, or problem solving, seeks a solution that addresses everyone's underlying concerns and generally produces the most durable outcome. Forcing, withdrawing, and smoothing may resolve the surface tension but leave the real issue unaddressed.

Why does a project manager perform stakeholder analysis early in a project?

• a.To eliminate the need for a project schedule
• b.To identify stakeholders' interests and influence so engagement can be tailored✓
• c.To assign blame for anticipated failures
• d.To avoid ever communicating with executives

Stakeholder analysis identifies who is affected by the project, their level of interest and influence, and their expectations, so the manager can plan appropriate engagement and communication for each. It does not replace scheduling or serve to assign blame.

Which document defines the specific deliverables, activities, and timelines a vendor is contracted to provide?

• a.Statement of work (SOW)✓
• b.Meeting minutes
• c.Risk register
• d.Organizational chart

A statement of work (SOW) details the deliverables, activities, and timelines expected from a vendor and becomes part of the contract. Meeting minutes record discussions, a risk register tracks risks, and an organizational chart shows reporting structure.

A project manager needs a visual schedule that shows tasks as horizontal bars along a timeline, including their durations and dependencies. Which tool is best?

• a.A pie chart of the budget
• b.A stakeholder register
• c.A Gantt chart✓
• d.A business case

A Gantt chart displays tasks as horizontal bars along a timeline, showing durations, start and end dates, and dependencies, which makes it ideal for visualizing and tracking a schedule. The other options serve budgeting, stakeholder, or justification purposes.

An organization wants to solicit detailed pricing and solution proposals from multiple vendors for a defined project. Which procurement document should it issue?

• a.A meeting agenda
• b.A lessons-learned report
• c.A project charter
• d.A request for proposal (RFP)✓

A request for proposal (RFP) asks vendors to propose complete solutions along with pricing for a defined need, allowing comparison of approaches. An RFQ focuses narrowly on price and an RFI gathers general information, while the other documents are internal and unrelated to soliciting bids.

What is the primary purpose of maintaining an issue log during a project?

• a.To store the project's source code
• b.To track identified problems, their owners, and resolution status✓
• c.To calculate employee payroll
• d.To replace the project charter

An issue log records problems that have already occurred, assigns an owner, and tracks status through resolution so nothing is lost. It differs from a risk register, which tracks potential future events, and it is not a code repository or payroll tool.

A software team promotes a change from a development environment, into testing, and finally into production only after validation. What is the main purpose of maintaining these separate environments?

• a.To increase the number of servers for its own sake
• b.To avoid ever having to document changes
• c.To validate changes safely before they affect live users✓
• d.To make the project take longer intentionally

Separate development, test, and production environments let teams build and validate changes without risking the live system, catching defects before they reach users. This is a core governance and change-management practice, not a way to add servers or delay work.

A project will process customer personal information subject to data-privacy regulations. What should the project manager do regarding these requirements?

• a.Incorporate the compliance requirements into scope, planning, and controls✓
• b.Ignore them because they are not technical tasks
• c.Delay considering them until after go-live
• d.Assume the vendor is solely responsible with no oversight

Regulatory and data-privacy requirements are constraints that must be built into scope, planning, and controls from the start, because non-compliance carries legal and financial consequences. Deferring or outsourcing accountability without oversight exposes the organization to risk.

In a fixed-price contract, which party primarily bears the risk of cost overruns if the work takes more effort than expected?

• a.The end users
• b.The regulatory agency
• c.The buyer
• d.The seller (vendor)✓

In a fixed-price contract the price is set regardless of the seller's actual costs, so the seller bears the risk of overruns. In a time-and-materials or cost-reimbursable arrangement, more of that risk shifts to the buyer.

Which best describes the role of a change advisory board (CAB) in IT change management?

• a.It writes all application source code for the project
• b.It reviews and authorizes proposed changes, weighing benefit against risk✓
• c.It sets the vendor's stock price
• d.It replaces the need for testing environments

A change advisory board reviews proposed changes, assessing their benefit, risk, and impact, and authorizes or defers them to protect the stability of production systems. It does not write code, set prices, or eliminate the need for testing.