Exam DP-300 topic 11 question 3 discussion

I say update connection strings. It is a sort of given (as it's recommended by Microsoft) that firewall rules be the same for master & secondary. https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview#keeping-credentials-and-firewall-rules-in-sync

application connection also need to update as Geo replication is being used, not automatic failover groups where you can have a listener

B. Update the connection strings of SalesSQLDb1App1. Here’s why: Geo-replicated Azure SQL Database setups typically require that the connection string be updated to point to the new primary database after a failover. Since SalesSQLDb1 is in a geo-replicated environment, the failover can cause the database role to switch, and the application’s connection string must point to the correct replica (the new primary). Updating the connection string ensures that the application (SalesSQLDb1App1) connects to the appropriate primary replica of SalesSQLDb1.

B is the correct answer. As per the case study scenario the database already has database -level firewall rules and the database is in geo-replication. No need to make changes in the firewall rules as they get replicated to the secondary replica.

https://azure.microsoft.com/en-us/blog/azure-sql-database-now-supports-transparent-geographic-failover-of-multiple-databases-featuring-automatic-activation/

https://azure.microsoft.com/en-us/blog/azure-sql-database-now-supports-transparent-geographic-failover-of-multiple-databases-featuring-automatic-activation/

B is the correct answer Geo-replicated db have to change the connection string for your application after a geo-failover.

The given answer is correct: C. Update the firewall rules of SalesSQLDb1. there will be two listeners in the failover group that do not change: Read/write listener endpoint: <sqlfailovergroup>.database.windows.net Read-only listener endpoint: <sqlfailovergroup>.secondary.database.windows.net https://docs.microsoft.com/en-us/azure/azure-sql/database/auto-failover-group-sql-db?tabs=azure-powershell Endpoint redirection Auto-failover groups provide read-write and read-only listener end-points that remain unchanged during geo-failovers. This means you do not have to change the connection string for your application after a geo-failover, because connections are automatically routed to the current primary. Whether you use manual or automatic failover activation, a geo-failover switches all secondary databases in the group to the primary role. After the geo-failover is completed, the DNS record is automatically updated to redirect the endpoints to the new region.

Update connection string in apps server

Update connection string

Update connection string is more reasonable

this question is not well formed because you dont know if they are talking about the failover after or before the migration since geo replication has failover and auto failover groups too

I think you are right, wouln't the firewall rules be there already, I would say update connection string is the correct answer