A SysOps administrator needs to create a report that shows how many bytes are sent to and received from each target group member for an Application Load Balancer (ALB). Which combination of steps…

The correct answer is A. Enable access logging for the ALB. Save the logs to an Amazon S3 bucket. C. Use Amazon Athena to query the ALB logs. Query the table. Use the received_bytes and. Enabling ALB access logging (A) captures granular per-request data - including received_bytes and sent_bytes per target - and saves it to S3, which is the required prerequisite for any log-based analysis. Amazon Athena (C) can then query that S3-stored log data directly using…

Submitted by klara.se· Mar 30, 2026Monitoring, Logging, and Remediation

Question

A SysOps administrator needs to create a report that shows how many bytes are sent to and received from each target group member for an Application Load Balancer (ALB). Which combination of steps should the SysOps administrator take to meet these requirements? (Choose two.)

Options

AEnable access logging for the ALB. Save the logs to an Amazon S3 bucket.
BInstall the Amazon CloudWatch agent on the instances in the target group.
CUse Amazon Athena to query the ALB logs. Query the table. Use the received_bytes and
DUse Amazon Athena to query the ALB logs. Query the table. Use the received_bytes and
ECreate an Amazon CloudWatch dashboard that shows the Sum statistic of the ProcessedBytes

How the community answered

(22 responses)

A
68% (15)
B
5% (1)
D
18% (4)
E
9% (2)

Explanation

Enabling ALB access logging (A) captures granular per-request data - including received_bytes and sent_bytes per target - and saves it to S3, which is the required prerequisite for any log-based analysis. Amazon Athena (C) can then query that S3-stored log data directly using SQL, referencing the received_bytes and sent_bytes columns to produce a per-target-group-member report without any data movement.

Why the distractors are wrong:

B - The CloudWatch agent collects OS-level metrics (CPU, memory, network interface totals) from EC2 instances, but it has no visibility into ALB request-level byte data tied to specific target group members.
D - Based on the truncated text, D likely references incorrect column names or a wrong query approach; C uses the correct received_bytes/sent_bytes fields from the ALB log schema.
E - CloudWatch's ProcessedBytes metric is an aggregate at the load balancer level, not broken down per individual target. It cannot produce a per-member report.

Memory tip: For any ALB "per-request detail" question, think A→S3→Athena: access logs are the only source of request-level granularity, S3 is always the destination, and Athena is the query engine. CloudWatch metrics are aggregates - they can't answer "how much traffic did this specific instance handle?"

Topics

#ALB Access Logs#Amazon S3#Amazon Athena#Log Analysis

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice