AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial-services company operates three on-premises application servers that expose the same public API. The servers use fixed public IP addresses (198.51.100.10, 198.51.100.11, 198.51.100.12) that are reachable over AWS Direct Connect. Public DNS for the api.example.com domain has been migrated to Amazon Route 53.
The architecture team must create a DNS record for api.example.com that meets these reliability and operational requirements:
Clients must receive all three IP addresses so that HTTP clients can retry a different address if the first connection fails.
The operations team must not create or maintain Route 53 health checks, weights, or any other advanced DNS routing features.
Infrastructure-as-Code templates must manage the DNS configuration as a single record set.
Which Route 53 configuration meets these requirements?
Create three A records that use multivalue answer routing and associate a Route 53 health check with each record.
Create three weighted A records, each specifying one IP address with equal weights and (optional) health checks.
Create a failover routing policy with a primary record for the first IP address and secondary records for the remaining IP addresses that become active when health checks fail.
Create one A record for api.example.com that uses the simple routing policy and lists the three IP addresses as separate values.
The simple routing policy is the default Route 53 routing type and supports a single record set that can contain multiple IP addresses. Route 53 returns all the values to the resolver in random order, allowing clients to retry other addresses. Because simple routing performs no health checks or weighted logic, it satisfies the requirement to avoid additional DNS features while still providing basic retry-based resilience.
Multivalue answer routing also returns multiple addresses, but it is specifically designed to work with (optional) Route 53 health checks and would require one record per address, adding operational overhead. Weighted routing introduces routing metadata (weights) and normally requires separate records for each target, which conflicts with the single-record requirement. Failover routing inherently depends on Route 53 health checks and supports only primary/secondary records, so it cannot represent three active addresses without extra complexity. Therefore, a single A record that uses the simple routing policy and lists all three IP addresses is the correct solution.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is the simple routing policy in Route 53 the best choice for this scenario?
Open an interactive chat with Bash
What are the differences between simple and multivalue answer routing policies?
Open an interactive chat with Bash
How does Route 53 handle client retries when multiple IPs are listed in a single record?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design for New Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access