Question 760
A regulated Azure tenant has this security condition: An application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress. Which result confirms the relevant security control is effective?
Explanation
Correct Answer
This validates the specific control for network watcher next hop diagnosis: A user-defined or propagated route controls the next hop independently of NSG allow decisions. The associated corrective action is: Inspect effective routes and run Network Watcher next hop against the intended destination IP. Testing a different component would not establish this result.
Incorrect Answers
The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable” would address that alternative cause, not the condition in this question: a user-defined or propagated route controls the next hop independently of NSG allow decisions.
“Configure a supported Private Link origin and restrict direct public access to the origin service” responds to this separate finding: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction. This question instead needs “Inspect effective routes and run Network Watcher next hop against the intended destination IP”, so the alternative does not meet the stated condition.
Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Configure relevant firewall diagnostic categories and secure retention for rule and threat events” applies to that separate problem. The observed case is an application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress; choosing this alternative would address the wrong failure mode.