12 mins read ·
9 questions
Calculate risk exposure (probability × impact) and prioritise risks in a risk register.
12 mins read ·
13 questions
Explain team organisation, communication overhead [n(n − 1)/2 channels], Brooks’s law, and the factors that affect team motivation and communication.
11 mins read ·
10 questions
Interpret the Standish Group CHAOS Report outcome categories (successful, challenged, failed) and its reported success factors.
11 mins read ·
9 questions
Evaluate the published methodological criticisms of the CHAOS Report and their implications for how its figures should be used.
12 mins read ·
10 questions
Define software configuration management and describe its activities: configuration identification, change control, status accounting and configuration audit.
13 mins read ·
18 questions
Explain version control in depth: baselines, merge conflict resolution, tagging, semantic versioning (MAJOR.MINOR.PATCH), and monorepo versus multi-repo organisation.
12 mins read ·
11 questions
Describe release management (release planning, packaging, release notes, rollback) and deployment strategies (blue–green, canary, rolling, feature flags).
12 mins read ·
8 questions
Distinguish continuous integration, continuous delivery and continuous deployment.
11 mins read ·
14 questions
Explain DevOps culture and principles (shared ownership; the “three ways” of flow, feedback and continual learning) and how DevOps differs from separate development and operations.
13 mins read ·
21 questions
Describe Infrastructure as code (declarative and imperative approaches; tools such as Terraform and Ansible) and the role of containerisation (Docker) and orchestration (Kubernetes).
13 mins read ·
17 questions
Describe monitoring and observability (logs, metrics, traces, alerting) and interpret the four DORA metrics: deployment frequency, lead time for changes, change failure rate and time to restore service.
13 mins read ·
13 questions
Analyse the Amazon deployment pipeline case study to explain how automation, small batch sizes and service ownership enable frequent, low-risk deployment.