Several city technology partners already operate Kafka clients and require Kafka-compatible tooling for an event pipeline into municipal systems. Which AWS service best provides a managed Kafka-compatible streaming option?
Select an answer to reveal the explanation.
Short Explanation
If partners already speak Kafka, don’t invent a dialect. Amazon MSK gives you managed Kafka-compatible streaming so their tools keep working. Redis-as-a-bus, Transfer Acceleration, and Synthetics canaries aren’t Kafka platforms.
Full Explanation
Amazon Managed Streaming for Apache Kafka (Amazon MSK) is the AWS managed service that provides Kafka-compatible brokers so city technology partners who already operate Kafka clients can keep their producers, consumers, and ecosystem tooling while AWS manages the control plane. That compatibility is the decisive requirement in this municipal event-pipeline scenario. Amazon ElastiCache for Redis used only as a public anonymous message bus is not Kafka-compatible, should not be exposed anonymously, and solves caching/session patterns rather than partner Kafka pipelines. Amazon S3 Transfer Acceleration speeds object uploads to S3 via edge locations; it is not a Kafka broker substitute and cannot speak the Kafka protocol. Amazon CloudWatch Synthetics canaries publishing heartbeats monitor endpoints; heartbeats are not an event backbone for partner event streaming. Exam caveat: MSK still requires sizing brokers/storage, planning networking (VPC, security groups), and choosing provisioning versus serverless options carefully for cost and ops. Operational check: connect an existing partner Kafka client to a pilot MSK cluster/topic, verify produce/consume under expected auth, monitor broker metrics and consumer lag, and only then migrate municipal event topics off any DIY brokers.