A city event bus keeps ordered records in distributed logs that apps publish to and subscribe from by topic. Which technology pattern matches that design?
Select an answer to reveal the explanation.
Short Explanation
Kafka-style buses are like a city-wide flight recorder: messages land in a durable, distributed log by topic. Lots of systems can publish or subscribe without tying themselves in knots.
Full Explanation
A city event bus that keeps ordered records in distributed logs that apps publish to and subscribe from by topic matches an Apache Kafka-style architecture: a distributed publish/subscribe log organized by topics. That pattern is the syllabus answer for durable, replayable municipal event streaming. A single desktop folder with no replication or consumer model is not a distributed log. Only nightly FTP drops with no streaming log abstraction lack the continuous pub/sub properties described. A voice mail system that cannot retain or replay digital events is an analogy without the technical log semantics. Exam caveat: Kafka-style systems provide retention and order within partitions—not magical global order across every city topic without design. Operational check: publish sample events to a topic, consume with two independent groups, and demonstrate replay from an earlier offset within retention. In production terms for Kafka-style distributed topic logs, assign an owning team, wire a dashboard that shows the pattern is healthy under peak civic load, and require a staging drill that rehearses failure and recovery before resident impact. Revisit the choice when traffic shape, retention, or integrity needs change, and keep a named rollback owner on the change record. Re-test both the happy path and the failure path for Kafka-style distributed topic logs after material dependency upgrades so regressions are caught before the next public release.