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

It is not A or B because ALB works with layer 7 of OSI model ( HTTP, HTTPS ) , NLB works with layer 4 ( TCP, UDP, TLS ) . it remains C or D . it is possible to have the eLB as the origin Cloudfront but CloudFront is designed to handle the HTTP protocol, while Global Accelerator is best used for HTTP and non-HTTP protocols such as TCP and UDP. So, my answer is D too.

In my opinion every answer so far is wrong. The question states it needs HTTP and NON-HTTP TCP tarffic. Therefore it cannot be an ALB and must be a NLB. AWS Global Accelerator: "When the internet is congested, AWS Global Accelerator optimizes the path to your application to keep packet loss, jitter, and latency consistently low." D is correct in my world.

The problem is the question is: 1) non-http traffic --> Global accelerator 2) in a single Region --> Cloud Front. All answers are not correct, but exam wants us to evaluate traffic protocols over locations

D it is

D. Create an Auto Scaling group with a Network Load Balancer (NLB). Add an accelerator with AWS Global Accelerator with the NLB as an endpoint. - TCP (Layer 4) => NLB - CloudFront + ALB : ok, but CloudFront + NLB: Never => AWS Global Accelerator with the NLB as an endpoint : good mix => D

NLB Deals with TCP Cloudfront cannot deal with non-HTTP traffic

HTTP/TCP and low latency by leveraging the AWS network. Option D has endpoint as a clue!

The Application Load Balancer (ALB) is a good choice for HTTP and HTTPS traffic, but it doesn't support non-HTTP TCP traffic. So, we can't choose options A and B. Network Load Balancer (NLB) supports load balancing of both TCP traffic and HTTP traffic, so we can use it in this case. The Amazon CloudFront distribution is primarily for caching static and dynamic content closer to viewers to reduce latency, and it doesn't directly support non-HTTP protocols or load balancing for EC2 instances. So, we can't choose option C.

D because you need support for http and non-http protocols

Without question, answer can only be D. The table comparison in the following link makes that perfectly clear: https://jayendrapatil.com/aws-cloudfront-vs-global-accelerator/

As per AAWS Global Accelerator FAQs, Global Accelerator is a good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP, as well as for HTTP use cases that specifically require static IP addresses or deterministic, fast regional failover. Both services integrate with AWS Shield for DDoS protection.

DDD is the correct option from my point of view. The key phrase here is "The application requires support for non-HTTP TCP traffic and HTTP traffic" and as we know, HTTP is layer 7 of the OSI model (Application layer). TCP and UDP are layer 4 and therefore it must be Network Load Balancer (NLB) Global Accelerator is a good fit for non-HTTP use cases, which is the reason that I'm inclined towards D.

D for sure

D is the answer.

Answer D. AWS Global Accelerator and Amazon CloudFront are separate services that use the AWS global network and its edge locations around the world. CloudFront improves performance for both cacheable content (such as images and videos) and dynamic content (such as API acceleration and dynamic site delivery). Global Accelerator improves performance for a wide range of applications over TCP or UDP by proxying packets at the edge to applications running in one or more AWS Regions. Global Accelerator is a good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP, as well as for HTTP use cases that specifically require static IP addresses or deterministic, fast regional failover. Both services integrate with AWS Shield for DDoS protection.

Yes, found 2 references. I agree with D. https://medium.com/awesome-cloud/aws-difference-between-application-load-balancer-and-network-load-balancer-cb8b6cd296a4 https://aws.amazon.com/global-accelerator/faqs/?nc1=h_ls

Ans:D CloudFront is designed to handle HTTP protocol meanwhile Global Accelerator is best used for both HTTP and non-HTTP protocols such as TCP and UDP. https://tutorialsdojo.com/aws-global-accelerator-vs-amazon-cloudfront/