AZ-305 Guide Path 6 · Module 2 · Well-Architected Framework: Reliability

Path 6 · Module 2

Well-Architected Framework: Reliability

📖 Microsoft Learn ~89 min❓ Quiz 20 questions✍ Design exercise 25 min

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: Reliability on Microsoft Learn. The units:

  1. Introduction
  2. Design for business requirements
  3. Design for resilience
  4. Design for recovery
  5. Design for operations
  6. Keep it simple
  7. Summary
Before you start the quiz

Close the Learn tab. Answering from memory is what makes it stick; looking it up just measures how fast you can scroll.

Part A

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 should you identify first when designing for reliability?

B. Flows have different criticality; requirements per flow drive the design.

2. What's a reliability target expressed as a percentage of time a flow must be available?

C. Service level objectives turn business needs into measurable targets.

3. Why should a workload's SLO usually be lower than the product of its components' best SLAs suggests?

D. Calculate composite SLAs and set realistic, achievable SLOs.

4. What's failure mode analysis (FMA)?

B. FMA finds single points of failure and failure impacts early.

5. Which design removes single points of failure inside a region?

B. Multiple instances in different zones survive a datacenter failure.

6. A downstream service is failing; callers keep retrying and make it worse. Which pattern helps?

D. A circuit breaker stops calls for a while so the failing service can recover.

7. How should clients retry transient failures?

C. Backoff avoids overloading a recovering service.

8. During an outage of the recommendations service, the shop still sells products without recommendations. What's this called?

D. Non-critical features degrade while critical flows keep working.

9. Which pattern decouples a front end from a slow back end so load spikes are absorbed?

D. A queue buffers requests; the back end processes at its own pace.

10. What's the purpose of a disaster recovery plan in the reliability pillar?

A. Recovery must be planned, automated where possible, and rehearsed.

11. Which backup practice best supports reliable recovery?

C. A backup you can't restore isn't a backup.

12. What does an active-active multi-region design give compared to active-passive?

A. Active-passive is cheaper but failover takes longer.

13. What should health monitoring for reliability include?

A. A health model shows whether a flow is healthy, degraded or unhealthy.

14. What's chaos engineering?

A. Fault injection proves that the design handles failures.

15. Why should you run reliability tests in pre-production and production-like environments?

A. Load, failover and fault-injection tests build confidence.

16. What does "keep it simple" mean for reliability?

C. Simpler designs have fewer failure points and are easier to operate.

17. Why prefer managed PaaS services for reliability where possible?

C. Offloading responsibility reduces operational risk.

18. What's a health endpoint (health probe) used for?

D. Health endpoint monitoring removes failing instances from rotation.

19. What does self-preservation (self-healing) include?

D. Self-healing reduces downtime without human intervention.

20. Why should critical and non-critical flows be isolated?

A. The bulkhead pattern isolates resources per flow or consumer.

Part B

Design exercise

On paper · about 25 minutes

Pinecrest Clinics runs an appointment booking app: web front end, API, Azure SQL Database, and an SMS reminder service via a third-party provider. Booking must be available 99.9%; reminders may be delayed by hours.

  1. Task

    Identify flows and failure modes

    List the critical and non-critical flows, and do a short failure mode analysis.

    Done when
    • Flows are classified.
    • At least four failure modes with impact.
    Model answer

    Critical: search slots, book, cancel. Non-critical: reminders, reporting. Failures: zone loss (all down), SQL failover (seconds of errors), SMS provider down (reminders delayed), API overload during flu season.

  2. Task

    Design resilience and recovery

    Propose patterns and services that meet 99.9% for booking.

    Done when
    • Zone redundancy is used.
    • Reminders are decoupled.
    • Recovery is tested.
    Model answer

    Zone-redundant App Service and SQL Database; retries with backoff; reminders via a queue (queue-based load leveling) with circuit breaker to the SMS provider; health endpoints; backups with tested restores; Chaos Studio experiments; health model per flow in Azure Monitor.