Exam AWS-SysOps topic 1 question 917 discussion

After researching some bit, I believe the answer to be C based on this article: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-troubleshooting.html Where it's possible that the custom ping path does not exist for one the web servers

In this scenario, the CloudFormation template has many changes, and it's possible that one of the changes affected the health checks or the custom ping path that the ALB is using. If the ALB is configured to use a custom ping path (e.g., "/ping") for its health checks, and that custom path is not present on the faulty server, the ALB will consider the faulty server as unhealthy, and it will stop directing traffic to it.

answer is C

answer is C

A. 200 is a success code ---Wrong | B. Stickiness is an attribute of the ASG, not ELB ---Wrong | D. Step4 in creating ALB is "Configure Routing", by default specifies HTTP1, which uses HTTP/1.1 and supports both HTTP/1.1 and HTTP/2, you also have HTTP/2 option without gRPC-specific features. Lastly you have gRPC protocol which is supported when the user requests are in gRPC protocol format. ----In short D is Wrong. | Therefore C is left standing and MUST be correct. | Additionally...if your webserver health check tests reachability of /foobar.html and the webserver only has /fobar.html, if there's a typo or file/link not there, then yes the health test will fail even if your server is perfectly working.

B it is. Create a target page for the health check and specify its path as the ping path.

Answer is B

I think it should be C. A is not correct, 200 is the success code, not failure code///