Question 140
After correcting this architecture issue: An Azure hub-and-spoke topology sends spoke traffic directly over VNet peering, bypassing its security hub. Which ongoing control belongs in the runbook?
Explanation
Correct Answer
Audit effective UDRs for every new spoke and subnet. This lowers the risk linked to: Azure peering reachability is not synonymous with centralized security inspection. Verification should show: Two controlled spoke flows traverse the approved inspection hub and return symmetrically.
Incorrect Answers
Include zone-failure traffic tests in production readiness review. This safeguard addresses another situation: An organization deploys one VM-Series appliance in one Azure availability zone despite a strong continuity target. It is less directly relevant than the control for: Azure peering reachability is not synonymous with centralized security inspection.
Run probe packet captures before declaring a firewall unavailable. This safeguard addresses another situation: An Azure internal load balancer distributes firewall flows but loses health probes because the probe path is blocked. It is less directly relevant than the control for: Azure peering reachability is not synonymous with centralized security inspection.
Test failover while monitoring inspection logs and session continuity. This safeguard addresses another situation: One GCP zone contains all inline security appliances for a customer-facing application with a multi-zone uptime target. It is less directly relevant than the control for: Azure peering reachability is not synonymous with centralized security inspection.