A service desk needs to recognize returning residents during the call, but party matching only runs in a weekly batch. What architectural concern does this raise?
Select an answer to reveal the explanation.
Short Explanation
If the match job only wakes up on Sundays, Monday's caller still looks like a stranger. Real-time desks need match latency that fits the conversation, not the batch calendar. Architecture follows the clock the business actually uses.
Full Explanation
Operational MDM consumers impose latency requirements on matching, retrieval, and synchronization. A weekly batch may suit overnight analytics cleansing but fail when agents must resolve identity during a live interaction. Designers must align match/sync patterns—near-real-time services, incremental updates, or hybrid approaches—with those timing needs rather than assuming batch cadence is universally adequate.