Correct Answer: Implement Route 53 Geoproximity routing policies and apply a positive bias to the us-west-2 resource record set and a negative bias to the eu-west-1 resource record set
Geoproximity routing allows Route 53 to route traffic to resources based on the geographic location of users and resources. Optionally, you can choose to route more or less traffic...
Correct Answer
Implement Route 53 Geoproximity routing policies and apply a positive bias to the us-west-2 resource record set and a negative bias to the eu-west-1 resource record set
Why This Answer Is Correct
Geoproximity routing allows Route 53 to route traffic to resources based on the geographic location of users and resources. Optionally, you can choose to route more or less traffic to a resource by specifying a value, known as a bias. A bias expands or shrinks the geographic region from which Route 53 routes traffic to a resource.
This question evaluates your knowledge of Amazon Route 53 — a core concept tested in AWS Certified Solutions Architect – Professional (SAP-C02). Understanding Amazon Route 53 is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
Your organization is hosting a globally available application. You want to route users to the closest healthy endpoint while automatically failing over to a secondary region if the primary region's health check fails. Which Route 53 routing policy and configuration should you use?
An enterprise uses Amazon Route 53 Private Hosted Zones (PHZs) inside a VPC for name resolution of database endpoints. The main database is hosted in us-east-1, and a replica is in us-west-2. On-premises datacenters resolve endpoints using Route 53 Inbound Resolvers. They want to set up an active-passive failover for the database endpoint (db.corp.internal) using Route 53. What configuration must they implement to ensure proper failover resolution for both VPC resources and on-premises users?
An online booking platform runs on a multi-region active-active architecture across us-east-1 and us-west-2. To prepare for disaster recovery, they want to implement a mechanism that can shift 100% of traffic away from a compromised region within 1 minute. They want to avoid automatic failover due to risk of split-brain, preferring a manual but rapid, centralized trigger that updates DNS. Which AWS capability is designed for this exact use case?
A security architect wants to prevent data exfiltration via DNS tunneling from EC2 instances running in a VPC. The instances use the default VPC DNS resolver (AmazonProvidedDNS). The architect needs to block outbound DNS queries to known malicious domains and dynamic DNS hosts, while allowing access to internal domains and AWS endpoints. What is the most operationally efficient way to implement this?