CIS-DF Exam Dumps : Certified Implementation Specialist - Data Foundations (CMDB and CSDM)

Custom CMDB class tables should begin with u_cmdb_ci . The u_ portion identifies a customer-created table, while cmdb_ci preserves the standard CMDB naming convention and clearly indicates that the table extends the Configuration Item hierarchy.

For example, appropriate custom class names may resemble u_cmdb_ci_custom_router or u_cmdb_ci_special_switch. The uploaded guide uses these exact naming patterns when discussing custom-class consolidation and the technical debt created by unnecessary custom classes.

Using only cmdb_ci would incorrectly suggest an out-of-box ServiceNow table. Prefixes such as u_ci_cmdb and ci_cmdb do not follow the standard hierarchy convention. Before creating any custom class, the administrator should still verify that a suitable supported class is not already available through the CMDB CI Class Models application.

=========

The Correctness scorecard evaluates whether CI data accurately represents the real environment. It includes the Duplicate , Orphan , and Staleness metrics.

Duplicate identifies cases where the same real-world configuration item is represented by multiple CMDB records. Orphan identifies CIs that lack expected relationships or supporting context. Staleness identifies records that have not been updated within the configured period and may no longer represent active infrastructure.

The other choices belong to different CMDB Health KPIs. Audit belongs to Compliance because it evaluates whether CI values satisfy defined standards or desired-state conditions. Required and Recommended belong to Completeness because they measure whether mandatory and useful attributes are populated.

Therefore, Duplicate, Orphan, and Staleness are the metrics shown under Correctness.

=========

This question tests understanding of reconciliation source priority in the Identification and Reconciliation Engine (IRE) in ServiceNow.

In reconciliation rules, lower numeric values represent higher priority. Therefore, the priority order is:

ServiceNow (100) – highest authority

Altiris (200)

SCCM (300) – lowest authority

Why A is correct

Because Altiris (200) has higher priority than SCCM (300), data from Altiris can update records originally inserted by SCCM. This is exactly how reconciliation precedence works—higher-priority sources can overwrite lower-priority ones.

Why C is correct

SCCM, even though it has the lowest priority, is still an authorized discovery source. It can insert new records into the Windows Server table when no existing CI is identified. Priority only affects updates, not the ability to create records.

Why B is incorrect

ServiceNow (priority 100) can update records from Altiris and SCCM because it has the highest priority. The statement incorrectly claims it cannot.

Why D is incorrect

SCCM does not have the highest authority. A higher numeric value means lower priority, so SCCM cannot update records created by higher-priority sources.