Traffic Mirroring Target: NLB vs Gateway Load Balancer
Short answer
A Use an NLB as the Traffic Mirroring target in front of an Auto Scaling group of EC2 analysis instances, because an NLB is a valid mirror target and scales mirrored traffic.
Question
Which solution will meet these requirements?
Key Takeaways
It tests whether you know the exact supported Traffic Mirroring target resource types and can avoid conflating a Gateway Load Balancer with a Gateway Load Balancer endpoint.
This ANS-C01 scenario asks for a highly available, scalable Traffic Mirroring target; the correct design is an NLB in front of an Auto Scaling group (A), not a Gateway Load Balancer target.
Common mistake: Choosing C because a Gateway Load Balancer is designed for security appliances, but Traffic Mirroring targets a GWLB endpoint, not the Gateway Load Balancer resource itself as option C states.
Expert Analysis
Why option C is so attractive
Option C looks tailor-made for this scenario. A Gateway Load Balancer is purpose-built to deploy, scale, and manage third-party virtual appliances such as firewalls, intrusion detection systems, and deep packet inspection tools, and the security team here runs analysis tooling on EC2. That makes C feel ideal: it offers high availability, an Auto Scaling fleet, and transparent distribution of copied packets. The option even says “Use Traffic Mirroring as necessary,” matching the requirement to relieve the overloaded single target without imposing business-hours limits.
Where option C stops being correct
The decisive phrase is “as the traffic mirror target.” AWS Traffic Mirroring does not accept the Gateway Load Balancer resource itself as a target. Supported targets are network interfaces, Network Load Balancers, and Gateway Load Balancer endpoints. An endpoint is a different resource that fronts a GWLB; option C says to deploy the GLB as the target and never mentions a GWLB endpoint. Community reasoning splits exactly here: one line of argument favors C because AWS now supports sending mirrored traffic to GWLB-backed appliances, while another stresses the wording and selects A because the valid target is a “GWLB endpoint.” That resource-level distinction is the exam-level point.
Why option A satisfies the requirement
Option A uses an NLB, explicitly a supported Traffic Mirroring target, and places a fleet of EC2 analysis instances in an Auto Scaling group behind it. The NLB distributes the mirrored Layer 4 traffic, health checks support high availability, and Auto Scaling handles demand. B and D fail earlier: an ALB is not a valid mirror target, and restricting mirroring to non-business hours or active events does not create a scalable, always-available troubleshooting design.
Therefore, A is the correct answer.
Official Reference
- https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-targets.html
- https://docs.aws.amazon.com/elasticloadbalancing/latest/gateway/introduction.html
- https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring.html
These links open the official vendor documentation in a new tab.
Exam Strategy
When a question uses exact AWS service names, treat them literally: Traffic Mirroring targets are network interfaces, NLBs, and Gateway Load Balancer endpoints, not a Gateway Load Balancer resource. Eliminate options that add irrelevant time-of-day limits or use ALB, which is not a valid mirror target. Then verify the remaining design distributes packets to an Auto Scaling fleet for high availability and scale. This technique transfers to any scenario where a familiar service sounds right but the API-level resource type is different.
Frequently Asked Questions
Can a Gateway Load Balancer itself be a Traffic Mirroring target?
Why is an Application Load Balancer not a valid Traffic Mirroring target?
How does an NLB with Auto Scaling handle mirrored traffic?
Community Votes
63% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 52 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 30 of 52
-
Cheam 👍 21 Answered AAnother tricky question and consider the wording in the answers choices - "as the traffic mirror target". I have selected A because the NLB is a valid mirror target, but the GWLB is not (Answer C). Yes, comments supporting Answer C say that GWLB must also mean/include GLWB-E. Then you have two valid answers to the question where you can only select one. Therefore, it is A for me. Ref: https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-targets.html All the best.
-
dremm 👍 17 Answered CC) Makes more sense for the updated exam, GWLB is relatively new. Read the release post for GWLB - https://aws.amazon.com/about-aws/whats-new/2022/05/amazon-vps-traffic-mirroring-supports-sending-mirrored-traffic-gateway-load-balancer-backed-monitoring-appliances/ "This helps simplify the monitoring of network traffic across AWS accounts and VPCs in a highly scalable and operationally efficient manner by removing routing complexity and operational overhead."
-
btech24 👍 4Answer is A, Gateway Load Balancer is not a valid traffic mirror target. There are 3 valid traffic mirror endpoints 1. Network Interface 2. Network Load Balancer 3. Gateway Load Balancer endpoints ref https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-targets.html
-
linuxek21 👍 4Just to add some reference: Use any of the following resources for a traffic mirror target: A network interface A Network Load Balancer Gateway Load Balancer endpoint Source: https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-targets.html
-
DPDK 👍 4 Answered AWell. Although NLB and GWLB are good to do this. Based on description of options, A is better, because Target should be GWLB ENDPOINT instead of GWLB itself
Show 25 more comments
-
slackbot 👍 4every GWLB that you deploy comes in the form of a VPC endpoint, unlike CLB, NLB and ALB. hence - whenever we speak of GWLB, we mean - GWLB endpoint
-
slackbot 👍 3 Answered Cit is a tricky one, but I would go with C: https://aws.amazon.com/blogs/networking-and-content-delivery/introduction-to-traffic-mirroring-to-gwlb-endpoints-as-target/
-
linuxek21 👍 3Correct answer is: A C sounds like a good option and preferable but you cannot have a Gateway Load Balancer as a target it must be a Gateway Load Balancer "Endpoint"
-
Untamables 👍 3 Answered CC This scenario is the typical use case for a Gateway Load Balancer. https://docs.aws.amazon.com/elasticloadbalancing/latest/gateway/introduction.html
-
Manh 👍 3 Answered Ain traffic mirror, NLB is the target
-
ohcan 👍 3 Answered CC. GLB is specific for this use case
-
Alabi 👍 2 Answered AA. Deploy a Network Load Balancer (NLB) as the traffic mirror target. Behind the NLB, deploy a fleet of EC2 instances in an Auto Scaling group. Use Traffic Mirroring as necessary. Network Load Balancer (NLB) is designed for handling TCP/UDP traffic and provides high availability, scalability, and low-latency performance. It is suitable for distributing the mirrored traffic to a fleet of EC2 instances. Deploying a fleet of EC2 instances in an Auto Scaling group ensures that you can scale the capacity of your analysis tools dynamically to meet the demand of the mirrored traffic. This addresses the issue of the EC2 instance being overwhelmed. Using Traffic Mirroring as necessary allows you to control when to capture mirrored traffic, reducing the load on the analysis tools during non-critical times.
-
PhilMultiCloud 👍 2 Answered CSince GLB is designed to easily deploy, scale, and manage third-party virtual appliances, it fits the requirement of handling the highly mirrored traffic without overwhelming the EC2 instance. GLB can distribute the mirrored traffic across multiple EC2 instances in an Auto Scaling group, providing high availability and scaling capabilities based on demand. Option A, Option B, and Option D do not mention using Gateway Load Balancer (GLB) and therefore, do not offer the same capabilities and benefits as Option C in handling the traffic mirroring requirements.
-
that1guy 👍 2 Answered AFrom: https://docs.aws.amazon.com/elasticloadbalancing/latest/gateway/introduction.html > "Gateway Load Balancers enable you to deploy, scale, and manage virtual appliances, such as firewalls, intrusion detection and prevention systems, and deep packet inspection systems. It combines a transparent network gateway (that is, a single entry and exit point for all traffic) and distributes traffic while scaling your virtual appliances with the demand. "
-
Arad 👍 2 Answered AB and D are not correct and ALB cannot be used as target of mirroring. C is not correct because GWLB is to be used in front of 3rd party appliances like Palo Alto Firewalls, not EC2 instances. A is the only option which makes sense and is correct.
-
notwhoyouthink 👍 2Endpoints are different constructs, you can have one GWLB but many GWLBe's and therefore would need to call the Endpoint as the target. So if we are splitting hairs here, the language in C is not 100% accurate. I would go with A.
-
jyrajan69 👍 2 Answered CIt depends on when you answered this question because based on the latest the answer is C https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-how-it-works.html
-
task_7 👍 2 Answered ANLB good choice if you have multiple EC2 instances that can analyze mirrored traffic. GLB Network analysis tools are virtual appliances
-
Anonymous learner 👍 2 Answered Ahttps://aws.amazon.com/blogs/networking-and-content-delivery/mirror-production-traffic-to-test-environment-with-vpc-traffic-mirroring/
-
AmSpOkE 👍 2 Answered AAnswer is A as GWLB (which could be a good answer) is not a valid target for a mirroring.
-
RavikantKumarRavi 👍 2 Answered ANLB incase of EC2 and GLB incase of security appliance as destination or target
-
awsguru1998 👍 2C i would go for GLB as this is networking exam :-)
-
Fati_2022 👍 1 Answered ABased on the options provided in the question, the suitable load balancer would be the Network Load Balancer (NLB). Deploying a Network Load Balancer (NLB) as the traffic mirror target and using an Auto Scaling group with EC2 instances behind the NLB is the recommended solution. NLB is designed for TCP/UDP traffic and operates at the transport layer (Layer 4), making it a suitable choice when dealing with non-HTTP protocols or when high performance and scalability are required. NLB offers several benefits, including: High performance: NLB is capable of handling extremely high volumes of traffic with low latency, making it suitable for demanding network environments.
-
Certified101 👍 1 Answered CC based on dremm's comments. and for the C01 exam. Also A Gateway Load Balancer (GLB) is designed to work with third-party virtual appliances, such as firewalls, intrusion detection and prevention systems, and deep packet inspection systems. It distributes traffic to these appliances and scales them to meet the demand of the mirrored traffic 1. On the other hand, a Network Load Balancer (NLB) is designed to handle high levels of traffic with ultra-low latencies and can route traffic based on IP address and TCP port 2. In this case, a GLB would be more suitable for handling the mirrored traffic.
-
zaazanuna 👍 1A - correct. Option A is the most appropriate solution because it uses a Network Load Balancer (NLB) as the traffic mirror target, which is designed to handle high volumes of traffic and provides high availability. By deploying a fleet of EC2 instances in an Auto Scaling group behind the NLB, the solution can scale to meet the demand of the mirrored traffic. The use of Traffic Mirroring as necessary enables the network engineer to control when the mirrored traffic is sent to the EC2 instances and prevent overloading the EC2 instances with too much traffic.
-
Raphaello 👍 1 Answered AI'd go with A. Valid traffic mirror targets include "GWLB ENDPOINTS"..for this, I'd go with A. Traffic mirror target concepts A traffic mirror target is the destination for mirrored traffic. You can use the following resources as traffic mirror targets: Network interfaces of type interface Network Load Balancers Gateway Load Balancer endpoints <<<< https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirroring-targets.html
-
Joselito79 👍 1 Answered CC. Deploy a Gateway Load Balancer (GLB) as the traffic mirror target. Behind the GLB, deploy a fleet of EC2 instances in an Auto Scaling group. Use Traffic Mirroring as needed. What the GLB does here: Receives encapsulated Layer 3/Layer 4 traffic (GENEVE) from Traffic Mirroring Distributes it transparently to multiple appliances Supports Auto Scaling Does not terminate sessions or protocols Does not alter the traffic
-
ogrefighter 👍 1 Answered AGLB operates at Layer 3. NLB operates at Layer 4 -- so an NLB cannot be directly the target of GLB. Simplest answer is A https://aws.amazon.com/compare/the-difference-between-the-difference-between-application-network-and-gateway-load-balancing/#:~:text=An%20NLB%20operates%20on%20layer,on%20ports%20and%20IP%20addresses.
-
payelix795 👍 1I suspect C is the answer From AWS's site on GWLB "Scale virtual appliances while managing costs Hitting the limit of what your virtual appliances can handle can bottleneck your entire network. To prevent this, Gateway Load Balancer automatically scales your virtual appliances up or down, based on demand."
-
AzureDP900 👍 1 Answered AA is right To create a highly available solution that can scale to handle mirrored traffic while minimizing the impact on the EC2 instance hosting tools for analyzing traffic, we should use a load balancer to distribute the mirrored traffic across multiple instances.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All ANS-C01 Questions
Access 137 questions with complete answers and detailed explanations.
View Full ANS-C01 Practice Test →