CompTIA DataSys+ (DS0-001)Database DeploymentMedium
A database administrator is planning to deploy a critical reporting database that must be available 24/7 with minimal downtime. The solution needs to support read scaling while maintaining data consistency. The architecture should allow for rapid recovery in case of a primary database failure. Which deployment pattern best describes these requirements?
- AMaster-replica replication with synchronous read replicas and automatic failover
- BSingle instance with daily backups
- CSharded database with eventual consistency
- DMaster-slave replication with asynchronous replicas
Show answer & explanationAnswer & explanation
Correct answer: A. Master-replica replication with synchronous read replicas and automatic failover
Master-replica replication with synchronous read replicas ensures strong data consistency and allows for read scaling. Automatic failover provides rapid recovery and meets the 24/7 availability requirement by promoting a replica to a new primary with minimal downtime during a failure.
Why the other options are wrong
- B. A single instance is a single point of failure and daily backups do not provide 24/7 availability with minimal downtime.
- C. Sharding addresses scalability but 'eventual consistency' does not meet the 'maintain data consistency' requirement for a critical reporting database.
- D. Asynchronous replicas do not guarantee strong consistency and may have data loss on primary failure, not meeting 'maintain data consistency'.
Master-Replica with Synchronous Read Replicas and Automatic Failover
A high-availability and read-scaling database architecture where a primary (master) writes data synchronously to replicas, which can serve reads and be promoted automatically upon primary failure.
- Ensures strong data consistency.
- Provides high availability through automatic failover.
- Scales read operations by distributing them among replicas.
Memory trick: HA is a dance of consistency, copies, and quick recovery.