⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All AWS & Cloud Architecture Interview Questions Scenario 20 of 179 in AWS & Cloud Architecture
Junior / Associate DevOps [L1] AWS Networking & VPC Core Fundamentals [L1]
🎯 Target Role / Context: AWS Scenario #13 (L1) · Networking & VPC

Q: What is the difference between a Security Group and a Network ACL (NACL)?

Architectural comparison between AWS Security Groups (stateful, instance-level firewall) and Network ACLs (stateless, subnet-level packet filter).

#AWS #Networking & VPC #L1 #Cloud #Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""In our AWS cloud environment, we managed high-traffic microservices where this exact scenario occurred. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "In our AWS cloud environment, we managed high-traffic microservices where this exact scenario occurred. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."

1️⃣

Production Solution & Architecture

Security Groups and Network Access Control Lists (NACLs) form AWS's defense-in-depth perimeter. Security Groups act as stateful firewalls at the virtual network interface (ENI) level, whereas NACLs act as stateless packet filters at the subnet boundary.

⚡ Security Group vs NACL Architectural Matrix
Architectural DimensionSecurity GroupNetwork ACL (NACL)
Enforcement LevelInstance / ENI LevelSubnet Boundary Level
Connection StateStateful (return traffic automatically allowed)Stateless (inbound & outbound evaluated separately)
Supported Rule TypesAllow rules onlyAllow AND Deny rules
Rule Evaluation OrderAll rules evaluated simultaneouslyProcessed strictly in numerical order (lowest first)
Ephemeral Port HandlingHandled automatically via state trackingRequires explicit outbound allow for ports 1024–65535
  • Security Groups Best Practice: Apply granular, least-privilege security between microservices and databases within your VPC.
  • NACLs Best Practice: Apply coarse subnet-level shields (such as dropping known malicious IP/CIDR ranges or blocking specific external protocols).
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Security Groups are stateful ENI firewalls evaluating all rules simultaneously; NACLs are stateless subnet firewalls evaluating ordered allow/deny rules."
⚡ 60-Second Elevator Pitch Talking Points
  • Security Group: Instance/ENI level, stateful connection tracking, allow-only rules.
  • Network ACL: Subnet boundary level, stateless packet inspection, ordered allow and deny rules.
  • Defense-in-Depth Pattern: Pair coarse NACL CIDR blocks at the subnet edge with fine-grained Security Groups per service tier.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when addressing difference Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
  2. Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
  3. Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
  4. Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.
Advertisement
Want more AWS & Cloud Architecture scenarios?
Explore our complete collection of scenario-based AWS & Cloud Architecture interview runbooks.
Browse All AWS & Cloud Architecture Questions →