PMBOK Knowledge Areas (Integration, Scope, Time, Cost) Summaries — PMP Exam Notes (PMI South Africa) for Unisa & CUT

PMBOK (Project Management Body of Knowledge) organises project management practices into Knowledge Areas. For PMP/CAPM study, the most important cross-links are between Integration, Scope, Time, and Cost, because these areas jointly determine the project’s baseline, trade-offs, and performance outcomes. This guide summarises the key ideas, typical exam-style interpretations, and practical scenarios—aligned with how candidates commonly prepare for Unisa and CUT project management modules such as MNG 0001/early PM foundations and related PMP-focused coursework (e.g., projects, cost and scope management assignments).

This document belongs to the collection “PMP & CAPM Certification Exam Notes (PMI South Africa)” and uses exam-friendly language with concrete examples and process logic rather than memorisation-only notes.

1) Integration Knowledge Area (PMBOK) — The “Glue” Between Scope, Time, and Cost

Integration is the Knowledge Area that answers the exam’s recurring question: “What do you do when changes happen, and how do you keep everything coordinated?” In PMBOK terms, Integration Management includes processes that develop the project charter, manage project plans, direct and manage work, manage project knowledge, monitor and control work, and perform overall change control.

Integration Management: Core Logic and Exam Angle

Think of the Integration Knowledge Area as a set of “decision and coordination” mechanisms:

Build the project plan (and align it to the charter and requirements).
Execute the plan (direct work and manage dependencies).
Measure performance against the baseline (schedule, cost, scope progress).
Decide on corrective actions (if performance deviates).
Control change so scope/time/cost updates don’t happen randomly.

In PMP exam questions, options that sound “locally perfect” but ignore integration principles are usually wrong. For example, a response that says “approve a change request directly because it solves the current issue” is often incorrect—Integration Management demands that change is evaluated through overall change control.

Key Integration Processes (What They Mean in Practice)

Below are the Integration-related processes most consistently tested through situational questions, with practical meanings.

Develop Project Charter

This creates the authority to start the project. The charter typically includes:

High-level requirements or business needs
Measurable objectives (often broad at this stage)
Summary budget and timeline (top-level)
Stakeholders and governance
High-level risks and assumptions

Exam emphasis: Charter is not a schedule, and it is not a detailed scope statement. If a scenario describes work that should wait for planning, the best answer usually references the charter as a baseline authority, not as a plan.

Develop Project Management Plan

This compiles subsidiary plans into a coherent whole. It usually includes:

Scope management plan
Schedule management plan
Cost management plan
Quality management plan
Resource and communications plans
Risk management plan
Change management plan (often described here and then operationalised later in change control)

Study insight: Integration Management requires consistency across plans. If you “build the schedule” without a cost baseline approach, you create a mismatch that exam questions frequently flag.

Direct and Manage Project Work

This is where execution becomes coordinated. It includes:

Directing work and performing project tasks
Ensuring team collaboration
Managing interfaces between stakeholders and subsystems
Implementing planned processes

A common exam trap is confusing “direct and manage” with “monitor and control.” Execution activities should be aligned to the plan; monitoring and controlling happens concurrently to detect deviations.

Manage Project Knowledge (Often Under-Tested but Conceptually Important)

This focuses on capturing and using lessons learned and knowledge assets. Typical outputs involve:

Lessons learned register updates
Knowledge base access

Exam angle: If options talk about “recording experience” for future projects, the correct response often connects to Manage Project Knowledge. However, if the question is specifically about schedule recovery actions, Knowledge Management might be a distractor.

Monitor and Control Project Work

This is performance tracking and status reporting:

Measuring schedule and cost performance
Comparing actual vs. planned deliverables
Identifying variances and recommending corrective actions
Reporting performance status and forecasts

In practice, this includes Earned Value concepts when applicable (which connect strongly to Cost and Time Knowledge Areas).

Perform Integrated Change Control (Overall Change Control)

This is the “exam star.” It coordinates changes across the whole project so that impacts are analysed across scope, schedule, cost, quality, and risk.

A proper integrated change control decision typically includes:

Review the change request
Analyse impacts (scope, schedule, cost, quality, risk)
Decide approve/reject/modify
Update baselines and relevant plans if approved
Communicate decisions to stakeholders

Exam emphasis: If a scenario says “team members updated the schedule informally to reflect a scope change,” that is often wrong. Integration requires formal change control.

Integration Mini-Case Study: Procurement Change vs. Project Baselines

Consider a project in South Africa (typical of many case-style exam questions): a mid-sized engineering firm, Thabo Mokoena Engineering (TME), is delivering a small industrial retrofit for a client in Gauteng. The project plan includes:

Scope: install two production lines and integrate safety systems
Time: 14-month schedule
Cost: R12,000,000 baseline budget

Halfway through, the client requests switching from standard steel piping to corrosion-resistant piping. The request affects:

Scope: additional technical requirements and installation steps
Time: procurement and installation may extend activities
Cost: higher material price and potential labour changes
Risk: new supplier lead times and technical qualification

The correct integration response is:

Submit a change request
Analyse impact across time and cost baselines
Approve and update baselines only if warranted
Communicate to stakeholders and update the relevant plans

An incorrect response would be to approve the materials purchase immediately without change control, because doing so can undermine baselines and lead to claims or misalignment later.

Integration Knowledge Area Key Takeaways (For PMP-style Questions)

Use these mental checkpoints when answering exam questions:

If the question is about authority to start, look for Project Charter.
If it’s about how plans fit together, look for Develop Project Management Plan.
If it’s about execution coordination, look for Direct and Manage Project Work.
If it’s about performance measurement and corrective actions, look for Monitor and Control Project Work.
If it’s about approving change, look for Perform Integrated Change Control.

Most failing candidates don’t miss definitions—they miss which situation the question is testing. Integration is the Knowledge Area that tells you how to respond when situations evolve.

2) Scope Knowledge Area (PMBOK) — Defining What’s Included, What’s Not, and How It’s Controlled

Scope Management is tested heavily because it determines the deliverables and boundaries of the project. Integration determines how changes are controlled; Scope determines what exactly is being changed.

Scope Management: Why It Matters for Outcomes

A project can have an excellent team and good project management—but still fail if it delivers the wrong things. Scope Management ensures:

Deliverables match requirements
Work has clear boundaries
Acceptance criteria are defined
Changes are managed without “scope creep”

In PMP exam style, “scope creep” often appears disguised as “quick fixes,” “minor additions,” or “just do it now.” Scope Management forces the project to treat those requests as managed changes, not informal work.

Plan Scope Management — Establishing Rules of Engagement

Plan Scope Management defines how scope will be created, validated, and controlled. It includes:

Scope planning approach (how you will elaborate requirements)
Requirements management approach
How requirements changes are handled
How the Work Breakdown Structure (WBS) will be created and verified

Exam angle: If a scenario starts with unclear deliverables and asks what comes first, the best answer typically references planning scope management—not jumping into WBS creation without first defining the approach.

Collect Requirements — Turning Stakeholder Needs into Requirements

Collect Requirements is about gathering needs and converting them into documented requirements. Inputs commonly involve stakeholder interviews, workshops, focus groups, surveys, and review of business documents.

Requirements can be:

Functional (what the system must do)
Non-functional (performance, security, usability)
Assumptions and constraints
Acceptance criteria

Important exam behaviour: If the answer options suggest “start building the deliverable immediately” without clearly capturing requirements, that is typically wrong. Requirements come before detailed scope definitions.

Stakeholder Requirements: The Classic Conflict

In scope questions, stakeholder expectations frequently conflict.

Example scenario:

The client wants a faster commissioning timeline
The operations team wants additional training included
Finance wants to limit budget

Scope Management addresses conflicts by documenting requirements, aligning them through analysis, and later confirming acceptance with proper verification processes.

Define Scope — Producing a Clear Scope Statement

Define Scope creates:

Project scope description
Product scope description
Deliverables and project boundaries

This is where you prevent “everything everywhere all at once.” A good scope statement explicitly indicates what is included and what is excluded.

Create WBS — Breaking Work into Manageable Components

The WBS (Work Breakdown Structure) is a hierarchical decomposition of project deliverables into work packages.

A strong WBS helps with:

Scheduling and estimating (Time and Cost rely on WBS)
Scope verification (confirming deliverables)
Control (tracking changes to specific components)

Exam logic: If a question asks how to measure scope performance, WBS is a cornerstone because it provides the structure for tracking what was supposed to be produced.

Validate Scope — Formal Acceptance

Validate Scope is where deliverables are accepted by stakeholders. This usually includes:

Inspections
Testing
Review of deliverables against acceptance criteria
Formal acceptance documents

Exam trap: Validation is not the same as controlling the scope. Validation is about acceptance; control is about ensuring changes and updates are managed.

Control Scope — Managing Changes and Scope Creep

Control Scope monitors status of the scope baseline and manages changes to it. It includes:

Tracking deliverables vs. WBS
Reviewing change requests
Reporting variance
Recommending corrective actions

In integrated projects, Control Scope interfaces tightly with:

Perform Integrated Change Control (Integration)
Monitor and Control Project Work (Integration)
Schedule control (Time)
Cost control (Cost)

Scope Control Mini-Case Study: “Small” Additions That Become Big Problems

Use a typical exam-style story:

A South African retail business is implementing a new point-of-sale system. Initial scope includes:

Installation of terminals
Configuration of payment gateways
Staff training (2 sessions)

During implementation, the client requests two additional features:

Adding inventory scanning for back-office staff
Adding a third training session

Each request seems small. However, it impacts:

requirements documentation
system configuration work
test cycles
training materials and staff scheduling
potentially licences and vendor support time

If scope change is not managed, the project ends up:

late
over budget
with acceptance delays

Correct approach:

document change requests
analyse impacts
route through integrated change control
update scope baseline if approved

Scope Summary for Exam Use

When reading exam questions, apply a “scope lens”:

Is the question about requirements? → Collect Requirements.
Is it about defining boundaries and deliverables? → Define Scope.
Is it asking how to structure work for tracking and estimation? → Create WBS.
Is it asking how deliverables are accepted? → Validate Scope.
Is it asking how changes are controlled and scope creep prevented? → Control Scope.

Because scope drives work decomposition, scope accuracy often determines whether time and cost management is meaningful.

3) Time Knowledge Area (PMBOK) — Scheduling the Work and Recovering When Reality Deviates

Time Management ensures the project is completed within the planned schedule. This is where many PMP candidates struggle, not because they cannot memorise terms, but because they misinterpret scheduling decisions in context.

Time Management: What “Good” Looks Like

A “good” schedule is not just a list of activities. It should reflect:

activity logic (dependencies)
realistic durations
resources and constraints
critical path visibility
baseline readiness for performance measurement

In exam questions, answers are often about using correct scheduling tools/inputs/outputs and making the right recovery plan.

Plan Schedule Management — How the Schedule Will Be Built

Plan Schedule Management defines:

scheduling methodology (e.g., predictive, iterative)
level of detail
units of measure
thresholds for change control
links to project charter and requirements

Exam angle: When a scenario begins with a poorly understood schedule-building approach, the best first step usually is Plan Schedule Management rather than directly performing scheduling analysis.

Define Activities — Decomposing Deliverables into Actions

Define Activities identifies the specific actions needed to produce deliverables.

Inputs may include:

WBS
scope baseline
enterprise environmental factors
organizational process assets

Outputs:

activity list
milestones
related attributes

Exam emphasis: If the question describes “we know the deliverable but not how to produce it,” Define Activities is the correct process.

Sequence Activities — Establishing Dependencies

Sequence Activities determines activity dependencies and relationships:

Finish-to-start
Start-to-start
Finish-to-finish
Start-to-finish

It also produces:

project schedule network diagram
assumptions about logical order

Common confusion: Candidates sometimes focus only on logical order from experience (“we always do X before Y”). Time Management requires explicit relationships as defined in sequencing.

Estimate Activity Durations — Quantifying How Long Work Takes

Estimate Activity Durations uses estimation methods (often analogous, parametric, three-point, expert judgement, etc.) to assign durations.

Important exam behaviour: If you see uncertainty and probabilistic ranges, the question may test three-point estimation concepts (optimistic, most likely, pessimistic) and risk response linkage. While CAPM and PMP differ in depth, both exams frequently test conceptual understanding.

Develop Schedule — Building the Baseline

Develop Schedule uses:

activity sequencing
duration estimates
resource calendars
constraints
schedule model

Outputs include:

schedule baseline
schedule forecasts
schedule and critical path information

Why schedule baseline matters: Without a baseline, you cannot measure schedule performance. This connects to Integration’s Monitor and Control and Cost’s performance measures.

Control Schedule — Managing Variances

Control Schedule compares planned vs. actual progress and uses change requests and corrective actions when variances occur.

It uses outputs such as:

variance analysis
performance reporting
recommended corrective actions
updates to the schedule and project management plan

Exam trap: “Acting without assessing impacts” is often wrong. Even when recovery is needed, the best response usually involves analysing options such as crashing or fast tracking and ensuring cost/scope impacts are considered.

Time Recovery: Crashing vs. Fast Tracking

A frequent exam area is schedule compression methods:

Crashing

Add resources to critical path activities
Usually increases cost
More controlled but may require additional budget

Fast Tracking

Overlap activities that normally happen sequentially
Can increase risk and rework

Integration connection: Since crashing affects cost, and fast tracking affects risk and possibly scope, both must pass through integrated change management logic.

Time Mini-Case Study: Deadline Pressure and the Critical Path

Scenario:
TME (Thabo Mokoena Engineering) is running the retrofit for two production lines. The project’s critical path includes:

Activity A: procure corrosion-resistant piping (depending on scope)
Activity B: install piping and connect to safety systems
Activity C: commissioning and testing

During the project:

procurement delays occur (supplier lead time increases)
testing requires extra time due to integration complexity

Candidate is asked: “What’s the best next step to ensure schedule recovery?”

Correct approach often involves:

Assess actual progress and schedule variance.
Identify what changed (duration vs. dependency).
Update schedule forecasts.
Consider schedule compression methods on critical path activities.
Ensure the chosen recovery approach aligns with Integration and Cost constraints.

If the answer suggests compressing non-critical path activities without affecting the critical path, it’s usually incorrect because it won’t improve the end date.

Time Knowledge Area Summary for Exam Use

Key mapping from question type to process:

How schedule is built? → Plan Schedule Management
Identify activities? → Define Activities
Determine dependencies? → Sequence Activities
Estimate durations? → Estimate Activity Durations
Produce schedule baseline? → Develop Schedule
Respond to schedule variances? → Control Schedule

Remember: exam questions often test the sequence of reasoning—plan first, then build, then monitor and control.

4) Cost Knowledge Area (PMBOK) — Budgeting, Estimating, and Controlling Expenditure Against Baselines

Cost Management ensures the project is completed within the approved budget. Like Time Management, it is often tested through scenario selection: what should be done when costs are trending upward, what baselines are used, and how to interpret variance.

Cost Management: What Costs Really Represent

Cost is not only “money paid.” It includes:

direct costs (labour, materials, equipment)
indirect costs (overhead allocation)
risk contingency (when used)
reserve (for unknowns, depending on the baseline strategy)

Exam questions may include:

estimate adjustments due to scope changes
change requests and their cost impacts
cost baseline updates and variance reporting

Plan Cost Management — Setting Cost Rules Before Estimates

Plan Cost Management defines:

estimation methodology
units of measure
accuracy thresholds
how cost performance will be measured
reporting formats
whether and how contingency and management reserves are used

Exam angle: If cost calculation methodology isn’t established and a scenario asks “what comes first,” Plan Cost Management is typically correct.

Estimate Costs — Quantifying the Budget

Estimate Costs develops an approximation of monetary resources required for activities and work packages.

Inputs:

WBS (scope drives cost decomposition)
resource requirements
cost estimates for materials and labour
historical databases (organizational process assets)
schedule information

Outputs:

cost estimates
supporting detail documents

Determine Budget — Creating the Cost Baseline

Determine Budget aggregates estimated costs to establish:

cost baseline
contingency reserves (sometimes in budget)
management reserves (depending on control approach)
funding requirements

Core idea: The cost baseline is what you compare against actual spending and earned value (if using EV).

Control Costs — Monitoring and Variance Response

Control Costs compares:

actual costs vs. planned values
earned value (if used)
forecasts of cost performance

Outputs include:

cost performance measurements
variance reports
recommended corrective actions
updates to cost estimates, and potentially the cost baseline via change control

Cost Performance and Common Interpretation (Earned Value Concepts)

In PMP-style questions, candidates often see patterns such as:

If cost variance is negative, costs are higher than earned value.
If schedule variance is negative, less progress than planned has been achieved.
If ETC/EAC projections increase, budget overrun is expected.

Even when the question doesn’t explicitly say “Earned Value,” many exam items rely on interpreting how “progress earned” ties to money spent.

Budgeting Under Change: Why Integrated Control Is Essential

A scope change typically leads to:

additional work packages (scope)
schedule impacts (time)
additional costs and re-estimation (cost)
potential risk changes

Thus, the correct process flow is:

Change request submitted
Integrated impact analysis
Decision (approve/reject/modify)
Update scope baseline, schedule baseline, and cost baseline as approved
Communicate and implement

Cost Mini-Case Study: Scope Creep and the Slow Budget Spiral

Scenario:
The retrofit project starts with a cost baseline of R12,000,000 for 14 months. The team builds a cost model based on the WBS.

Later, the client requests additional reporting dashboards for operations. The request initially appears minor, but it adds:

additional configuration activities
new data integration work
additional testing cycles
staff training updates

If the team treats this as informal work and continues spending without updating the budget baseline, cost control reporting becomes misleading. By the time costs are obviously trending, the project is already off baseline.

Correct response:

submit change request
analyse cost and schedule impact
update baselines through integrated change control if approved
re-baseline forecasts accordingly

This prevents the “slow spiral” of untracked scope and untracked spending.

Cost Knowledge Area Summary for Exam Use

Process mapping:

Define how costs will be managed → Plan Cost Management
Create cost estimates → Estimate Costs
Aggregate into cost baseline → Determine Budget
Monitor and correct spending → Control Costs

Because Cost Management depends heavily on WBS and schedule outputs, time and scope accuracy directly improve cost predictability.

5) Integrated Practice Across Integration, Scope, Time, and Cost — Exam-Ready Scenarios and Decision Patterns

The previous sections summarised each Knowledge Area. In real exam questions, you’re usually tested on how they work together—especially around change control, baselines, and performance responses. This final section focuses on integrated scenario patterns and decision logic that candidates can apply quickly.

The “Baseline Triangle”: Scope Baseline, Schedule Baseline, Cost Baseline

A practical way to study integration across the Knowledge Areas is to visualise three baselines:

Scope baseline: defines approved scope deliverables and WBS components
Schedule baseline: approved schedule model and planned dates
Cost baseline: approved budget distribution across time/resources

When a project is controlled properly:

actual work produces deliverables
progress is measured against WBS and planned milestones
costs are tracked against the earned progress (if EV is used)
changes are evaluated across all three baselines before approval

If one baseline is updated without the others, you break consistency and violate integrated control logic. Exam questions frequently reflect this by including “incorrect” answers that update only one element.

A Full Scenario Walkthrough: Request Change, Do Impact Analysis, Approve Via Integrated Control

Use this integrated story (with consistent project numbers and timeline to mirror exam arithmetic thinking):

Project: A retrofit project delivered by Thabo Mokoena Engineering (TME).
Baseline:

Schedule: 14 months
Budget: R12,000,000
Scope baseline: includes install two production lines and integrate safety systems with standard requirements.

Event: At month 7, the client requests switching to corrosion-resistant piping and adding an extra operator training session.

Impact areas:

Scope: additional technical specification + additional training requirement
Time: increased procurement lead time and added training scheduling
Cost: higher materials and training costs

Exam question might ask: “What should the project manager do first?”
Correct integration logic:

Record the request as a change request
Perform integrated change control analysis
Decide approve/reject/modify
If approved, update scope baseline, schedule baseline, and cost baseline via approved change
Communicate updates and ensure the team uses the updated baselines

Incorrect options often:

bypass integrated analysis,
approve immediately to “save time,”
or focus only on cost without schedule/scope effects.

Decision Pattern 1: “Who Has Authority to Approve Changes?”

A recurring exam theme is governance and authority. Integrated change control does not mean “any team member can change anything.” It involves:

change request processing
impact analysis
recommended action
final decision by the appropriate authority (often a change control board, depending on organisational structure)

If a scenario states that an external stakeholder can demand changes directly, the correct project manager still routes the request through the change control process rather than treating it as an automatic mandate.

Integration + Scope link: approval should reflect whether the scope baseline changes and what deliverables are impacted.

Integration + Time/Cost link: approval should reflect schedule and cost impacts.

Decision Pattern 2: Corrective Action vs Preventive Action

Another exam pattern is distinguishing responses based on whether problems have occurred.

Corrective action: to fix performance that has deviated from plan (e.g., schedule slippage already occurred)
Preventive action: to reduce likelihood of future problems (e.g., improve procurement monitoring before delays occur)

Integration Management helps ensure both are integrated into the project plan. Scope/Time/Cost processes then define where corrective actions apply:

scope corrective action: clarify requirements, update WBS if needed
time corrective action: resequence activities, consider schedule compression
cost corrective action: adjust cost forecasts, re-evaluate estimates, control spending

Decision Pattern 3: When to Update Baselines

Candidates often assume that once you change something, the baseline should be updated immediately. PMBOK logic is stricter:

baselines are formal and changes require approval through integrated change control
baselines are updated when approved changes are integrated
minor adjustments that do not qualify as baseline changes still require documentation and may require corrective actions rather than baseline replacement

Exam options that say “change the baseline because we adjusted the plan” are usually wrong unless the scenario indicates approval through integrated change control.

Integrated Arithmetic in Exam Scenarios (Consistent Reasoning)

While this guide does not provide all Earned Value formulas as a full tutorial, many exam questions ask you to choose the best management response based on inconsistent or changing values. Here’s a consistent logic-based approach:

Suppose the project budget baseline is R12,000,000. During month 7, the project is behind and cost is higher than expected.

Even without doing full EV calculations, the best response usually includes:

identify whether the variance is driven by scope changes, schedule slippage, or resource inefficiencies
ensure scope is not silently increasing
ensure time deviations are addressed in schedule control
ensure spending decisions are governed by cost control and integrated change control

Key exam logic: When multiple drivers are present, the best answers coordinate across Knowledge Areas rather than isolating one.

Integrated Case Study: “Testing Delays” and Conflicting Stakeholder Advice

Scenario:

After receiving the first production line installation, the testing team reports delays.
The client suggests extending the schedule without changing cost.
Finance says cut costs by reducing testing time.
Operations says testing must meet acceptance criteria; scope cannot be compromised.

Correct integrated resolution:

Use Validate Scope and acceptance criteria to confirm what “done” means.
Use Control Schedule to analyse where delay occurred (duration estimates vs. dependency vs. resources).
Use Control Costs to forecast impact of extended testing time and any required additional resources.
If the change impacts cost/schedule baselines, route through Perform Integrated Change Control.

A wrong answer would be to reduce testing time because it “saves money,” since it violates acceptance criteria and risks failing acceptance (scope and quality expectations). Another wrong answer is to extend schedule without cost analysis, because extended time often increases overhead or labour cost.

Typical Exam-Style “Best Answer” Framing

In many CAPM/PMP multiple-choice items, the correct answer is framed as:

“review impact to the project baselines”
“update project management plan through integrated change control”
“perform schedule/cost variances analysis”
“ensure deliverables meet acceptance criteria”
“use WBS to confirm scope alignment”

Wrong answers often:

skip the change control mechanism,
jump to execution changes without analysis,
treat scope acceptance as interchangeable with schedule status,
or update one baseline while ignoring integrated consistency.

How These Knowledge Areas Appear Together in Common Study Modules (Unisa & CUT-aligned framing)

South African students preparing for project management modules (often across business faculty courses) frequently encounter tasks requiring:

project plans and baselines
WBS development
schedule network logic and milestone charts
budgeting, cost estimates, and cost control narratives

In modules where candidates study foundational PM concepts or integrated planning (for example, early university course elements often referred to in practice as MNG 0001-type management foundations and adjacent applied PM modules), the integration lesson is the same: you can’t treat scope, schedule, and cost as separate homework assignments. Real projects connect them through baselines and change control.

CUT and Unisa learners often practise:

writing structured project plans
presenting risk and change management reasoning
explaining why deviations must trigger formal control mechanisms

This guide’s integrated scenarios mirror that exam logic: when a requirement changes, the correct approach is not a quick patch—it’s governed change management across scope, time, and cost.

Final Integrated Checklist (Use During Exam Practice)

When answering an integrated Knowledge Areas question, quickly ask:

Is this about defining or clarifying what is included? → Scope processes (Collect/Define/WBS/Validate/Control).
Is this about scheduling logic, duration, milestones, or schedule variance response? → Time processes (Define Activities/Sequence/Estimate/Develop/Control).
Is this about budget, estimates, cost baseline, or cost variance response? → Cost processes (Plan/Estimate/Determine/Control).
Is this about coordinating decisions, approving changes, or updating plans/baselines? → Integration processes (Develop Project Management Plan, Monitor and Control, Integrated Change Control).
Are stakeholders pushing for an informal shortcut? → Choose answers that respect integrated change control and baselines.

Integrated Knowledge Areas: The Big Picture Summary

Integration ensures coordinated planning, monitoring, and change control across the whole project.
Scope ensures the project delivers the correct deliverables within clear boundaries, using WBS and acceptance criteria.
Time ensures activities are sequenced, scheduled, and controlled so the project finishes within the planned timeline.
Cost ensures expenditures align with the cost baseline and are controlled through variance analysis and forecast updates.

Together, these Knowledge Areas form the practical exam answer logic: deliver the right work, in the right time, for the right budget—while formally managing changes.