Informatica MDM SaaS Foundation flashcards
Informatica MDM SaaS Foundation · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- IDMC
- Informatica Intelligent Data Management Cloud, the cloud platform hosting MDM SaaS; MDM & 360 applications are provisioned and administered as services within it.
- Customer 360
- A 360 application that masters customer/party data across sources, producing a consolidated, deduplicated customer view for CRM, marketing, and service consumers.
- Product 360
- A 360 application that masters product data such as SKUs, attributes, and classifications, delivering a governed single product record to commerce and ERP systems.
- Supplier 360
- A 360 application that consolidates supplier and vendor records, including identifiers and relationships, into a governed master usable by procurement and risk processes.
- Reference 360
- The reference data management application that stores code sets, hierarchies, and crosswalks with versioning, and can publish reference values to other 360 applications.
- Business 360
- A configurable 360 application where you define a custom business entity and its model, rather than using a prebuilt entity like Customer or Product.
- Business entity
- The core modeling object of a 360 app; it defines the logical model, fields, relationships, and the pipelines that cleanse, match, and consolidate its records.
- Logical model
- The design-time definition of a business entity's fields, types, and relationships; it is mapped to a physical model that stores the actual master data.
- Physical model
- The persisted representation of a business entity's logical model in the SaaS data store; it holds staging and mastered records for the entity.
- Match rule
- A rule specifying match columns, match types (exact, fuzzy, mixed), and thresholds used to decide whether two source records refer to the same real-world entity.
- Match review
- A workflow step where ambiguous or low-confidence match clusters are presented to a data steward for manual confirmation or rejection before consolidation.
- Survivorship rule
- A rule that selects which source value wins for each master field, using trust scores, recency, or source priority when multiple records are consolidated.
- Trust score
- A per-source, per-field weighting that expresses confidence in a source's data quality; survivorship uses it to decide the winning value.
- Validation rule
- A rule that checks field values against required formats, domains, or reference values during the cleanse stage, flagging or rejecting nonconforming records.
- Cleanse stage
- The pipeline step invoking Cloud Data Quality services to standardize, parse, and validate ingested records before matching and consolidation.
- Consolidation
- The pipeline stage that merges a matched cluster into one best-version master record by applying survivorship rules field by field.
- Best version
- The consolidated master record produced for a matched cluster; it represents the governed, published view of that entity for consumers.
- Crosswalk
- A mapping between equivalent codes in different code sets or systems, maintained in Reference 360 so consumers can translate values across standards.
- Hierarchy
- A parent-child structure among reference values or entity records, such as a product category tree or account rollup, modeled and versioned in the application.
- Relationship type
- A modeled association between entity instances, such as parent-child or supplier-to-product, that can carry its own attributes and is managed with the entity.
- Data steward
- The business user who reviews match clusters, resolves data issues, and approves changes through the 360 application's review workflows.
- Source system
- An upstream system registered to feed records into a business entity; its records are ingested, cleansed, and matched against existing masters.
- Ingest stage
- The first pipeline step that loads source records into the entity's staging area and applies initial structural validation before cleansing.
- Fuzzy match
- A match type that scores similarity between values (e.g., name variants) rather than requiring exact equality, enabling identification of near-duplicate records.
- Exact match
- A match type requiring identical values on the configured match columns; commonly applied to strong identifiers such as tax ID or email.
- Match threshold
- The score boundary in a match rule that determines whether a pair is auto-matched, sent to review, or treated as a non-match.
- Cloud Data Quality
- The IDMC service providing parsing, standardization, and validation capabilities that MDM pipelines invoke during the cleanse stage.
- Published record
- The consolidated master record exposed to downstream consumers through views or APIs, as opposed to raw staging records used internally.
- 360 application UI
- The end-user interface of a 360 app where stewards search, view, edit, and review master records and their relationships.
- Entity field
- An attribute defined on a business entity's logical model, with a data type and optional validation, that becomes a column in the physical model.
- Code set
- A managed list of allowed reference values, such as country or industry codes, stored in Reference 360 and reused by other applications.
- Reference data
- Shared, slowly changing lookup values and hierarchies used to classify and validate master data, governed centrally rather than per application.