ExamTopics Logo
Mail Us[email protected]
Menu
Amazon Discussions
exam questions

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

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

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

Exam question from Amazon's AWS Certified Solutions Architect - Associate SAA-C02
Question #: 435
Topic #: 1
[All AWS Certified Solutions Architect - Associate SAA-C02 Questions]

A company is using Amazon Route 53 latency-based routing to route requests to its UDP-based application for users around the world. The application is hosted on redundant servers in the company's on-premises data centers in the United States, Asia, and Europe. The company's compliance requirements state that the application must be hosted on premises. The company wants to improve the performance and availability of the application.
What should a solutions architect do to meet these requirements?

  • A. Configure three Network Load Balancers (NLBs) in the three AWS Regions to address the on-premises endpoints. Create an accelerator by using AWS Global Accelerator, and register the NLBs as its endpoints. Provide access to the application by using a CNAME that points to the accelerator DNS.
  • B. Configure three Application Load Balancers (ALBs) in the three AWS Regions to address the on-premises endpoints. Create an accelerator by using AWS Global Accelerator, and register the ALBs as its endpoints. Provide access to the application by using a CNAME that points to the accelerator DNS.
  • C. Configure three Network Load Balancers (NLBs) in the three AWS Regions to address the on-premises endpoints. In Route 53, create a latency-based record that points to the three NLBs, and use it as an origin for an Amazon CloudFront distribution. Provide access to the application by using a CNAME that points to the CloudFront DNS.
  • D. Configure three Application Load Balancers (ALBs) in the three AWS Regions to address the on-premises endpoints. In Route 53, create a latency-based record that points to the three ALBs, and use it as an origin for an Amazon CloudFront distribution. Provide access to the application by using a CNAME that points to the CloudFront DNS.
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by AnuhyaTech at May 2, 2021, 10:13 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

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
cadim
Highly Voted 3 years, 2 months ago
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.
upvoted 65 times
...
charlpl
Highly Voted 3 years, 1 month ago
Answer A: Global Accelerator can be used for all TCP and UDP traffic. CloudFront can cache HTTP objects at edge locations and it uses a DNS name with changing IP addresses rather than static ones
upvoted 19 times
...
marufxplorer
Most Recent 1 year, 6 months ago
A By using AWS Global Accelerator, the company can improve the performance and availability of the application by taking advantage of Amazon's global network infrastructure. The three Network Load Balancers (NLBs) in the US, Asia, and Europe regions will handle routing traffic to the on-premises data centers. The AWS Global Accelerator will act as a single entry point for the application, providing efficient routing and load balancing.
upvoted 1 times
...
BECAUSE
1 year, 6 months ago
Selected Answer: A
A is the answer
upvoted 1 times
...
bora4motion
2 years, 5 months ago
Selected Answer: A
You cant put UDP next to CloudFront. A!
upvoted 1 times
...
naveenagurjara
2 years, 5 months ago
Selected Answer: A
Cloud front is purely TCP/HTTP.
upvoted 1 times
...
Ivanyan
2 years, 9 months ago
Selected Answer: A
The correct answer is A: Global Accelerator
upvoted 2 times
...
luckybme
2 years, 11 months ago
Selected Answer: A
Global accelerator can route TCP/UDP based on latency and health checks.
upvoted 1 times
...
gargaditya
3 years, 1 month ago
A for Answer! ----------------- My short note effectively explaining visualising Global Accelerator by 3 diagrams: https://1drv.ms/w/s!Al2WmWQmp2xZtnFRIierzW-1E_9W?e=njXZJX ---------------------- Global accelerator: 1.Reduces latency as we use edge location and quickly get into AWS nw 2.Gives latency based routing(has R53 latency routing inbuilt) 3.Acts as a cross region LB (note LB does balancing across AZ in single region)
upvoted 5 times
gargaditya
3 years, 1 month ago
-------------- https://aws.amazon.com/global-accelerator/faqs/ Q: How does AWS Global Accelerator work together with Elastic Load Balancing (ELB)? A: Both of these services solve the challenge of routing user requests to healthy application endpoints. AWS Global Accelerator relies on ELB to provide the traditional load balancing features such as support for internal and non-AWS endpoints, pre-warming, and Layer 7 routing. However, while ELB provides load balancing within one Region, AWS Global Accelerator provides traffic management across multiple Regions. A regional ELB load balancer is an ideal target for AWS Global Accelerator. By using a regional ELB load balancer, you can precisely distribute incoming application traffic across backends, such as Amazon EC2 instances or Amazon ECS tasks, within an AWS Region. AWS Global Accelerator complements ELB by extending these capabilities beyond a single AWS Region, allowing you to provision a global interface for your applications in any number of Regions
upvoted 3 times
gargaditya
3 years, 1 month ago
further,UDP implies use L4 LB ie NLB not ALB
upvoted 5 times
...
...
...
Seb
3 years, 1 month ago
Answer A, https://tutorialsdojo.com/aws-global-accelerator-vs-amazon-cloudfront/
upvoted 3 times
...
mrkid3085
3 years, 1 month ago
UDP --> Global accelerator + NLB A.
upvoted 3 times
...
Afsal_K_R
3 years, 1 month ago
answer should be A. Global accelerator is best for udp use cases. 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.
upvoted 3 times
...
damot
3 years, 1 month ago
all the comments luck of explanation I'm sorry any ways it should be A
upvoted 2 times
bigchange
3 years, 1 month ago
Your explanation superb!
upvoted 5 times
...
...
thirstylion
3 years, 1 month ago
Answer : A https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/DownloadDistS3AndCustomOrigins.html#concept_origin_groups
upvoted 4 times
...
KSrikantan
3 years, 2 months ago
Can't be 'A'. Pay attention to the line mentioned in A - 'Provide access to the application by using a CNAME that points to the accelerator DNS'. Global Accelerator does not have a DNS for us to create a CNAME. It comes with two static Anycast IPs. Please correct me if I am wrong
upvoted 5 times
Iamrandom
3 years, 2 months ago
Very good point! But seems the most fit (besides this point). Also the others have some problems: - Application LB is not fit for UDP application - can't use NLB as source for Cloudfront So... I'm very confused.
upvoted 2 times
...
Phyo007
3 years ago
company's compliance standards state that application must be hosted in on-premise only, meaning that cloudfront caching is not compliant.
upvoted 1 times
...
reliquary
3 years, 1 month ago
Global Accelerator assigns each accelerator a default Domain Name System (DNS) name, similar to a1234567890abcdef.awsglobalaccelerator.com, that points to the static IP addresses that Global Accelerator assigns to you or that you choose from your own IP address range. Depending on the use case, you can use your accelerator's static IP addresses or DNS name to route traffic to your accelerator, or set up DNS records to route traffic using your own custom domain name. https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-components.html
upvoted 4 times
...
...
andriikor
3 years, 2 months ago
UDP based - only NLB, across NLB variants - AWS Global Accelerator = increasing performance, so, match company's demand. So, A is correct.
upvoted 6 times
...
Samantha23
3 years, 2 months ago
A..NLB cant be used as cloudfront origin
upvoted 6 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago