Topic 1 Question 167
A company is running a web application in a VPC. The web application runs on a group of Amazon EC2 instances behind an Application Load Balancer (ALB). The ALB is using AWS WAF.
An external customer needs to connect to the web application. The company must provide IP addresses to all external customers.
Which solution will meet these requirements with the LEAST operational overhead?
Replace the ALB with a Network Load Balancer (NLB). Assign an Elastic IP address to the NLB.
Allocate an Elastic IP address. Assign the Elastic IP address to the ALProvide the Elastic IP address to the customer.
Create an AWS Global Accelerator standard accelerator. Specify the ALB as the accelerator's endpoint. Provide the accelerator's IP addresses to the customer.
Configure an Amazon CloudFront distribution. Set the ALB as the origin. Ping the distribution's DNS name to determine the distribution's public IP address. Provide the IP address to the customer.
ユーザの投票
コメント(11)
- 正解だと思う選択肢: C
https://docs.aws.amazon.com/global-accelerator/latest/dg/about-accelerators.alb-accelerator.html Option A is wrong. AWS WAF does not support associating with NLB. https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html Option B is wrong. An ALB does not support an Elastic IP address. https://aws.amazon.com/elasticloadbalancing/features/
👍 11Untamables2023/02/10 - 正解だと思う選択肢: C
this option has the least admin effort. A has more admin effort, B is not possible, D will not give static IP address
👍 4bititan2023/02/02 static IP can made below method. ・NLB (replace NLB from ALB) ・NLB + ALB ・global accelarator + ALB ・original load balancer (ex. made by EC2 + nginx)
👍 4masssa2023/02/04
シャッフルモード