A database must keep running if a zone fails. What do you configure?
Why D is the answer
Replication and failover
Replication and failover keep a database running when a zone fails.
In detail
- Replication and failover keep it running through a zone failure.
- Test failover regularly.
Use case
An illustrative scenario, not a real incident.
A zone fails, and a replica takes over within moments, so the database stays up.
See it in different ways
flowchart LR A["Primary zone or region"] --> B["Replica"] A -->|"Failure"| C["Failover to the replica"]
mindmap
root((Stores))
BigQuery
Analytics
Bigtable
Key lookups at scale
Spanner
Global relational
AlloyDB
PostgreSQL
Firestore
Mobile documents
Memorystore
Microsecond cache
Cloud Storage
ObjectsstateDiagram-v2 state "Primary running" as s0 state "Zone fails" as s1 state "Replica promoted" as s2 [*] --> s0 s0 --> s1: failure s1 --> s2: failover s2 --> [*]
Key point: Replication and failover handle zone failure.
Why the other options are wrong
- A. A longer DAG
- A DAG does not protect a database.
- B. A larger dashboard
- A dashboard has no effect.
- C. Table partitioning
- Partitioning organizes tables.