An enterprise wants to ensure that data stewards are automatically notified when duplicate CIs are detected by the Identification and Reconciliation Engine (IRE). How can this governance requirement be streamlined?
CMDB Duplicate Remediation rules generate tasks automatically when IRE detects duplicate CIs, assigning them to the relevant data stewards. This satisfies the governance requirement for automatic notification without manual monitoring, since the rules run as part of the duplicate remediation workflow.
Why this answer
Configuring CMDB Duplicate Remediation rules allows the system to automatically detect duplicate CIs and notify data stewards based on predefined conditions. These rules can trigger notifications, assign tasks, or even merge duplicates, streamlining governance. This approach leverages out-of-the-box functionality rather than custom scripting, ensuring maintainability and scalability.
Exam trap
CIS-DF often tests the misconception that custom scripts or direct modifications are needed for governance, but the correct answer is to use built-in CMDB Duplicate Remediation rules.
How to eliminate wrong answers
Option A is wrong because a scheduled data import transform map script is for data loading, not for duplicate detection and notification. Option B is wrong because modifying the Identification Engine processor script directly is risky, unsupported, and not a streamlined governance approach; it could break IRE functionality. Option D is wrong because writing a custom Business Rule on the sys_object_source table is a custom solution that may not be triggered by IRE duplicate detection and is not the recommended streamlined method.