Answer is A Explanation - AWS Global Accelerator vs CloudFront • They both use the AWS global network and its edge locations around the world • Both services integrate with AWS Shield for DDoS protection. • CloudFront • Improves performance for both cacheable content (such as images and videos) • Dynamic content (such as API acceleration and dynamic site delivery) • Content is served at the edge • Global Accelerator • Improves performance for a wide range of applications over TCP or UDP • Proxying packets at the edge to applications running in one or more AWS Regions. • Good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP • Good for HTTP use cases that require static IP addresses • Good for HTTP use cases that required deterministic, fast regional failover

Q: How is AWS Global Accelerator different from Amazon CloudFront? A: 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.

Correct Answer is B

It would have made sense to use S3 bucket as the origin for cloud front and ALB as the end point for global accelerator. However the option C messes it up when it mentions also the cloud front distribution as the end point for global accelerator standard (which is not supported). As this is not possible the only option left is A to use Cloud front for both S3 & ALB.

This question is absolutely insane

My chatGPT4 answer me it is A. It said C has a structural problem so it cannot really be made in practice. I leave this comment for who be confused by chatGPT3.5.

CloudFront can be used for both static and dynamic content distribution.

Answer is A

chatGPT give the answer is C

GlobaAccelerator helps routing users to closest region. The question doesn't say anything about latency due to region so BCD don't really solve much problems.

Answer: A

Ans is C:, This solution involves using Amazon CloudFront for caching the static content, which will improve performance and reduce latency for the static data. Additionally, by creating an AWS Global Accelerator standard accelerator with the ALB and the CloudFront distribution as endpoints, the company can further improve the availability and performance of the web application. Finally, creating a custom domain name that points to the accelerator DNS name will allow the company to use the custom domain name as an endpoint for the web application, providing a seamless experience for the users. The search results provide information about the benefits of using a standard accelerator in AWS Global Accelerator to improve the availability and performance of applications, as well as the steps for creating a standard accelerator and working with standard accelerators in AWS Global Accelerator

Answer is A

A is correct; Option B and option C are incorrect because they include invalid endpoint configurations for Global Accelerator. Global Accelerator Standard does not support S3 endpoints or CloudFront distribution endpoints.

I just tested, there is no option in Global Accelerator to make CloudFront distribution as endpoints. so anwer is A

I'm wavering between A and C. With dynamic content, CloudFront is cacheable and that's not good. But with answer C, AWS Global doesn't support Cloudfront endpoint "Endpoints for standard accelerators in AWS Global Accelerator can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses. " So I choose A

C seems reasonable due to the fact that CloudFront is tedious when it comes to Dynamic content, you need to expire the content everytime it changes, which adds extra work and might lead to inconsistent results.