Multiple municipal systems need read access to a trusted golden customer record, while local updates are reconciled centrally before republishing. Which architecture pattern best fits this requirement at a conceptual level?
Select an answer to reveal the explanation.
Short Explanation
Picture a city hall switchboard that keeps the official resident card and tells every desk what changed. That central switchboard is the MDM hub idea. Systems read the golden record; conflicts get sorted in the middle, not in a tangle of one-off syncs.
Full Explanation
Hub-style MDM consolidates or governs a mastered record in a central store that consuming applications read (and often write through or against). Local updates are reconciled against hub rules before republishing, which matches the need for a golden customer view with controlled synchronization. Spreadsheet shares, analytics-only lakes, and unmanaged pairwise meshes do not provide that governed central golden record pattern.