Free CIS-DF Exam Flashcards

Completeness (attributes filled), Compliance (passes Desired State audit), and Correctness (no duplicates, orphans, or staleness). These three Cs combine into an overall CMDB Health Score.

Compliance, not Completeness. Completeness only checks whether fields are filled in; Compliance checks whether the CI actually matches its configured standard.

60 days with no update, by default. A CI untouched beyond that window is flagged stale and drags down the Correctness score.

Required attributes are defined in the System Dictionary; recommended attributes are flagged inside CI Class Manager. Both feed the Completeness KPI.

An orphan CI has no configured relationship rules linking it to anything; a duplicate CI matches an existing identification rule against another record. One is a missing-link problem, the other is a matching problem.

Because orphan relationship rules ship unconfigured out of the box and must be manually configured - Discovery alone will not create relationships without them.

It changes only the CI's status field. The record stays in the active cmdb_ci table and the action is reversible.

Archive moves the record to a read-only archive state, out of active tables but still recoverable. Delete permanently removes the record with no recovery.

Attestation - the CI owner verifies the action before it is applied, preventing accidental loss of records still in use.

CMDB Data Manager, which runs retire, archive, delete, and attestation actions through scheduled policies.

lifecycle_stage. It records the CI's governance lifecycle position for CSDM-aligned reporting.

Serial number, because it is a stable identifier that does not change. Matching on a volatile attribute produces unreliable duplicate detection.

Merge them (or delete the redundant record), consolidating relationships and history onto a single surviving CI.

Completeness = fields are filled in. Compliance = the CI matches its configuration standard. Correctness = free of duplicates, orphans, and staleness. Confusing 'filled in' with 'correct' is a common exam trap.

A technically complete CMDB is worthless if it is not trustworthy - Governance ties together the Health KPIs and lifecycle controls that keep the data reliable for every other domain (Insight, Ingestion, and beyond).

Stale, since 90 days exceeds the default 60-day staleness threshold used in the Correctness KPI.

Sustained CMDB trustworthiness - ensuring downstream consumers such as ITSM, Discovery, and reporting can rely on the data without re-verifying it themselves.

False. Delete permanently removes the record; only Retire (status change) and Archive (read-only relocation) preserve the underlying data.

Build multi-class, relationship-aware queries that traverse CI relationships across classes, not just filter a single table.

Dependency Views (top-down dependency visualization) and Service Mapping (application-to-infrastructure discovery), consolidated into a single map.

Application-to-infrastructure dependencies - the actual runtime connections between a business app and the servers or services it relies on.

Accurate CI relationships. Impact Analysis walks the relationship graph to surface everything else that would be affected by changing or removing a CI.

Top-down, starting from a business service and drilling into its underlying dependencies.

Because the map rolls up health and relationship data from underlying CIs - if those CIs are incomplete, non-compliant, or incorrect, the rollup reporting is unreliable too.

Relationship direction (the parent-child traversal path) - queries and maps follow these directional links to build their picture.

Unified Map, since it merges Dependency Views and Service Mapping into a single consolidated view.

Insight is built entirely on top of CMDB data - broken relationships, stale records, or duplicate CIs propagate directly into inaccurate maps and impact analyses.

Dependency Views visualize already-known relationships top-down; Service Mapping actively discovers new application-to-infrastructure dependencies.

Identification runs first (match the payload to an existing CI or create a new one), then Reconciliation runs second (decide which data source is allowed to write). Reversing this order is a common exam trap.

Whether an incoming payload matches an existing CI (triggering an update) or requires creating a brand-new CI record.

Data source precedence - which authoritative source is allowed to write to a given class or attribute when multiple sources send conflicting data.

It raises an error instead of merging or guessing. Ambiguous matches always require manual resolution, never an automatic merge.

Service Graph Connector - a prebuilt, IRE-aware integration that is preferred over building a custom Import Set.

Higher ongoing maintenance: custom transform maps must be built and kept in sync manually, versus a connector's prebuilt, certified mappings.

Discovery automatically finds and populates infrastructure CIs such as servers and network devices. The IRE governs how any incoming CI data - from Discovery or any other source - is identified and reconciled.

Field-level source history - which data source last wrote each individual attribute, enabling reversion to a prior source's value.

Multisource CMDB's field-level tracking, which retains prior source values instead of permanently overwriting them.

It updates only the fields included in that payload; any fields not sent are left untouched, not cleared or overwritten.

CI Class Manager - ServiceNow's graphical interface for configuring the CMDB class schema.

cmdb_ci. Table inheritance means new classes should extend cmdb_ci (or an existing subclass) rather than being built as unrelated tables.

Extend an existing class where possible. Creating unrelated new classes breaks the inheritance hierarchy and duplicates functionality already available through it.

An identifier entry that needs a parent identifier to already match before it can be evaluated - it cannot stand alone.

Serial number is a stable identifier that does not change; IP address is volatile and can be reassigned, causing false non-matches or false matches over time.

The order in which candidate attributes are tried to match or create a CI - higher-priority entries are evaluated before lower-priority ones.

Contains / Contained by (containment), Runs on / Runs (hosting), and Depends on / Used by (dependency).

Foundation, Design, Build, Manage Technical Services, and Sell/Consume - remembered as 'Foundation, Design, Build, Manage, then Sell or Consume.'

A Business Application is the owned software product, a design-time entity. An Application Service is the operational, running instance of that product, a runtime entity.

A Business Service is the customer-facing capability itself, typically one per service. A Service Offering is a sellable variant or tier of that service, and there can be many offerings per service.

Foundational data shared across the whole model - locations, users, and groups - the base entities that everything else in CSDM references.

So every part of the platform - CMDB, service catalog, ITSM, and reporting - shares one consistent language for services, avoiding conflicting definitions of the same business capability.