A network engineer configured Traffic Mirroring to help detect and troubleshoot network anomalies, but the mirrored traffic is saturating the Amazon EC2 instance acting as the mirror target. That EC2 instance runs security analysis tools. The engineer needs a highly available, scalable design to handle the mirrored traffic. Which solution satisfies these requirements?

The correct solution is to deploy a Network Load Balancer (NLB) as the traffic mirror target, with a fleet of EC2 instances in an Auto Scaling group behind it. NLBs operate at Layer 4 (TCP/UDP) and are designed for high throughput and low latency, making them ideal for forwarding raw mirrored traffic without modification. The Auto Scaling group ensures scalability and high availability by automatically adjusting the number of EC2 instances based on demand. This allows the security analysis tools to process the mirrored traffic effectively without saturation. Incorrect options: An Application Load Balancer (ALB) operates at Layer 7 (HTTP/HTTPS) and would not be suitable for raw network traffic mirroring, which is typically at Layer 3 or 4. A Gateway Load Balancer (GLB) is designed for inserting third-party virtual appliances transparently into the network path for inspection, not directly as a target for mirrored traffic. While it offers high availability and scalability, it's not the primary or most direct solution for this use case. Limiting Traffic Mirroring to non-business hours or active events does not address the need for a scalable and highly available design to handle the traffic when it is mirrored.