Exam AWS Certified Solutions Architect - Professional topic 1 question 776 discussion

A. https://docs.aws.amazon.com/global-accelerator/latest/dg/preserve-client-ip-address.how-to-enable-preservation.html Global Accelerator does not support client IP address preservation for Network Load Balancer and Elastic IP address endpoints.

A . B and D are out coz : Global Accelerator does not support client IP address preservation for Network Load Balancer and Elastic IP address endpoints. C is also out coz it create two seperate accelerators.. It need seperate endpoint in same accelerators instead.. Thus answer is A

GA does not need two separate accelerators in order to route traffic between regions so C and D are out. https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-how-it-works.html#introduction-traffic-dials-weights between A and B - A is out since GA with NLB cannot support IP preservation. Also its better to use alias records with AWS resources. https://docs.aws.amazon.com/global-accelerator/latest/dg/preserve-client-ip-address.how-to-enable-preservation.html

A for me

A sounds better.

Answer is A. Both GC and R53 can be used for Regional Active-Passive Failover. One GC fulfills all requirements, and do not need to create two GC. Search keyword "Global Accelerator" in the link below: https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-options-in-the-cloud.html

go with c

going with c simply because of active failover. Not sure how you would do it with a.

You don`t need DNS failover for Global accelerators. It handles failover it by default based on dials and weights you set for endpoint groups and endpoints respectively. "Failover With a multi-Region active/active strategy, if your workload cannot operate in a Region, failover will route traffic away from the impacted Region to healthy Region(s). You can accomplish this with Route 53 by updating the DNS records. Make sure you set TTL (time to live) on these records low enough so that DNS resolvers will reflect your changes quickly enough to meet your RTO targets. Alternatively, you can use AWS Global Accelerator for routing and failover. It does not rely on DNS. Global Accelerator gives you two static IP addresses. You then configure which Regions user traffic goes to based on traffic dials and weights you set." From https://aws.amazon.com/blogs/architecture/disaster-recovery-dr-architecture-on-aws-part-iv-multi-site-active-active/

A is right

***accelerator DOES NOT SUPPORT client ip address preservation for NLB***** answer is B

An global accelerator supports multiple endpoints in different regions (which can be ALBs or NLBs, so two accelerators are not required. This leaves only A and B. Between A and B, A is the better option as its easier to preserve the client IP with an ALB. Answer: A See - https://docs.aws.amazon.com/global-accelerator/latest/dg/getting-started.html#getting-started-add-endpoints

It's A - since one GA standard accelerator can config for multiple Regions

I will go with B 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

A is correct. ALB preserve the source IP address of the client. So B is wrong. 1 GA is enough.

C - https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-workloads-on-aws.pdf

In my opinion C is correct "needs ... to use static IP addresses, ... a failover event to the secondary Region" - means that primary is used and switched to secondary only if primary fails therefore you must use two separate GA and active-passive DNS failover