ServiceNow CIS-DF Certified Implementation Specialist Data Foundations — Sister Set

Discovery detected connection and process dependency evidence and created the relationship automatically — Discovery can create relationships from observed processes, listening ports, and network connections between components.

The relationship was created only because the database class was marked Principal — Principal designation does not create relationships.

CMDB Health generated the relationship after detecting a missing dependency — Health can flag relationship quality issues but does not invent dependencies.

A reconciliation rule converted matching attributes into a dependency relationship — Reconciliation governs attribute updates, not relationship creation from runtime evidence.

Service Graph Connector for supported cloud resources — A maintained connector provides supported mappings and an established IRE-aware ingestion path, reducing the custom code and maintenance burden of a bespoke integration.

MID Server-backed Discovery for reachable on-premises servers — A MID Server runs Discovery and JDBC activities inside the restricted network and communicates outbound to the instance, avoiding direct inbound access to protected systems.

Scheduled import set and transform map for the quarterly facilities CSV — Import sets and transform maps provide a repeatable staging and field-mapping process for batch files, with IRE-aware handling added when the target data is a CI.

Manual list edits for all three sources — Manual list editing does not provide repeatable, source-appropriate, IRE-aware ingestion for cloud, on-premises, and batch data.

Principal class settings as the ingestion engine — Principal-class configuration curates CI classes emphasized in task CI lookups. It does not control identification, reconciliation, lifecycle processing, relationships, or data quality.

Reporting tools cannot compensate for inconsistent service definitions and relationships underneath — Reliable reports require consistent CSDM concepts and relationship patterns in the underlying data.

CSDM prevents dashboards from reading service records — CSDM is intended to improve service reporting; it does not block dashboard access to service records.

Business services must be discovered by SNMP before reports work — Business services are modeled and governed business objects, not records that must be discovered through SNMP.

Principal classes must be disabled for every service record — Principal-class configuration is unrelated to whether service definitions are consistent enough for reporting.

The required sequence is Source rows land in an import set staging table, then Transform logic invokes CMDBTransformUtil or an equivalent IRE-aware CMDB path, then IRE applies identification logic to determine whether each CI is new or existing, and finally Reconciliation rules determine whether source values may update governed attributes.

Staging must occur before transform processing, identification must resolve the CI before updates are considered, and reconciliation then applies source authority. Invoking the transform before data is staged or applying reconciliation before identification breaks that dependency chain.

Orphan rule — An orphan or relationship-correctness rule identifies a CI that lacks an expected relationship, such as a disk not linked to a host.

Reconciliation rule — Reconciliation decides source authority for attributes and does not assess missing host relationships.

Principal class rule — Principal configuration affects CI pickers, not relationship health.

Identification rule — Identification rules match incoming CIs and do not determine whether a disk has a required host relationship.