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.
Can someone help explain (so I can learn :)) why they both would be synchronous? Thanks in advance.
0
1
Because in asynchronous data replication some recent updates can be lost in the event of disaster. So AD1 needs to be synchronous and automatic.
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-high-availability-dr
0
0
https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/availability-modes-always-on-availability-groups#AsyncCommitAvMode
0
0
For me the answer should be like that:
In AD1, configure synchronous replication and automatic failover. In PD1, configure asynchronous replication and manual failover from AD1.
But this answer is not an option. Could somebody explin why in PD1 is synchronous replication?
2
0
I believe you are right, for automatic failover must use synchronous. For manual with accepted data lost asynchronous.
2
0
agreed as well.
1
0
these requirements though…
-ensure that there is NO data loss
-some data loss is oKAY
what?
0
0
Nvm i’m dumb i re-read the question.
2
0
@Scott.. Nope-still a dumb requirement 🙂
0
0
By the way, part of the new 243Q 70-533 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpfnV3MVl6X3pXOWw1Z3YtQUpJRVRiTkNkbGNFbVBNRXhjSkw3bWk1WHdYcW8
Best Regards!
0
0
When these replicas are connected and the database is synchronized, manual failover is supported. If the secondary replica goes down, the primary replica is unaffected. The primary replica runs exposed if no SYNCHRONIZED replicas exist (that is, without sending data to any secondary replica). If the primary replica is lost, the secondary replicas enter the RESOLVING state, but the database owner can force a failover to the secondary replica (with possible data loss).
1
0