MDM Hub Configuration and Management 4 — Questions and Answers
Question 1: Which MDM Hub batch job must be run before the Match job to ensure source data is available in the staging tables?
- Tokenize job
- Stage job (Correct answer)
- Load job
- Recalculate BVT job
Correct answer: Stage job
The Stage job moves and cleanses data from landing tables into staging tables, making it available for subsequent Match and Load jobs.
Question 2: In MDM Hub, what is the primary function of the 'Tokenize' batch job?
- To generate match tokens (standardized keys) from staging records used in the match process (Correct answer)
- To encrypt sensitive fields in the base object before storage
- To assign unique row IDs to incoming landing records
- To purge expired cross-reference records from the Hub Store
Correct answer: To generate match tokens (standardized keys) from staging records used in the match process
The Tokenize job creates standardized match tokens from staging data so the Match job can efficiently compare records using indexed key lookups.
Question 3: Which component in Informatica MDM Hub manages the execution of cleanse functions applied to staging data?
- Hub Server
- Process Server (Cleanse Match Server) (Correct answer)
- Message Queue Server
- Repository Server
Correct answer: Process Server (Cleanse Match Server)
The Process Server, also called the Cleanse Match Server, executes cleanse functions and match operations, offloading intensive processing from the Hub Server.
Question 4: What is the purpose of configuring a 'Cleanse Function' in MDM Hub Schema Manager?
- To standardize and normalize incoming data values before they are matched or loaded into the base object (Correct answer)
- To remove duplicate records from the landing table before staging
- To validate that source records meet minimum trust score requirements
- To archive base object records that have not been updated in over a year
Correct answer: To standardize and normalize incoming data values before they are matched or loaded into the base object
Cleanse functions transform raw source values—such as standardizing phone formats or uppercasing names—to improve data quality and match accuracy.
Question 5: In MDM Hub's Security Access Manager (SAM), what is a 'resource group'?
- A logical collection of Hub resources (base objects, packages, etc.) to which roles are granted access (Correct answer)
- A set of servers grouped for load-balancing purposes
- A cluster of batch jobs that run together as a unit
- A named collection of source systems sharing the same trust configuration
Correct answer: A logical collection of Hub resources (base objects, packages, etc.) to which roles are granted access
Resource groups bundle Hub objects so that a single role assignment grants or restricts access to multiple related resources simultaneously.
Question 6: When configuring the MDM Hub Server's cmxserver.properties file, what does the 'cmx.server.datalayer.cleanse.plugindir' property specify?
- The file system path where custom cleanse library JARs are deployed (Correct answer)
- The database schema where cleanse functions are stored
- The URL of the external cleanse web service endpoint
- The maximum number of concurrent cleanse threads
Correct answer: The file system path where custom cleanse library JARs are deployed
This property points to the directory containing custom cleanse plug-in JARs so the Process Server can load and execute them during staging.
Question 7: Which MDM Hub batch job recalculates the Best Version of Truth (BVT) for golden records after source data or trust configurations change?
- Recalculate BVT job (Correct answer)
- Revalidate job
- Promote job
- Refresh Lookup job
Correct answer: Recalculate BVT job
The Recalculate BVT job reapplies trust rules across all cross-reference records to update golden record field values after configuration or data changes.
MDM Hub Configuration and Management 4
Which MDM Hub batch job must be run before the Match job to ensure source data is available in the staging tables?