Question 160
A production Azure security implementation shows this failure: A subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet. What should the engineer implement first to address the weakness?
Explanation
Correct Answer
The cause is: Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The appropriate change is: Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls. Verify it with this outcome: Unauthorized Internet egress fails while approved endpoints remain reachable through logged channels.
Incorrect Answers
This action concerns asymmetric routing around network virtual appliance, where Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. The reported incident instead involves Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.
This action concerns stateful nsg return traffic behavior, where NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The corrective response here is “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls”; this alternative does not provide that response.
This action concerns subnet versus nic nsg evaluation, where Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. The stem reports a subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet; this control addresses a different failure condition.