Collect metrics to S3 on a schedule, catalog with a Glue crawler, query with Athena, and visualize in QuickSight

Why the Answer Is Correct

The requirement is to audit, analyze, and visualize workload metrics from an application API at scale, which maps onto three stages. For collection, an EventBridge schedule invokes a Lambda function that calls the API to retrieve the metrics and stores the data in Amazon S3, giving automated, durable, and scalable storage that is well suited to analytical query volumes (A). For cataloging and querying, an AWS Glue crawler catalogs the metric data in the S3 bucket and Amazon Athena views are created over the cataloged data, providing SQL access without moving the data (C). For visualization, Amazon QuickSight datasets are created from the Athena views and a QuickSight analysis renders the metric data as a dashboard, giving the required visual representation (E). A, C, and E are the correct combination.

Why the Other Options Are Wrong

B replaces the S3 storage layer with a DynamoDB table that has a stream enabled. DynamoDB is an operational key-value database optimized for request-driven workloads, not an analytical store for large volumes of metric history, so it is a poor fit for the at-scale analysis the requirement describes, and the remaining cataloging steps are built around S3. D goes further and connects an AWS Glue crawler to a DynamoDB stream to catalog the metric data. A Glue crawler crawls S3 buckets and supported data stores; it does not subscribe to a DynamoDB stream, so this integration is not something the crawler supports and the cataloging step would not function. The visualization and collection steps in those options are sound, but the storage and cataloging choices are not. A, C, and E are correct.

Community Comment Notes

Community voted A,C,E unanimously. trungtd laid out the three stages explicitly: EventBridge schedule with Lambda and S3 for data collection and storage, a Glue crawler with Athena for cataloging and querying, and QuickSight for visualization, which is the same decomposition used in the correct answer. jamesf explained that the EventBridge schedule with Lambda storing to S3 provides a scalable and automated way to collect the metrics. getadroit cited the AWS Management Tools blog on analyzing CloudWatch Internet Monitor measurement logs with Athena and QuickSight, which follows this exact pipeline. No alternative received support.