AWS Certified Advanced Networking Specialty Practice Exam

Disable ads (and more) with a membership for a one time $4.99 payment

Prepare for the AWS Certified Advanced Networking Specialty Exam with detailed flashcards and multiple-choice questions. Each question includes hints and explanations. Ace your exam with confidence!

Practice this question and more.


What two actions need to be taken if instance hostnames are not resolving in a private Route 53 hosted zone?

  1. Set enableDnsSupport and enableDnsHostnames to true.

  2. Update security group rules and network ACLs.

  3. Allocate additional Elastic IPs.

  4. Create an internet gateway for the VPC.

The correct answer is: Set enableDnsSupport and enableDnsHostnames to true.

The actions necessary to ensure that instance hostnames are resolving in a private Route 53 hosted zone primarily involve enabling DNS resolution features specific to Amazon EC2 instances. When you set both enableDnsSupport and enableDnsHostnames to true, you allow your VPC to support DNS resolution and to use the instance hostnames assigned by AWS. When enableDnsSupport is set to true, the Amazon-provided DNS server at the VPC level will be able to resolve DNS queries for instances that have public or private addresses. Meanwhile, enableDnsHostnames being set to true ensures that any instances that are part of your VPC (Virtual Private Cloud) receive DNS hostnames that can be resolved to their respective private IP addresses. This is crucial in a VPC setting where communication often occurs over internal IP addresses and where knowing the instance hostname can facilitate easier management and configuration. By ensuring that these two settings are both enabled, you effectively enable the full capabilities of DNS within your VPC, which directly addresses the problem of hostnames not resolving in a private Route 53 hosted zone. The other actions do not address the hostname resolution within the context of a private hosted zone.