Exam AWS Certified Solutions Architect - Associate SAA-C02 All Questions

View all questions & answers for the AWS Certified Solutions Architect - Associate SAA-C02 exam

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

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C02

Question #: 27
Topic #: 1

[All AWS Certified Solutions Architect - Associate SAA-C02 Questions]

A company's website runs on Amazon EC2 instances behind an Application Load Balancer (ALB). The website has a mix of dynamic and static content. Users around the globe are reporting that the website is slow.
Which set of actions will improve website performance for users worldwide?

A. Create an Amazon CloudFront distribution and configure the ALB as an origin. Then update the Amazon Route 53 record to point to the CloudFront distribution.
B. Create a latency-based Amazon Route 53 record for the ALB. Then launch new EC2 instances with larger instance sizes and register the instances with the ALB.
C. Launch new EC2 instances hosting the same web application in different Regions closer to the users. Then register instances with the same ALB using cross- Region VPC peering.
D. Host the website in an Amazon S3 bucket in the Regions closest to the users and delete the ALB and EC2 instances. Then update an Amazon Route 53 record to point to the S3 buckets.

Show Suggested Answer

Suggested Answer: A 🗳️
What Is Amazon CloudFront?
Amazon CloudFront is a web service that speeds up distribution of your static and dynamic web content, such as .html, .css, .js, and image files, to your users.
CloudFront delivers your content through a worldwide network of data centers called edge locations. When a user requests content that you're serving with
CloudFront, the user is routed to the edge location that provides the lowest latency (time delay), so that content is delivered with the best possible performance.
Routing traffic to an Amazon CloudFront web distribution by using your domain name.
If you want to speed up delivery of your web content, you can use Amazon CloudFront, the AWS content delivery network (CDN). CloudFront can deliver your entire website ג€" including dynamic, static, streaming, and interactive content ג€" by using a global network of edge locations. Requests for your content are automatically routed to the edge location that gives your users the lowest latency.
To use CloudFront to distribute your content, you create a web distribution and specify settings such as the Amazon S3 bucket or HTTP server that you want
CloudFront to get your content from, whether you want only selected users to have access to your content, and whether you want to require users to use HTTPS.
When you create a web distribution, CloudFront assigns a domain name to the distribution, such asd111111abcdef8.cloudfront.net. You can use this domain name in the URLs for your content, for example:
[1]
Alternatively, you might prefer to use your own domain name in URLs, for example:
[1]
If you want to use your own domain name, use Amazon Route 53 to create an alias record that points to your CloudFront distribution. An alias record is a Route
53 extension to DNS. It's similar to a CNAME record, but you can create an alias record both for the root domain, such as example.com, and for subdomains, such aswww.example.com. (You can create CNAME records only for subdomains.) When Route 53 receives a DNS query that matches the name and type of an alias record, Route 53 responds with the domain name that is associated with your distribution.
Reference:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-cloudfront-distribution.html https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Introduction.html

by DK2 at June 4, 2020, 2:28 a.m.

Disclaimers:

- ExamTopics website is not related to, affiliated with, endorsed or authorized by Amazon.
- Trademarks, certification & product names are used for reference only and belong to Amazon.

Comments

Submit Cancel

DK2

Highly Voted 3 years, 7 months ago

A here.

upvoted 55 times

aguy9

3 years, 6 months ago

Yes definitely A

upvoted 3 times

...

HudsonNg

Highly Voted 3 years, 6 months ago

For those who think CloudFront cant be used for DYNAMIC content, read this doc: https://aws.amazon.com/blogs/networking-and-content-delivery/dynamic-whole-site-delivery-with-amazon-cloudfront/ In short, you can config CF to look into the path of the URL, i.e. /admin and treat URLs with your specified pattern as NO CACHABLE so that CloudFront will forward the requests to the origin, which in this case usually is a ALB.

upvoted 11 times

rac_sp

2 years, 7 months ago

That is correct. I was watching Samsung IP TV and analyzing the traffice I just found out the Streaming was coming fro the Cloud Front. Very interesting.

upvoted 1 times

...

48cd959

Most Recent 1 year, 1 month ago

Selected Answer: A

Answer A Clue - Increase performance Static content - Cloudfront is the answer.

upvoted 1 times

...

apchandana

2 years, 1 month ago

Why Not C ?? apparently, C is correct. but VPC peering across regions is possible. how many regions do we need to do that with how many number of instances. how to update the contents across regions. therefore, it is nota practical scenario . correct is A

upvoted 1 times

...

rubds

2 years, 11 months ago

Why not B here?

upvoted 1 times

...

lordstans

3 years ago

Selected Answer: A

Since its dynamic content, we cannot host that on S3. A is the right answer

upvoted 1 times

...

jack4090

3 years, 4 months ago

A = Correct answer

upvoted 1 times

...

joshuaquek

3 years, 5 months ago

I think it is A. Curious about the 'Dynamic' content part, which means that it could be that the application is a monolith with the frontend on the `/` route and the apis hosted on the `/api` route. If this is the case, then the API responses would be dynamic. However, Cloudfront caching should be disabled (https://stackoverflow.com/questions/52704816/how-to-properly-disable-cloudfront-caching-for-api-requests) so that API requests will not return old data for the same API call. This brings up a question, will this defeat the purpose of Cloudfront when it has to continuously fetch data from the original region? (despite it being an Edge location resource)

upvoted 4 times

...