Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 564 discussion

Accerator is answer https://aws.amazon.com/global-accelerator/?blogs-global-accelerator.sort-by=item.additionalFields.createdDate&blogs-global-accelerator.sort-order=desc&aws-global-accelerator-wn.sort-by=item.additionalFields.postDateTime&aws-global-accelerator-wn.sort-order=desc

C - CloudFront, static resource, cache in edge

Correct Answer is C:: CloudFront uses a local cache to provide the response, AWS Global accelerator proxies requests and connects to the application all the time for the response.

ccccccccccccccccccccccccccff

C- Cloudfront to reduce latency. Key words.

For anyone doubting that it might be Global Accelerator, keep in mind that it only supports endpoints for Network and Application LBs, Elastic IPs, and EC2.

CCCCCCCCCCCCCCCCCCC

Answer is C

Cache is happening on App Side

Answer is C, key keyword is caching

C GA reduces latency but does not implement a cache.

Agreed with C. Global Accelerator need to have IP in placed.

First, try to remove the obvious: 1. SQS is out of question. 2. You might be tempted to check DataSync, however you aren't doing migrations over here do you? Now here's the meat, most of you would select caching as CF, however check the requirement for material source to be: a. Rapidly served b. Should be available globally. c. Regardless of the origin of the request. (Meaning no playing around with HTTP headers) d. The content is most likely for VOD services, although Cloudfront do support for VOD, rapidly distributing is far fetched idea, as it requires network based service to with low latency and high throughput. Hence B

Global Accelerator is only for reduce network latency , Data Sync for data transfer from Onprem to AWS...why would you use SQS in this case

Answer C. Global Accelerator is a network solution. Not caching.

Global Acc has nothing to do with cache. But it works on routing request via least latency. For caching it would always be CF.

Cloudfront = OAI for security + caching for faster content delivery: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html#private-content-granting-permissions-to-oai