Path 6 · Module 5
Well-Architected Framework: Operational Excellence
Read the module on Microsoft Learn, then come back here: test yourself with the quiz and apply it in the design exercise. Write down what you want to remember with the ✎ Note buttons.
Step 1 · Read the module
Open Well-Architected Framework: Operational Excellence on Microsoft Learn. The units:
- Introduction
- Embrace DevOps culture
- Establish development standards
- Evolve operations with observability
- Automate for efficiency
- Adopt safe deployment practices
- Summary
Close the Learn tab. Answering from memory is what makes it stick; looking it up just measures how fast you can scroll.
Quiz
20 exam-style questions, roughly in the order of the units. Click an answer to see the explanation. Your best score is saved and shown on the path page; use Retry at the end to go again.
1. What's the core idea of a DevOps culture?
C. Collaboration, accountability and learning are central.
2. After an incident, what does a blameless postmortem focus on?
D. Blameless reviews encourage openness and real fixes.
3. Why use standardized tools, templates and coding standards across teams?
C. Standards reduce friction and errors.
4. Which practice keeps infrastructure changes reviewable and repeatable?
A. IaC with reviews gives traceability and consistency.
5. What's the difference between monitoring and observability?
A. Observability combines telemetry to explain system behavior.
6. Which three telemetry types are the basis of observability?
B. Distributed tracing links calls across services.
7. Which tool provides distributed tracing for an application on Azure?
D. Application Insights collects requests, dependencies and traces.
8. Alerts wake people up for things that need no action. What's the fix?
D. Alert fatigue hides real problems.
9. Which tasks should be automated first?
A. Automating toil frees time and reduces errors.
10. Which service runs scheduled PowerShell/Python runbooks for operational tasks like start/stop VMs?
D. Automation accounts host runbooks and update management features.
11. Configuration of VMs drifts from the baseline. What prevents and detects this?
B. Machine Configuration audits and enforces in-guest settings.
12. What does continuous integration (CI) do?
C. CI catches problems early.
13. Which deployment practice limits the blast radius of a bad release?
B. Roll out gradually and stop if health degrades.
14. How should a failed deployment be handled?
C. Safe deployment includes a way back.
15. What's a feature flag used for?
C. Feature flags enable gradual exposure and quick disable.
16. Blue-green deployment means:
B. Switching back is instant if problems appear.
17. Why treat every deployment, including infrastructure and configuration, the same way?
A. Many incidents come from config changes.
18. What's the role of a workload supply chain in operational excellence?
A. The supply chain must be trusted and reproducible.
19. What does "shift left" mean for quality and security?
C. Earlier detection is cheaper and faster to fix.
20. How should operational procedures (runbooks) be maintained?
C. Runbooks must work when needed.
Design exercise
On paper · about 25 minutes
Wavecrest Energy has 6 teams deploying 15 services by hand from the portal, about twice a month. Outages often follow releases. Monitoring is CPU alerts on VMs that page everyone at night. Nobody writes down what went wrong.
-
Task
Design the delivery pipeline
Describe the path from commit to production.
Done when- IaC and CI/CD are included.
- Progressive exposure and rollback are included.
Model answer
Git with pull requests and branch protection → CI (build, unit tests, security scans, IaC validation) → artifacts → CD to dev → test → canary ring in production → full rollout, with automated health gates and rollback; feature flags in App Configuration; infrastructure in Bicep/Terraform through the same pipeline.
-
Task
Fix observability and culture
What changes in monitoring, alerting and incident handling?
Done when- Alerts are actionable.
- Learning after incidents is built in.
Model answer
Application Insights with distributed tracing, health model per service, SLO-based alerts with severity and on-call rota per team, runbooks linked from alerts, automated remediation where safe, blameless postmortems with tracked actions.