Stand up the web tier in the new Region, use Aurora Global Database to create a secondary Region cluster, configure Amazon Route 53 health checks with failover routing, and promote the secondary to primary when needed is correct because it deploys the full application stack in the new Region and uses a purpose built cross Region database solution to minimize downtime and data loss during regional failure or maintenance.

Aurora Global Database provides physical storage based replication that keeps replication lag extremely low and it allows controlled or unplanned promotion of the secondary Region to primary with minimal RPO and RTO. Deploying the web tier locally in the new Region and pairing the database with Amazon Route 53 failover health checks lets you shift traffic automatically to the healthy Region while keeping user latency as low as possible.

Build the application in the new Region with a fresh Aurora MySQL cluster, use AWS Database Migration Service for ongoing replication from the primary, and use Route 53 failover routing to the new Region is weaker because AWS Database Migration Service is optimized for migrations and change data capture and it does not provide the low latency cross Region failover guarantees that Aurora Global Database offers.

Enlarge the existing Auto Scaling group to span both Regions, enable Aurora Global Database between Regions, and use Route 53 health checks with failover to the new Region is invalid because Amazon EC2 Auto Scaling groups are regional resources and cannot span multiple Regions, so you must provision separate web tiers per Region.

Deploy the application in the new Region and create a cross-Region Aurora MySQL read replica, use Route 53 failover, and promote the replica on primary failure is less desirable because cross Region read replicas normally involve higher failover time and greater risk of data loss compared with Aurora Global Database which is designed for fast, low RPO cross Region replication.

Full AWS Practitioner Certification Question