A technology company is creating a dashboard that will visualize and analyze time-sensitive data. The data will come in through Amazon Kinesis Data Firehose with the butter interval set to 60…

Question

Options

• ASelect Amazon Elasticsearch Service (Amazon ES) as the endpoint for Kinesis Data Firehose.
• BSelect Amazon S3 as the endpoint for Kinesis Data Firehose.
• CSelect Amazon Redshift as the endpoint for Kinesis Data Firehose.
• DSelect Amazon S3 as the endpoint for Kinesis Data Firehose.

• A
  81% (43)
• B
  2% (1)
• C
  11% (6)
• D
  6% (3)

Explanation

Amazon OpenSearch Service (formerly Amazon Elasticsearch Service) is the correct Firehose destination for near-real-time dashboards. Firehose can stream directly into an OpenSearch/ES index, and Kibana (bundled with ES) provides live dashboards that refresh as data arrives - achieving near-real-time visualization aligned with the 60-second buffer. Options B and D both select Amazon S3 as the endpoint; S3 is a storage destination that requires a separate query layer (like Athena) and has no native near-real-time dashboard capability. Option C (Redshift) involves batch loading and SQL querying, which adds latency unsuitable for near-real-time requirements.

No community discussion yet for this question.