An enterprise security engineer needs to analyze VPC traffic flows in AWS to identify anomalous outbound communication from internal EC2 instances to unknown external IP addresses. Which AWS feature should be enabled and analyzed?
VPC Flow Logs capture IP traffic metadata for elastic network interfaces, including source, destination, ports, and accept or reject decisions. Analysing these records reveals anomalous outbound connections from EC2 instances to unknown external addresses, satisfying the stem's traffic-flow analysis requirement.
Why this answer
AWS VPC Flow Logs capture IP traffic metadata (source/destination IP, port, protocol, bytes, action) for network interfaces in a VPC, making them the correct feature to analyze outbound communication from EC2 instances to unknown external IPs. They can be published to CloudWatch Logs or S3 and queried with Athena for anomaly detection.
Exam trap
CND often tests the distinction between network-level telemetry (VPC Flow Logs) and API-level telemetry (CloudTrail), and candidates mistakenly pick CloudTrail thinking it captures all AWS activity including network traffic.
How to eliminate wrong answers
Option B is wrong because GuardDuty Kubernetes audit logs focus on EKS control plane activity (API calls, RBAC events), not VPC-level network flows. Option C is wrong because Trusted Advisor network optimization checks are cost/performance recommendations, not security traffic analysis. Option D is wrong because CloudTrail Management Events record AWS API calls (e.g., RunInstances, CreateUser), not network traffic flows between EC2 instances and external IPs.