Worked example
A NACL on a subnet allows all inbound HTTPS. The team adds a NACL rule to block one abusive source IP. Requests from that IP still get through. What is the most likely cause?
- ASecurity groups override network ACL deny rules
- BThe deny rule has a higher rule number than the allowCorrect
- CThe IP must also be removed from the route table
- DNACLs cannot deny traffic, only allow it
Why B
NACL rules are evaluated in ascending number order and the first match wins, so a broad allow at a lower number matches before the specific deny. Renumbering the deny below the allow makes it take effect; SGs and route tables are unrelated here.
Our blueprint tag — not a source
SAA-C03 · Domain 1 of 4 · Design Secure Architectures
We wrote this question and filed it under that domain. The domain name and its position in the outline come from the SAA-C03 exam guide (PDF, opens d1.awsstatic.com in a new tab).