SK0-005 · Question #577
The management team informs a server administrator that a database requires high availability. There can be no data loss with a single server failure. Which of the following solutions should the…
The correct answer is A. Two database servers, both online and synchronizing in real time. To achieve high availability with no data loss from a single server failure, the administrator should recommend two online database servers synchronizing in real time using synchronous replication.
Question
The management team informs a server administrator that a database requires high availability. There can be no data loss with a single server failure. Which of the following solutions should the administrator recommend?
Options
- ATwo database servers, both online and synchronizing in real time
- BTwo database servers, one online and one off-line, synchronizing every five hours
- CThee database servers, both off-line and synchronizing after restoring to the third node
- DThree database servers, with a heartbeat between each of them, using asynchronous replication
How the community answered
(58 responses)- A71% (41)
- B16% (9)
- C5% (3)
- D9% (5)
Why each option
To achieve high availability with no data loss from a single server failure, the administrator should recommend two online database servers synchronizing in real time using synchronous replication.
Two database servers, both online and synchronizing in real time, typically indicates a synchronous replication setup (e.g., a database cluster with shared storage or Always On Availability Groups). This configuration ensures that all transactions are committed to both servers before being acknowledged, thus guaranteeing no data loss in the event of a single server failure and providing high availability through immediate failover.
Synchronizing every five hours means there would be up to five hours of data loss if the online server failed, violating the "no data loss" requirement.
Having both database servers offline and requiring restoration to a third node describes a disaster recovery strategy, not a high availability solution, and would involve significant downtime and potential data loss.
Asynchronous replication, by its nature, allows for a window of potential data loss because transactions are committed on the primary before being replicated to the secondary, failing the "no data loss" requirement.
Concept tested: Database high availability and replication types
Source: https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/overview-of-sql-server-alwayson-availability-groups-sql-server?view=sql-server-ver16
Topics
Community Discussion
No community discussion yet for this question.