Question 480
While validating an Azure workload, the security team finds: A private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure. Which outcome most clearly verifies that the issue is resolved?
Explanation
Correct Answer
This validates the specific control for connection troubleshoot destination metrics: A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. The associated corrective action is: Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results. Testing a different component would not establish this result.
Incorrect Answers
Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. “Associate intended eligible VNets with the correct plan and validate protection settings” would address that alternative cause, not the condition in this question: a point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.
“Inspect effective routes and run Network Watcher next hop against the intended destination IP” responds to this separate finding: a user-defined or propagated route controls the next hop independently of NSG allow decisions. This question instead needs “Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results”, so the alternative does not meet the stated condition.
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” applies to that separate problem. The observed case is a private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure; choosing this alternative would address the wrong failure mode.