Question 15
Domain 1: Agent Architecture, Design, and DevelopmentMultiple specialized agents in your distributed system must coordinate asynchronously without tight coupling. Communication patterns must survive agent restarts, scale to bursty traffic, and let agents come online or go offline independently. Select TWO communication patterns that satisfy these constraints.
Correct answer: BC
Explanation
A publish/subscribe topic model fits because agents can "subscribe to event types they care about" and do not need direct knowledge of the publishers, which supports loose coupling and independent startup or shutdown. It also handles asynchronous coordination and bursty traffic by decoupling senders from receivers through the topic, so agents can restart without requiring direct point-to-point connections.
Why each option is right or wrong
A. A shared in-memory dictionary held by a single coordinator process that all agents read from and write to via direct method calls.
B. A publish/subscribe topic model where agents subscribe to event types they care about and don't need direct knowledge of which other agents emit those events.
Publish/subscribe is the fit under the usual messaging architecture rules because the brokered topic removes any point-to-point dependency: the publisher only emits to a named topic, while subscribers are bound by event type, not by agent identity. That satisfies asynchronous coordination and independent lifecycle management, and in systems such as JMS/Kafka-style topic messaging the broker can buffer bursts and let consumers restart or reconnect without the sender needing a live direct session.
C. A durable message queue or event bus (e.g., RabbitMQ, NATS, Kafka) where producers and consumers are decoupled and messages persist until acknowledged.
D. Synchronous HTTP request/response calls between every pair of agents that share data, with retry-on-failure logic at the application layer.
E. Polling each agent's REST endpoint on a fixed interval to detect new state changes and propagating them through the orchestrator.