Q: 3
You use Azure virtual machines to run a custom application that uses an Azure SQL database on the
back end.
The IT apartment at your company recently enabled forced tunneling,
Since the configuration change, developers have noticed degraded performance when they access
the database
You need to recommend a solution to minimize latency when accessing the database. The solution
must minimize costs
What should you include in the recommendation?
Options
Discussion
Option D here. Setting up a VNet service endpoint lets the VM traffic hit Azure SQL directly without hairpinning through on-premises, so latency drops a lot. I think C is more for HA, not really fixing the forced tunneling problem. If anyone’s gotten D wrong in practice exams let me know, but pretty sure this is it.
D is the way to go since VNET service endpoints cut out the forced tunneling and let traffic take the faster Azure path. Makes it way less latent and doesn't add cost. I think that's what MS wants here, but open to other ideas.
D imo. C is tempting but it's more about HA, D fixes the forced tunnel latency trap.
D for sure. C’s only tempting if you miss that forced tunneling is the trap, D actually fixes the latency.
C/D? I was thinking C since Always On can improve app performance through replication, but not sure it tackles the forced tunneling latency issue here. D seems more direct, but C looked tempting for HA fans.
C tbh, since Always On availability groups could help with redundancy and maybe improve performance. Saw a similar scenario mentioned in the official study guide where AGs were recommended for high availability, so thought it'd fit here. I might be mixing up fault tolerance with latency though. Anyone check this in practice tests?
Be respectful. No spam.
