nerdexam
Amazon

ANS-C01 · Question #39

A data analytics company has a 100-node high performance computing (HPC) cluster. The HPC cluster is for parallel data processing and is hosted in a VPC in the AWS Cloud. As part of the data…

The correct answer is C. Create Route 53 Resolver outbound endpoints. Create Route 53 Resolver rules to forward. To handle the increased DNS query load for a growing HPC cluster that needs to resolve both AWS and on-premises domains, Route 53 Resolver outbound endpoints and rules should be used for scalable and centralized DNS forwarding.

Submitted by omar99· Mar 6, 2026

Question

A data analytics company has a 100-node high performance computing (HPC) cluster. The HPC cluster is for parallel data processing and is hosted in a VPC in the AWS Cloud. As part of the data processing workflow, the HPC cluster needs to perform several DNS queries to resolve and connect to Amazon RDS databases, Amazon S3 buckets, and on-premises data stores that are accessible through AWS Direct Connect. The HPC cluster can increase in size by five to seven times during the company's peak event at the end of the year. The company is using two Amazon EC2 instances as primary DNS servers for the VPC. The EC2 instances are configured to forward queries to the default VPC resolver for Amazon Route 53 hosted domains and to the on-premises DNS servers for other on-premises hosted domain names. The company notices job failures and finds that DNS queries from the HPC cluster nodes failed when the nodes tried to resolve RDS and S3 bucket endpoints. Which architectural change should a network engineer implement to provide the DNS service in the MOST scalable way?

Options

  • AScale out the DNS service by adding two additional EC2 instances in the VPC. Reconfigure half
  • BScale up the existing EC2 instances that the company is using as DNS servers. Change the
  • CCreate Route 53 Resolver outbound endpoints. Create Route 53 Resolver rules to forward
  • DCreate Route 53 Resolver inbound endpoints. Create rules on the on-premises DNS servers to

How the community answered

(22 responses)
  • A
    14% (3)
  • B
    27% (6)
  • C
    50% (11)
  • D
    9% (2)

Why each option

To handle the increased DNS query load for a growing HPC cluster that needs to resolve both AWS and on-premises domains, Route 53 Resolver outbound endpoints and rules should be used for scalable and centralized DNS forwarding.

AScale out the DNS service by adding two additional EC2 instances in the VPC. Reconfigure half

Scaling out EC2 instances for DNS introduces management overhead, still requires managing DNS software, and doesn't inherently offer the same level of integration or scalability for hybrid DNS as Route 53 Resolver.

BScale up the existing EC2 instances that the company is using as DNS servers. Change the

Scaling up EC2 instances for DNS might offer temporary relief but is not as cost-effective or scalable for peak loads compared to a managed service like Route 53 Resolver.

CCreate Route 53 Resolver outbound endpoints. Create Route 53 Resolver rules to forwardCorrect

Route 53 Resolver outbound endpoints allow queries originating from the VPC to be forwarded to on-premises DNS servers, while Resolver rules can direct specific domain queries to these endpoints, providing a scalable and managed solution for hybrid DNS resolution without managing EC2-based DNS servers.

DCreate Route 53 Resolver inbound endpoints. Create rules on the on-premises DNS servers to

Route 53 Resolver inbound endpoints are used to allow on-premises DNS servers to query AWS (VPC) hosted domains, not for EC2 instances in the VPC to query on-premises DNS, making it unsuitable for the described problem.

Concept tested: Route 53 Resolver for Hybrid DNS Resolution

Source: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html

Topics

#Route 53 Resolver#DNS scaling#VPC DNS#Hybrid DNS

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full ANS-C01 Practice