A company has an application that is deployed to two AWS Regions in an active-passive configuration. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB) in each Region. The instances are in an Amazon EC2 Auto Scaling group in each Region. The application uses an Amazon Route 53 hosted zone for DNS. A SysOps administrator needs to configure automatic failover to the secondary Region.
What should the SysOps administrator do to meet these requirements?
To configure automatic failover to the secondary Region, the correct approach is to use Amazon Route 53 with alias records that point to each Application Load Balancer (ALB) in the two Regions. Choosing a failover routing policy ensures that Route 53 directs traffic to the secondary Region if the primary Region's ALB health check fails. Enabling 'Evaluate Target Health' means Route 53 will only route traffic to ALB endpoints that are healthy, facilitating a seamless failover in case of issues in the primary Region.
A Route 53 failover routing
Alias allow duplicate record name which is the case here
To configure automatic failover to the secondary Region for an application that is deployed to two AWS Regions in an active-passive configuration, the following steps should be taken: Configure Route 53 alias records that point to each ALB in the two Regions. Choose a failover routing policy, such as Failover or Geolocation. Set Evaluate Target Health to Yes to ensure that Route 53 only responds to DNS queries with healthy ALB endpoints.
Active / Standby = one region active at a time. Health checks and Route53.
I believe it's Active/Active unless app in one region is inaccessible for whatever reason. If that happens, Route 53 directs all user traffic to the running region. Yes, access may be slower for some users, but slower is beater than dead in the water.
C C. Store the data in S3 Standard for the first 90 days. Set up an S3 Lifecycle rule to move the data to S3 Glacier Flexible Retrieval after 90 days. Explanation: First 90 Days: S3 Standard provides high availability and low latency, which meets the requirement of providing access to the data in milliseconds during the first 90 days when the data is infrequently accessed but must remain highly available. After 90 Days: S3 Glacier Flexible Retrieval is a cost-effective storage class designed for long-term data archiving with retrieval times typically within a few hours, meeting the requirement of retrieval time under 5 hours. This option provides a significant cost saving compared to S3 Standard while still ensuring that data can be retrieved relatively quickly.