Question 350
An Azure security engineer investigates the following incident: An Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path. Which safeguard would best prevent this issue from recurring?
Explanation
Correct Answer
This guardrail addresses application gateway backend health probes: The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The prevention measure is: Validate probe host/path behavior whenever application URLs or certificates change. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
The function hosting plan and network integration/DNS are not configured for the required private destination. “Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services” would address that alternative cause, not the condition in this question: the backend health probe is failing due to its configured request host, path or expected response rather than VM availability.
“Test TLS protocol settings and certificate expiry after changes to public application endpoints” responds to this separate finding: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. This question instead needs “Validate probe host/path behavior whenever application URLs or certificates change”, so the alternative does not meet the stated condition.
The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. “Review the APIM tier's supported private networking features before selecting gateway architecture” applies to that separate problem. The observed case is an Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path; choosing this alternative would address the wrong failure mode.