A primary AWS Region hosts a web application and a secondary Region is a standby for disaster recovery. Requirements: session data must replicate across regions near-real-time; 1% of traffic should be routed to secondary continuously; automatic failover to secondary on primary disruption; secondary must scale to handle full traffic. How should these requirements be met?

This solution meets all requirements. Elastic Beanstalk provides a managed platform for deploying the web application in both regions, simplifying scaling and management. DynamoDB global tables offer near-real-time, multi-region replication for session data, ensuring data consistency for the 1% continuous traffic and during failover. Route 53's weighted routing policy with health checks allows for continuous 1% traffic distribution to the secondary region and automatic failover if the primary region becomes unhealthy. The secondary region, being a full deployment, can scale to handle 100% of the traffic. Incorrect options: Using a Route 53 failover routing policy would not allow for continuous 1% traffic to the secondary region. Lambda and API Gateway are suitable for serverless applications, but RDS for PostgreSQL with cross-region replication might introduce higher latency for session data compared to DynamoDB Global Tables, and the client-side logic for API Gateway is not ideal for a web application. CloudFront is a CDN and would cache content, but it's not the primary mechanism for routing live application traffic between regions for disaster recovery and continuous small traffic distribution. Route 53 is better suited for DNS-level traffic management between regions.