Additionally instances that have public IP addresses must receive corresponding public hostnamesWhich solution will meet these requirements to ensure that the domain names are correctly resolved within the VPC?
Create a private hosted zone. Activate the enableDnsSupport attribute and the enableDnsHostnames attribute for the VPC. Update the VPC DHCP options set to include domain-name-servers=10.24.34.2.
Create a private hosted zone Associate the private hosted zone with the VPC. Activate the enableDnsSupport attribute and the enableDnsHostnames attribute for the VPC. Create a new VPC DHCP options set, and configure domain-name-servers=AmazonProvidedDNS. Associate the new DHCP options set with the VPC.
Deactivate the enableDnsSupport attribute for the VPActivate the enableDnsHostnames attribute for the VPCreate a new VPC DHCP options set, and configure doman-name-servers=10.24.34.2. Associate the new DHCP options set with the VPC.
Create a private hosted zone. Associate the private hosted zone with the VPC. Activate the enableDnsSupport attribute for the VPC. Deactivate the enableDnsHostnames attribute for the VPC. Update the VPC DHCP options set to include domain-name-servers=AmazonProvidedDNS.
Explanations:
This option does not create or associate a private hosted zone with the VPC, which is necessary for DNS queries to resolve properly within the VPC. Additionally, it suggests using a specific IP for DNS, which may not accommodate public hostname requirements.
This option creates and associates a private hosted zone with the VPC, ensuring DNS queries are resolved correctly. It also activates both enableDnsSupport and enableDnsHostnames, allowing instances with public IPs to receive public hostnames while also ensuring private DNS resolution within the VPC.
This option deactivates enableDnsSupport, which is necessary for DNS resolution in the VPC. Although it activates enableDnsHostnames, the lack of DNS support will prevent any DNS queries from being processed, violating the requirement for private hosted zones.
While this option creates a private hosted zone and associates it with the VPC, it incorrectly deactivates enableDnsHostnames, which is required for instances with public IPs to receive corresponding public hostnames. Additionally, it uses a specific IP for DNS instead of AmazonProvidedDNS.
I rank that the answer is:
Create a private hosted zone Associate the private hosted zone with the VPC. Activate the enableDnsSupport attribute and the enableDnsHostnames attribute for the VPC. Create a new VPC DHCP options set, and configure domain-name-servers=AmazonProvidedDNS. Associate the new DHCP options set with the VPC.