Topic 1 Question 294
A company runs an application on hundreds of Amazon EC2 instances in three Availability Zones. The application calls a third-party API over the public internet. A SysOps administrator must provide the third party with a list of static IP addresses so that the third party can allow traffic from the application.
Which solution will meet these requirements?
Add a NAT gateway in the public subnet of each Availability Zone. Make the NAT gateway the default route of all private subnets in those Availability Zones.
Allocate one Elastic IP address in each Availability Zone. Associate the Elastic IP address with all the instances in the Availability Zone.
Place the instances behind a Network Load Balancer (NLB). Send the traffic to the internet through the private IP address of the NLB.
Update the main route table to send the traffic to the internet through an Elastic IP address that is assigned to each instance.
ユーザの投票
コメント(4)
- 正解だと思う選択肢: A
From my perspective, you can't assign an elastic IP to multiple instances in an AZ. Also, the API will never see a private IP on the AWS side. To me, the answer is to have a static public IP (EIP) assigned to the NAT gateway in each AZ, and have the EC2 instances on a private subnet. Everytime and instance hits the external API, the API is going to see one of three unchanging EIPs. Enough said.
👍 6Gomer2023/05/03 - 正解だと思う選択肢: A
Option A makes more sense to me.
👍 3AndyMartinez2023/04/22 - 正解だと思う選択肢: B
By allocating one Elastic IP address in each Availability Zone, the SysOps administrator can assign a unique static IP address to each instance running in that Availability Zone. Once the Elastic IP addresses are associated with the instances, the administrator can provide the list of Elastic IP addresses to the third-party API provider to allow traffic from the application.
👍 1Abdullxh2023/05/02
シャッフルモード