A utility company is architecting a smart grid telemetry system on AWS. The system must ingest high-frequency, key-value power consumption readings from millions of smart meters globally with single-digit millisecond latency. Separately, the business intelligence team needs to perform complex, multi-year analytical queries on this historical data to forecast regional energy demand. To achieve a loosely coupled architecture, the company wants to select the appropriate database services.
Which combination of AWS database services should the company choose to meet these requirements? (Select TWO.)
- Amazon DynamoDB to ingest and store the high-frequency key-value telemetry dataAnswer
- Amazon Redshift to act as a data warehouse for complex analytical queries on historical dataAnswer
- CAmazon Aurora to consolidate all workloads, handling both the high-frequency writes and the multi-year analytical queries within a single database cluster
- DAmazon DynamoDB to store the historical archive and run complex SQL join queries across multiple dimensions
- EA database hosted on Amazon EC2 to automatically transfer database operating system patching and scaling responsibilities to AWS
Answer
The correct database combination consists of Amazon DynamoDB for telemetry ingestion and Amazon Redshift for multi-year data warehousing and analytical queries.
The correct response involves choosing the option describing Amazon DynamoDB to ingest and store the high-frequency key-value telemetry data, alongside the option describing Amazon Redshift to act as a data warehouse for complex analytical queries. Amazon DynamoDB is a NoSQL service built for low-latency, high-volume key-value ingestion, which aligns with the smart meter write requirements. Amazon Redshift is an OLAP (Online Analytical Processing) data warehouse optimized for complex queries across massive historical datasets. Together, they create a specialized, decoupled architecture.
Step-by-Step Solution
Key Concept
Selecting specialized, decoupled database services based on transactional versus analytical requirements