You have an application that uses SQL Server in an Azure virtual machine (VM) to store data.If the VM running the primary instance of SQL Server fails:
– The application must automatically begin using a backup copy of the SQL Server data.
– The recovery solution must guarantee that no data is lost.
If the primary datacenter fails:
– There must be a way to manually switch to a secondary data center.
– Some data loss is acceptable.
You create an active datacenter named AD1 and a passive datacenter named PD1. AD1 has two SQL Server
instances. PD1 has one SQL Server instance.
You need to implement the replication and failover solutions for the application.
What should you do?
A.
In AD1, configure asynchronous replication and automatic failover. In PD1, configure synchronous
replication and manual failover from AD1.
B.
In AD1, configure synchronous replication and automatic failover. In PD1, configure synchronous replication
and manual failover from AD1.
C.
In AD1, configure synchronous replication and manual failover. In PD1, configure asynchronous replication
and manual failover from AD1.
D.
In AD1, configure asynchronous replication and manual failover. In PD1, configure asynchronous replication
and manual failover from AD1.
Should be “C”. Synchronous replication across DCs will drop the performance and it is stated that some loss is allowed. Asynchronous replication and manual failover looks a better suitable solution.
would agree with that
-The recovery solution must guarantee that no data is lost
Asynchronous setting chances of data lose, that the reason Answer B
The answer is C. Setting synchronous replication across DC will decrease the speed of the SQL dramatically.
Active geo-replication leverages the Always On technology of SQL Server to asynchronously replicate committed transactions on the primary database to a secondary database using read committed snapshot isolation (RCSI). Auto-failover groups provide the group semantics on top of active geo-replication but the same asynchronous replication mechanism is used. While at any given point, the secondary database might be slightly behind the primary database, the secondary data is guaranteed to never have partial transactions. Cross-region redundancy enables applications to quickly recover from a permanent loss of an entire datacenter or parts of a datacenter caused by natural disasters, catastrophic human errors, or malicious acts. The specific RPO data can be found at Overview of Business Continuity.
New 70-533 VCE Dumps: https://www.braindump2go.com/70-533.html
Reman’s dump is not the current one
Answer is be based upon the words “must automatically begin” and “must guarantee that no data is lost” only answer B (auto failover at AD1) meets the first criteria and synchronous replication for both sites meets the second.