Question 50
An Azure security engineer investigates the following incident: Azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week. Which outcome most clearly verifies that the issue is resolved?
Explanation
Correct Answer
This validates the specific control for firewall diagnostic settings and retention: Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The associated corrective action is: Configure relevant firewall diagnostic categories and secure retention for rule and threat events. Testing a different component would not establish this result.
Incorrect Answers
The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. “Configure a supported Private Link origin and restrict direct public access to the origin service” would address that alternative cause, not the condition in this question: required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination.
“Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” responds to this separate finding: an application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. This question instead needs “Configure relevant firewall diagnostic categories and secure retention for rule and threat events”, so the alternative does not meet the stated condition.
The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. “Run Network Watcher IP flow verify with the test source, destination, direction and port” applies to that separate problem. The observed case is azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week; choosing this alternative would address the wrong failure mode.