Chapter 5 · Implement an Instrumentation Strategy·v2.0.0·Updated 6/3/2026·~10 min

What's changed: Deepened AZ-400 Chapter 5 (added comparison tables, scenarios, FAQs, exam traps, deep-dive paragraphs to each section; localized figures to Japanese)

5.3Feedback and SRE Practices

Key points

Understand continuous feedback—SLI/SLO/error budgets, blast radius control, postmortems, continuous improvement, and user feedback. Improve reliability through learning.

DevOps is completed by a learning loop. Quantify reliability with SLI/SLO, learn from failures via postmortems, and improve continuously.

5.3.1SRE and feedback

Diagram of SRE reliability practices: from SLI (measured reliability indicators, e.g., success rate/latency) define SLO (targets), compute the error budget (headroom against SLO) to decide how aggressively to change, limit blast radius during incidents (canary/feature flags/staged rollout), conduct blameless postmortems to learn root cause and prevention, and combine with user feedback in a continuous-improvement loop. — SRE and feedback

SLI/SLO: SLI = measured reliability indicators, SLO = targets; quantify the service promise.
Error budget: headroom against the SLO; risky changes are acceptable while budget remains.
Blast radius control: limit failure impact via canary/feature flags/staged rollout.
Postmortems: blameless retros to learn root cause/prevention and improve continuously.

Exam point

Common on AZ-400: measured = SLI, target = SLO, headroom = error budget, limit impact = blast radius control (canary/flags), blameless retro = postmortem. Use error budgets to decide: move fast while budget remains, prioritize stability when exhausted.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.

Get started free Log in