70-473 · Question #80
Your environment contains a Microsoft Azure machine that has Microsoft SQL Server Standard installed. An application named App1 uses the data stored in SQL server. The Service level Agreement (SLA)…
The correct answer is D. Log Shipping. To provide disaster recovery for SQL Server Standard Edition with a 10-minute RPO and availability across two additional Azure regions, Log Shipping is the appropriate solution.
Question
Options
- AMerge Replication
- BAlwaysOn Failover Cluster Instances
- CAlwaysOn Availability Groups
- DLog Shipping
How the community answered
(35 responses)- A11% (4)
- B9% (3)
- C34% (12)
- D46% (16)
Why each option
To provide disaster recovery for SQL Server Standard Edition with a 10-minute RPO and availability across two additional Azure regions, Log Shipping is the appropriate solution.
Merge Replication is primarily designed for data synchronization in disconnected or occasionally connected environments and is not an optimal or robust solution for achieving low RPO disaster recovery for a critical application.
AlwaysOn Failover Cluster Instances provide high availability within a single Windows Server Failover Cluster, typically across nodes in the same datacenter or region, but do not provide disaster recovery across multiple Azure regions.
AlwaysOn Availability Groups are not available in SQL Server Standard Edition, which is specified in the question, and thus cannot be implemented.
Log Shipping supports cross-region disaster recovery for SQL Server Standard Edition by periodically backing up transaction logs from the primary server and restoring them to one or more secondary servers. This method allows for a low Recovery Point Objective (RPO) within minutes and ensures data availability even if two Azure regions fail, by configuring multiple secondary servers.
Concept tested: SQL Server disaster recovery, Edition features
Source: https://learn.microsoft.com/en-us/sql/database-engine/log-shipping/about-log-shipping-sql-server
Topics
Community Discussion
No community discussion yet for this question.