What is a Region versus an Availability Zone, and why does the difference matter?
What they are really testing: Whether you understand the physical failure domains your reliability rests on. They want you to connect the concept to a real decision: how you spread workloads to survive failures.
A real interview question
What is a Region versus an Availability Zone, and why does the difference matter?
What most people say
drag me
“A region is a bigger area and an availability zone is a smaller one inside it.”
Geographically true but misses the entire point: AZs are independent failure domains, and that independence is why you spread across them. No connection to a reliability decision.
The follow-ups they ask next
Why not just run everything across multiple regions for max safety?
Cross-region adds latency, data-transfer cost, replication complexity, and consistency headaches. Multi-AZ covers the common failure cheaply; multi-region is reserved for the top reliability tier.
A managed database offers "multi-AZ" mode, what is it actually doing?
Maintaining a synchronous standby in another AZ with automatic failover, so an AZ failure promotes the standby with minimal downtime, no data loss for committed writes.
What the interviewer is listening for
- Defines AZ as an independent failure domain
- Connects to a multi-AZ/multi-region decision
- Knows multi-AZ is the production default
What sinks the answer
- Only describes size/geography
- Thinks AZs are just for latency
- Defaults to multi-region without naming its cost
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“A region is [a geographic location, picked for latency/law/services]. An AZ is [an isolated datacenter inside it with independent power/network]. It matters because [the AZ is your failure domain, so you spread across AZs to survive an outage, and across regions only for DR/global latency].”
Keep going with reliability
Foundation
What is the difference between vertical scaling and horizontal scaling, and when would you reach for each?
Foundation
What does "highly available" actually mean, and how do you achieve it?
Foundation
Why are stateless services easier to scale and make reliable than stateful ones?
Junior
How should a service retry a failed call to a dependency, and what is a retry storm?
Junior
What is idempotency, and why does it matter for reliable distributed systems?
Junior
What is graceful degradation, and when would you fail open versus fail closed?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free