Exam AWS Certified SysOps Administrator - Associate topic 1 question 26 discussion

It's D. "Network Load Balancer is optimized to handle sudden and volatile traffic patterns while using a single static IP address per Availability Zone." https://aws.amazon.com/elasticloadbalancing/network-load-balancer/

AWS Global Accelerator provides a static IP address that acts as a fixed entry point to your application, which can be beneficial for applications with sudden and volatile traffic patterns. It intelligently routes traffic to the optimal endpoint based on health, geography, and routing policies. Application Load Balancer (B) is also a good option for distributing traffic but does not provide a single static IP address for each Availability Zone. Network Load Balancer (D) can handle millions of requests per second and provides static IP addresses, but it is more suited for TCP/UDP traffic rather than HTTP/HTTPS. Amazon SQS (A) is a message queuing service and does not directly distribute traffic to EC2 instances.

Key words: High performance, static IP

'Network Load Balancer' these words like introduction content at https://aws.amazon.com/elasticloadbalancing/network-load-balancer/

Option C (AWS Global Accelerator) can provide a single static anycast IP address for an application endpoint across multiple AWS regions. However, it does not provide a single static IP address per Availability Zone, which is specifically required in this scenario.

D. Network Load Balancer

If the question was addressing EC2 instances across multiple regions, I think that Global Accelerator (in front of multiple network load balancers) would be the solution. However, it only specifies multiple AZ's, which IMHO implies the application is contained within a region. If it were global in scope, they'd need to specify that. I think the answer they want here is D because they are focusing primarily on performance requirement.

with this question you kinda just have to know what the services are used for. After reading this Its between Application load balancer and Network load balancer. The reason its Network load balancer is because it says "Millions" and ALB cannot handle this much

DDDD is the right way to go. https://aws.amazon.com/elasticloadbalancing/network-load-balancer/

dddddddddd

must be able to scale to millions of requests each second - the NLB can scale that much

D, as it mentions static IP address.

D. Network Load balancer.

D..Network load Balancer

D. Network Load Balancer

Associate the static IP addresses provided by AWS Global Accelerator to regional AWS resources or endpoints, such as Network Load Balancers, Application Load Balancers, EC2 Instances, and Elastic IP addresses. The IP addresses are anycast from AWS edge locations so they provide onboarding to the AWS global network close to your users. Easily move endpoints between Availability Zones or AWS Regions without needing to update your DNS configuration or change client-facing applications. Dial traffic up or down for a specific AWS Region by configuring a traffic dial percentage for your endpoint groups. This is especially useful for testing performance and releasing updates. Control the proportion of traffic directed to each endpoint within an endpoint group by assigning weights across the endpoints. https://aws.amazon.com/global-accelerator/faqs/

Answer is D. It cannot be C because you only get 2 anycast IPs for the global accelerator.