A SysOps administrator notices a scale-up event for an Amazon EC2 Auto Scaling group. Amazon CloudWatch shows a spike in the RequestCount metric for the associated Application Load Balancer. The…

Question

Options

• AAuto Scaling logs
• BAWS CloudTrail logs
• CEC2 instance logs
• DElastic Load Balancer access logs

• A
  2% (1)
• B
  5% (3)
• C
  2% (1)
• D
  92% (61)

Explanation

Elastic Load Balancer (ELB) access logs capture detailed information about every request sent to the load balancer, including the client IP address, request path, response codes, and timestamps - making them the definitive source for identifying who is sending traffic. Auto Scaling logs (A) track scaling activity like instance launches and terminations, not request-level traffic data. CloudTrail (B) records AWS API calls for auditing and governance, not application-layer HTTP request details. EC2 instance logs (C) might contain some request data depending on the application, but they are not a reliable or centralized source, and the load balancer may distribute requests across many instances.

Memory tip: Think of ELB access logs as the "front door camera" - every visitor (request) that passes through the load balancer is recorded with their origin (IP address), so it's always your first stop when investigating suspicious or unexpected traffic patterns.

No community discussion yet for this question.