Topic 1 Question 231
A company hosts a highly available, scalable, and resilient application on Amazon EC2 instances that are part of an Auto Scaling group. A network engineer is planning to integrate IPv6 support with the application deployment in phases. The first phase is to enable IPv6 service consumption on the public Network Load Balancers (NLBs) that are deployed across the infrastructure. The target groups for the NLBS are configured as the Auto Scaling groups of the EC2 instances that host the application. The NLBs are configured for dual-stack operation.
During the testing of the first phase, the IPv6 application queries are not reaching the backend servers.
What is the cause of this issue?
The subnets where the EC2 instances are deployed do not have IPv6 addresses configured.
The route tables for the NLB subnets do not have IPV6 routing configured.
The route tables for the EC2 subnets do not have IPV6 routing configured.
The security groups that are associated with the NLBs do not allow IPv6 traffic.
ユーザの投票
コメント(2)
- 正解だと思う選択肢: A
The EC2 subnets (where the Auto Scaling group instances run) do not have IPv6 addresses configured. Therefore, even though the Network Load Balancer (NLB) is operating in dual-stack mode and can accept IPv6 connections, it cannot forward IPv6 traffic to instances that do not themselves have IPv6 addresses in the same subnet.
👍 3djangoGroup2025/01/08 - 正解だと思う選択肢: B
See https://docs.aws.amazon.com/whitepapers/latest/ipv6-on-aws/scaling-the-dual-stack-network-design-in-aws.html NLB does the IPv6 to IPv4 conversion during this first phase so that no IPv6 configuration is necessary in the EC2 subnet
👍 1c1193d42025/02/27
シャッフルモード