Question 480
Following the issue — An Azure Firewall DNS proxy is required for FQDN filtering but spoke clients use unrelated resolvers. — the team takes this action: Configure the approved firewall DNS proxy and spoke resolver path coherently. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Audit DNS proxy and forwarder paths after network topology modifications. This mitigates the control weakness because: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. Keep the intervention, Configure the approved firewall DNS proxy and spoke resolver path coherently., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Hub security policy works only when routing actually passes the inspection point. The continuing risk here is determined by: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. The targeted safeguard is “Audit DNS proxy and forwarder paths after network topology modifications”.
“Continuously review public management-port exposure and NSG rule exceptions” addresses a different recurring failure: Network security group rules filter traffic by specified source, destination, ports, direction, and priority. For the condition in this question, maintain “Audit DNS proxy and forwarder paths after network topology modifications” because name resolution differences can cause FQDN-based firewall policies to behave unexpectedly.
This safeguard is for the dependency described by: Private endpoint creation does not automatically mean every public endpoint path is prohibited. The continuing risk here is determined by: Name resolution differences can cause FQDN-based firewall policies to behave unexpectedly. The targeted safeguard is “Audit DNS proxy and forwarder paths after network topology modifications”.