ANS-C01 · Question #11
A company is using custom DNS servers that run BIND for name resolution in its VPCs. The VPCs are deployed across multiple AWS accounts that are part of the same organization in AWS Organizations…
The correct answer is B. Create an Amazon Route 53 Resolver outbound endpoint in the central VPC. Update all the VPC D. Create an Amazon Route 53 Resolver rule to forward queries for the on-premises domain to the. https://aws.amazon.com/blogs/security/simplify-dns-management-in-a-multiaccount-environment- with-route-53-resolver/ You can mount an Amazon EFS file system on an Amazon EC2 instance using DNS names. The file system DNS name automatically resolves to the mount target’s IP…
Question
A company is using custom DNS servers that run BIND for name resolution in its VPCs. The VPCs are deployed across multiple AWS accounts that are part of the same organization in AWS Organizations. All the VPCs are connected to a transit gateway. The BIND servers are running in a central VPC and are configured to forward all queries for an on-premises DNS domain to DNS servers that are hosted in an on-premises data center. To ensure that all the VPCs use the custom DNS servers, a network engineer has configured a VPC DHCP options set in all the VPCs that specifies the custom DNS servers to be used as domain name servers. Multiple development teams in the company want to use Amazon Elastic File System (Amazon EFS). A development team has created a new EFS file system but cannot mount the file system to one of its Amazon EC2 instances. The network engineer discovers 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 needs to implement a solution so that development teams throughout the organization can mount EFS file systems. Which combination of steps will meet these requirements? (Choose two.)
Options
- AConfigure the BIND DNS servers in the central VPC to forward queries for efs.us-east-
- BCreate an Amazon Route 53 Resolver outbound endpoint in the central VPC. Update all the VPC
- CCreate an Amazon Route 53 Resolver inbound endpoint in the central VPUpdate all the VPC
- DCreate an Amazon Route 53 Resolver rule to forward queries for the on-premises domain to the
- ECreate an Amazon Route 53 private hosted zone for the efs.us-east-1.amazonaws.com domain.
How the community answered
(60 responses)- A7% (4)
- B55% (33)
- C12% (7)
- E27% (16)
Explanation
https://aws.amazon.com/blogs/security/simplify-dns-management-in-a-multiaccount-environment- with-route-53-resolver/ You can mount an Amazon EFS file system on an Amazon EC2 instance using DNS names. The file system DNS name automatically resolves to the mount target’s IP address in the Availability Zone of the connecting Amazon EC2 instance. To be able to do that, the VPC must use the default DNS provided by Amazon to resolve EFS DNS names. If you plan to use EFS in your environment, I recommend that you resolve EFS DNS names locally and avoid sending these queries to central DNS because clients in that case would not receive answers optimized for their availability zone, which might result in higher operation latencies and less durability.
Topics
Community Discussion
No community discussion yet for this question.