You notice that a specific data source (e.g., SCCM) is overwriting critical configuration attributes that are manually maintained by your infrastructure team. How should you prevent this data source from updating those specific attributes?
Trap 1: Create a Business Rule on the cmdb_ci table to check the updated-by…
Custom Business Rules on cmdb tables impact performance and bypass native IRE reconciliation features.
Trap 2: Modify the Identification Rule to exclude the manual attributes.
Identification rules dictate how records are matched, not which attributes are allowed to be updated once matched.
Trap 3: Disable the data source integration entirely.
Disabling the integration loses all other valuable telemetry gathered by the data source.
- A
Create a Business Rule on the cmdb_ci table to check the updated-by user.
Why wrong: Custom Business Rules on cmdb tables impact performance and bypass native IRE reconciliation features.
- B
Modify the Identification Rule to exclude the manual attributes.
Why wrong: Identification rules dictate how records are matched, not which attributes are allowed to be updated once matched.
- C
Configure Reconciliation Definitions with attribute-level precedence rules.
Reconciliation definitions specify which discovery sources have authority to update designated attributes.
- D
Disable the data source integration entirely.
Why wrong: Disabling the integration loses all other valuable telemetry gathered by the data source.