What's changed: Created Professional Cloud Architect Chapter 6 (Domain 4 "Analyze and optimize": cost optimization and business alignment = billing/budget alerts (notify-only)/CUD/Spot/Active Assist/lifecycle/label allocation/KPI alignment; technical process optimization = SRE (SLI/SLO/error budget)/CI-CD (Cloud Build/Cloud Deploy)/deployment strategies (canary/blue-green/rollback)/incident response/postmortems).
6.1Cost optimization and aligning business processes
Understand cost visibility (billing reports, budgets and alerts), optimization levers (committed-use discounts, Spot VMs, Active Assist recommendations, lifecycle), cost allocation via labels, and aligning with business goals/KPIs and continually revisiting stakeholder requirements.
Architecture is not "build and forget." Continuously revisit cost and value and optimize toward business goals. The architect analyzes processes and drives improvement.
6.1.1Cost visibility and optimization
First make spend visible with billing reports and budgets and alerts (note budgets only notify—they do not auto-stop). Optimize with committed-use discounts (CUDs) for steady use, Spot VMs for interruptible work, Active Assist recommendations to flag waste, and lifecycle rules for storage. Labels on resources let you allocate cost by department/project for analysis. Map "auto-suggest waste = Active Assist," "cost allocation = labels," and "discount steady use = CUDs."
6.1.2Aligning with business goals
Technical optimization creates value only when tied to business goals and KPIs. The architect continually revisits stakeholder requirements, reflecting changing demand and new needs in the architecture. E.g., prioritize availability/scale during growth and cost efficiency at steady state—reweighting by phase. Map "tie technical decisions to KPIs/business goals" and "revisit requirements continually, not once."
Common: requirement → means. E.g., "visualize spend and alert at thresholds" = budgets and alerts; "auto-flag waste" = Active Assist; "allocate cost by department" = labels; "discount steady use" = CUDs; "cheap interruptible work" = Spot VMs. Note: budgets only notify, they do not auto-stop.
Watch the mix-ups: (1) Budgets and alerts only notify—they do not auto-stop spending. (2) Do not divorce cost optimization from business goals/KPIs (do not chase cheapness alone). (3) Labels underpin allocation/analysis—standardize naming.
6.1.3Section summary
- Visualize cost via billing reports + budgets/alerts (budgets only notify, no auto-stop)
- Optimize = CUD/Spot VMs/Active Assist/lifecycle; allocate via labels
- Tie technical decisions to business goals/KPIs; revisit requirements continually
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. To get notified when spend exceeds a threshold, what do you use?
Q2. Which is correct about budgets and alerts?
Q3. To auto-flag wasteful resources and cost-saving opportunities, what do you use?
Q4. To allocate and analyze cost by department/project, which best fits?
Q5. What is the best stance when pursuing cost optimization?
Q6. Which correctly describes reweighting design by growth vs steady phase?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.