You administer all the deployments of Microsoft SQL Server 2012 in your company. You have two servers in
the same data center that hosts your production database.
You need to ensure that the database remains available if a catastrophic server failure or a disk failure occurs.
You also need to maintain transactional consistency of the data across both servers.
You need to achieve these goals without manual intervention.
Which configuration should you use?
A.
Two servers configured in a Windows Failover Cluster in the same data center SQL Server configured as a
clustered instance
B.
SQL Server that includes an application database configured to perform transactional replication
C.
Two servers configured in the same data center
A primary server configured to perform log-shipping every 10 minutes A backup server configured as a
warm standby
D.
Two servers configured in different data centers
SQL Server Availability Group configured in Synchronous-Commit Availability Mode One server configured
as an Active Secondary
E.
Two servers configured in the same data center
SQL Server Availability Group configured in Asynchronous-Commit Availability Mode One server configured
as an Active Secondary
F.
Two servers configured in different data centers
SQL Server Availability Group configured in Asynchronous-Commit Availability Mode
G.
SQL Server that includes an application database configured to perform snapshot replication
H.
Two servers configured on the same subnet
SQL Server Availability Group configured in Synchronous-Commit Availability Mode
Explanation:
Always On availability groups supports two availability modes—asynchronous-commit mode and synchronous-commit mode
Synchronous-commit mode emphasizes high availability over performance, at the cost of increased transaction
latency.
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/availabilitymodes-always-on-availability-groups#SyncCommitAvMode