A regional 911 analytics team needs a managed wide-column store that speaks Cassandra Query Language (CQL) for existing telemetry tables. Which AWS service matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
If the team already writes CQL against Cassandra-style wide tables, Keyspaces is the managed AWS desk that speaks that dialect—not Aurora pretending to be Cassandra or DocumentDB speaking Mongo.
Full Explanation
A regional 911 analytics team that already stores telemetry in Cassandra-style wide-column tables and writes Cassandra Query Language (CQL) needs an AWS service that speaks that dialect, not a lookalike forced into another API. Amazon Keyspaces (for Apache Cassandra) is the managed, Cassandra-compatible service designed for CQL workloads: teams can migrate or re-point compatible clients toward Keyspaces while retaining wide-column modeling for high-volume civic telemetry. That alignment preserves schema investment and operational familiarity for emergency-analytics pipelines that cannot pause for a full re-architecture mid-incident season.
Amazon Aurora PostgreSQL with only JSONB columns may store flexible payloads, but JSONB does not make Aurora into Cassandra: CQL clients, partitioner semantics, and wide-column access patterns are not the same as relational SQL plus JSON documents. Amazon DocumentDB targets MongoDB-compatible document APIs; MongoDB drivers do not replace CQL clients, so DocumentDB fails the stated CQL requirement. Amazon Neptune with Gremlin addresses graph relationships; ignoring an existing CQL schema to force graph traversal tools onto wide-column telemetry is a mismatch of both model and query language.
Exam caveat: Keyspaces compatibility covers Cassandra APIs and CQL for many workloads, but feature parity with every self-managed Cassandra capability is not absolute—validate throughput modes, consistency options, and application assumptions. Do not pick Keyspaces merely because data is “big”; pick it when Cassandra/CQL compatibility is the requirement.
Operational check: reconnect a non-production 911 telemetry producer/consumer using CQL against Keyspaces, compare read/write behavior and partition key designs to on-prem Cassandra, enable appropriate on-demand or provisioned capacity for incident spikes, and confirm IAM and VPC endpoint patterns meet the emergency operations network controls.