Exam AWS Certified SysOps Administrator - Associate topic 1 question 290 discussion

We are talking about two on-premise web servers, meaning we have IP addresses for them. What we should do is to create proper records in a public hosted zone, e.g. A-record in this case. We are not working with aliases for on-premise resources. Aliases are for resources in Cloud, e.g. ELB. Last thing is that we are talking about HTTP protocol.

wow almost all of these posts are wrong. it is 100% A and not C. You CANT use alias for on-prem

a record can't failover

A record also works, but alias is more recommended.

Not sure, but C looks better answer.

Explanation: In this scenario, you want Route 53 to route traffic to the primary server if the associated health check returns 2xx or 3xx HTTP codes. All other traffic should be directed to the secondary passive server. To achieve this, you need to create alias records for each server with evaluate target health set to yes, which means Route 53 will perform health checks on the targets associated with these records. Choosing an alias record is appropriate because alias records can be used to map the domain name to an Elastic Load Balancer, an Amazon S3 bucket, an Amazon CloudFront distribution, or another Route 53 resource record set. Alias records also support health checks. Using an HTTP health check is suitable because you need to check the health of the servers based on HTTP responses. Route 53 will evaluate the HTTP status codes and determine which server is healthy to direct traffic to.

"Evaluate health of an AWS resource (alias records)" "If you're using alias records to route traffic to selected AWS resources, such as ELB load balancers, you can configure Route 53 to evaluate the health of the resource and to route traffic only to resources that are healthy." https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-simple-configs.html