AWS Certified Advanced Networking - Specialty
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
A data analytics company operates a 100-node high-performance computing (HPC) cluster for parallel data processing within an AWS VPC. The HPC cluster requires frequent DNS queries to resolve and connect to Amazon RDS databases, Amazon S3 buckets, and on-premises data stores accessible via AWS Direct Connect. During peak events, the cluster size can grow five to seven times. Currently, the company uses two Amazon EC2 instances as primary DNS servers in the VPC, forwarding queries to the default VPC resolver for Route 53 domains and to on-premises DNS servers for other domains. However, DNS query failures occur when HPC nodes attempt to resolve RDS and S3 endpoints, leading to job failures. What architectural change should a network engineer implement to ensure the DNS service is highly scalable?
A
Scale out the DNS service by adding two additional EC2 instances in the VPC. Reconfigure half of the HPC cluster nodes to use these new DNS servers. Plan to scale out by adding additional EC2 instance-based DNS servers in the future as the HPC cluster size grows.
B
Scale up the existing EC2 instances that the company is using as DNS servers. Change the instance size to the largest possible instance size to accommodate the current DNS load and the anticipated load in the future.
C
Create Route 53 Resolver outbound endpoints. Create Route 53 Resolver rules to forward queries to on-premises DNS servers for on premises hosted domain names. Reconfigure the HPC cluster nodes to use the default VPC resolver instead of the EC2 instance-based DNS servers. Terminate the EC2 instances.
D
Create Route 53 Resolver inbound endpoints. Create rules on the on-premises DNS servers to forward queries to the default VPC resolver. Reconfigure the HPC cluster nodes to forward all DNS queries to the on-premises DNS servers. Terminate the EC2 instances.