AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A solutions architect is designing a multi-tier web application in a VPC. The architecture consists of a fleet of web servers in a public subnet and a fleet of application servers in a private subnet. The web servers must accept HTTPS traffic (TCP port 443) from clients on the internet. The security group for the web servers correctly allows inbound traffic on TCP port 443 from 0.0.0.0/0. Despite this, users report intermittent connection timeouts when accessing the application. A review of VPC Flow Logs shows that SYN packets from clients are reaching the web servers, but the corresponding SYN-ACK responses from the servers are being dropped. What is the MOST likely cause of this issue and the correct way to resolve it?
The security group for the web servers is missing an outbound rule. Add an outbound rule to the security group to allow traffic on TCP ports 1024-65535 to 0.0.0.0/0.
The network ACL for the private subnet is blocking return traffic. Add an outbound rule to the private subnet's NACL to allow traffic on TCP ports 1024-65535 to the public subnet's CIDR range.
The network ACL for the public subnet is blocking inbound traffic. Add an inbound rule with a lower number than the default deny rule to allow TCP port 443 from source 0.0.0.0/0.
The network ACL for the public subnet is blocking outbound return traffic. Add an outbound rule to the public subnet's NACL to allow traffic on TCP ports 1024-65535 to destination 0.0.0.0/0.
The correct answer is that the network ACL (NACL) for the public subnet is missing an outbound rule for ephemeral ports. Security groups are stateful, meaning that if inbound traffic is allowed, the corresponding return traffic is automatically permitted. NACLs, however, are stateless. This means that for every inbound request allowed, a corresponding outbound rule must exist to allow the response traffic back to the source. When a client connects to a server, it opens a random, high-numbered port (an ephemeral port, typically in the range of 1024-65535) to receive the return traffic. The public subnet's NACL must explicitly allow outbound traffic destined for this ephemeral port range to permit the web server's response to reach the client. Without this rule, the server's response packets are dropped at the subnet boundary, causing the client to eventually time out.
Modifying the security group's outbound rules is incorrect because security groups are stateful; return traffic for an allowed inbound connection is automatically permitted without a specific outbound rule.
Adding an inbound NACL rule for port 443 is not the solution because the scenario states that SYN packets are already reaching the web servers, indicating that inbound traffic is permitted. The issue lies with the return (outbound) traffic.
Modifying the NACL for the private subnet is incorrect as the problem described is between the internet clients and the web servers in the public subnet, not between the web and application tiers.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the difference between stateful and stateless rules in AWS security mechanisms?
Open an interactive chat with Bash
What are ephemeral ports, and why are they important in this scenario?
Open an interactive chat with Bash
Why is modifying the private subnet NACL not the correct solution here?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access