Low-Latency Time Series Visualization with OpenSearch
A company is creating near real-time dashboards to visualize time series data. The company ingests data into Amazon Managed Streaming for Apache Kafka (Amazon MSK). A customized data pipeline consumes the data. The pipeline then writes data to Amazon Keyspaces (for Apache Cassandra), Amazon OpenSearch Service, and Apache Avro objects in Amazon S3. Which solution will make the data available for the data visualizations with the LEAST latency?
Community Votes
80% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the understanding of storage and compute separation versus integrated search engines, with the common trap being the assumption that Athena or S3 Select can match the speed of a dedicated search cluster.
This question evaluates the optimal AWS service for visualizing near real-time time series data with minimal latency. It establishes that Amazon OpenSearch Service is superior to S3-based query services for this specific use case.
Many learners choose options involving Amazon Athena because it is a popular serverless query tool, failing to realize that querying object storage (S3) inherently introduces higher latency compared to indexing in OpenSearch.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Amazon OpenSearch Service is designed specifically for full-text search, log analytics, and real-time data visualization. By writing data directly to OpenSearch Service, the pipeline leverages Lucene's inverted index structure, allowing for sub-second query responses on time series data. This architecture eliminates the need for complex ETL processes required by columnar query engines like Athena, thus providing the LEAST latency for near real-time dashboards.Why the Other Options Are Wrong
Options B, C, and D all rely on Amazon Athena or S3 Select to query Avro objects stored in Amazon S3. While Athena is powerful for ad-hoc analysis, it is not optimized for low-latency, high-frequency dashboarding because it scans S3 objects (even if partitioned) and lacks the persistent, indexed state of OpenSearch. Additionally, Option C incorrectly suggests using Keyspaces as a data catalog for Athena, which is technically invalid as Athena uses Glue or Hive metastores. Option A is the only choice that utilizes a service built for immediate retrieval and visualization.Community Comment Notes
The community consensus strongly favors Option A, with users noting that "OpenSearch is designed for low-latency data retrieval" and is ideal for these scenarios. One commenter mentioned using Grafana, but clarified that the backend data source matters most for latency; connecting Grafana to OpenSearch (not Athena) would be the correct pattern, reinforcing why A is better than B.Exam Strategy
When asked about 'least latency' for dashboards, avoid object storage solutions like S3 + Athena unless the data is historical or batch-oriented. Prefer managed search or database services (like OpenSearch, DynamoDB, or Timestream) that keep data indexed and ready for instant retrieval.
Frequently Asked Questions
Why is Amazon Athena too slow for real-time dashboards?
Athena queries S3 objects, which involves scanning and parsing files. Even with partitioning, it cannot match the sub-second response time of an indexed search engine like OpenSearch for frequent, small queries.
Can I use Amazon Managed Grafana with OpenSearch?
Yes, Amazon Managed Grafana integrates seamlessly with OpenSearch Service. However, the key factor for latency is the data store (OpenSearch), not the visualization tool itself.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →