-
Hi Privat33r,
Thank you for your detailed feedback, and I appreciate you bringing this to our attention.
You are correct that the scenario lacks clarity regarding the type of VPC used, whether it’s IPv4-only or IPv6-enabled. However, the scenario does mention that the company has multiple VPCs with IPv6 enabled for its web applications, which reasonably implies that IPv6 is supported in the current environment.
Additionally, you are correct that AWS now allows creating IPv6-only subnets without first requiring an IPv4 subnet, as highlighted in the blog post you shared. This significant update enables users to deploy EC2 instances in IPv6-only subnets, provided that they are using Nitro EC2 instance type.
However, since the question does not specify the instance type, which is crucial for IPv6-only subnets, and because this feature is limited to Nitro EC2 instance type, the option that says “Set up a new IPv6-only subnet with a large CIDR range. Associate the new subnet with the VPC then launch the instance.“ is incorrect in all cases.
Hence, the option that says “Set up a new IPv4 subnet with a larger CIDR range. Associate the new subnet with the VPC and then launch the instance.” is the correct answer. By expanding the IPv4 subnet’s CIDR range, the Solutions Architect can ensure enough IP addresses are available, regardless of the instance type or IPv6 capabilities.
Thank you again for highlighting these important points, and we appreciate your understanding as we work to keep our content accurate and aligned with the latest AWS developments.
Regards,
Nikee @ Tutorials Dojo
