Security groups vs NACLs decision in AWS - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Security Groups and NACLs

Which statement correctly describes the main difference between Security Groups and Network ACLs (NACLs) in AWS?

A NACLs are stateful and control traffic for individual instances, while Security Groups are stateless and control traffic at the subnet level.

B Security Groups act as virtual firewalls for instances and are stateful, while NACLs are stateless and operate at the subnet level.

C Both Security Groups and NACLs are stateful and operate at the instance level.

D Security Groups and NACLs both operate at the subnet level and are stateless.

💡 Hint

Think about where each one applies and whether they remember previous traffic.

Security Groups are stateful and attached to instances, meaning they remember traffic and automatically allow return traffic. NACLs are stateless and apply to subnets, so return traffic must be explicitly allowed.

❓ Architecture

intermediate

Choosing Between Security Groups and NACLs

You want to protect a public subnet in your VPC from unwanted inbound traffic but allow all outbound traffic. Which AWS feature should you configure primarily to block unwanted inbound traffic efficiently?

A Configure only Security Groups to deny unwanted inbound traffic; NACLs are not needed.

B Configure a Security Group with rules to deny unwanted inbound traffic and allow all outbound traffic.

C Configure both Security Groups and NACLs to deny unwanted inbound traffic and allow all outbound traffic.

D Configure a Network ACL with rules to deny unwanted inbound traffic and allow all outbound traffic.

💡 Hint

Consider which feature applies at the subnet level and can block traffic before it reaches instances.

NACLs operate at the subnet level and can block unwanted inbound traffic before it reaches instances. Security Groups control traffic at the instance level but cannot block traffic before it reaches the subnet.

❓ security

advanced

Impact of Stateless NACLs on Return Traffic

You have a NACL that allows inbound HTTP (port 80) traffic but does not explicitly allow outbound HTTP traffic. What will happen when a client tries to access a web server in the subnet?

A The client will connect, but responses will be delayed due to NACL processing.

B The client connection will fail because Security Groups block inbound HTTP traffic by default.

C The client will not receive responses because NACLs are stateless and outbound HTTP traffic is blocked by default.

D The client will successfully connect and receive responses because Security Groups allow return traffic automatically.

💡 Hint

Remember that NACLs are stateless and require explicit rules for both inbound and outbound traffic.

NACLs do not remember traffic state, so if outbound HTTP traffic is not allowed explicitly, the return traffic will be blocked, causing the client to not receive responses.

✅ Best Practice

advanced

Best Practice for Layered Security in AWS Networking

Which approach best follows AWS security best practices for controlling traffic to instances in a public subnet?

A Use NACLs to block unwanted inbound traffic and Security Groups to allow only necessary inbound traffic to instances.

B Use only Security Groups to control all inbound and outbound traffic to instances.

C Use Security Groups to block all inbound traffic and NACLs to allow only necessary inbound traffic to instances.

D Use only NACLs to control all inbound and outbound traffic at the subnet level.

💡 Hint

Think about defense in depth and where each control is applied.

Best practice is to use NACLs as a coarse filter at the subnet level and Security Groups as fine-grained controls at the instance level, providing layered security.

❓ service_behavior

expert

Effect of Overlapping Rules in Security Groups and NACLs

You have a Security Group that allows inbound SSH (port 22) from anywhere and a NACL that denies inbound SSH from all IPs. What will be the result when you try to SSH into an instance in that subnet?

A SSH connections will be blocked because NACLs deny traffic before Security Groups allow it.

B SSH connections will succeed because Security Groups allow the traffic and are stateful.

C SSH connections will be allowed only if the instance is in a private subnet.

D SSH connections will fail due to conflicting rules causing a timeout.

💡 Hint

Consider the order in which AWS processes NACLs and Security Groups.

NACLs are evaluated before Security Groups. If a NACL denies traffic, it is blocked before reaching the instance, regardless of Security Group rules.

Practice

1. Which statement best describes the main difference between AWS Security Groups and Network ACLs (NACLs)?

easy

A. Security Groups control subnet-level traffic; NACLs control instance-level traffic.

B. Security Groups are stateful and control instance-level traffic; NACLs are stateless and control subnet-level traffic.

C. Both Security Groups and NACLs are stateful and control instance-level traffic.

D. NACLs are stateful and control instance-level traffic; Security Groups are stateless and control subnet-level traffic.

Solution

1. Step 1: Understand Security Groups behavior

   Security Groups are stateful, meaning they remember allowed connections and automatically allow return traffic. They work at the instance level.

2. Step 2: Understand NACLs behavior

   NACLs are stateless, so they do not remember previous traffic and require explicit rules for both inbound and outbound traffic. They apply at the subnet level.

3. Final Answer:

   Security Groups are stateful and control instance-level traffic; NACLs are stateless and control subnet-level traffic. -> Option B

4. Quick Check:

   Stateful = Security Groups, Stateless = NACLs [OK]

Hint: Security Groups = instance + stateful; NACLs = subnet + stateless [OK]

Common Mistakes:

• Confusing which is stateful or stateless
• Mixing instance-level and subnet-level controls
• Assuming both control the same traffic scope

2. Which of the following is the correct way to allow inbound HTTP traffic on port 80 using a Security Group rule in AWS?

easy

A. Allow outbound TCP traffic on port 80 from 0.0.0.0/0

B. Allow inbound UDP traffic on port 80 from 0.0.0.0/0

C. Allow inbound TCP traffic on port 80 from 0.0.0.0/0

D. Allow inbound TCP traffic on port 22 from 0.0.0.0/0

Solution

1. Step 1: Identify correct protocol and port for HTTP

   HTTP uses TCP protocol on port 80, so the rule must allow inbound TCP traffic on port 80.

2. Step 2: Confirm direction and source

   Inbound traffic must be allowed from any IP (0.0.0.0/0) to accept public HTTP requests.

3. Final Answer:

   Allow inbound TCP traffic on port 80 from 0.0.0.0/0 -> Option C

4. Quick Check:

   HTTP = TCP port 80 inbound [OK]

Hint: HTTP uses TCP port 80 inbound, not UDP or outbound [OK]

Common Mistakes:

• Allowing UDP instead of TCP
• Setting outbound instead of inbound
• Using wrong port like 22 (SSH)

3. You have a subnet with a NACL that allows inbound traffic on port 443 but denies all outbound traffic. A Security Group attached to an instance in this subnet allows inbound and outbound HTTPS traffic on port 443. What will happen when the instance tries to respond to an HTTPS request?

medium

A. The response will be blocked because the NACL denies outbound traffic.

B. The response will be allowed because Security Groups are stateful.

C. The response will be allowed because NACLs override Security Groups.

D. The response will be blocked because Security Groups deny outbound traffic.

Solution

1. Step 1: Analyze NACL outbound rules

   The NACL denies all outbound traffic, so no outbound packets can leave the subnet regardless of Security Group settings.

2. Step 2: Analyze Security Group statefulness

   Security Groups are stateful and allow return traffic, but they cannot override the stateless NACL's explicit deny on outbound traffic.

3. Final Answer:

   The response will be blocked because the NACL denies outbound traffic. -> Option A

4. Quick Check:

   NACL deny outbound blocks response despite Security Group [OK]

Hint: NACL deny rules always block, even if Security Group allows [OK]

Common Mistakes:

• Assuming Security Groups override NACLs
• Ignoring NACL outbound deny effect
• Confusing stateful and stateless behavior

4. A developer configures a NACL to allow inbound SSH (port 22) traffic but forgets to add an outbound rule to allow return traffic. The Security Group allows inbound and outbound SSH traffic. What issue will occur when trying to SSH into an instance in this subnet?

medium

A. SSH connection will fail because NACL outbound traffic is blocked.

B. SSH connection will succeed because Security Groups allow traffic.

C. SSH connection will fail because Security Groups block inbound traffic.

D. SSH connection will succeed because NACLs are stateful.

Solution

1. Step 1: Check NACL outbound rules

   NACLs are stateless, so return traffic must be explicitly allowed. Missing outbound rule blocks return SSH packets.

2. Step 2: Check Security Group rules

   Security Groups allow inbound and outbound SSH, but cannot override NACL blocking outbound return traffic.

3. Final Answer:

   SSH connection will fail because NACL outbound traffic is blocked. -> Option A

4. Quick Check:

   NACL stateless requires outbound allow for return traffic [OK]

Hint: NACLs need both inbound and outbound rules for two-way traffic [OK]

Common Mistakes:

• Assuming Security Groups fix NACL outbound block
• Forgetting NACLs are stateless
• Thinking inbound allow is enough

5. You want to secure a multi-tier web application in AWS. The web servers are in a public subnet, and the database servers are in a private subnet. Which combination of Security Groups and NACLs is the best practice to control traffic securely?

hard

A. Use NACLs to allow web traffic to web servers and database traffic only from web servers; use Security Groups to block all traffic.

B. Use NACLs to allow all traffic between web and database subnets; use Security Groups to block all traffic.

C. Use Security Groups to allow all traffic between subnets; use NACLs to allow all inbound and outbound traffic.

D. Use Security Groups to allow web traffic to web servers and database traffic only from web servers; use NACLs to block all inbound traffic except HTTP/HTTPS on the public subnet.

Solution

1. Step 1: Use Security Groups for instance-level control

   Security Groups should allow web servers to receive HTTP/HTTPS and allow database servers to accept traffic only from web servers for tight control.

2. Step 2: Use NACLs for subnet-level filtering

   NACLs should block unwanted inbound traffic on the public subnet except HTTP/HTTPS to reduce exposure at the subnet level.

3. Final Answer:

   Use Security Groups to allow web traffic to web servers and database traffic only from web servers; use NACLs to block all inbound traffic except HTTP/HTTPS on the public subnet. -> Option D

4. Quick Check:

   Security Groups for instances, NACLs for subnet filtering [OK]

Hint: Security Groups for instances, NACLs for subnet-wide rules [OK]

Common Mistakes:

• Using NACLs to allow all traffic defeats subnet security
• Blocking all traffic with Security Groups breaks communication
• Confusing roles of Security Groups and NACLs