3.2 - Cloud operations and optimization
Cloud+ CV0-004 objective 3.2 covers day-to-day cloud operations and optimisation. Right-sizing reviews usage and resizes over-provisioned instances to cut spend without hurting performance. Tagging adds labels such as a cost center to every resource so spend and ownership can be grouped and reported, and it also drives automation and governance. A runbook is a documented step-by-step procedure operators follow to handle a known task or incident consistently. Capacity planning predicts future resource needs from growth trends to avoid shortfalls before they cause outages. You should also know automation, patch and lifecycle management, and orchestration. Expect scenario questions that describe trimming oversized instances, labelling resources for reporting, following a documented procedure, or forecasting demand, and ask which operational practice - right-sizing, tagging, runbook or capacity planning - the situation calls for.
Resize over-provisioned instances = right-sizing. Label resources (e.g. cost center) for reporting = tagging. Documented step-by-step procedure = runbook. Forecast future needs from trends = capacity planning.
Practice questions
1. Reviewing usage and resizing over-provisioned instances to cut spend is called:
- Overprovisioning
- Right-sizing (correct answer)
- Throttling
- Bursting
Right-sizing matches instance type/size to actual utilization, cutting waste. Throttling limits request rates; bursting temporarily exceeds a baseline.
2. Adding a cost-center label to every resource so spend can be grouped and reported by team is:
- Right-sizing
- Throttling
- Tagging (correct answer)
- Bursting
Tagging attaches metadata (owner, cost center, environment) to resources so cost and access can be grouped, reported and governed. Right-sizing changes instance size.
3. A documented step-by-step procedure operators follow to handle a known task or incident is a:
- Manifest
- Runbook (correct answer)
- Blueprint
- Changelog
A runbook lists the exact steps to resolve a known operational task, enabling consistent response and automation. A blueprint describes an architecture, not a procedure.
4. Predicting future resource needs from growth trends to avoid shortfalls is called:
- Instance right-sizing
- Capacity planning (correct answer)
- Peak-load testing
- Cost chargeback
Capacity planning forecasts demand from trends so resources are provisioned ahead of need, avoiding outages or waste. Right-sizing tunes existing instances to current usage.
5. Scheduling patches during a defined low-traffic window to limit disruption uses a:
- Maintenance window (correct answer)
- Failover event
- Snapshot chain
- Scaling policy
A maintenance window is an approved low-impact time slot for patching and changes, reducing user disruption and coordinating rollback if needed. A scaling policy governs capacity, not patching.
6. Coordinating many automated tasks into one end-to-end workflow across systems is called:
- Single-task scripting
- Continuous monitoring
- Orchestration (correct answer)
- Resource tagging
Orchestration chains individual automated tasks into a coordinated multi-step workflow with logic and dependencies across systems. A single script automates just one task in isolation.