
Ultimate access to all questions.
A company operates custom DNS servers running BIND for name resolution across multiple VPCs in different AWS accounts within the same AWS Organizations setup. These VPCs are interconnected via a transit gateway, with the BIND servers hosted in a central VPC and configured to forward queries for an on-premises DNS domain to on-premises DNS servers. To ensure all VPCs use the custom DNS servers, a VPC DHCP options set specifying these DNS servers has been applied to all VPCs.
A development team is unable to mount a newly created Amazon EFS file system to an Amazon EC2 instance because the 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 to enable all development teams in the organization to mount EFS file systems.
Which two steps should the network engineer take to meet these requirements?
A
Configure the BIND DNS servers in the central VPC to forward queries for efs.us-east-1.amazonaws.com to the Amazon provided DNS server (169.254.169.253).
B
Create an Amazon Route 53 Resolver outbound endpoint in the central VPC. Update all the VPC DHCP options sets to use AmazonProvidedDNS for name resolution.
C
Create an Amazon Route 53 Resolver inbound endpoint in the central VPUpdate all the VPC DHCP options sets to use the Route 53 Resolver inbound endpoint in the central VPC for name resolution.
D
Create an Amazon Route 53 Resolver rule to forward queries for the on-premises domain to the on-premises DNS servers. Share the rule with the organization by using AWS Resource Access Manager (AWS RAM). Associate the rule with all the VPCs.
E
Create an Amazon Route 53 private hosted zone for the efs.us-east-1.amazonaws.com domain. Associate the private hosted zone with the VPC where the EC2 instance is deployed. Create an A record for fs-33444567d.efs.us-east-1.amazonaws.com in the private hosted zone. Configure the A record to return the mount target of the EFS mount point.