A SysOps Administrator is hosting a web application on an Amazon EC2 instance in a public subnet. To allow public HTTP access, the administrator creates a custom Network Access Control List (NACL) associated with the subnet and adds an inbound rule allowing TCP traffic on port 80 from 0.0.0.0/0. The security group associated with the EC2 instance already allows all inbound and outbound traffic. However, external web clients are still unable to load the website. Which configuration change must the administrator make to allow clients to establish HTTP connections?
- Add an outbound rule to the custom NACL allowing TCP traffic on ports 1024-65535 to 0.0.0.0/0.Answer
- BAdd an outbound rule to the custom NACL allowing TCP traffic on port 80 to 0.0.0.0/0.
- CAdd an outbound rule to the EC2 instance's security group allowing TCP traffic on ports 1024-65535 to 0.0.0.0/0.
- DAdd an inbound rule to the custom NACL allowing TCP traffic on ports 1024-65535 from 0.0.0.0/0.
Answer
Add an outbound rule to the custom NACL allowing TCP traffic on ports 1024-65535 to 0.0.0.0/0.
The correct option is the one stating that an outbound rule must be added to the custom NACL to allow TCP traffic on ports 1024-65535. Network Access Control Lists (NACLs) operate at the subnet level and are stateless, meaning they do not track connection states. Therefore, outbound response traffic must be explicitly permitted. When client browsers send requests to port 80, they expect the return traffic on a randomly allocated ephemeral port (1024-65535). Adding this rule allows the response traffic to flow back to the clients.
Step-by-Step Solution
Key Concept
Stateless Network Access Control Lists (NACLs) require explicit outbound rules for ephemeral port ranges to allow response traffic back to clients.
Estimated Time:1m 0s