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
D . VNET service endpoint avoids the forced tunneling hairpin and gives a direct Azure path, which solves the latency with no extra cost. A looks tempting but it's more expensive for this scenario. Anyone disagree?
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.
Its D, but only because forced tunneling delays get fixed by VNET service endpoints specifically in this forced route case.
Devs hit latency because forced tunneling pushes traffic through on-prem, adding delay. D lets you bypass that by using VNET service endpoints for direct Azure backbone access. Pretty sure that's the cheapest fix too. Agree?
D
Guessing D, had something like this in a mock and service endpoints solved the latency after forced tunneling was enabled.
D , since VNET service endpoints cut out the forced tunnel so latency drops. Anyone see a valid case for B here?
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.
Nah, you want D here. A trips people up but doesn't solve the tunnel latency like a VNET service endpoint.
Be respectful. No spam.
