A healthcare insurer runs claims, membership, and provider network teams that each generate large datasets. Leadership wants each team to control its own data, while other teams can find and consume those datasets across the company. Which operating model fits this goal best?
Show answer and explanation
Answer: B
Data mesh organizes data around business domains. Each domain team owns its datasets as products that meet quality and documentation standards, while a shared self-serve platform and federated governance let other teams discover and consume them. That combination gives the claims, membership and provider groups control over their data without isolating it. A central group approving every table recreates the bottleneck the insurer wants to avoid, and nightly consolidation into an IT-owned schema centralizes ownership again. Manual joins of separate marts provide no owned products or governed sharing.
Why the other options are wrong
- A. A central group approving every table is the centralized model that domain ownership is meant to replace. It would slow the claims and membership teams instead of giving them control of their data.
- C. Consolidating everything into an IT-owned canonical schema moves ownership back to one central team. The domains would lose control of the data they generate, which the insurer specifically wants to keep.
- D. Separate regional marts joined manually by analysts provide no owned, discoverable data products and no governed sharing. Cross-team use would stay ad hoc and inconsistent.