MDM & 360 Applications
MDM & 360 Applications
This domain tests how Informatica MDM SaaS creates governed master data in IDMC and how the Business 360 applications deliver it to stewards and downstream systems. Questions focus on Business 360 app types, the business entity model, match/merge, trust and survivorship, hierarchies, security, and publication.
Core rules
- MDM SaaS is provisioned through IDMC Cloud Provisioning. A Business 360 application such as Customer 360, Product 360, Supplier 360, or Reference 360 provides the model, configuration console, and stewardship UI.
- A business entity is the master-data object, for example Customer. Fields, lookups, relationships, and hierarchy definitions make up its model. Source records are held as cross-references linked to the consolidated record.
- Match rules find duplicate candidates. Merge creates or updates the consolidated record. Trust scores rank sources; survivorship rules choose the winning value for each field.
- Stewards use the 360 application UI; administrators configure the model in Business 360 Console. Role and record-level permissions control view, edit, merge, and publish actions.
- Publication sends mastered data to target systems. REST APIs and Data as a Service provide programmatic access.
Worked example
A CRM record and an ERP record share a customer name and tax ID. The match rule identifies them as a candidate pair; the steward reviews and merges them. CRM has higher trust for email, ERP for legal name. Survivorship puts the CRM email and ERP legal name on the consolidated record, while both cross-references remain linked. A publication job sends the mastered customer to Salesforce.
Traps
- Treating match and merge as one step; matching only proposes candidates.
- Assuming a high trust score alone merges records; survivorship applies per field after merge.
- Forgetting that cross-references are preserved for lineage and source lookup.
- Confusing the 360 application UI with the Business 360 Console configuration area.
- Thinking publication is required before data can be queried through APIs.