Pass the ServiceNow CIS-Data Foundations (CMDB and CSDM) CIS-DF Questions and answers with CertsForce

Removing obsolete or inactive CIs from the CMDB must be handled carefully to avoid data loss, audit issues, and unintended operational impact. In ServiceNow, the recommended and governed approach is to use an archive policy.

Archive policies are designed to manage CI lifecycle cleanup based on defined conditions such as class, last updated date, lifecycle status, or operational state. In this scenario, the condition would target Linux Server CIs that have not been updated in six months. Archive policies can either archive or permanently delete records in a controlled, auditable manner, ensuring compliance with data retention and governance standards.

Creating a business rule (Option A) is strongly discouraged for bulk CMDB cleanup because it introduces technical debt, upgrade risk, and unpredictable side effects. A scheduled job (Option C) may automate execution but lacks governance logic and lifecycle awareness on its own.

Archive policies integrate with CMDB Data Manager, provide visibility into actions taken, and support approval and rollback where appropriate. This aligns fully with Data Foundations best practices for maintaining a lean, accurate, and trusted CMDB.

Therefore, the correct and recommended action is B – Create an archive policy.

In the CSDM lifecycle model, the Life Cycle Stage represents the broad phase of a CI or asset, while the Life Cycle Stage Status supplies a more precise condition within that phase. When a hardware-backed server reaches End of Life, valid disposition-oriented statuses include Disposed and Donated . These values indicate how the organization concluded responsibility for the physical item after its operational use ended.

“Charity” is not a standard lifecycle status. A charitable transfer would be represented by the standardized status Donated , rather than by creating a separate nonstandard value. “Broken” describes a physical condition and is not the appropriate standardized End-of-Life disposition status in this question.

The Data Foundations material distinguishes Life Cycle Stage as the macro lifecycle phase and Life Cycle Stage Status as its more granular condition. It also identifies “Disposed” as a lifecycle-status value rather than a CMDB Data Manager policy type. ServiceNow likewise defines lifecycle state as the combination of an item’s stage and status.

=========

The CMDB Data Foundations Dashboard is designed to help administrators identify priority data issues and take structured remediation actions. When several metrics have low scores, the correct approach is not to randomly clean records or manipulate scoring rules. Instead, the administrator should prioritize the most important issues and use the recommended remediation guidance.

Option A is correct because Data Foundations emphasizes prioritizing metrics with Critical and High priority first. These metrics usually represent the most important issues affecting CMDB trust, operational readiness, service visibility, and downstream ITSM processes such as Incident, Change, and Problem Management. Focusing on the highest-priority metrics ensures remediation effort is aligned with business and operational risk.

Option C is also correct because the dashboard provides Remediation Playbooks linked to specific metrics. These playbooks give structured guidance for analyzing the issue, identifying impacted records, correcting the data, and improving governance so the problem does not return. This is the preferred Data Foundations approach because it supports repeatable, auditable, and best-practice remediation.

Option B is not recommended because changing exclusions simply to improve the score can hide poor data quality rather than fix it. Exclusion rules should only be used when records are legitimately out of scope. Option D may be valid in some lifecycle cleanup scenarios, but blindly removing non-operational or retired CIs is not the primary recommended action for improving dashboard health.

Delete and archive policies are designed for end-of-life CMDB lifecycle governance. They should apply to records that are no longer active operational CIs and have reached an appropriate retired state. End of Life - Retired is the correct lifecycle state because it indicates that the CI has completed its useful operational lifecycle and can be governed through archival or deletion according to retention rules. Applying delete or archive policies to Inventory - Available records would be dangerous because those CIs may still be valid and usable. “In any lifecycle state” is wrong because unrestricted archival or deletion can remove active, dependent, or operationally important records. “Missing - Stolen” is more aligned with asset disposition and exception handling, not the standard CMDB Data Manager delete/archive target state. Therefore, these policies should affect servers in End of Life - Retired.

=========

Automatic relationship creation is fundamental to maintaining a service-aware and trustworthy CMDB. In ServiceNow, this capability is primarily delivered by Discovery and Service Mapping.

Discovery (Option C) automatically identifies infrastructure components—such as servers, network devices, and storage—and creates technical relationships between them (for example, “runs on,” “connected to,” or “depends on”). These relationships form the backbone of infrastructure dependency mapping.

Service Mapping (Option B) builds on Discovery by creating application- and service-level relationships. It maps how application components interact across servers, databases, and middleware, resulting in accurate Application Service models aligned with CSDM. These relationships are created and maintained automatically as the environment changes.

Option A (IntegrationHub ETL) focuses on data ingestion and transformation; it does not inherently create or maintain relationships unless explicitly scripted. Option D (Workflow Studio) orchestrates processes and automations but does not discover or infer CI relationships.

Therefore, the ServiceNow solutions that create automatic relationships are Service Mapping and Discovery, making Options B and C correct.

Data Refresh Rules allow a lower-priority source to update an attribute when the higher-priority authoritative source has not refreshed that attribute within a configured period. This prevents CI data from remaining indefinitely outdated merely because the preferred source has stopped reporting.

Reconciliation rules establish the normal source priority and determine which authorized source wins when multiple sources report values for the same attributes. The guide confirms that source precedence is assigned through reconciliation rules. Data Refresh Rules supplement that precedence by defining a freshness exception: after the higher-priority source becomes inactive for the configured interval, a lower-priority source may supply a more current value.

Identification Rules determine whether an incoming payload matches an existing CI. Health Inclusion Rules control which CIs participate in CMDB Health calculations. Neither addresses temporary source inactivity or freshness-based update authorization.

=========

When transitioning to CSDM-aligned lifecycle management, ServiceNow introduces a structured lifecycle framework that separates high-level intent from detailed operational state.

Life Cycle Stage represents the macro phase of a CI’s existence (for example: Plan, Build, Deploy, Operate, Retire ).

Life Cycle Stage Status refines that phase with granular, sub-level states that vary by CI type.

Life Cycle Object determines which lifecycle stages and statuses apply, based on what kind of CI is being managed (hardware, application, document, etc.).

Life Cycle Mapping ensures a safe transition from legacy status fields by translating existing values into standardized CSDM lifecycle values—avoiding data loss or process disruption.

Together, these objects enable consistent lifecycle governance, improve reporting accuracy, and support automation across ITSM, ITOM, and IRM use cases—while remaining backward compatible with legacy CMDB data.

Identification Inclusion Rules restrict the population of existing CIs that the Identification and Reconciliation Engine considers when attempting to identify an incoming CI. They add qualifying conditions to the identification process so that IRE searches only the relevant subset of records instead of evaluating every CI in the class.

For example, an inclusion rule could constrain matching to CIs belonging to a particular company, environment, domain, or other defined population. After narrowing the candidate records, IRE applies the class’s identifier entries and identification criteria to decide whether an existing CI matches the incoming data. Identification rules determine whether an incoming record matches an existing CI or requires creation of a new record.

Option A describes reconciliation rules, which control source authority over attributes. Option B is incorrect because inclusion rules do not stop the source from submitting data.

The video displays “Health Inclusion Rules,” but that is a terminology error. Health Inclusion Rules control CMDB Health scope; Identification Inclusion Rules are used by IRE.

=========

In Data Foundations, “Configuration” includes modeling CI relationships in a way that reflects real-world technology dependencies and supports operational use cases such as impact analysis, troubleshooting, and service mapping. For “Application Servers host Applications,” the scenario describes that multiple Application Servers can host one or more Applications. In most enterprise environments, the reverse is also true: an Application can be hosted across multiple Application Servers (for example, horizontal scaling, clustered deployments, active-active architectures, and separate servers for different tiers or components of the same application).

Because both sides can have multiple related records, the correct logical relationship is many-to-many:

One Application Server → hosts many Applications

One Application → can be hosted on many Application Servers

In ServiceNow CMDB terms, many-to-many relationships are represented through the CMDB relationship model (parent/child relationships), enabling the platform to store multiple relationship records linking servers and applications without forcing an unnatural single-reference constraint. This supports better CMDB quality and stronger downstream outcomes—especially for incident triage (“what apps are affected if this server is down?”) and change impact analysis (“what servers could be impacted if we change this app component?”).

A one-to-many or many-to-one model would incorrectly restrict either the server to one application or the application to one server, which does not align with common hosting patterns and would reduce the CMDB’s usefulness and accuracy.

This question tests understanding of how the Identification and Reconciliation Engine (IRE) evaluates incoming CI data against Identification Rules and their priority order in ServiceNow.

From the identification rule shown:

Serial number (+ type) → Priority 100

Serial number → Priority 200

Name (Hardware) → Priority 300

MAC address + name (Network Adapter) → Priority 400

For a CI to be identified and matched, the incoming record must satisfy one complete identifier entry exactly as defined for that class.

CI1 (Name match only)

Although the name matches an existing Hardware CI, name alone is a low-priority identifier (300) and is not sufficient to uniquely identify a Hardware CI unless no higher-priority identifiers exist and the identifier entry criteria are fully satisfied. In practice, Hardware identification relies on serial number–based identifiers, not name-only matching, to avoid false positives. Therefore, CI1 cannot be confidently matched and is inserted as a new record.

CI2 (IP address match)

IP address is not part of any Hardware identification rule shown. IP address is typically used for discovery correlation or network relationships, not as a primary Hardware identifier. Since no identifier entry includes IP address, CI2 does not match any valid identification rule and is also inserted as a new record.

Because neither CI satisfies a valid identifier entry, both records are inserted as new CIs.