Exam AWS-SysOps topic 1 question 559 discussion

When ELB access logs are enabled, detailed logs of all requests made to the load balancer are stored in an Amazon S3 bucket. These logs include information such as the source IP address, request timestamp, HTTP status codes, and more. By analyzing the access logs, the Administrator can identify the clients or IP addresses that generated the 4XX errors and gain insights into the problematic requests. It's important to note that enabling ELB access logs is a recommended best practice for troubleshooting and monitoring the health and performance of applications running behind an ELB. By default, ELB access logs are not enabled, so it's necessary to have enabled them in advance to access this valuable information.

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-access-logs.html

Correct Answer: A https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-access-logs.html

Elastic Load Balancing provides access logs that capture detailed information about requests sent to your load balancer. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. You can use these access logs to analyze traffic patterns and to troubleshoot issues. Access logging is an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logging for your load balancer, Elastic Load Balancing captures the logs and stores them in the Amazon S3 bucket that you specify. You can disable access logging at any time.