Exam DP-300 topic 6 question 42 discussion

C: Connect each VM to a single subnet in a vnet. Because, in this scenario we can use DNN, which allows for: Failover time: Failover time is faster when using a DNN listener since there's no need to wait for the network load balancer to detect the failure event and change its routing. Existing connections: Connections made to a specific database within a failing-over availability group will close, but other connections to the primary replica will remain open since the DNN stays online during the failover process. https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview?view=azuresql-vm#connectivity

I would go with D , and not C as Connect each virtual machine to a single subnet on a single virtual network: This option misses the need for a load balancer to properly route traffic to the appropriate replica in case of failover, which is crucial for maintaining connection continuity during failover.

I would go with D

Answer C is correct because one of the requirements is to maintain existing connections to Primary replica during failover, which is only possible with DNN configuration and this settings works best when Azure SQL Server VMs to a single subnet. we can only go with OPTION C because option D has Azure standard load balancer in the choice which means you can not use DNN so, you either configure Azure Load balancer/VNN with single subnet OR configure DNN with single subnet. Option c meets the requirement, Hence clearly Answer is C. https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview?view=azuresql

Answer C is correct because one of the requirements is to maintain existing connections to Primary replica during failover, which is only possible with DNN configuration and this settings works best when Azure SQL Server VMs to a single subnet. we can only go with OPTION C because option D has Azure standard load balancer in the choice which means you can not use DNN so, you either configure Azure Load balancer/VNN with single subnet OR configure DNN with single subnet. Option c meets the requirement, Hence clearly Answer is C

distributed network name (DNN)

it is B without a doubt, as singled out by kenn1234 and vcloudpmp. plus I have done this quite a number of times already: different subnets in the same VNET.

To match the on-premises experience for connecting to your availability group listener, deploy your SQL Server VMs to multiple subnets within the same virtual network. Having multiple subnets negates the need for the extra dependency on an Azure Load Balancer, or a distributed network name (DNN) to route your traffic to your listener. ref: https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-overview?view=azuresql-vm#connectivity

https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-load-balancer-portal-configure?view=azuresql-vm There are many methods to deploy an availability group. Simplify your deployment and eliminate the need for an Azure Load Balancer or distributed network name (DNN) for your Always On availability group by creating your SQL Server virtual machines (VMs) in multiple subnets within the same Azure virtual network. If you've already created your availability group in a single subnet, you can migrate it to a multi-subnet environment.

D is correct

any reason why not d, i think the lb will help in minimizing time?