SAP-C02 · Question #839
A company needs a hybrid DNS architecture. The architecture must include the company's on- premises network and a VPC. An AWS Site-to-Site VPN connection connects the VPC to the on- premises…
The correct answer is A. Create an Amazon Route 53 private hosted zone for the myvpc.example.com reserved domain. C. Use Amazon Route 53 Resolver to create an inbound endpoint in the AWS Region of the VPC. F. Configure the on-premises DNS resolvers with a conditional forwarding rule for DNS queries for. You want the myvpc.example.com namespace to resolve only inside the VPC/hybrid environment, not publicly. A Route 53 private hosted zone attached to the VPC gives authoritative private DNS for that domain inside AWS. On-premises resolvers must be able to ask AWS for…
Question
A company needs a hybrid DNS architecture. The architecture must include the company's on- premises network and a VPC. An AWS Site-to-Site VPN connection connects the VPC to the on- premises network. The company already hosts the onprem.mydc.com domain name on premises. The company wants to host the myvpc.example.com domain name in the company's AWS account and resolve to the VPC. The company also needs the on-premises devices to resolve DNS queries to the myvpc.example.com domain. Which combination of steps will meet these requirements? (Choose three.)
Options
- ACreate an Amazon Route 53 private hosted zone for the myvpc.example.com reserved domain.
- BCreate an Amazon Route 53 public hosted zone for the myvpc.example.com reserved domain.
- CUse Amazon Route 53 Resolver to create an inbound endpoint in the AWS Region of the VPC.
- DUse Amazon Route 53 Resolver to create an outbound endpoint in the AWS Region of the VPC.
- EUse Amazon Route 53 Resolver to create a forwarding rule for the Route 53 private hosted zone
- FConfigure the on-premises DNS resolvers with a conditional forwarding rule for DNS queries for
How the community answered
(18 responses)- A61% (11)
- B6% (1)
- D11% (2)
- E22% (4)
Explanation
You want the myvpc.example.com namespace to resolve only inside the VPC/hybrid environment, not publicly. A Route 53 private hosted zone attached to the VPC gives authoritative private DNS for that domain inside AWS. On-premises resolvers must be able to ask AWS for myvpc.example.com. An inbound endpoint provides IPs in the VPC that your on-prem DNS can forward those queries to over the VPN. Point your on-prem DNS servers to the inbound endpoint for the myvpc.example.com zone. This lets on-prem clients resolve that domain by forwarding only those queries to AWS.
Community Discussion
No community discussion yet for this question.