A company is configuring network security for a web application hosted on Amazon EC2 instances in a VPC. The security team has two requirements:
1. Apply rules at the subnet boundary where both inbound and outbound traffic must be explicitly allowed, as rules are evaluated independently for return traffic.
2. Apply rules at the instance boundary where allowing inbound traffic automatically permits the corresponding outbound return traffic.
Which combination of AWS security features should the company use to meet these requirements?
- Network Access Control Lists (NACLs) at the subnet level because they are stateless, and Security Groups at the instance level because they are statefulCevap
- BSecurity Groups at the subnet level because they are stateless, and Network Access Control Lists (NACLs) at the instance level because they are stateful
- CNetwork Access Control Lists (NACLs) at the subnet level, and Amazon Inspector at the instance level to automatically detect and block malicious network traffic
- DAWS Shield at the subnet level, and relying on AWS to automatically manage all operating system-level firewall rules on the EC2 instances
Cevap
Network Access Control Lists (NACLs) at the subnet level because they are stateless, and Security Groups at the instance level because they are stateful
The correct answer combines Network Access Control Lists (NACLs) for the subnet-level requirement and Security Groups for the instance-level requirement. NACLs are stateless firewalls that control inbound and outbound traffic at the subnet boundary, meaning outbound return traffic must be explicitly permitted. Security Groups are stateful firewalls that apply to individual EC2 instances, meaning once inbound traffic is allowed, the outbound return traffic is automatically allowed.
Adım Adım Çözüm
Anahtar Kavram
The difference between stateful Security Groups (operating at the instance level) and stateless Network Access Control Lists (operating at the subnet level).
Tahmini Süre:1m 30s