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

https://aws.amazon.com/pt/premiumsupport/knowledge-center/fail-over-s3-r53/

No Health Check to secudary fail over.

Everyone saying CE is wrong, period. If you were not using the ALB then yes, CE would be correct. Pay attention to this which clearly says that if you are using an alias record, as you can with a ELB/ALB, then the health check is configured directly on Route 53. If you were just routing directly to the EC2 instance, then yes, you would need the health check, but that is not the case here. https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-simple-configs.html

No needed for configure health check for S3 static website, only for ALB. Image if you have both health check and both of them unhealthy. In this scenarion no meaning of failover routing.

A and E ALB and S3 are both alias record so no need to create and associate additional health checks. Instead you configuring active-passive failover with one primary and one secondary resource. Useful links: https://repost.aws/questions/QUhlXjnA87QwCWeTjlplv13g/route-53-alb-alias-record-health-checks#COLFaTiEnLSbiJABZjCXO7OQ https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-types.html https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-simple-configs.html

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-simple-configs.html

For Evaluate target health, turn off the option. When the target is an S3 bucket, the option doesn't wor

C E are correct answers

Why not CD?

why would you not associate a health check to the secondary fail over? it doesn't say not to

D E The combination of actions that will meet these requirements is creating a primary failover routing policy record, configuring the value to be the ALB, and creating a secondary failover routing policy record, configuring the value to be the static website. This allows the SysOps administrator to use the static website as a backup to the web application, and automatically fail over to the static website if the health check fails. The administrator can also associate the record with a Route 53 health check to monitor the health of the web application and trigger the failover if necessary. Option A is not appropriate for this situation, as it does not include the secondary failover routing policy record that is necessary for automatic failover. Option B is not appropriate, as it does not involve configuring the routing policy records, which are necessary for directing traffic to the appropriate website. Option C is not appropriate, as it does not include the secondary failover routing policy record that is necessary for automatic failover.

C and E

Ans: CD

C E read carefully this link. It's mentioned that for the primary routiong policy you must specify Helat Check YES, instead for the secondary routing failover routing policy with don't specify Healt Check

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-types.html#dns-failover-types-active-passive-one-resource

CE. No health check for secondary failover.

Create the failover endpoint Open the Amazon Route 53 console, and then choose Hosted zones. Choose the hosted zone that you want to create the record for. Choose Create record, and input the following: For Record name, use the same value that you entered for the primary record. For Record type, choose A – Routes traffic to an IPV4 address and some AWS resources. For Alias, choose Yes. Note: Aliases automatically use a time to live (TTL) that matches the alias target. For Alias Target, choose the S3 bucket that you created previously. For Routing Policy, choose Failover. For Failover Record Type, choose Secondary. For Set ID, enter a name. Note: The name for the Set ID on your failover endpoint must be different from the name of the Set ID on your primary endpoint. For Associate with Health Check, choose No. Choose Create records.