SOA-C02 Question 260
Single answerYour company has a hybrid cloud architecture with on-premises servers and resources hosted in AWS. You are tasked with setting up DNS resolution so that on-premises servers can resolve the private domain names of AWS resources in your VPC. Which configuration should you implement to achieve this?
- A
Set up an Amazon Route 53 private hosted zone and associate it with the VPC.
- B
Configure a Route 53 Resolver inbound endpoint in the VPC and update the on-premises DNS server to forward queries to this endpoint.
- C
Enable DNS hostnames and DNS resolution in the VPC settings.
- D
Use an Amazon Route 53 public hosted zone and create records for the private domain names.
Show answer and explanation
Correct answer: B
Explanation
To enable DNS resolution for private domain names of AWS resources from on-premises servers, you must configure a Route 53 Resolver inbound endpoint. This allows the on-premises DNS server to forward DNS queries to the VPC. Setting up private hosted zones or enabling DNS in the VPC alone does not provide the necessary DNS forwarding capability.
- A. Incorrect.
Setting up a private hosted zone in Route 53 allows you to create private DNS records for your VPC, but this alone does not enable DNS resolution for on-premises servers. A mechanism to forward queries from the on-premises environment is still required.
- B. Correct.
Configuring a Route 53 Resolver inbound endpoint allows on-premises DNS servers to forward DNS queries to the VPC. This enables the on-premises servers to resolve private domain names associated with AWS resources.
- C. Incorrect.
Enabling DNS hostnames and DNS resolution in the VPC settings allows EC2 instances within the VPC to resolve internal domain names, but it does not address DNS resolution from on-premises servers.
- D. Incorrect.
Using a public hosted zone is meant for public DNS resolution and is not suitable for resolving private domain names. Additionally, exposing private domain names publicly would be a security risk.