QuestionQ53

VerifiedNetwork Security, Compliance, and Governance

A company uses custom DNS servers running BIND for name resolution in its VPCs. The VPCs are deployed across multiple AWS accounts that belong to the same AWS Organizations organization. All VPCs are connected to a transit gateway. The BIND servers run in a central VPC and are configured to forward every query for an on-premises DNS domain to DNS servers hosted in an on-premises data center. To make sure that every VPC uses the custom DNS servers, a network engineer has configured a VPC DHCP options set in every VPC that specifies the custom DNS servers as the domain name servers.

Multiple development teams in the company want to use Amazon Elastic File System (Amazon EFS). A development team created a new EFS file system but cannot mount it to one of its Amazon EC2 instances. The network engineer finds that the EC2 instance cannot resolve the IP address for the EFS mount point fs-33444567d.efs.us-east-1.amazonaws.com. The network engineer must implement a solution so development teams throughout the organization can mount EFS file systems.

Which combination of steps meets these requirements?

Choose two
Explanation

AmazonProvidedDNS uses the Route 53 Resolver built into each VPC, which resolves AWS-provided private DNS names, including EFS mount-point names. A Route 53 Resolver outbound endpoint and a forwarding rule for the on-premises domain preserve hybrid DNS resolution by forwarding only matching on-premises queries to the on-premises DNS servers. Sharing that rule through AWS RAM and associating it with the VPCs lets multiple accounts use the central outbound endpoint.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!