Your FREE CompTIA Project+ Practice Test 2026 – 200+ Q&A

Correct answer: Specifying and controlling the work included in the project

"Specifying and controlling the work included in the project" is the focus of scope management, so that the project contains all the required work and only that work, with anything else kept out. Forecasting and budgeting the costs incurred in the project belongs to cost management. Sharing and archiving the messages generated in the project belongs to communications management. Identifying and ranking the risks documented in the project belongs to risk management.

Correct answer: Project

A Project is a temporary endeavor undertaken to create a unique product, service, or result; it has a defined start and end. A Program is a group of related projects managed together for benefits they could not deliver separately. A Portfolio is a collection of projects, programs and operations managed to meet strategic objectives. An Operation is ongoing and repetitive work that sustains the business, the opposite of a temporary, unique effort.

Correct answer: Cost, Scope, and Schedule

The Triple Constraint model is made up of Cost, Scope, and Schedule (schedule is often called time); a change to any one of the three affects the other two. Cost, Risk, and Resources drops scope and schedule in favor of factors that are managed within the constraints. Quality, Time, and Budget is the common mix-up: time and budget do cover two sides, but quality sits at the center of the triangle as the result of balancing them, and scope, the third side, is missing. Schedule, Scope, and Risk leaves out cost, and risk is a separate knowledge area that threatens all three sides rather than being one of them.

Correct answer: Procurement Management

Procurement Management covers obtaining goods and services from outside the project team, including make-or-buy decisions, solicitation, vendor selection, contracts and contract closure. Resource Management acquires and manages the project's own team, equipment and materials, not external purchases. Schedule Management defines and controls activity timing. Integration Management coordinates all the other knowledge areas into one plan; it does not buy from outside sellers.

Correct answer: To guide the expectations and engagement of affected parties

The aim of stakeholder management is "To guide the expectations and engagement of affected parties": identify the people and groups the project touches, understand their needs, and keep them appropriately involved and informed. To minimize the probability and severity of identified risks is the aim of risk management. To negotiate the prices and conditions of supplier contracts belongs to procurement management. To verify the quality and accuracy of completed deliverables is quality control.

Correct answer: The relative priority of project requirements

The MoSCoW method sorts requirements into Must have, Should have, Could have and Won't have, so it determines "The relative priority of project requirements". "The estimated probability of project setbacks" is set by qualitative risk analysis with a probability-impact matrix. "The internal dependency of project activities" is worked out when sequencing activities in a network diagram. "The quality specifications of project outputs" are set in quality planning, not by ranking requirements.

Correct answer: The unapproved growth of project scope

Scope creep is "The unapproved growth of project scope": features and requests are added without going through change control and without adjusting time, cost or resources. "The planned reduction of project scope" is descoping, a deliberate and controlled change. "The formal acceptance of project scope" is scope validation or baselining, the opposite of uncontrolled change. "The layered breakdown of project scope" is decomposition into a work breakdown structure.

Correct answer: The chain of dependent activities that sets the earliest project finish

The critical path is "The chain of dependent activities that sets the earliest project finish": it is the longest path through the network, so its total duration is the minimum time in which the project can be completed. "The class of risky activities that carries the highest project exposure" describes a risk ranking, not the schedule path. "The group of costly activities that drives the largest project expenses" confuses cost with duration. "The series of flexible activities that holds the leftover project float" describes the noncritical paths, since critical activities have zero float.

Correct answer: Ensuring that project outputs fulfill stakeholder needs

Quality management is focused on "Ensuring that project outputs fulfill stakeholder needs", meaning the deliverables meet the quality requirements and expectations set for them. "Ensuring that project expenses match designated budgets" is cost management. "Ensuring that project changes receive official approval" is integrated change control. "Ensuring that project sponsors receive frequent updates" is communications management.

Correct answer: Human Resource Planning

Human Resource Planning is the process that identifies and documents project roles, responsibilities, required skills and reporting relationships, producing the staffing management plan and organization charts. Change Control Planning sets how change requests will be submitted, reviewed and approved. Cost Management Planning sets how costs will be estimated, budgeted and controlled. Risk Management Planning decides how risk activities will be carried out on the project.

Correct answer: The economic justification for the project

A cost-benefit analysis compares the expected costs with the expected benefits, so it determines "The economic justification for the project", that is, whether it is financially worth doing. "The stakeholder priorities for the project" come from stakeholder analysis, not from comparing costs with benefits. "The contingency allowances for the project" are set by reserve analysis based on identified risks. "The quarterly expenditures for the project" are laid out in the time-phased budget and cost baseline after approval.

Correct answer: Shifting project activities to fit limited resources

Resource leveling means "Shifting project activities to fit limited resources": start and finish dates are adjusted so that no resource is overallocated, which often lengthens the schedule. "Overlapping project phases to meet earlier deadlines" is fast-tracking, a schedule compression technique that adds risk rather than resolving resource conflicts. "Adding project resources to compress phase durations" is crashing, which shortens the schedule at extra cost. "Matching project resources to specialized skill sets" is resource assignment, not leveling.

Correct answer: Uncovering and recording the possible project risks

Risk identification is focused on "Uncovering and recording the possible project risks" that could affect the objectives, usually in a risk register; it is the first step after risk planning. "Scoring and prioritizing the captured project risks" is qualitative risk analysis. "Modeling and simulating the aggregate project risks" is quantitative risk analysis, for example a Monte Carlo simulation. "Monitoring and reassessing the active project risks" is the monitor risks process.

Correct answer: Flagging key checkpoints in the project schedule

A milestone is a zero-duration marker used for "Flagging key checkpoints in the project schedule", such as the end of a phase, a major deliverable or a decision point. "Logging unresolved issues in the project tracker" is done in the issue log. "Tracking incurred expenses in the project budget" is cost control. "Itemizing detailed tasks in the project timeline" describes activities, which have duration and effort, whereas a milestone marks a point in time.

Correct answer: To identify which people the project will affect

Stakeholder analysis is done "To identify which people the project will affect", along with their interests, influence and expectations, so they can be engaged appropriately. "To choose which vendors the project will onboard" is source selection in procurement. "To forecast which charges the project will incur" is cost estimating. "To set which updates the project will distribute" is communications planning, which uses the results of stakeholder analysis but is a separate step.

Correct answer: Coordinating the various project processes and plans

Project integration management focuses on "Coordinating the various project processes and plans" so that they work as one whole, including developing the overall plan, directing the work and handling integrated change control. "Purchasing the needed project materials and services" is procurement management. "Verifying the completed project outputs and features" is quality control and scope validation. "Monitoring the identified project risks and triggers" is risk management.

Correct answer: Time, Cost, Scope

The triple constraint is Time, Cost, Scope: the three are interdependent, so a change in one affects at least one of the others. Scope, Risk, Time replaces cost with risk, which threatens the constraints but is not one of the three. Time, Cost, Quality is the classic mix-up: quality is usually shown at the center as the result of balancing the three sides, and it pushes out scope, which is the third side. Quality, Time, Risk leaves out both scope and cost and adds two factors that sit outside the triangle.

Correct answer: Resources

Resources is the constraint covering the people, equipment and materials needed to do the work, and their availability. Requirements is the constraint covering what the solution must do. Deliverables is the constraint covering the products the project must hand over. Quality is the constraint covering the standards the deliverables must meet, not the people and materials used to produce them.

Correct answer: Added duration and expense

Because scope, time and cost are linked, more scope normally brings Added duration and expense: extra work needs more effort, more resources and a longer schedule. Unchanged dates and budget is the assumption behind scope creep; it only holds if other work is removed. Enhanced quality and value is not a direct result, since stretching the same team over more work tends to put quality at risk. Stable teams and workloads is wrong because the added work has to be done by someone, raising workload or staffing.

Correct answer: The project's timeline and costs

"The project's timeline and costs" is correct: raising or lowering the quality standard changes how much testing, inspection and rework the team must do, so it moves the schedule and the budget. "The project's scope and sponsors" is wrong because a quality decision changes how well the agreed work is done, not what the scope contains or who sponsors the project. "The project's charter and budget" is wrong because the charter is fixed at authorization and is not reopened by a quality decision, and the pair says nothing about the schedule effect. "The project's exposure and scope" is wrong because quality trades off against time and cost: a quality decision changes how well the agreed deliverables are built, not what the scope contains, and it does not reset the project's risk exposure as a constraint.

Correct answer: Delivery schedule

"Delivery schedule" is correct: losing a critical team member delays the work while the role is backfilled or the workload is redistributed, so the time constraint is hit most directly. "Budget allocation" is wrong because any cost effect follows from the delay rather than coming first. "Deliverable scope" is wrong because the work to be delivered does not change when a person leaves. "Quality standards" is wrong because the quality standard stays the same; only the time needed to meet it grows.

Correct answer: Deliverable items

"Deliverable items" is correct: the scope constraint defines and controls what is and is not included, so it governs whether the project delivers what was promised. "Delivery schedule" is wrong because the schedule concerns when the work finishes, not what it contains. "Budget allocation" is wrong because the budget concerns how much the work may cost, not what the deliverables must contain. "Team availability" is wrong because team availability concerns the people who do the work, not a definition of what the work must deliver.

Correct answer: Scope and budget

"Scope and budget" is correct: a fixed-price contract locks the price, so cost is fixed and the scope must be tightly defined and controlled to stay within it. "Quality and risk" is wrong because quality and risk are managed through specifications and the risk register, not set by the pricing model. "Effort and staff" is wrong because effort and staff levels are the seller's planning decisions and are not what the contract price fixes. "Time and quality" is wrong because neither time nor quality is the term a fixed-price agreement pins down; the price and the defined work are.

Correct answer: It raises the project's risks and scope.

"It raises the project's risks and scope." is correct: an unexpected regulatory change adds uncertainty and usually adds compliance work, so both risk and scope grow. "It lowers the project's risk and budget." is wrong because a surprise regulation adds uncertainty and compliance cost rather than lowering risk or the budget. "It boosts the project's buffer and pace." is wrong because the added compliance work uses up the schedule buffer and slows the pace of delivery rather than boosting either. "It locks the project's scope and roster." is wrong because a regulation forces changes to the scope and often the team instead of locking them.

Correct answer: Schedule limits

"Schedule limits" is correct: a legally mandated deadline fixes the date the project must finish, so time becomes the primary constraint. "Budget baseline" is wrong because the external factor fixes a date, not the cost baseline. "Quality targets" is wrong because the legal deadline says nothing about the quality standard. "Risk thresholds" is wrong because risk thresholds express how much uncertainty the organization will accept; the deadline itself is a time limit.

Correct answer: Insufficient project resource allocation

"Insufficient project resource allocation" is correct: when complexity is underestimated, the plan does not allocate enough people and materials to handle the real work. "Overstated project expenditure forecasts" is wrong because underestimating complexity produces estimates that are too low, not too high. "Diminished intrinsic project uncertainty" is wrong because a planning error cannot lower the uncertainty built into the work itself; the intrinsic uncertainty is exactly as large as before, and the underestimate leaves more of it unmanaged. "Overcautious project milestone estimates" is wrong because underestimated work makes milestone estimates too optimistic, not overcautious.

Correct answer: Added risk and expense

"Added risk and expense" is correct: compressing the schedule with the same scope adds risk from the tighter timeline and adds cost because crashing brings in extra resources. "Reduced cost and labor" is wrong because crashing adds labor and money rather than saving them. "Smaller scope and team" is wrong because the scope is held constant and crashing adds people, so neither the scope nor the team shrinks. "Extra scope and buffer" is wrong because the scope is held constant and a compressed schedule uses up its buffer rather than adding to it.

Correct answer: Raises the likelihood of new risks

"Raises the likelihood of new risks" is correct: added scope brings new work, variables and interfaces that were not in the original plan, so the likelihood of risks occurring rises. "Lowers the severity of known risks" is wrong because more scope does not make existing risks less severe. "Shifts the ownership of open risks" is wrong because risk owners are assigned in the risk register and are not reassigned by a scope increase. "Narrows the number of active risks" is wrong because new scope adds to the list of active risks rather than narrowing it.

Correct answer: Product definition

"Product definition" is correct: a new regulation imposed partway through usually adds required activities or deliverables, which changes what the project must deliver. "Delivery timetable" is wrong because any schedule impact follows from the added work rather than being the constraint the regulation sets. "Budget allocations" is wrong because the cost effect is likewise a consequence of the added work. "Workforce capacity" is wrong because resources are the means to deliver the work, not the definition of what must be delivered.

Correct answer: Rise in overall project expenses

"Rise in overall project expenses" is correct: higher quality standards demand better materials, more testing and more effort, which raises overall costs. "Reduction in total project costs" is wrong because the added testing, inspection and materials needed to meet a higher standard add cost now, and any later savings from avoided rework do not cancel that increase. "Uptick in project overheads only" is wrong because direct costs rise as well: better materials and the labor for extra testing and inspection are charged straight to the work, so the increase is not confined to indirect overhead. "Growth in spare project reserves" is wrong because the extra testing and inspection draw reserves down, leaving less unspent money rather than a growing pool of spare reserves.

Correct answer: Heightened project risk and cost

"Heightened project risk and cost" is correct: delivering the same scope in less time raises risk from the tighter deadline and raises cost because extra resources or overtime are needed. "Lowered project costs and effort" is wrong because compressing the schedule adds cost and effort rather than lowering them. "Narrowed project scope and staff" is wrong because the scope is unchanged by definition and crashing adds staff rather than narrowing the team. "Raised project scope and quality" is wrong because the scope is unchanged by definition and rushed work tends to lower quality rather than raise it.

Correct answer: Raised project risk and wider scope

"Raised project risk and wider scope" is correct: stakeholders who gain influence late tend to request new features and changes, which widens the scope and adds risk to a plan that is already well advanced. "Cut project cost and faster closure" is wrong because late change requests add cost and delay rather than cutting cost or speeding closure. "Quicker project pace and more float" is wrong because late change requests slow the work and consume schedule float rather than speeding it up or leaving more slack. "Early project closure and cut risks" is wrong because added requests push closure back and add risk rather than cutting it.

Correct answer: Raises the probability and severity of risks

"Raises the probability and severity of risks" is correct: a more complex project has more variables, interfaces and unknowns, so risks become both more likely to occur and more damaging when they do. "Reduces the frequency and magnitude of risks" is wrong because complexity makes risks more likely and more damaging, not less. "Boosts the visibility and ownership of risks" is wrong because complexity buries risks among more interfaces and unknowns, making them harder to see, and risk owners are assigned in the risk register rather than created by complexity. "Stabilizes the count and priorities of risks" is wrong because complexity adds new risks and reshuffles priorities rather than stabilizing them.

Correct answer: Raised project costs and longer duration

"Raised project costs and longer duration" is correct: meeting significantly higher quality requirements takes more resources, more testing and possible rework, so cost rises and the schedule lengthens. "Shorter project timeline and milder risk" is wrong because extra quality work lengthens the timeline and adds risk of missing the standard. "Expanded project scope and greater float" is wrong because higher quality requirements raise the standard for the same deliverables rather than adding scope, and the extra testing consumes float instead of creating more. "Narrowed project scope and reduced costs" is wrong because stricter requirements apply to the same agreed deliverables rather than removing any of them, and the added testing and rework push costs up, not down.

Correct answer: It confines the project scope to key deliverables

"It confines the project scope to key deliverables" is correct: with a tight budget there is little room to expand, so the team prioritizes the essential deliverables and limits the scope. "It expands the project scope to optional features" is wrong because a constrained budget removes the money needed for optional additions. "It converts the project scope to quality criteria" is wrong because a budget limit does not turn scope into quality criteria; scope and quality remain separate constraints. "It transfers the project scope to outside vendors" is wrong because outsourcing is a procurement decision and costs money; it is not the direct effect of a tight budget on scope.

Correct answer: Growth in project costs and risks

"Growth in project costs and risks" is correct: losing key resources to another project forces the team to find and onboard replacements, which adds cost and introduces delay and uncertainty. "Gain in project quality and speed" is wrong because the remaining team has less capacity, so neither quality nor speed improves. "Drop in project risk and workload" is wrong because the same work still has to be done by fewer or less experienced people, which adds risk rather than reducing it. "Rise in project staff and mandate" is wrong because the team has just lost people and its approved mandate is unchanged, so neither the staff nor the mandate rises.

Correct answer: It enlarges project scope and risk.

"It enlarges project scope and risk." is correct: bringing new technology in midway adds integration work and unfamiliar challenges, so both the scope and the risk grow. "It trims project cost and duration." is wrong because integrating new technology adds effort and time rather than cutting cost or duration. "It locks project quality and risks." is wrong because new technology usually forces changes to quality checks and team skills and brings new risks rather than locking quality and risk in place. "It shrinks project scope and tests." is wrong because integration adds scope and tests instead of shrinking them.

Correct answer: Extension of the project timeline

"Extension of the project timeline" is correct: when a critical component arrives late, the activities that depend on it cannot start, so the project duration increases. "Restoration of the project buffer" is wrong because a late delivery consumes the schedule buffer rather than restoring it. "Firmness of the project timetable" is wrong because a delay on a critical component moves the schedule, so the timetable does not stay firm. "Augmentation of the project float" is wrong because the delay uses up float rather than adding to it.

Correct answer: Scope baseline

"Scope baseline" is correct: market changes that require modified deliverables change what the project must produce, which is the scope. "Resource plans" is wrong because resource plans are revised only as a consequence of the modified work; the change acts on the deliverables. "Cost estimates" is wrong because cost estimates are likewise revised as a result of the scope change rather than being the constraint it acts on. "Quality grades" is wrong because the quality grade of the deliverables is not what the market shift redefines.

Correct answer: Prolongs the project timeline

"Prolongs the project timeline" is correct: when the needed skills are missing, time is spent training staff or recruiting a specialist, which extends the project timeline. "Shrinks the project headcount" is wrong because the gap is usually filled by adding someone, not by shrinking the team. "Streamlines the project scope" is wrong because the work that needs the specialized skill still has to be delivered; a skills gap changes who can do the work and when, not what the agreed scope contains. "Stabilizes the project budget" is wrong because hiring or training adds cost, so the budget does not stay stable.

Correct answer: Elevated project risk and expense

"Elevated project risk and expense" is correct: high turnover means lost knowledge plus repeated recruiting and onboarding, which raises both risk and expense. "Trimmed project risks and backlog" is wrong because turnover adds risk and does not remove work from the backlog; the same work remains. "Boosted project morale and output" is wrong because frequent departures disrupt the team rather than boosting morale and output. "Widened project scope and mandate" is wrong because people leaving adds no work or authority to the project; the scope and mandate stay as approved while the team struggles to deliver them.

Correct answer: Work boundaries

"Work boundaries" is correct: an environmental regulation imposed on a construction project adds required measures, such as controls, permits or mitigation work, which changes what the project must include, so the scope is affected most directly. "Completion date" is wrong because any slip in the finish date is a knock-on effect of the added work. "Budget baseline" is wrong because the budget changes only as a consequence of the added scope. "Quality targets" is wrong because the regulation adds work to be done rather than redefining the quality targets of the building itself.

Correct answer: Boosts the project budget and duration

"Boosts the project budget and duration" is correct: a team unfamiliar with an advanced technology needs training, research and trial and error, which adds cost and stretches the schedule. "Lowers the project risk and complexity" is wrong because unfamiliar technology adds risk and complexity rather than lowering them. "Raises the project velocity and output" is wrong because the learning curve slows the team, so velocity and output fall at first rather than rising. "Fixes the project quality and timeline" is wrong because the learning curve disturbs the timeline and the quality checks rather than fixing them in place.

Correct answer: Raised project budgets and delays

"Raised project budgets and delays" is correct: when a key supplier fails, the team must find and qualify a replacement, which takes time and often costs more. "Lowered project risk and overhead" is wrong because losing a supplier adds supply risk and the overhead of re-sourcing. "Larger project scope and features" is wrong because losing a supplier changes who provides the goods, not what the project must deliver, so neither the scope nor the feature list grows. "Early project rollout and payback" is wrong because the disruption pushes the rollout and any payback later, not earlier.

Correct answer: Expansion in project scope and risk

"Expansion in project scope and risk" is correct: new legislation or compliance requirements add tasks needed to meet the new standard and bring uncertainty about how to satisfy it, so scope and risk both grow. "Growth in project buffer and margin" is wrong because the extra compliance work uses up the schedule buffer and its cost eats into the margin rather than growing either. "Uplift in project speed and quality" is wrong because compliance work slows delivery and does not lift quality beyond what the rule requires. "Decrease in project scope and risks" is wrong because compliance adds work and new risks rather than reducing the scope or the risk.

Correct answer: Swells the project's costs and duration

"Swells the project's costs and duration" is correct: building quality beyond the agreed specification, often called gold plating, takes more resources, testing and refinement, so cost and time rise. "Trims the project's timeline and budget" is wrong because extra quality work lengthens the timeline and spends more budget rather than trimming them. "Expands the project's float and margins" is wrong because the extra refinement consumes schedule float and spends money, so float and margins shrink rather than expand. "Shrinks the project's cost and workload" is wrong because the added refinement increases the cost and the workload rather than shrinking them.

Correct answer: To approve or refuse requested revisions

"To approve or refuse requested revisions" is correct: the change control board is the group of stakeholders and experts that reviews proposed changes and decides whether each one is approved or rejected, protecting the baselines. "To estimate or monitor project overheads" is wrong because estimating and monitoring costs is the project manager's cost management work, not the board's role. "To review or report schedule performance" is wrong because reporting schedule performance belongs to status and performance reporting. "To interview or induct project personnel" is wrong because recruiting and onboarding staff is part of resource management, not change control.

Correct answer: Improving clarity and comprehension

"Improving clarity and comprehension" is correct: repeating the cycle of sending, feedback and clarification lets misunderstandings surface and be corrected, so everyone ends up with a clear, shared understanding. "Cutting expenses and administration" is wrong because repeated exchanges take time and effort rather than cutting expenses or administration. "Shortening schedules and milestones" is wrong because the purpose of iteration is understanding, not a shorter schedule. "Standardizing templates and formats" is wrong because templates and formats are standardized in the communications plan, not by iterating on messages.

Correct answer: Interference and confusion that disrupt communication

"Interference and confusion that disrupt communication" is correct: in the communication model, noise is anything that distorts or interrupts the message, such as distractions, jargon, language barriers or misunderstandings. "Technologies and channels that transmit communication" is wrong because technologies and channels are the medium that carries the message, not the interference. "Feedback and acknowledgment that verify communication" is wrong because feedback and acknowledgment are the steps that confirm a message was understood. "Originators and receivers that exchange communication" is wrong because originators and receivers are the sender and receiver in the model, not the noise between them.

Correct answer: Collaborating

"Collaborating" is correct: collaborating, also called problem solving, brings the parties together to work out a solution that addresses everyone's concerns, which tends to give a lasting resolution and a stronger team. "Accommodating" is wrong because accommodating, also called smoothing, plays down differences and settles the conflict by giving way rather than resolving it. "Withdrawing" is wrong because withdrawing, also called avoiding, postpones the conflict without solving it. "Reconciling" is wrong because reconciling, also called compromising, gives each side only part of what it wants, which is less effective than a joint solution.

Correct answer: Onsite group session

An "Onsite group session" (a face-to-face meeting) is the most appropriate method for complex technical detail, because the presenter can read the audience, answer questions immediately and adjust the explanation for a diverse team. A "Recorded screen demo" is one-way and allows no live clarification, a "Company email digest" is asynchronous text that invites misreading of complex material, and a "Written wiki article" is a reference page that offers no dialogue at all.

Correct answer: To weigh the effects of proposed modifications

An impact analysis exists "To weigh the effects of proposed modifications" on scope, schedule, cost and quality before anyone decides on a change request. "To forecast the duration of planned activities" is activity duration estimating, "To quantify the likelihood of identified risks" is risk analysis, and "To document the approval of submitted requests" is the job of the change log after a decision; none of them assesses what a proposed change would do to the project.

Correct answer: Holding recurrent video conferences

"Holding recurrent video conferences" is the effective strategy for a global team: regular virtual meetings give everyone timely, interactive contact across locations and can be scheduled to share the burden of time zones. "Sending monthly printed newsletters" is slow and one-way, "Requiring headquarters office hours" forces remote members to work outside their own day, and "Convening quarterly onsite retreats" is too infrequent and costly to manage day-to-day communication.

Correct answer: To comprehend the full message

Active listening means attending, paraphrasing and asking clarifying questions so the listener is able "To comprehend the full message" accurately and thoroughly. "To prepare the immediate reply" is the habit active listening is meant to break, since planning a response stops the listener from hearing the speaker; "To capture the written minutes" is note-taking, a separate meeting task; and "To rate the presenter delivery" is evaluation, not understanding.

Correct answer: Integrated change control

"Integrated change control" (change control) is the process that reviews, approves or rejects every change against the project's objectives and baselines, so it keeps changes consistent with those objectives. "Change request submission" only raises a request and evaluates nothing, "Approved change broadcast" communicates a decision already made, and "Change document retention" archives records; none of them tests a change against the objectives.

Correct answer: Summarizing overall progress and major issues

High-level stakeholders need the big picture, so the main consideration is "Summarizing overall progress and major issues" that may need their decisions. "Itemizing granular measures and minor defects" buries the message in detail executives do not use, "Postponing unresolved problems and open risks" hides exactly what sponsors must hear early, and "Emphasizing staff morale and employee rewards" is an internal team matter rather than project status.

Correct answer: Adapting formats to individual preferences

With varied communication styles, the effective technique is "Adapting formats to individual preferences" so each member receives information in the way they understand best. "Restricting dialogue to structured reports" forces one written style on everyone, "Forwarding disagreements to senior leaders" hands off conflict rather than communication style, and "Assigning members to homogeneous subgroups" splits the team instead of managing its diversity.

Correct answer: To resolve problems beyond team authority

Escalation management moves an issue to someone with the authority to act, so its goal is "To resolve problems beyond team authority" that the project team cannot settle on its own. "To report progress against baseline goals" is status reporting, "To shift residual risk exposure elsewhere" is the transfer risk response handled through contracts, and "To penalize staff behind missed deadlines" is a personnel matter; escalation is about getting a decision, not assigning blame.

Correct answer: Client satisfaction questionnaires

"Client satisfaction questionnaires" (customer satisfaction surveys) collect feedback directly from the people the project serves, showing how well its deliverables met their needs. "Employee timesheet reconciliations" verify hours charged, "Supplier qualification assessments" judge whether a vendor can deliver, and "Competitor marketplace comparisons" study other organizations' offerings; none of them asks customers how the project performed.

Correct answer: Convening a dedicated review session

"Convening a dedicated review session" (a meeting with the stakeholders) is most effective for a significant scope change, because it allows immediate discussion, questions and agreement on the implications. "Publishing a monthly newsletter item" is slow and one-way, "Circulating a revised scope document" informs but gives no chance to discuss or confirm understanding, and "Submitting a detailed change request" starts the approval process rather than communicating an approved change.

Correct answer: Keeps official messages uniform

In a top-down approach information flows from leadership down the hierarchy, so its main advantage is that it "Keeps official messages uniform" and everyone hears the same priorities. "Captures frontline worker ideas" is a strength of bottom-up communication, where suggestions travel up from the people doing the work. "Boosts overall staff motivation" is not the main advantage, since one-way messages from leadership do less for motivation than participative, two-way communication. "Shortens upward feedback cycles" also describes bottom-up channels, because top-down messaging carries little feedback back up.

Correct answer: To mediate interpersonal disagreements

A communication facilitator keeps discussion productive, and the primary role is "To mediate interpersonal disagreements" so conflicts within the team are resolved and every voice is heard. "To negotiate subcontractor commitments" is procurement work, "To scrutinize individual contributions" is performance management, and "To standardize technical architectures" belongs to a technical lead or architect.

Correct answer: Prioritizing product requirements

The MoSCoW method (Must have, Should have, Could have, Won't have) is used for "Prioritizing product requirements" so the team knows what to deliver first. "Prioritizing organizational risks" is done with probability and impact ratings in a risk assessment, not with MoSCoW categories, which rank requirements. "Evaluating stakeholder engagement" uses an engagement assessment matrix. "Calculating performance variances" is part of earned value analysis, not requirement ranking.

Correct answer: To formally initiate work on the project

"To formally initiate work on the project" is the purpose of a kick-off meeting, which brings the sponsor, team and key stakeholders together to introduce members, confirm objectives, roles and expectations, and mark the official start. To present monthly status on the project is the job of recurring status meetings once work is under way. To review lessons learned on the project happens in retrospectives and at closure, not at the start. To accept change requests on the project is the role of the change control board during monitoring and controlling.

Correct answer: To gauge the practicality and soundness of a proposed project

A feasibility study is carried out "To gauge the practicality and soundness of a proposed project": it examines technical, economic, legal, operational and schedule feasibility before the organization commits to the work. "To establish the budgets and milestones of a proposed project" is planning work done only after the project is approved. "To designate the sponsor and leadership of a proposed project" is done in the project charter. "To document the deliverables and owners of a proposed project" is the work of the scope statement, WBS and responsibility matrix.

Correct answer: To capture lessons learned and formally conclude the project

The closing process aims "To capture lessons learned and formally conclude the project": it obtains final acceptance, archives records, releases resources and records what the organization learned. "To secure sponsor commitment and formally launch the project" happens in initiating, when the charter is issued. "To analyze variance data and formally rebaseline the project" is monitoring and controlling work done through change control. "To decompose work packages and formally schedule the project" is planning work, where activities are defined, sequenced and placed on the schedule long before closure.

Correct answer: Checking that finished deliverables meet the stated scope

Scope verification (now called validate scope) is concerned with "Checking that finished deliverables meet the stated scope" and obtaining the customer's formal acceptance of them. "Ensuring that requested changes update the baseline scope" is scope control through the change process. "Showing that gathered requirements form the planned scope" describes collecting requirements and defining scope during planning. "Ensuring that subdivided packages cover the overall scope" is the 100 percent rule applied when building the WBS during planning.

Correct answer: To judge the change's effectiveness

"To judge the change's effectiveness" is correct: a post-implementation review takes place after the change is in place to evaluate whether it succeeded and met its objectives, and to capture lessons learned. "To apportion the change's resources" is wrong because resources are apportioned before implementation, not reviewed afterward. "To schedule the change's deployment" is wrong because deployment is scheduled before the change goes live. "To reestimate the change's expenses" is wrong because cost estimates are prepared when the change is being approved, not after it has been implemented.

Correct answer: To record successes and improvement areas

A lessons learned session exists "To record successes and improvement areas": what went well and what should change, so later phases and projects benefit. "To approve deliverables and scope changes" describes scope validation and change control decisions, "To appraise individuals and bonus payouts" turns a blameless review into a performance appraisal, and "To rebaseline budgets and milestone dates" is a planning update; none of them captures knowledge for reuse.

Correct answer: Initiation

The project charter is created and the project formally authorized during Initiation, when the sponsor approves the charter and the project manager is assigned. Discovery comes earlier and prepares the business case and feasibility work that justify starting a project. Planning follows authorization and builds the detailed plan from the charter. Deployment is when finished deliverables are released into use, long after authorization.

Correct answer: Planning

Planning is the phase in which the detailed schedule, budget, scope baseline, risk plan and communication plan are developed. Initiation produces only the high-level charter and authorization. Closing formally ends the project after the work is accepted rather than planning it. Deployment releases finished deliverables into use.

Correct answer: Execution

Execution is the phase in which the team performs the planned work and produces most of the deliverables. Discovery assesses the idea and business case before the project starts. Planning defines how the work will be done but does not produce the deliverables. Closing obtains acceptance, records lessons learned and releases resources after the work is complete.

Correct answer: Confirming customer acceptance, capturing lessons learned, and releasing resources

Confirming customer acceptance, capturing lessons learned, and releasing resources is the work of closure: the customer or sponsor accepts the deliverables, the team captures its lessons, and people and resources are released before the project formally ends. Writing project charters, identifying key stakeholders, and securing authorization belong to initiation, when the project is first approved. Decomposing project scope, sequencing related activities, and estimating durations are planning activities. Supervising team members, managing supplier contracts, and generating deliverables describe execution, not closure.

Correct answer: Monitoring and controlling

Monitoring and controlling is the activity that measures actual progress against the schedule and cost baselines, identifies variances, and raises change requests or corrective actions; it runs alongside execution. Authorizing and chartering happen in initiation, before any baseline exists to compare against. Decomposing and sequencing are planning steps that build the baselines rather than measure performance against them. Directing and coordinating describe execution, where the work itself is carried out.

Correct answer: Business case

Business case is the document produced during discovery or pre-initiation to justify the project: it weighs the problem, the proposed solution, costs, benefits, and risks so leaders can decide whether to authorize it. Risk register is wrong because that log tracks identified risks once the project is underway. Status report is wrong because it describes progress on work already in execution. Issue tracker is wrong because it logs problems that have already occurred, not the justification to start.

Correct answer: To align on objectives, roles, and expectations

To align on objectives, roles, and expectations is the purpose: the kickoff brings the team and stakeholders together to align on what the project must achieve, who does what, and how the plan will run before work begins. To decide on changes, deviations, and baselines is the job of a change control board once baselines exist. To report on progress, variances, and forecasts describes a status meeting during execution, when there is progress to report. To reflect on results, shortfalls, and closeout describes a closing or retrospective session, not the start of execution.

Correct answer: Lessons learned register

Lessons learned register is the closure deliverable that captures what went well, what went poorly, and recommendations for future work; it is finalized at closure and kept as an organizational asset. Schedule management plan is a planning document that sets the rules for building and controlling the schedule. Approved change requests record authorized modifications, not reflections on performance. Formal acceptance record documents the customer sign-off on deliverables but does not capture what could be improved.

Correct answer: Closeout

Closeout is the phase in which the customer or sponsor formally signs off that the delivered product meets the agreed requirements; that acceptance is needed before the project can be closed and its resources released. Planning is the phase that sets the requirements and acceptance criteria, long before there is a finished product to accept. Execution is when the product is built, before final acceptance is given. Discovery is the concept phase that builds the business case before any product exists.

Correct answer: Directing project work, coordinating teams, and handling stakeholder engagement

Directing project work, coordinating teams, and handling stakeholder engagement is the focus of execution: the project manager directs and manages the work, coordinates people and resources, and manages stakeholder communications so deliverables are produced to plan. Drafting project charters, identifying sponsors, and obtaining initial approval are initiation tasks. Archiving project records, releasing contractors, and documenting final lessons are closing tasks. Decomposing project scope, sequencing activities, and estimating task durations are planning tasks completed before execution starts.

Correct answer: Discovery, initiation, planning, execution, closing

Discovery, initiation, planning, execution, closing is the Project+ order: discovery (also called concept) builds the business case, initiation charters and authorizes the project, planning sets the detailed scope, schedule, and plans, execution does the work, and closing validates deliverables and formally ends the project. Initiation, concept, planning, executing, closing is wrong because authorization cannot come before the concept work and business case that justify it. Concept, planning, initiation, execution, closure is wrong because detailed planning begins only after the charter is approved in initiation. Discovery, initiation, executing, planning, closure is wrong because the work is executed against the plan, so planning has to come before executing, not after it.

Correct answer: Capital expenditure

Capital expenditure is the right classification: CapEx funds one-time purchases of long-lived assets, which is exactly what the finance director describes. Operational expense (OpEx) covers recurring, day-to-day running costs such as subscriptions and salaries, the opposite of this funding. Management reserves are funds held back for unknown risks, not a category for a planned asset purchase. Contingency reserve is money set aside for identified risks, not a way to classify how the purchase itself is funded.

Correct answer: An SOW

An SOW is right: a client statement of work is the document the client writes to define what the vendor must deliver, and Project+ lists it, alongside client terms of reference, among the preexisting contract documents reviewed in discovery. An MOU is a memorandum of understanding that records broad mutual intent, not a definition of vendor deliverables. An LOI is a letter of intent signaling a planned award before any contract exists. An RFI is a request for information used to learn what vendors can offer, not to specify the work they must deliver.

Correct answer: The charter grants formal authority and sets broad objectives, while the scope statement defines inclusions and exclusions

The charter grants formal authority and sets broad objectives, while the scope statement defines inclusions and exclusions: the charter is the initiation artifact that authorizes the project and gives the project manager authority, and the detailed scope statement is refined in planning to state exactly what is and is not included. The scope statement empowers managers and outlines general goals, while the charter lists exact deliverables and omissions reverses the two documents. The charter monitors budget overruns and incurred costs, while the scope statement records approved changes and deviations describes cost reports and the change log, not either document. The charter ends technical design and locks baselines, while the scope statement precedes sponsor review and authorization inverts the timing, since the charter comes first and the detailed scope statement follows in planning.

Correct answer: Responsible, Accountable, Consulted, Informed

Responsible, Accountable, Consulted, Informed is the RACI expansion: who does the work, who owns the outcome, who gives input, and who is kept up to date. It is the most common form of a responsibility assignment matrix. Responsible, Assigned, Communicated, Involved swaps in words that are not the standard RACI roles for the A, C, and I. Reviewed, Accountable, Copied, Included replaces the R, C, and I with nonstandard terms. Reviewed, Approved, Consulted, Informed misnames the first two roles, confusing doing the work with reviewing it and owning the outcome with approving it.

Correct answer: Responsibility assignment matrix (RAM)

Responsibility assignment matrix (RAM) is the formal name: a RAM maps project activities to the people who perform, own, or support them, and RACI is its most widely used format. Requirements traceability matrix (RTM) links each requirement to its source and to the deliverables and tests that satisfy it, not to people. Work breakdown structure (WBS) decomposes scope into work packages but does not assign roles. Risk breakdown structure (RBS) groups risks by category and has nothing to do with task ownership.

Correct answer: One individual

One individual should be marked Accountable for any single task, so there is never doubt about who ultimately owns the outcome; several people may be Responsible for doing the work, but accountability is not shared. Several owners spreads accountability and defeats the purpose of the matrix. Dual approvers still splits ownership between two people, which reintroduces the confusion RACI is meant to remove. Senior leaders as a group cannot hold accountability either, because the rule is one accountable person per task, not a leadership tier.

Correct answer: A stakeholder register

A stakeholder register is the document created when stakeholders are identified during initiation; it records each one's role, interest, influence, and contact details so engagement can be planned. A stakeholder heatmap is a visual that plots stakeholders by power or interest but does not serve as the full record of each person's role and details. A stakeholder profile describes a single stakeholder or persona rather than listing everyone identified. A communication matrix sets what information goes to whom and how often, not who the stakeholders are.

Correct answer: Study the charter and business case, then interview sponsors and experts to find affected and powerful parties

Study the charter and business case, then interview sponsors and experts to find affected and powerful parties is the sound approach: reviewing existing artifacts and interviewing sponsors and subject matter experts surfaces everyone who is affected by the project or able to affect it, early enough to plan engagement. Recycle the register and contact lists, then email sponsors and managers to confirm known and earlier contacts copies an old list and misses stakeholders unique to this project. Scan the budget and approval records, then interview sponsors and executives to find funded and senior signers limits the search to people with budget authority. Await the kickoff and status reviews, then question attendees and vendors to record vocal and worried factions waits too long and catches only those who speak up, leaving quieter but influential parties unidentified.

Correct answer: A kickoff meeting

A kickoff meeting launches the project by introducing team members, aligning everyone on objectives and scope, and confirming roles and expectations. A standup meeting is a short daily check-in on progress and blockers once work is underway. A cutover meeting coordinates the switch to a new system at go-live, near the end of the project. A handoff meeting transfers a finished product to operations or the next team, not the start of the project.

Correct answer: Defining approved communication methods

Defining approved communication methods is the activity described: setting the accepted channels the team and stakeholders will use, early in initiation, so information flows consistently before detailed planning begins. Defining records retention requirements concerns how long documents are kept, part of records management rather than how people share information. Defining repository access requirements covers who may open project files and systems, not which channels people use to communicate. Defining team responsibility allocation assigns roles, as a RACI chart does, rather than choosing communication channels.

Correct answer: A records management plan

A records management plan addresses how project data and documents are stored, retained, and accessed, including access requirements, so information is controlled from the outset. A quality management plan sets quality standards and how they will be assured and controlled. A release management plan schedules and controls how product releases are deployed. A program management plan coordinates several related projects and does not set rules for storing this project's records.

Correct answer: Work breakdown structure (WBS)

Work breakdown structure (WBS) is the result: a hierarchy that decomposes the entire project scope into progressively smaller, deliverable-oriented components down to work packages that can be estimated, assigned, and tracked. Risk breakdown structure (RBS) is a hierarchy of risk categories, not of the scope. Cost breakdown structure (CBS) organizes costs by account rather than decomposing the deliverables. Arrow diagramming method (ADM) is a scheduling network technique that shows activity sequence, not a decomposition of scope.

Correct answer: Design, development, content, and testing deliverables, each split into work packages

Design, development, content, and testing deliverables, each split into work packages is a correct WBS decomposition: a WBS organizes the deliverables of the website into a hierarchy of progressively smaller components down to work packages, such as wireframes, coding, and QA. Designers, developers, writers, and testers, each gathered into department work units decomposes the organization, which is an organizational breakdown structure rather than a WBS. Kickoff, construction, launch, and review milestones, each translated into work weeks is a timeline or schedule, not a breakdown of deliverables. Hosting, cybersecurity, financial, and vendor risks, each ranked into severity levels is a ranked risk list, not a work breakdown structure.

Correct answer: A product backlog

A product backlog is the prioritized list of features and requirements used to define units of work on agile projects, in place of a WBS on predictive ones; items are refined and pulled into iterations by priority. A product roadmap shows the high-level direction and timing of releases, not the itemized, prioritized work. A project charter authorizes the project and records high-level objectives. A project mandate is the trigger that asks for a project to be started, not a list of work items.

Correct answer: A communication plan

A communication plan defines what information goes to whom, how often, and through which methods, including the meeting cadence. A resource histogram charts how many people or hours are needed per period. A milestone schedule lists key dates and events but does not set how information is distributed. A stakeholder matrix classifies stakeholders by power or interest rather than specifying distribution methods and cadence.

Correct answer: A project scope statement

A project scope statement is the planning document that defines the deliverables, boundaries, assumptions, and explicit exclusions so everyone agrees on what is and is not included, which helps prevent scope creep. A project closeout report summarizes results at the end of the project. A project network diagram shows the sequence and dependencies of activities. A project assumptions log tracks assumptions and constraints but does not define deliverables, boundaries, or exclusions.

Correct answer: A quality management plan

A quality management plan, often called the QA plan in Project+ planning, describes the quality standards the deliverables must meet and how quality will be planned, assured, and controlled. A quality audit checklist is a tool used during audits to verify specific items, not the plan for the whole quality approach. A quality defect register logs defects found during control activities. A quality metrics summary reports measured results after work is performed rather than planning how quality will be managed.

Correct answer: Building the detailed schedule

Building the detailed schedule is the activity described: in planning, the schedule is developed by sequencing activities, applying duration estimates, and setting cadences such as sprint or release cycles to fix when work will occur. Building the requirements list captures what the product must do, not when work happens. Building the quality checklist defines items to verify for quality, not the timeline. Building the budget allocation uses estimates to assign costs, but it answers how much the work costs rather than when it occurs.

Correct answer: List activities, link dependencies, estimate durations, then assign resources and dates

List activities, link dependencies, estimate durations, then assign resources and dates best reflects building a schedule: activities are defined from the WBS, sequenced by their dependencies, given duration estimates, and then resourced and placed on the timeline. Impose deadlines, apportion time, allocate personnel, then append tasks and checkpoints works backward from an imposed end date and ignores real durations and dependencies. Reserve personnel, block calendars, collect requests, then position tasks and timelines starts from resource availability before the work has been defined. Calculate budgets, secure sponsorship, sketch tasks, then approve outlays and baselines builds the cost budget first and never sequences or times the activities.

Correct answer: A baseline

A baseline is the approved version of the scope, schedule, or cost against which actual performance is measured; it is set during planning as part of the project management plan and changes only through formal change control. A forecast is a prediction of future results, such as an estimate at completion, and it changes as work progresses. A template is a reusable format for documents, not an approved version of this project's plans. A contract is a legal agreement with a supplier or customer, not the internal reference used to measure performance.

Correct answer: The cost baseline is approved phased expenditure for tracking performance, while the total budget adds management reserves held separately

The cost baseline is approved phased expenditure for tracking performance, while the total budget adds management reserves held separately: contingency reserves for known risks sit inside the time-phased cost baseline, while management reserves for unknown risks are held outside it, so the total budget is larger. The cost baseline is budgeted outlay including management reserves for unknown risks, while the total budget excludes contingency reserves reverses where the two reserves sit. The cost baseline is actual disbursements recorded for accomplished work, while the total budget forecasts probable final project spending confuses the baseline with actual cost and the budget with an estimate at completion. The cost baseline is negotiated vendor contract sums for outsourced deliverables, while the total budget carries internal staffing outlays mistakes a procurement figure for the baseline, which covers all approved project costs.

Correct answer: A milestone marks a significant point with zero duration, while a deliverable is an output the project produces

A milestone marks a significant point with zero duration, while a deliverable is an output the project produces: milestones such as design approved carry no work effort, whereas deliverables are the tangible or intangible products or results. A milestone delivers a tangible result with team effort, while a deliverable is an instant the schedule records reverses the two terms: it is the deliverable that takes effort to produce and the milestone that is an instant of zero duration. A milestone labels a product with formal sponsor acceptance, while a deliverable is an artifact the team drafts wrongly ties milestones to acceptance and deliverables to drafts, when a deliverable is any produced output. A milestone releases a payment with final client approval, while a deliverable is an invoice the vendor submits confuses milestones with billing events and deliverables with invoices.

Correct answer: A transition plan

A transition plan, also called a release plan, is developed during planning to cover operational training, go-live, and the operational handoff so the product can move into production use. A continuity plan keeps the business running through a disruption, not a product launch. A validation plan sets how deliverables will be tested against requirements, without covering training or handoff. A mitigation plan lists actions to reduce specific risks rather than moving the product into operations.

Correct answer: To identify and analyze likely risks so responses and reserves are planned upfront

To identify and analyze likely risks so responses and reserves are planned upfront is the purpose: an initial risk assessment in planning lets the team build response strategies and contingency reserves into the plan before work begins. To monitor and report realized risks so owners and sponsors are informed regularly describes ongoing risk monitoring during execution, not the initial assessment. To close and archive resolved risks so lessons and records are preserved centrally is a closing activity. To transfer and insure costly risks so vendors and insurers are contracted quickly names one possible response, which can be chosen only after risks have been identified and analyzed.

Correct answer: Approved plans, baselines, and a schedule that direct how the project is executed and controlled

Approved plans, baselines, and a schedule that direct how the project is executed and controlled is the output of planning, which turns the authorized charter into a detailed roadmap of scope, schedule, cost, quality, risk, and communication plans. Signed charters, mandates, and a sponsor that authorize how the project is launched and financed are initiation outputs. Finished deliverables, products, and a handover that show how the project is built and delivered come from execution. Accepted deliverables, archives, and a closeout that note how the project is reviewed and closed are closing outputs.

Correct answer: Execution

Execution is the phase in which the team carries out the work in the project management plan to create the deliverables, while the project manager manages vendors, meetings, conflict, and reporting. Planning produces the plans the team is now following, so it is already complete. Discovery builds the business case before the project is authorized. Closeout validates and formally finishes the work after the deliverables are done.

Correct answer: Driving organizational change management

Driving organizational change management is the activity described: during execution it handles the people side of the change through training, communication, reinforcement, and new knowledge bases so the organization actually adopts the new processes. Drafting stakeholder communication plans is a planning task that decides who receives which information; it does not train users or reinforce adoption. Conducting procurement compliance audits checks that vendors meet contract terms. Performing quality assurance inspections checks that work processes and outputs meet quality standards, not that staff adopt new ways of working.

Correct answer: Deliverable approval

Deliverable approval is the vendor-management activity described: during execution the project manager confirms that what the vendor delivered meets the agreed requirements and then formally accepts it. Contract termination ends the vendor agreement, which is not what happens when an acceptable component arrives. Source qualification screens potential suppliers before any contract is awarded. Invoice verification matches the vendor's bill to the order and receipt for payment; it does not judge whether the component meets requirements.

Correct answer: A status report

A status report is the concise document that tells stakeholders the current progress, accomplishments, issues, and upcoming work as part of tracking and reporting during execution. A risk register records identified risks, their ratings, owners, and responses rather than summarizing progress. A resource plan describes how people and equipment will be acquired and assigned. A project brief is a short overview of the project's purpose and goals written at the start, not a periodic progress update.

Correct answer: A stage gate review

A stage gate review, also called a phase gate review, is the formal decision point between phases where stakeholders judge whether the project has met the criteria to continue, hold, or stop before entering the next phase. A risk audit review examines how well risk responses and risk processes are working, not whether the project may advance. A vendor bid review evaluates seller proposals during procurement. A change board vote decides whether individual change requests are approved, not whether the project may move to the next phase.

Correct answer: Ordering rework, suspending progress, or terminating outright

Ordering rework, suspending progress, or terminating outright is consistent with a phase gate: it is a go/no-go decision point, so a committee that finds the criteria unmet can require rework, put the project on hold, or cancel it before more resources are committed. Proceeding anyway, documenting gaps, or deferring remediation treats the gate as a formality that never stops the project. Granting waivers, lowering criteria, or approving advancement turns the gate into a rubber stamp that passes a project that failed its criteria. Revising charters, swapping sponsors, or reopening initiation sends the project back to its start; an unmet gate calls for a decision on the current phase, not a new initiation.

Correct answer: Because ongoing work revises budget and timeline figures as measured progress and approved changes occur

Because ongoing work revises budget and timeline figures as measured progress and approved changes occur: execution includes keeping the budget and timeline current as work is performed and changes are approved. Because closing work locks budget and timeline figures as acceptance records and signed contracts arrive describes the closing phase, and this project is not closing. Because planning work freezes budget and timeline figures as signed baselines and sponsor orders require is false, since baselines can be revised through change control. Because chartering work drafts budget and timeline figures as business cases and sponsor demands dictate describes initiation, which produces only high-level summary figures and is long over by the time slippage is tracked.

Correct answer: Collaborating

Collaborating (problem-solving) works through the differences to reach a solution that satisfies all parties' underlying needs, which is what the project manager is doing. Compromising finds a middle ground where each side gives something up, so no one is fully satisfied. Accommodating, also called smoothing, plays up areas of agreement and concedes to the other side. Withdrawing, also called avoiding, sidesteps or postpones the conflict.

Correct answer: Scope validation

Scope validation is the closing activity described: validating the deliverables means obtaining the customer's formal acceptance that the completed deliverables meet the agreed acceptance criteria before the project is signed off. Contract closure settles and formally ends vendor agreements; it does not obtain the customer's acceptance of the project's own deliverables. Product handover transfers accepted work to operations or the customer, which follows acceptance rather than obtaining it. Records archival stores project documentation for future reference.

Correct answer: It secures documented customer acceptance, enabling signoff and preventing later disputes

It secures documented customer acceptance, enabling signoff and preventing later disputes: validating deliverables in closing confirms that the customer formally accepts the work as meeting requirements, so the project can be signed off and the organization is protected from later disagreement. It captures recorded lessons learned, sharpening estimates and reducing repeated mistakes describes the lessons-learned activity, not validation. It returns borrowed specialists elsewhere, freeing capacity and lowering overhead expense describes releasing resources. It settles unpaid supplier invoices, closing procurements and releasing retained payments describes contract closure with vendors rather than customer acceptance of the deliverables.

Correct answer: Validate deliverables, close contracts, revoke access, release resources, archive records, reconcile budgets, and secure signoff

Validate deliverables, close contracts, revoke access, release resources, archive records, reconcile budgets, and secure signoff is the closure checklist: these are the formal wrap-up tasks of the closing phase. Sequence activities, estimate durations, baseline scope, plan quality, register risks, schedule personnel, and allocate reserves lists planning work. Draft charters, identify stakeholders, assess feasibility, define objectives, appoint sponsors, weigh benefits, and run kickoffs lists initiation work. Direct teams, distribute updates, assure quality, conduct procurements, engage stakeholders, implement changes, and track issues lists execution work.

Correct answer: Rescinding privileges

Rescinding privileges is the closing step described: the system permissions and physical access granted for the project are withdrawn so they cannot be used after the work ends, an important security and governance task. Terminating contracts formally ends vendor agreements and does not touch team members' access. Releasing contractors returns people to their employers or pools; it frees the people, but their logins and badges still have to be revoked separately. Consolidating records gathers project documentation for the archive.

Correct answer: Cost reconciliation

Cost reconciliation is the closing activity described: actual spending is compared with the approved budget and any outstanding financial items are settled so the project's finances can be formally closed. Expense projections forecast future spending while work is still under way. Budget disbursement pays out approved funds as work proceeds; it spends the budget rather than closing out the accounts. Contingency release draws on reserves to cover realized risks during execution and does not settle the final accounts.

Correct answer: Formally ending the project by validating deliverables, securing signoff, settling contracts, freeing resources, and recording lessons

Formally ending the project by validating deliverables, securing signoff, settling contracts, freeing resources, and recording lessons describes the closing phase: the orderly wrap-up that confirms acceptance, closes agreements, frees people, and captures lessons learned. Actively executing the project by directing work, managing personnel, engaging contractors, distributing updates, and assuring quality describes the execution phase. Thoroughly shaping the project by defining requirements, sequencing tasks, estimating costs, baselining schedules, and analyzing risks describes planning. Initially justifying the project by assessing feasibility, building cases, naming sponsors, drafting charters, and estimating benefits describes discovery and initiation.

Correct answer: Project charter

The Project charter is the initiating document that formally authorizes the project and records its high-level scope, objectives and participants, including the sponsor and the project manager's authority. The Scope statement is written later in planning and details deliverables, exclusions and acceptance criteria, but it does not name the participants or authorize the project. A Project calendar only sets the working days and shifts available for scheduling. A Project schedule lists activities with dates and dependencies; it does not define objectives or participants.

Correct answer: Timing and monitoring project activities

A Gantt chart is a bar chart of activities against a calendar, used for "Timing and monitoring project activities": it shows each task's start, finish and duration and lets the team track progress against plan. Prioritizing and assessing project risks is done with a risk register and a probability-impact matrix. Ranking and categorizing project defects is the job of a Pareto chart. Allocating and clarifying project duties is the job of a RACI chart, which shows who does what but not when.

Correct answer: The minimum achievable duration for the project

The Critical Path Method finds the longest chain of dependent activities, and that chain sets "The minimum achievable duration for the project". It does not identify "The cheapest execution strategy for the project"; cost is analyzed separately, for example when crashing is priced. The optimal resource allocation for the project comes from resource planning and leveling, which may even lengthen the critical path. The acceptable quality criteria for the project are set in quality planning.

Correct answer: Clarifying member duties and task ownership

A RACI chart is a responsibility assignment matrix used for "Clarifying member duties and task ownership": for each task it shows who is Responsible, Accountable, Consulted and Informed. Logging defect rates and inspection results is quality control work recorded in quality reports. Choosing report formats and update channels is done in the communications management plan. Mapping activity durations and finish dates is the job of the schedule, such as a Gantt chart.

Correct answer: Change management plan

The Change management plan is the document that describes how changes will be requested, reviewed, approved, implemented and controlled across the project. A Change impact analysis assesses the effect of one proposed change on scope, schedule and cost; it does not set the overall process. A Change request tracker (change log) lists the changes that have been submitted and their status. A Change approval record captures the decision on one change after review.

Correct answer: To log interested parties and their profiles

A stakeholder register exists "To log interested parties and their profiles": it lists each identified stakeholder with details such as role, interests, expectations and influence. "To log unresolved issues and their assignees" is the purpose of the issue log. "To log prioritized risks and their responses" is the purpose of the risk register. "To log requested changes and their decisions" is the purpose of the change log.

Correct answer: Gantt Chart

A Gantt Chart draws each task as a bar along a timeline, so it shows the sequence and duration of tasks across the project schedule. A RACI Chart is a responsibility matrix showing who is Responsible, Accountable, Consulted and Informed. A Kanban Board shows work items moving through workflow columns such as to do, doing and done, with no time scale. A Burnup Chart plots completed work against total scope over time; it does not show individual task bars or their sequence.

Correct answer: To display unfinished iteration work per day

A burndown chart is used "To display unfinished iteration work per day": it plots the work remaining in the sprint against time so the team can see whether it will finish. "To display averaged team velocity per sprint" is the job of a velocity chart. "To display open defect frequencies per cause" is what a Pareto chart does. "To display actual project expenses per month" is a cost or spending report, not an Agile progress chart.

Correct answer: Measuring project performance against the baselines

Earned value analysis is used for "Measuring project performance against the baselines": it compares planned value, earned value and actual cost to give schedule and cost variances and performance indices. "Evaluating project contractors against the criteria" is source selection in procurement. "Ranking project requirements against the objectives" is requirements prioritization. "Checking project outputs against the specifications" is quality control inspection, which looks at the product rather than at cost and schedule performance.

Correct answer: Project management plan

The Project management plan is the document that outlines the objectives, scope, approach and implementation of the project, bringing the subsidiary plans and baselines together to guide execution and control. The Project scope statement describes scope and deliverables in detail but not the approach for carrying out the whole project. The Project charter summary restates the high-level objectives and scope that authorize the project, but it is written before planning and does not set out the approach or how the work will be implemented. The Project progress report describes performance to date, not how the project will be carried out.

Correct answer: Analogous estimating

Correct answer: Analogous estimating. Explanation: Analogous estimating uses the actual duration and cost of a similar past project as the basis for the new estimate, which makes it the historical-data technique used early when detail is limited. Three-point estimating averages optimistic, most likely and pessimistic values for an activity rather than drawing on a past project. Affinity estimating is an Agile relative-sizing method in which the team groups backlog items by comparative size. Definitive estimating refers to the most accurate class of estimate, prepared late from detailed design, not to a technique based on past projects.

Correct answer: Communication management plan

"Communication management plan" is correct: this component of the project management plan sets out how project communications will be planned, structured, monitored and controlled, including methods, frequency, audiences and protocols. "Configuration management plan" is wrong because it governs how product and document versions are identified and controlled, not how communications are handled. "Procurement management plan" is wrong because it governs how goods and services are acquired from outside the project. "Stakeholder management plan" is wrong because it sets strategies for engaging stakeholders; the detailed rules for how information is distributed and controlled sit in the communications plan.

Correct answer: To guide stakeholder involvement and expectations

"To guide stakeholder involvement and expectations" is correct: a stakeholder engagement plan sets the strategies and actions for involving stakeholders in decisions and managing their expectations throughout the project. "To record stakeholder contacts and classification" is wrong because contact details and classification are recorded in the stakeholder register. "To document stakeholder requirements and criteria" is wrong because requirements and acceptance criteria are captured in the requirements documentation. "To administer stakeholder contracts and purchases" is wrong because contracts and purchases are handled under procurement management.

Correct answer: Logging project deliverable versions

A configuration management system controls the versions of project deliverables, so its primary role is "Logging project deliverable versions": every approved change to a deliverable is documented and the current baseline stays identifiable. "Logging project resource allocations" is the job of resource management tools, "Logging project quality measurements" is part of quality control, and "Logging project unresolved obstacles" is what an issue log does; none of them documents how deliverables change.

Correct answer: Depicting task dates and dependencies

A Gantt chart plots each activity as a bar against a calendar, so its benefit in communication is "Depicting task dates and dependencies": everyone can see start and finish dates and which tasks link to which. "Ranking defect causes and frequencies" describes a Pareto chart, "Rating risk probabilities and impacts" describes a probability and impact matrix, and "Charting scope hierarchy and packages" describes a work breakdown structure.

Correct answer: Project scope statement

The "Project scope statement" manages stakeholder expectations because it states the deliverables, acceptance criteria and exclusions, so stakeholders know exactly what will and will not be delivered. A "Project budget estimate" forecasts cost and says nothing about what stakeholders will receive. A "Project charter summary" records only the high-level requirements and success criteria agreed at authorization, too broad to show whether each detailed requirement is being met. A "Project risk assessment" evaluates uncertain events rather than defining what will be delivered.

Correct answer: Power/interest matrix

The "Power/interest matrix" (the stakeholder power/interest grid) plots each stakeholder by authority and by level of interest, which is exactly the influence and interest the question names. The "Influence/impact grid" plots involvement against ability to cause change, not interest; the "Likelihood/impact map" is a risk heat map that rates risks, not people; and the "Value/effort quadrant" ranks work by value against effort; neither of those last two maps stakeholders at all.

Correct answer: To pinpoint the sources of quality problems

A fishbone (Ishikawa, cause-and-effect) diagram is used "To pinpoint the sources of quality problems" by grouping possible root causes under categories. "To rank the frequency of failure categories" describes a Pareto chart, "To monitor the variation of process outputs" describes a control chart, and "To illustrate the sequence of process steps" describes a flowchart.

Correct answer: To track proposed modifications and their status

A change log exists "To track proposed modifications and their status": every change request is recorded and monitored from submission through approval or rejection. "To track potential threats and their mitigations" is the risk register, "To track unresolved issues and their resolutions" is the issue log, and "To track stakeholder concerns and their priority" is the stakeholder register.

Correct answer: Engagement assessment matrix

The "Engagement assessment matrix" (stakeholder engagement matrix) shows each stakeholder's current and desired engagement, so it is the tool for managing and visualizing stakeholder relationships. The "Resource breakdown structure" groups resources by category and type, the "Requirements management plan" explains how requirements will be handled, and "Work performance information" is analyzed performance data; none of them maps stakeholders.

Correct answer: Complete Scope Statement

The "Complete Scope Statement" (the project scope document) sets out the deliverables and the measurable acceptance criteria, both qualitative and quantitative, that the project must meet. The "Project Charter Document" authorizes the project with only high-level requirements, the "Resource Management Plan" explains how people and equipment are acquired and managed, and the "Project Status Dashboard" reports progress; none of them defines the acceptance criteria.

Correct answer: Fishbone Diagram

The "Fishbone Diagram" (Ishikawa or cause-and-effect diagram) displays the possible causes of a problem grouped on branches, showing how they relate, so it is the tool for finding a root cause. A "Pareto Diagram" ranks causes by frequency only after they are known. An "Affinity Diagram" sorts brainstormed ideas into groups of similar items, but it does not trace them back to a problem as causes or show how they relate to it. A "Scatter Diagram" plots two variables to show whether they are correlated, so it tests one suspected relationship at a time rather than laying out the various causes of a problem.

Correct answer: Configuration Management System

A "Configuration Management System" identifies each version of project documents and deliverables and records every approved change to them, so it is the tool for managing and tracking those changes. A "Communications Management System" distributes project information, an "Infrastructure Management System" monitors servers and networks, and a "Knowledge Management System" stores lessons and expertise; none of them controls versions of deliverables.

Correct answer: Scope Statement

The "Scope Statement" gives a detailed description of the deliverables, acceptance criteria, exclusions and assumptions, so stakeholders understand exactly what the project will produce. The "Project Charter" authorizes the project with only high-level objectives. The "Budget Forecast" projects costs rather than outcomes. The "Business Case" justifies the investment by weighing expected benefits against costs before approval, but it does not detail the deliverables the project will produce.

Correct answer: To plot unfinished work versus time

A burndown chart exists "To plot unfinished work versus time" in a sprint or project, so the team can see whether the work left is falling fast enough to finish. "To plot defect counts versus causes" describes a Pareto chart, "To plot staff hours versus capacity" describes a resource histogram, and "To plot actual cost versus forecast" describes a cost performance chart; none of them shows work remaining.

Correct answer: Cost Benefit Analysis

A "Cost Benefit Analysis" (cost-benefit analysis) sets the costs of each candidate solution against its benefits, so it is the tool for comparing the advantages and disadvantages of alternatives. "Earned Value Analysis" measures schedule and cost performance on work already under way, "Process Flow Analysis" examines the steps of a process, and "Resource Gap Analysis" compares available skills with required skills; none of them weighs alternative solutions.

Correct answer: To highlight major schedule checkpoints

A milestone chart exists "To highlight major schedule checkpoints": it shows the significant events in the project timeline without activity detail. "To document detailed activity durations" is what a Gantt chart does, "To record individual member assignments" is the role of a responsibility assignment matrix, and "To summarize cumulative scope additions" belongs to scope change reporting.

Correct answer: Network Diagram

A project schedule "Network Diagram" shows activities as nodes linked by arrows, so it outlines their sequence and interdependencies. A "Milestone Chart" shows only key dates, an "Effort Estimate" gives how much work each activity needs, and a "Resource Roster" lists who is available; none of them maps the logical links between activities.

Correct answer: To sanction the initiative and state its goals

The Project Charter exists "To sanction the initiative and state its goals": it formally authorizes the project, names the project manager and sets out the objectives. "To decompose the scope and define its packages" is the work breakdown structure, "To settle the contract and archive its records" belongs to procurement closure, and "To build the schedule and monitor its progress" is schedule development and control.

Correct answer: To split the effort into manageable components

A Work Breakdown Structure (WBS) exists "To split the effort into manageable components": it decomposes the total work into smaller work packages that can be estimated, assigned and controlled. "To aggregate the estimates into cost baselines" is cost budgeting, "To group the stakeholders into priority levels" is stakeholder analysis, and "To order the activities into logical sequences" is activity sequencing in a network diagram; the WBS shows what work exists, not its order or cost.

Correct answer: Change Log

The "Change Log" captures every change request to the scope, records its priority and decision, and tracks it to closure. The "Issue Log" tracks current problems that need resolution, the "Decision Log" records decisions and who made them, and the "Incident Log" records operational service disruptions; none of them is the register of scope changes.

Correct answer: To find the minimum possible completion time

The Critical Path Method (CPM) identifies the longest chain of dependent activities, and that chain fixes the shortest time in which the project can finish, so its function is "To find the minimum possible completion time". "To find the weighted average activity length" is the PERT three-point calculation, "To find the cumulative planned cost baseline" is cost budgeting for earned value, and "To find the maximum concurrent resource load" comes from a resource histogram; CPM itself uses single duration estimates and ignores cost and resources.

Correct answer: To gauge the influence of interested parties

A Stakeholder Analysis Matrix exists "To gauge the influence of interested parties": it identifies stakeholders and assesses their power, interest and impact on the project so engagement can be planned. "To specify the ownership of individual tasks" is a RACI or responsibility assignment matrix, "To record the decisions of governance boards" is a decision log, and "To establish the boundaries of project scope" is the scope statement.

Correct answer: Earned Value Management (EVM)

Earned Value Management (EVM) compares planned value, earned value and actual cost to date, and indices such as CPI and SPI turn that past performance into forecasts like estimate at completion. Critical Path Method (CPM) finds the longest chain of dependent activities and the float on each, not a forecast from performance data. Total Quality Management (TQM) is an organization-wide quality philosophy of continuous improvement, not a performance forecasting technique. Agile Project Management (APM) is an iterative delivery approach built on short cycles and adaptive planning, not a technique that forecasts cost or schedule from earned results.

Correct answer: Project Management Plan

The Project Management Plan integrates the baselines and all subsidiary plans and describes how the project will be executed, monitored, controlled and closed, so it is the guideline for execution and control. The Signed Project Charter formally authorizes the project and records its high-level objectives, requirements and sponsor, but it does not set out how the work will be executed and controlled. The Risk Management Plan describes only how risk activities will be structured and performed, so it is one subsidiary component rather than the integrated guide to execution and control. The Project Scope Statement records the scope, deliverables, acceptance criteria, assumptions and exclusions, but it is one baseline input, not the document that guides how the whole project is executed and controlled.

Correct answer: To set the means and cadence for project updates

A Communication Plan defines who receives which information, by which methods and how often, so its purpose is To set the means and cadence for project updates. To set the budget and reserves for project costs is the job of the cost management plan and cost baseline. To set the triggers and owners for project risks belongs to the risk management plan and risk register. To set the limits and baseline for project scope is done by the scope management plan and scope baseline, not by the Communication Plan.

Correct answer: To display workforce usage across each period

A Resource Histogram is a bar chart of the resource units required or assigned in each time period, so its function is To display workforce usage across each period and reveal overallocation. To display defect counts across each category describes a Pareto chart. To display task durations across each quarter describes a Gantt chart of the schedule. To display cumulative spend across each month describes an S-curve of the cost baseline, not resource loading.

Correct answer: Control Chart

A Control Chart plots a measured value in time order against a mean and upper and lower control limits, so it shows trends and variances over time. A Pareto Chart ranks categories of causes by frequency and has no time axis. A Gantt Chart shows scheduled activities against a calendar, not measured variance of a process. A Scatter Chart plots one variable against another to show correlation rather than change over time.

Correct answer: To record insights acquired for reuse by successor teams

A Lessons Learned Document captures what went well and what did not during the project, so its purpose is To record insights acquired for reuse by successor teams. To record changes requested for review by control boards is the purpose of a change log. To record threats identified for response by risk owners is the purpose of a risk register. To record problems raised for resolution by issue owners is the purpose of an issue log, which tracks current problems rather than knowledge for future work.

Correct answer: To estimate probabilities of risk scenarios

Monte Carlo simulation runs a schedule or cost model thousands of times with randomly sampled inputs, so its function is To estimate probabilities of risk scenarios such as the chance of finishing by a date or within a budget. To identify sequences of chained activities is done with a network diagram and the critical path method. To order frequencies of customer complaints is done with a Pareto chart. To assign ownership of project deliverables is done with a responsibility assignment matrix, not a simulation.

Correct answer: Bottom-Up Estimating

Bottom-Up Estimating estimates each work package or activity and then sums those figures upward through the WBS into a total, which is the aggregation the question describes. Top-Down Estimating starts from a total taken from a similar past project and works downward, so it does not aggregate detailed costs. Three-Point Estimating averages optimistic, most likely and pessimistic values for a single estimate rather than summing many. Activity-Based Costing is an accounting method that allocates overhead to activities by their cost drivers; it assigns indirect costs rather than summing work package estimates into a project budget.

Correct answer: Requirements Traceability Matrix

The Requirements Traceability Matrix lists each requirement with its attributes and specification details and links it to the deliverable that satisfies it, so it records requirements down to the deliverable level. The Requirements Management Plan describes how requirements will be gathered, analyzed and managed, not the requirements themselves. A Requirements Acceptance Checklist lists the sign-off conditions a customer checks at handover rather than recording each requirement and its specification. A Requirements Validation Checklist lists the review questions used to confirm requirements are complete and testable; it is a quality aid, not the record of the requirements.

Correct answer: To compare expected values of possible choices

A Decision Tree maps each decision and its chance outcomes with probabilities and payoffs, so its purpose is To compare expected values of possible choices. To compare root causes of recurring breakdowns is done with a cause-and-effect diagram. To compare actual costs of completed contracts is a cost variance or procurement audit task. To compare skill levels of available employees is done with a skills matrix during resource planning, not with a Decision Tree.

Correct answer: To group uncertainties by source category

A Risk Breakdown Structure is a hierarchy of risk categories and subcategories by source, such as technical, external, organizational and management, so its purpose is To group uncertainties by source category. To group deliverables by hierarchy levels describes the work breakdown structure. To group expenditures by control accounts describes a cost breakdown structure. To group personnel by organizational unit describes an organizational breakdown structure, not the Risk Breakdown Structure.

Correct answer: To stop unapproved changes to planned deliverables

A Scope Creep Management Plan exists to keep work from growing beyond the approved baseline without going through change control, so its function is To stop unapproved changes to planned deliverables. To route stakeholder updates to project recipients is the role of the communications management plan. To assign trained personnel to upcoming activities is handled by the resource management plan. To charge incurred expenditures to budget accounts is part of cost control, not scope control.

Correct answer: Flowchart

A Flowchart, also called a process map, shows the steps, decisions, inputs and outputs of a process and how work flows between them. A Histogram is a bar chart of how often values fall into each range and shows no sequence of steps. A Scatter Diagram plots pairs of values to show whether two variables are correlated and shows no inputs, outputs or process steps. A Network Diagram does show a flow, but of schedule activities and their dependencies, used to find the critical path; it does not trace inputs and outputs through processes.

Correct answer: To reach consensus via anonymous expert rounds

The Delphi Technique sends questionnaires to experts who answer anonymously, see the summarized responses fed back, and repeats until opinions converge, so its purpose is To reach consensus via anonymous expert rounds. To rank alternatives via weighted group voting describes nominal group technique or multicriteria decision analysis, where members vote openly together. To cluster brainstormed ideas via theme labels describes an affinity diagram. To trace failures via causal category branches describes a fishbone (cause-and-effect) diagram.

Correct answer: To link each activity to responsible members

A Responsibility Assignment Matrix (RAM), such as a RACI chart, crosses work packages or activities with team members, so its main purpose is To link each activity to responsible members. To link each requirement to acceptance tests is the job of a requirements traceability matrix. To link each threat to probability estimates is done with a probability and impact matrix during risk analysis. To link each stakeholder to influence levels is done with a power/interest grid or stakeholder register.

Correct answer: Governance, Risk, and Compliance

In an IT environment GRC stands for Governance, Risk, and Compliance: setting direction and oversight, managing risk, and meeting legal, regulatory and policy requirements in one coordinated program. Governance, Reporting, and Costs is a misreading that swaps in financial reporting and cost terms. Governance, Roles, and Contracts confuses GRC with organizational and procurement topics. Governance, Release, and Control mixes in release management, which is a service management practice rather than part of the acronym.

Correct answer: GDPR

The GDPR (General Data Protection Regulation) is the European Union regulation that governs the processing of personal data and the privacy rights of individuals in the EU. The CCPA is a California state privacy law, so it does not govern the EU. HIPAA protects health information held by US covered entities. FERPA protects US student education records, not personal data across the European Union.

Correct answer: HIPAA

HIPAA (Health Insurance Portability and Accountability Act) sets the US privacy and security rules for protected health information, so it applies directly to a system storing patient health records. FERPA covers student education records, not health records. GLBA covers customer financial information held by financial institutions. GDPR is the European Union data protection regulation, so it is not the standard most directly applicable to US patient records.

Correct answer: PCI DSS

PCI DSS (Payment Card Industry Data Security Standard) is the card brands' standard that any organization storing, processing or transmitting cardholder data must meet. CIS CSC (the CIS Critical Security Controls) is a general prioritized set of security safeguards, not a payment card mandate. NIST CSF (the NIST Cybersecurity Framework) is a voluntary risk framework that does not govern cardholder data specifically. SOX ITGC refers to IT general controls tested for Sarbanes-Oxley financial reporting, not card data security.

Correct answer: Environmental, Social, and Governance

ESG stands for Environmental, Social, and Governance: the three groups of criteria used to judge an organization's sustainability and ethical impact. Economic, Stewardship, and Governance replaces the environmental and social pillars with financial terms. Enterprise, Standards, and Governance confuses ESG with enterprise architecture or standards bodies. Employee, Stakeholder, and Governance narrows the social pillar to particular groups and drops the environmental one entirely.

Correct answer: Restricting information access to vetted personnel

Confidentiality means information is disclosed only to those permitted to see it, so it is best described as Restricting information access to vetted personnel. Preventing unapproved changes to project documents describes integrity. Providing continuous service to business customers describes availability. Duplicating important databases to offsite storage describes a backup and recovery practice that supports availability, not the confidentiality principle.

Correct answer: That data stays accurate and complete without improper alterations

In the CIA triad, integrity ensures That data stays accurate and complete without improper alterations, whether by error or by unauthorized change. That content stays secret and unexposed without approved clearance describes confidentiality. That service stays online and responsive without unplanned outages describes availability. That traffic stays ciphered and unreadable without decryption keys describes encryption in transit, which is a confidentiality control rather than the meaning of integrity.

Correct answer: Physical security

Badge readers, locks and guards that limit who can enter a data center are Physical security controls, because they protect the facility and hardware itself. Technical security relies on hardware and software mechanisms such as firewalls and encryption inside systems. Personnel security covers screening, training and managing the people who are granted access, not the door controls themselves. Logical security controls access to systems and data through accounts, passwords and permissions, not entry to a room.

Correct answer: Infrastructure as a Service (IaaS)

Infrastructure as a Service (IaaS) provides virtualized servers, storage and networking over the internet while the customer manages the operating systems and applications. Communications as a Service (CaaS) delivers voice, video and messaging services, not general computing resources. Platform as a Service (PaaS) provides a managed platform for building and running applications, hiding the underlying servers. Function as a Service (FaaS) runs individual pieces of code on demand without the customer managing any servers, so it does not hand over raw infrastructure.

Correct answer: Change control

Change control is the process in which every proposed change is documented, assessed, approved or rejected, and recorded before it is implemented. A Change freeze is a period during which no changes are allowed at all, so it does not define how changes are reviewed and approved. A Change audit checks after the fact that implemented changes followed the process, rather than approving them beforehand. An Asset register is an inventory of hardware and software assets, not a process for approving infrastructure changes.

Correct answer: Production serves live customers; staging screens releases beforehand

Production is the environment real users depend on, and staging is a production-like copy used for final testing, so the difference is Production serves live customers; staging screens releases beforehand. Production previews upcoming changes; staging carries genuine traffic reverses the two roles. Production stores nightly backups; staging hosts developer workspaces confuses the environments with backup storage and development. Production hosts training classes; staging provides disaster recovery confuses them with training and failover sites.

Correct answer: Continuous Integration / Continuous Deployment

CI/CD stands for Continuous Integration / Continuous Deployment (or delivery): code changes are merged and automatically built and tested, then automatically released through the pipeline. Configuration Inventory / Configuration Design confuses CI with a configuration item record. Component Inspection / Component Documentation describes a manual review step, not an automated pipeline. Compliance Inspection / Compliance Declaration relates to audit and attestation, which is not what CI/CD means.

Correct answer: To honor mandated record preservation periods

Retention schedules and legal holds are imposed by law, regulation and litigation, so a project manager must understand them To honor mandated record preservation periods and avoid deleting data that must be kept. To reduce recurring offsite storage overheads is a cost goal that retention rules can actually work against. To accelerate analytical query response times is a performance goal unrelated to how long data must be kept. To simplify periodic access privilege reviews is an access management task, not the reason for learning retention and hold requirements.

Correct answer: ITIL

ITIL (formerly the IT Infrastructure Library) is the widely used set of best practices for IT service management. COBIT is a framework for the governance and management of enterprise IT and its control objectives, not an ITSM practice library. TOGAF is an enterprise architecture framework. PMBOK is the PMI guide to project management, not to running IT services.

Correct answer: To shield individual privacy and satisfy legal duties

PII is classified and protected chiefly To shield individual privacy and satisfy legal duties under privacy laws and regulations. To trim storage expenses and simplify backup routines is an operational benefit at most, not the reason PII needs protection. To speed file searches and improve staff productivity is a convenience that classification may bring but is not the purpose. To justify security funding and expand audit coverage treats protection as a budgeting exercise rather than a duty owed to the individuals.

Correct answer: To define mandatory protection controls for company data

An information security policy sets the rules and expectations everyone must follow to protect the organization's information, so its purpose is To define mandatory protection controls for company data, which the project must follow. To define approved spending limits for company purchases is the role of a procurement or financial authority policy. To define formal retention schedules for company records is the role of a records retention policy. To define ethical conduct standards for company managers is the role of a code of conduct.

Correct answer: Environmental impacts

Environmental impacts are the environmental pillar of Environmental, Social, and Governance (ESG): a project's effect on the natural surroundings, such as emissions, resource use, and disruption of the local site, which is what the project manager is summarizing. Social responsibility is the social pillar, covering effects on people such as employees, customers, and the community. Governance structures are the governance pillar, covering how the organization is directed and held accountable. Financial performance is a profit measure from the economic side of reporting and is not one of the three ESG pillars.

Correct answer: Because honoring vision, mission, and values protects governance integrity and brand value

Because honoring vision, mission, and values protects governance integrity and brand value: the governance domain expects a project manager to know the organization's vision, mission statements, and values, since a project that conflicts with them can damage governance and the company brand. Because quoting vision, mission, and values replaces governance checks and impact analyses is wrong, since alignment does not remove any review or analysis step. Because noting vision, mission, and values sets governance budgets and acceptance criteria is wrong, since budgets and acceptance criteria come from planning and scope documents. Because posting vision, mission, and values clears governance audits and statutory filings is wrong, since publishing statements does not satisfy audit or regulatory obligations.

Correct answer: Corporate brand value impact

Corporate brand value impact is the consideration being protected: the governance domain expects project managers to weigh how project decisions affect the company's brand and how customers perceive it. Greenhouse gas emission caps are an environmental consideration about pollution, not customer perception. Supplier labor rights audits are a social consideration about working conditions in the supply chain. Board member diversity goals are a governance consideration about the composition of leadership, which a packaging design does not affect.

Correct answer: Dependable uptime and reachability for legitimate users

Dependable uptime and reachability for legitimate users is what availability ensures: the people who are allowed to use the systems and data can reach them when they need them, which relies on uptime, redundancy, and resilience. Unaltered accuracy and consistency for archived records describes integrity. Restricted visibility and secrecy for sensitive records describes confidentiality. Traceable audits and attribution for privileged changes describes accountability and auditing controls, which sit outside the three elements of the confidentiality, integrity, and availability (CIA) triad.

Correct answer: Physical security (portable equipment controls)

Physical security (portable equipment controls) is the category: the Project+ blueprint lists mobile device and removable media considerations under physical security, because laptops that leave the site can be lost or stolen, and encryption and lost-device reporting protect that hardware. Digital security (multifactor login safeguards) covers how users prove their identity when signing in. Operational security (staff background reviews) covers vetting the people on the project. Data security (sensitivity classification tags) labels information by sensitivity rather than protecting portable devices.

Correct answer: Operational security (staff clearances and vetting checks)

Operational security (staff clearances and vetting checks) is the category: the Project+ blueprint places clearance requirements and background screening under operational security because they govern which people may work on the project. Physical security (facility badging and visitor registers) controls entry to buildings and rooms. Digital security (endpoint hardening and drive encryption) protects devices and stored data. Data security (classification tagging and retention rules) governs how information is labeled and kept, not who may be assigned to the team.

Correct answer: Restricting resource privileges to role necessity

Restricting resource privileges to role necessity is the practice applied: access and permissions are granted on a need-to-know basis, so each team member can open only the modules their tasks require. Requiring multifactor logins to sensitive systems strengthens how users prove their identity but does not limit what they can open once signed in. Assigning critical duties to separate individuals is separation of duties, which splits a sensitive process among people rather than scoping each person's access. Converting stored records to encrypted ciphertext is encryption at rest, which protects data from outsiders rather than limiting authorized users to their tasks.

Correct answer: Designate them as intellectual property and trade secrets and restrict access

Designate them as intellectual property and trade secrets and restrict access: the data classification topic lists intellectual property and trade secrets as sensitive categories, and the classification then drives tighter access controls. Categorize them as public and internal materials and distribute copies widely under-classifies proprietary designs and exposes them to anyone. Register them as personal information and health records and alert regulators misclassifies them, because patented designs and formulas are not data about individuals and trigger no privacy notification. Archive them as outdated and superseded drawings and postpone cloud migration treats current, valuable records as outdated and stalls the project instead of protecting them.

Correct answer: To apply protective controls according to information sensitivity

To apply protective controls according to information sensitivity is the purpose: data classification groups information by sensitivity level so the appropriate handling, access, and storage controls can be applied to each category. To allocate storage infrastructure according to dataset footprint is capacity planning, which depends on size rather than sensitivity. To sequence migration batches according to interface dependencies is migration planning. To forecast subscription expenses according to employee headcount is cost estimating; none of these is what a Public/Internal/Confidential/Restricted scheme is for.

Correct answer: Controlled offsite access and multifactor authentication

Controlled offsite access and multifactor authentication are the measures: the digital security portion of the blueprint lists remote access restrictions, such as requiring a verified VPN, and multifactor authentication, such as a password plus a one-time code. Partitioned enterprise networks and intrusion prevention are network defenses inside the company and do not govern how remote staff sign in. Credentialed facility entrances and escorted contractors are physical security controls for buildings. Encrypted removable hardware and exfiltration prevention protect data on devices and stop it from leaving, not how users connect from home.

Correct answer: Determine which national, state, or provincial regulations govern the gathered PII

Determine which national, state, or provincial regulations govern the gathered PII is the best first step: privacy rules vary by jurisdiction, so a project handling personal data from several countries must first establish which laws apply before it can design anything to meet them. Select which encryption, redaction, or tokenization tools protect the gathered PII picks technical controls before knowing which legal requirements they must satisfy. Evaluate which cloud, regional, or offshore datacenters warehouse the gathered PII is a hosting decision that itself depends on data-residency rules. Establish which retention, deletion, or disposal timetables cover the gathered PII also depends on the applicable regulations, so it cannot come first.

Correct answer: Pinpoint sector and company compliance obligations that might affect the project

Pinpoint sector and company compliance obligations that might affect the project reflects the expected awareness: the blueprint requires project managers to know the industry-specific and organization-specific compliance concerns that could derail their project. Reuse generic and boilerplate compliance checklists that might cover the project ignores the rules specific to banking and to this organization. Benchmark peer and competitor compliance practices that might inform the project looks at what others do rather than at the obligations that bind this project. Delegate legal and regulatory compliance decisions that might impact the project hands the awareness to the legal team, when the project manager is expected to hold it personally.

Correct answer: Because mishandled health data can trigger the legal and regulatory penalties providers face

Because mishandled health data can trigger the legal and regulatory penalties providers face: PHI is a sensitive data type with significant legal and regulatory impacts, so the project manager must plan for those obligations. Because service agreements can transfer the legal and regulatory exposure to hosting vendors is wrong, since a covered organization stays accountable for PHI even when a vendor hosts it. Because signed attestations can replace the legal and regulatory duty of auditing safeguards is wrong, since attestations do not substitute for the required protections. Because internal privacy policies can override the legal and regulatory limits to disclosure is wrong, since company policy cannot loosen what the law requires.

Correct answer: IaaS

IaaS (Infrastructure as a Service) provides virtualized processing, storage, and networking that the customer provisions and manages, while the provider maintains only the physical hardware. SaaS (Software as a Service) delivers finished applications. PaaS (Platform as a Service) supplies a managed development and deployment platform, so the team would not manage the operating systems themselves. FaaS (Function as a Service) runs individual event-triggered functions without the team provisioning any servers, storage, or networks.

Correct answer: PaaS

PaaS (Platform as a Service) provides a managed platform, including operating systems, runtimes, and development tools, so developers can build and deploy applications without administering the underlying servers. IaaS (Infrastructure as a Service) would leave the team managing the servers and operating systems. SaaS (Software as a Service) delivers a finished application rather than a platform to build on. NaaS (Network as a Service) delivers network connectivity and services only, with no development environment.

Correct answer: SaaS

SaaS (Software as a Service) delivers complete, ready-to-use applications over the internet, such as web email and document editing, with the vendor managing everything and users simply logging in through a browser. PaaS (Platform as a Service) and IaaS (Infrastructure as a Service) leave more of the stack to the customer to build or manage. DaaS (Desktop as a Service) streams entire virtual desktops to users rather than providing a specific application suite.

Correct answer: Multitiered architecture

Multitiered architecture is the concept: the Project+ IT topics list multitiered (tiered) architecture, in which the presentation, business logic, and data layers are separated so each can be scaled and maintained independently. Container virtualization packages applications with their dependencies to run in isolated containers, regardless of how the application is layered. Microservices deployment splits a system into many small independent services by business function, not into presentation, logic, and data tiers. Database denormalization restructures tables for read performance and says nothing about separating the interface from the logic.

Correct answer: To reinstate the earlier stable setup if the upgrade fails or misbehaves

To reinstate the earlier stable setup if the upgrade fails or misbehaves is the purpose of a rollback plan: it lets the team restore the previous working state quickly so a failed deployment causes as little downtime as possible. To forewarn the affected customer base if the upgrade stalls or stutters is the job of customer notifications, a separate change-control element. To reconvene the change advisory board if the upgrade crashes or freezes describes escalation for a new decision, not reversing the change. To extend the planned maintenance window if the upgrade lags or overruns prolongs the outage rather than restoring service.

Correct answer: Within a preproduction environment such as staging or beta

Within a preproduction environment such as staging or beta is where the build should be validated: the blueprint distinguishes production from beta and staging environments so changes are tested in a non-production setting before they reach live users. Within a customer environment such as launch or onboarding puts untested builds in front of real customers. Within a recovery environment such as standby or mirroring uses disaster-recovery infrastructure, which exists to take over from production rather than to test new builds. Within a production environment such as payroll or banking tests directly on live systems, exposing real users to defects.