Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Amazon Route 53 Resolver endpoints allow DNS queries to securely cross between Amazon VPCs and on-premises networks, enabling hybrid DNS resolution without managing extra servers. Inbound endpoints enable external DNS servers to query VPC-hosted private zones, while outbound endpoints forward queries from VPCs to on-premises resolvers using rules
C is right The company needs to resolve DNS requests from EC2 instances in a VPC to an on-premises Active Directory domain that runs in a data center with an AWS Direct Connect connection. Amazon Route 53 Resolver is specifically designed for this use case, providing a secure way to enable name resolution between your on-premises and cloud-based resources. By using Route 53 Resolver, you can create DNS endpoints within the VPC that resolve DNS queries to the on-premises Active Directory domain without requiring any additional infrastructure or overhead in the data center.
Option C: Amazon Route 53 Resolver with Conditional Forwarding Rules Least Administrative Overhead: This option leverages AWS-managed services to handle DNS resolution without the need to manage additional infrastructure or complicated configurations. Route 53 Resolver Endpoints: Create inbound and outbound endpoints to handle DNS queries between AWS and the on-premises environment. Inbound Endpoints: Allow on-premises systems to resolve DNS names hosted in AWS. Outbound Endpoints: Forward DNS queries from AWS to on-premises DNS servers. Conditional Forwarding Rules: Set up rules to forward specific domain queries (like your Active Directory domain) to the on-premises DNS servers. This ensures seamless DNS resolution for the applications in the VPC. B: Private hosted zones are intended for DNS records within AWS. A & D: too much overhead