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

"ELB provides load balancing within one Region, AWS Global Accelerator provides traffic management across multiple Regions [...] 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. If you have workloads that cater to a global client base, we recommend that you use AWS Global Accelerator. If you have workloads hosted in a single AWS Region and used by clients in and around the same Region, you can use an Application Load Balancer or Network Load Balancer to manage your resources." https://aws.amazon.com/global-accelerator/faqs/

i feel C

Answer C - Clue - Global accelerator can combine multiple endpoints of different ALB in different regions to one.

A and B are wrong. In D weighted policy seems not appropriate here. Hence C seems more accurate than D.

AWS Global Accelerator is a networking service that helps you improve the availability, performance, and security of your public applications. Global Accelerator provides two global static public IPs that act as a fixed entry point to your application endpoints, such as Application Load Balancers, Network Load Balancers, Amazon Elastic Compute Cloud (EC2) instances, and elastic IPs.

THE OPTIMAL SOLUTION MUST BE Create a VPC in each of the us-east-1 and us-west-1 Regions. Launch EC2 instances in multiple Availability Zones within each VPC.WHICH WILL RUN OUR WEB APPLICATION Create an Application Load Balancer in each Region in front of the EC2 instances. Create a Global Accelerator and specify the two Application Load Balancers as endpoints. Update DNS records to route traffic to the Global Accelerator. Monitor performance and make adjustments as necessary.

Q: What can I do with AWS Global Accelerator? Easily move endpoints between Availability Zones or AWS Regions without needing to update your DNS configuration or change client-facing applications. https://aws.amazon.com/global-accelerator/faqs/

Route53 will not actually route the records. It just returns the appropriate CNAME or A record. To route the traffic among different regions use Global Accelerator.

There is no correct answer. The 2 answers that only include the Load Balancers are wrong - they do not work multi-region The Global Accelerator answer would be a good solution, however they say adding the 2 different load balancers to 1 Endpoint group. An Endpoint Group can only contain Endpoints from a single Region -> thus also wrong. Route 53 could also be an option, but not with weighted policies, those will not help us spread load across regions. The following policies could help: latency, geolocation, Geoproximity, latency-based. So this answer is also not correct.

This provides justification to add endpoints from different regions to the ALB: https://catalog.us-east-1.prod.workshops.aws/workshops/effb1517-b193-4c59-8da5-ce2abdb0b656/en-US/traffic-dials Add endpoint groups to the accelerator The new requirement is to make sure your web application is deployed in at least two different AWS regions, different reasons can explain this requirement: compliance latency blue/green deployments, A/B testing, failover in case for example something happens to the Lambda function, handle increased traffic, etc. This does a comparative analysis of latency between options C and D specifcally for a small number of regions: https://binx.io/2021/11/17/latency-based-routing-in-aws/ Also, We already know that Route 53 latency-based routing makes use of DNS telemetry and network latency to return the best latency record for a given query. Therefore it spends more time on the ISP network and the Internet than the Global Accelerator does.

C is the appropriate answer

AWS Global Accelerator provides you with a set of static IP addresses that can map to multiple application endpoints across AWS Regions, to improve redundancy.

How is it gonna be D? Weighted policy won't account for location, you're going to have to set it to 50/50 or some other amount. Clearly states here that you can have more than one endpoint group in the accelerator and direct traffic to an endpoint group based on client location.... https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoint-groups.html

None of the options are correct. Surprised? Read D again... Weighted routing policy does NOT take latency or user location into account. So how can it provide the low latency requirements?

"How AWS Global Accelerator works PDF RSS The static IP addresses provided by AWS Global Accelerator serve as single fixed entry points for your clients. When you set up your accelerator with Global Accelerator, you associate the static IP addresses to regional endpoints in one or more AWS Regions. For standard accelerators, the endpoints are Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses." "When you add a listener in a standard accelerator, you specify the endpoint groups for Global Accelerator to direct traffic to. An endpoint group, and all the endpoints in it, must be in one AWS Region." Plane English An Accelerator is multi-region the condition is that all endpoint into the group must be in the same region.

Answer is C. "For each AWS Region that you want to direct traffic to, add one endpoint group. Endpoint groups include one or more endpoints in the Region. You can't have more than one endpoint group per Region"

Answer is C "AWS Global Accelerator is a service that improves the availability and performance of your applications with local or global users. It provides static IP addresses that act as a fixed entry point to your application endpoints in a single or multiple AWS Regions, and uses the AWS global network to optimize the path from your users to your applications."