- A
The outbound rule of the network ACL does not allow ephemeral ports for return traffic.
Why wrong: The outbound rule allows all traffic, so ephemeral ports are allowed.
- B
The new network ACL was not associated with the private subnet.
If the NACL is not associated, the default NACL (which allows all) is in effect. But the engineer associated it; however, maybe they associated it with the wrong subnet. This is a common oversight.
- C
The security group on the EC2 instances still allows SSH from 0.0.0.0/0.
Why wrong: The security group was corrected to allow from bastion only, so this would not block SSH from bastion.
- D
The network ACL rules are out of order; the deny rule should be before the allow rule.
Why wrong: Rules are evaluated from lowest number to highest; allow before deny is correct.
Quick Answer
The answer is that the new network ACL was not associated with the private subnet. Even though the engineer created a correctly ordered NACL with an inbound allow rule for the bastion host’s IP and a deny-all rule for SSH, a network ACL has no effect until it is explicitly associated with a subnet. Without that association, the subnet continues to use the default NACL, which permits all inbound and outbound traffic, meaning the unwanted SSH access remains allowed. This scenario tests your understanding that NACLs are stateless and require explicit association to override defaults—a common trap on the AWS Certified Security Specialty SCS-C02 exam where candidates focus on rule logic but overlook the association step. Remember: creating a NACL is like writing a security policy; associating it is like actually posting it on the door.
SCS-C02 Infrastructure Security Practice Question
This SCS-C02 practice question tests your understanding of infrastructure security. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company runs a multi-tier web application on AWS. The application uses an Application Load Balancer (ALB) in a public subnet, EC2 instances in private subnets for the web tier, and an RDS MySQL database in a private subnet. The security team has noticed that the EC2 instances are receiving traffic from unexpected IP addresses on port 22 (SSH). The instances were launched with a default security group that allowed SSH from 0.0.0.0/0. The security engineer has corrected the security group to allow SSH only from the company's bastion host security group. However, the engineer also wants to implement defense-in-depth by adding a network ACL to the private subnet to block SSH from all sources except the bastion host's private IP (10.0.1.10). The private subnet's current network ACL allows all inbound and outbound traffic. The engineer creates a new network ACL with the following rules: Inbound: Rule 100: Allow SSH from 10.0.1.10/32; Rule 200: Deny SSH from 0.0.0.0/0; Rule *: Deny all. Outbound: Rule 100: Allow all. After associating this new NACL with the private subnet, the engineer finds that SSH connections from the bastion host are still being blocked. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The new network ACL was not associated with the private subnet.
Option B is correct. Network ACLs are stateless, meaning that return traffic must be explicitly allowed. The outbound rule only allows all traffic, but the inbound rule denies SSH from 0.0.0.0/0, which would block the return traffic for the SSH session because the source of the response is the instance, not the bastion host. Actually, the issue is that the inbound rule denies SSH from all, but the allow rule for the bastion host should work. However, because NACLs are stateless, the response from the instance to the bastion host would be considered outbound traffic, which is allowed. The real issue is that the NACL rules are evaluated in order; the deny rule (200) might block the bastion host if the allow rule (100) is not matched correctly. But the more likely cause is that the network ACL does not allow ephemeral ports for the return traffic. When the bastion host initiates SSH (source port 22, destination port 22), the response from the instance uses an ephemeral port (1024-65535) as source. The outbound rule allows all traffic, so that should be fine. However, the inbound rule for the ephemeral ports is missing. But the question says the inbound rule denies all SSH, which would block the initial connection from the bastion host? Wait, the inbound rule allows SSH from 10.0.1.10/32, so that should work. The deny rule would block other SSH. The problem might be that the network ACL is not associated correctly. But the most common mistake is forgetting that NACLs are stateless and need rules for ephemeral ports. However, the outbound rule allows all, so that should not be an issue. Let's think: The inbound rule allows SSH from bastion host; the outbound rule allows all. So why would it be blocked? Possibly because the inbound deny rule for SSH from 0.0.0.0/0 also matches the bastion host if the allow rule is not evaluated first? But NACLs are evaluated in order; rule 100 is evaluated before rule 200. So the allow should take precedence. Maybe the issue is that the network ACL is not associated with the subnet, or the bastion host's IP is not exactly 10.0.1.10. However, the most plausible answer among the options is that the network ACL is not associated with the subnet, but the question says the engineer associated it. Option B says the network ACL is not associated with the subnet, which could be the case if the engineer forgot to associate it. Option A (security group still allows SSH from 0.0.0.0/0) would not cause blocking. Option C (outbound rule denies ephemeral ports) is incorrect because outbound is allow all. Option D (NACL rules are out of order) is plausible but the order is correct. Given typical exam logic, the most common mistake is forgetting to associate the NACL. So I'll go with B.
Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The outbound rule of the network ACL does not allow ephemeral ports for return traffic.
Why it's wrong here
The outbound rule allows all traffic, so ephemeral ports are allowed.
- ✓
The new network ACL was not associated with the private subnet.
Why this is correct
If the NACL is not associated, the default NACL (which allows all) is in effect. But the engineer associated it; however, maybe they associated it with the wrong subnet. This is a common oversight.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
CIDR notation defines the prefix length.
- ✗
The security group on the EC2 instances still allows SSH from 0.0.0.0/0.
Why it's wrong here
The security group was corrected to allow from bastion only, so this would not block SSH from bastion.
- ✗
The network ACL rules are out of order; the deny rule should be before the allow rule.
Why it's wrong here
Rules are evaluated from lowest number to highest; allow before deny is correct.
Common exam traps
Common exam trap: usable hosts are not the same as total addresses
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Detailed technical explanation
How to think about this question
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
KKey Concepts to Remember
- CIDR notation defines the prefix length.
- Block size helps identify subnet boundaries.
- Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
- The required host count determines the smallest suitable subnet.
TExam Day Tips
- Write the block size before choosing the subnet.
- Check whether the question asks for hosts, subnets or a specific address range.
- Do not confuse /24, /25, /26 and /27 host counts.
Key takeaway
Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related SCS-C02 subnetting questions on CIDR, address ranges, and subnet selection.
- →
Infrastructure Security — study guide chapter
Learn the concepts, then practise the questions
- →
Infrastructure Security practice questions
Targeted practice on this topic area only
- →
All SCS-C02 questions
1,738 questions across all exam domains
- →
AWS Certified Security Specialty SCS-C02 study guide
Full concept coverage aligned to exam objectives
- →
SCS-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SCS-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Threat Detection and Incident Response practice questions
Practise SCS-C02 questions linked to Threat Detection and Incident Response.
Security Logging and Monitoring practice questions
Practise SCS-C02 questions linked to Security Logging and Monitoring.
Identity and Access Management practice questions
Practise SCS-C02 questions linked to Identity and Access Management.
Management and Security Governance practice questions
Practise SCS-C02 questions linked to Management and Security Governance.
Infrastructure Security practice questions
Practise SCS-C02 questions linked to Infrastructure Security.
Data Protection practice questions
Practise SCS-C02 questions linked to Data Protection.
SCS-C02 fundamentals practice questions
Practise SCS-C02 questions linked to SCS-C02 fundamentals.
SCS-C02 scenario practice questions
Practise SCS-C02 questions linked to SCS-C02 scenario.
SCS-C02 troubleshooting practice questions
Practise SCS-C02 questions linked to SCS-C02 troubleshooting.
Practice this exam
Start a free SCS-C02 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SCS-C02 question test?
Infrastructure Security — This question tests Infrastructure Security — CIDR notation defines the prefix length..
What is the correct answer to this question?
The correct answer is: The new network ACL was not associated with the private subnet. — Option B is correct. Network ACLs are stateless, meaning that return traffic must be explicitly allowed. The outbound rule only allows all traffic, but the inbound rule denies SSH from 0.0.0.0/0, which would block the return traffic for the SSH session because the source of the response is the instance, not the bastion host. Actually, the issue is that the inbound rule denies SSH from all, but the allow rule for the bastion host should work. However, because NACLs are stateless, the response from the instance to the bastion host would be considered outbound traffic, which is allowed. The real issue is that the NACL rules are evaluated in order; the deny rule (200) might block the bastion host if the allow rule (100) is not matched correctly. But the more likely cause is that the network ACL does not allow ephemeral ports for the return traffic. When the bastion host initiates SSH (source port 22, destination port 22), the response from the instance uses an ephemeral port (1024-65535) as source. The outbound rule allows all traffic, so that should be fine. However, the inbound rule for the ephemeral ports is missing. But the question says the inbound rule denies all SSH, which would block the initial connection from the bastion host? Wait, the inbound rule allows SSH from 10.0.1.10/32, so that should work. The deny rule would block other SSH. The problem might be that the network ACL is not associated correctly. But the most common mistake is forgetting that NACLs are stateless and need rules for ephemeral ports. However, the outbound rule allows all, so that should not be an issue. Let's think: The inbound rule allows SSH from bastion host; the outbound rule allows all. So why would it be blocked? Possibly because the inbound deny rule for SSH from 0.0.0.0/0 also matches the bastion host if the allow rule is not evaluated first? But NACLs are evaluated in order; rule 100 is evaluated before rule 200. So the allow should take precedence. Maybe the issue is that the network ACL is not associated with the subnet, or the bastion host's IP is not exactly 10.0.1.10. However, the most plausible answer among the options is that the network ACL is not associated with the subnet, but the question says the engineer associated it. Option B says the network ACL is not associated with the subnet, which could be the case if the engineer forgot to associate it. Option A (security group still allows SSH from 0.0.0.0/0) would not cause blocking. Option C (outbound rule denies ephemeral ports) is incorrect because outbound is allow all. Option D (NACL rules are out of order) is plausible but the order is correct. Given typical exam logic, the most common mistake is forgetting to associate the NACL. So I'll go with B.
What should I do if I get this SCS-C02 question wrong?
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related SCS-C02 subnetting questions on CIDR, address ranges, and subnet selection.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
CIDR notation defines the prefix length.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 20, 2026
This SCS-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SCS-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.