Block storage availability across AZ failure
WHAT IT TESTS: HA design and RTO/RPO trade-offs. OUTLINE: block volumes are AZ-bound, so use snapshots, synchronous replication, or app-level replication, trading cost for lower RTO/RPO.
WHAT IT TESTS: whether you understand block storage is zone-scoped and can map solutions to RTO and RPO. ANSWER OUTLINE: a block volume lives in one AZ, so an AZ failure makes it unreachable. Options span async snapshots (cheap, high RTO and RPO), synchronous block replication or regional disks (low RPO, moderate cost), and application-level replication like a database with a standby (near-zero RTO and RPO). RED FLAG: assuming a single volume is automatically cross-AZ durable, or ignoring the cost-versus-recovery trade-off.
Read the original → interview
- #high-availability
- #block-storage
- #rto-rpo
- #replication
- #disaster-recovery
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.