Your team has developed a web application that will run on an EC2 Instance.
There is a deployment requirement wherein if the primary application fails.
The requests need to be routed to a static website.
Which of the following can help you achieve this?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - C.
The AWS Documentation mentions the following.
Amazon Route 53 health checks monitor the health and performance of your web applications, web servers, and other resources.
Each health check that you create can monitor one of the following.
The health of a specified resource, such as a web server.
The status of other health checks.
The status of an Amazon CloudWatch alarm.
Options A and B are incorrect since the Load balancers are used to distribute traffic and not divert traffic.
Option D is incorrect since the application is not being hosted on Elastic Beanstalk.
For more information on DNS failover, please refer to the below URL-
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.htmlTo achieve the requirement of routing requests to a static website in case of primary application failure, we need to ensure that we have a failover mechanism in place.
Option A: A Classic Load Balancer placed in front of EC2 Instances A Classic Load Balancer is a Layer 4 (transport layer) load balancer that distributes incoming traffic across multiple targets such as EC2 instances, containers, and IP addresses in a single availability zone or multiple availability zones. However, it does not have the ability to route traffic based on application content or provide advanced request routing features. As a result, it cannot achieve the required failover mechanism.
Option B: An Application Load Balancer placed in front of EC2 Instances An Application Load Balancer is a Layer 7 (application layer) load balancer that is capable of distributing incoming traffic based on application content, such as HTTP requests and URL paths. It provides advanced routing features such as routing based on hostnames, paths, and query parameters. Additionally, it has the ability to route traffic to specific targets based on rules and also supports failover mechanisms by enabling health checks on the targets. Therefore, this option is a good fit for the requirement of routing requests to a static website in case of primary application failure.
Option C: A health check in Route 53 Route 53 is a DNS web service that can be used to route traffic to various AWS resources such as EC2 instances, load balancers, and S3 buckets. It can also perform health checks on the resources and route traffic based on their health status. However, Route 53 alone cannot achieve the required failover mechanism as it cannot route traffic based on application content or provide advanced request routing features.
Option D: The swap URL feature in Elastic Beanstalk Elastic Beanstalk is a fully managed service that makes it easy to deploy and scale applications. It provides the ability to perform blue/green deployments, which involves creating a new environment with updated code and then swapping the URLs of the old and new environments. However, this option is not a good fit for the requirement of routing requests to a static website in case of primary application failure as it does not provide failover mechanisms.
Therefore, the best option to achieve the requirement of routing requests to a static website in case of primary application failure is to use an Application Load Balancer placed in front of the EC2 instances.