PRINCE2 Foundation PRINCE2 Practices: Control โ MCQs
Questions across 2 chapters of PRINCE2 Foundation PRINCE2 Practices: Control. Pick a chapter, read sample questions with answers, then take a free test. Available in English.
๐ Chapters
โ Practice questions with answers
The three types of issue in PRINCE2 are:
Issues Practice & Change Control
- risk, opportunity, threat
- time, cost, quality
- plan, report, log
- request for change, off-specification, and problem/concern
Show answer
Answer: D โ request for change, off-specification, and problem/concern
Issue types.
How to solve:Issue types: request for change, off-specification, problem/concern. Issue management procedure: capture, assess, recommend, decide, implement. Baseline products are changed only through change control. Change authority and change budget. Configuration management keeps product versions under control.
Tolerance is:
Progress Practice & Tolerances
- the project duration
- a type of risk
- the permissible deviation above and below a plan's target before escalation is needed
- the total budget
Show answer
Answer: C โ the permissible deviation above and below a plan's target before escalation is needed
Tolerance.
How to solve:Tolerances: business layer sets project tolerances, project board sets stage tolerances, PM sets work package tolerances. Controls: event-driven (stage end, exception) and time-driven (highlight reports from PM to board, checkpoint reports from team manager to PM). Exceptions escalate one level up.
A request for change is:
Issues Practice & Change Control
- a benefit
- a product that does not meet its specification
- a proposal for a change to a baseline
- a risk
Show answer
Answer: C โ a proposal for a change to a baseline
Request for change.
How to solve:Issue types: request for change, off-specification, problem/concern. Issue management procedure: capture, assess, recommend, decide, implement. Baseline products are changed only through change control. Change authority and change budget. Configuration management keeps product versions under control.
Project-level tolerances are set by:
Progress Practice & Tolerances
- the team manager
- the business layer (corporate, programme or customer)
- the project board
- the PM
Show answer
Answer: B โ the business layer (corporate, programme or customer)
Project tolerance.
How to solve:Tolerances: business layer sets project tolerances, project board sets stage tolerances, PM sets work package tolerances. Controls: event-driven (stage end, exception) and time-driven (highlight reports from PM to board, checkpoint reports from team manager to PM). Exceptions escalate one level up.
An off-specification is:
Issues Practice & Change Control
- a request for a new feature
- something that should be provided but is not, or does not meet its specification
- a stage plan
- a risk
Show answer
Answer: B โ something that should be provided but is not, or does not meet its specification
Off-specification.
How to solve:Issue types: request for change, off-specification, problem/concern. Issue management procedure: capture, assess, recommend, decide, implement. Baseline products are changed only through change control. Change authority and change budget. Configuration management keeps product versions under control.
Stage-level tolerances are set by:
Progress Practice & Tolerances
- the project board
- the business layer
- the PM
- the team manager
Show answer
Answer: A โ the project board
Stage tolerance.
How to solve:Tolerances: business layer sets project tolerances, project board sets stage tolerances, PM sets work package tolerances. Controls: event-driven (stage end, exception) and time-driven (highlight reports from PM to board, checkpoint reports from team manager to PM). Exceptions escalate one level up.
A problem/concern is:
Issues Practice & Change Control
- any other issue the PM needs to resolve or escalate
- a benefit
- an off-specification
- a change request
Show answer
Answer: A โ any other issue the PM needs to resolve or escalate
Problem/concern.
How to solve:Issue types: request for change, off-specification, problem/concern. Issue management procedure: capture, assess, recommend, decide, implement. Baseline products are changed only through change control. Change authority and change budget. Configuration management keeps product versions under control.
Work package tolerances are set by:
Progress Practice & Tolerances
- the project board
- the senior user alone
- the business layer
- the project manager
Show answer
Answer: D โ the project manager
WP tolerance.
How to solve:Tolerances: business layer sets project tolerances, project board sets stage tolerances, PM sets work package tolerances. Controls: event-driven (stage end, exception) and time-driven (highlight reports from PM to board, checkpoint reports from team manager to PM). Exceptions escalate one level up.
The issue management procedure steps are:
Issues Practice & Change Control
- identify, assess, plan, implement, communicate
- plan, do, check, act
- start, run, close
- capture, assess, recommend, decide and implement
Show answer
Answer: D โ capture, assess, recommend, decide and implement
Issue procedure.
How to solve:Issue types: request for change, off-specification, problem/concern. Issue management procedure: capture, assess, recommend, decide, implement. Baseline products are changed only through change control. Change authority and change budget. Configuration management keeps product versions under control.
If a work package is forecast to exceed its tolerances, the team manager should:
Progress Practice & Tolerances
- inform the project board directly
- ignore it
- raise an issue to the project manager
- stop the project
Show answer
Answer: C โ raise an issue to the project manager
Escalate one level.
How to solve:Tolerances: business layer sets project tolerances, project board sets stage tolerances, PM sets work package tolerances. Controls: event-driven (stage end, exception) and time-driven (highlight reports from PM to board, checkpoint reports from team manager to PM). Exceptions escalate one level up.
๐ก How to practise
- Read each rule (UCP 600, ISBP, URDG, ISP98) article by article and practise the matching chapter.
- Case-scenario questions test how rules work together โ review every explanation.
- Take a timed exam to get used to answering under pressure.
- Repeat chapters where you score below 75%.