A transit disruptions agent must notify both a rider-notification agent and an ops-dashboard agent when delays occur. Which communication style best fits that citywide event fan-out?
Select an answer to reveal the explanation.
Short Explanation
Delay news is a city loudspeaker moment—many listeners at once. Pub/sub lets rider alerts and ops dashboards subscribe to the same event instead of playing telephone one whisper at a time.
Full Explanation
Citywide delay fan-out from a transit disruptions agent to both rider-notification and ops-dashboard agents fits a pub/sub-style event broadcast: one delay event, many subscriber agents. That communication style decouples producers from the growing set of municipal consumers and keeps each subscriber’s handling independent.
A single point-to-point chat that can only whisper to one peer forever fails because fan-out to multiple city consumers cannot scale through a permanent one-to-one whisper. Manual copy-paste by dispatchers fails by concept: it is human glue, not an agent communication architecture, and it breaks under delay volume. Storing delay text only in a local file others cannot subscribe to fails because there is no event distribution path for subscriber agents.
Exam caveat: choose pub/sub when the stem stresses one event to many independent consumers. Point-to-point request/reply remains appropriate for single pairwise handoffs with required responses.
Operational check: publish a test delay event; confirm both notification and dashboard agents receive the same event ID; add a third subscriber and verify it receives subsequent events without changing the disruptions producer.