Topic 1 Question 384

AWS Certified Solutions Architect - Professional

Topic 1 Question 384
A company provides a software as a service (SaaS) application that runs in the AWS Cloud. The application runs on Amazon EC2 instances behind a Network Load Balancer (NLB). The instances are in an Auto Scaling group and are distributed across three Availability Zones in a single AWS Region.

The company is deploying the application into additional Regions. The company must provide static IP addresses for the application to customers so that the customers can add the IP addresses to allow lists. The solution must automatically route customers to the Region that is geographically closest to them.

Which solution will meet these requirements?
- Create an Amazon CloudFront distribution. Create a CloudFront origin group. Add the NLB for each additional Region to the origin group. Provide customers with the IP address ranges of the distribution’s edge locations.
- Create an AWS Global Accelerator standard accelerator. Create a standard accelerator endpoint for the NLB in each additional Region. Provide customers with the Global Accelerator IP address.
- Create an Amazon CloudFront distribution. Create a custom origin for the NLB in each additional Region. Provide customers with the IP address ranges of the distribution’s edge locations.
- Create an AWS Global Accelerator custom routing accelerator. Create a listener for the custom routing accelerator. Add the IP address and ports for the NLB in each additional Region. Provide customers with the Global Accelerator IP address.
ユーザの投票
コメント(7)
- 正解だと思う選択肢: B
  Answer is B not D. CloudFront does not work with NLB nor does it accept a fixed IP address
  
  A Standard accelerators automatically route traffic to a healthy endpoint that is nearest to your user. Since they're designed to load balance traffic, you can't deterministically route multiple users to a specific EC2 destination behind your accelerator. Custom routing accelerators allows you to do just that.
  
  Another difference is that standard routing accelerators support Network Load Balancers, Application Load Balancers, EC2 instances, and Elastic IPs as endpoints. Custom routing accelerators support only VPC subnet endpoints, each containing one or more EC2 instances that are running your application.
  
  https://aws.amazon.com/global-accelerator/faqs/#:~:text=A%3A%20Standard%20accelerators%20automatically%20route,you%20to%20do%20just%20that.
  
  👍 4
  ayadmawla2023/12/10
- 正解だと思う選択肢: B
  Answer: B
  
  👍 2
  cypkir2023/11/21
- 正解だと思う選択肢: B
  Answer B. For standard accelerators, the endpoints are Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses. For custom routing accelerators, the endpoints are virtual private cloud (VPC) subnets with one or more EC2 instances.
  
  👍 2
  shaaam802023/11/29
シャッフルモード

ユーザの投票

コメント(7)