City asset inventory consumers need timely notice when an asset record changes, not only a nightly warehouse refresh. Which movement pattern fits?
Select an answer to reveal the explanation.
Short Explanation
If the hydrant map changes at noon, waiting for tonight’s batch is like reading yesterday’s weather for today’s storm. Event-driven movement tells consumers when something changed so freshness matches the job.
Full Explanation
Event-driven data movement publishes changes so downstream systems can react when latency needs exceed what nightly ETL provides. Asset inventory and similar operationally relevant datasets often require timely propagation. Architecture selects event patterns when consumer freshness SLAs demand change notification rather than only scheduled bulk loads.