A SysOps administrator is maintaining a web application using an Amazon CloudFront web distribution, an Application Load Balancer (ALB), Amazon RDS, and Amazon EC2 in a VPC. All services have…

Question

Options

• AVPC Flow Logs
• BAWS CloudTrail logs
• CALB access logs
• DCloudFront access logs
• ERDS logs

• A
  3% (1)
• B
  3% (1)
• C
  87% (34)
• E
  8% (3)

Explanation

ALB access logs (C) and CloudFront access logs (D) both record HTTP Layer 7 status codes because they operate at the application layer - ALB logs capture the status code returned to the client for each request it processes, and CloudFront logs capture the HTTP status code for every edge request, including cache hits and origin responses.

VPC Flow Logs (A) operate at Layer 3/4 (IP/TCP), capturing source/destination IPs and ports but no HTTP-level information - they have no concept of status codes. CloudTrail (B) logs AWS API calls (control plane actions like CreateBucket or DescribeInstances), not application traffic. RDS logs (E) contain database-level information such as queries and errors, not HTTP status codes from the web tier.

Memory tip: Think "which services touch the HTTP request directly?" - CloudFront sits at the edge and ALB sits in front of your app; both are HTTP-aware proxies that naturally log what HTTP said. Anything below the HTTP layer (VPC Flow Logs, RDS) or beside it (CloudTrail) won't have status codes.

No community discussion yet for this question.