Free Practice Questions for ServiceNow CIS-DF Exam

In ServiceNow, Service Graph Connectors deliver data ingestion patterns using protected, upgrade-safe artifacts, including script transforms. When a customer customizes a script transform provided by a Service Graph Connector, ServiceNow follows standard update set and upgrade behavior to protect customer customizations.

During a subsequent upgrade, if the out-of-box (default) script transform definition changes, ServiceNow does not overwrite the customized version. Instead, the platform records a skipped change, indicating that an update was available but intentionally not applied due to a local customization. This ensures customer-specific logic is preserved while still maintaining transparency about what changed in the newer release.

Option A is incorrect because upgrades do not halt due to customized transforms. Option C is also incorrect because Service Graph Connector upgrades proceed normally; they do not refuse to start because of customizations.

This behavior aligns with Data Foundations best practices: avoid modifying OOTB content when possible, but when customization is necessary, ensure it is protected during upgrades. Administrators should review skipped changes after upgrades to decide whether to manually adopt new OOTB logic.

Therefore, the correct answer is B – A skipped change is created and no change is made to the script transform definition.

The correct answer is Technology Management Service Offering, also called a Technical Service Offering. In CSDM-aligned configuration, Technical Service Offerings can be related to Dynamic CI Groups so that operational ownership values are synchronized to the member CIs. This includes the Support Group, which is used by ITSM processes for routing incidents, problems, and operational work. A Dynamic CI Group alone defines CI membership, but it does not provide the service-offering ownership context by itself. A Technology Management Service represents the broader technical service, while the offering is the consumable operational layer that carries support and management group information. CI Class Manager is used for class and schema configuration, not for automatically maintaining CI support groups. Therefore, the correct mechanism is the Technology Management Service Offering.

=========

The CMDB Data Manager is the ServiceNow capability responsible for generating actionable governance tasks and assigning them to CI class owners and data stewards. These tasks appear directly in the “My Work” tab within the CMDB Workspace, enabling proactive and role-based CMDB governance.

CMDB Data Manager focuses on data lifecycle management, including archival, retirement, and cleanup of CIs based on defined policies. When lifecycle rules or retention thresholds are met—or when human validation is required—the Data Manager creates tasks to prompt responsible owners to take action. This ensures that CMDB data remains accurate, compliant, and lean over time.

The CMDB Health Dashboard (Option C) provides visibility into health metrics such as completeness, correctness, and compliance, but it does not generate tasks. Similarly, De-duplication templates (Option A) support duplicate identification and remediation workflows, but they do not create ongoing governance tasks in the CMDB Workspace.

By surfacing tasks in “My Work,” CMDB Data Manager operationalizes governance and embeds accountability into daily workflows, which is a key principle of CMDB Data Foundations.

Therefore, the correct answer is Option B – CMDB Data Manager.

Identification rules can be reviewed and configured through CI Class Manager and the CI Identifiers module .

CI Class Manager provides the modern class-centric interface for managing a CMDB class. It consolidates class hierarchy information, attributes, identification rules, reconciliation settings, principal-class configuration, and recommended relationships. This allows an administrator to understand an identification rule in the context of the class to which it applies.

The CI Identifiers module provides direct access to identification-rule definitions used by the Identification and Reconciliation Engine. These rules specify the attribute combinations that determine whether incoming data represents an existing CI or requires creation of a new CI.

API Integrations does not define IRE identification criteria. “IRE Application” is not the applicable class-level configuration location presented by the platform for this task.

=========

The Identification and Reconciliation Engine (IRE) is a core platform capability in ServiceNow and does not require CMDB 360 / Multisource CMDB to function. Even without the ITOM Discovery license, organizations can still define and use IRE reconciliation rules across multiple data sources.

IRE rules are source-aware and can evaluate attributes based on source precedence, regardless of whether CMDB 360 is enabled. CMDB 360 enhances visibility, governance, and monitoring of multiple sources, but it is not a prerequisite for reconciliation logic itself.

Option A is incorrect because purchasing ITOM Discovery is not mandatory to use multisource reconciliation. Option C is also incorrect because CMDB 360 / Multisource CMDB is a licensed add-on, not a universally available platform feature.

Therefore, the Data Owner can proceed by configuring IRE reconciliation rules directly, making Option B the correct answer.

In ServiceNow, the Duplicate CI Remediator is a governed tool designed to safely resolve duplicate Configuration Items while preserving the most valuable and authoritative record. The first step in the remediation wizard is identifying the Main CI, which will be retained after remediation.

ServiceNow uses two primary attributes to help determine the best candidate for the Main CI:

Oldest Created (Option A)

The oldest CI is often preferred because it typically has a longer operational history, may be referenced by historical incidents, changes, problems, or audits, and is more likely to be embedded in downstream processes and reports. Retaining the oldest CI helps avoid breaking historical references.

Most Related Items (Option B)

A CI with the most relationships (for example, links to applications, services, incidents, or other CIs) is generally the most valuable from a business and operational context perspective. Preserving these relationships is critical for impact analysis, Change Management, and CSDM-aligned service modeling.

Options C (Newest Created) and D (Least Related Items) are not used as selection criteria because newer or weakly-related CIs typically contain less historical and relational value and are better candidates for removal or merging.

By prioritizing Oldest Created and Most Related Items, the Duplicate CI Remediator aligns with CMDB Data Foundations best practices, ensuring minimal data loss, preserved business context, and safer de-duplication outcomes.

Therefore, the correct answers are A and B.

CI Class Manager is used to configure class-level health requirements, including attributes designated as required or recommended for a selected CI class. The administrator can identify Support Group and Managed By Group as recommended attributes for the Linux Server class. Recommended fields provide operational and diagnostic value even when they are not technically mandatory for inserting a CI.

Health Preferences control how CMDB Health findings are processed, including task-generation behaviour for CIs that fail applicable health conditions. Once the health calculations identify operational Linux servers with missing recommended values, remediation tasks can be generated and assigned for corrective action. The guide confirms that task behaviour for unhealthy CIs is governed through the relevant health metric configuration rather than through the dashboard itself.

Technical Service Offerings and Dynamic CI Groups can populate and synchronize group values, but they are not the modules used to define recommended-field health checks and generate health tasks. Therefore, B is correct.

=========

A Technology Management Service Offering associated with the applicable Dynamic CI Group synchronizes operational group information to its member CIs. The fields designed for this synchronization include Managed by Group and Support Group .

Therefore, Linux Server CIs included in the offering’s CI population receive Enterprise IT Services as their Managed by Group. The CI Class Manager value can provide class-level ownership or governance context, but the service-offering alignment actively maintains the operational group value on the related member CIs.

The conflicting values do not cause Discovery or ingestion to fail. ServiceNow applies the configured group-synchronization mechanism rather than leaving the field empty. Change Management Team is assigned to the Change Group field, not the Managed by Group field, so Option D does not answer the question.

Consequently, the Managed by Group assigned to the discovered Linux Server instances is Enterprise IT Services.

Agent Client Collector

Automated agent-based solution running patterns

Import Sets

Organization-built solution using transform maps

Service Graph Connector

Pre-built store integration solutions that require minimal customization

ServiceNow Discovery

Automated agentless solution running patterns

Agent Client Collector: This is ServiceNow ' s agent-based approach. It requires a software agent to be installed on the target host to run discovery patterns locally.

Import Sets: This is the traditional, manual way to bring in data. You define the source, and the organization builds the logic (Transform Maps) to move that data into the CMDB.

Service Graph Connector: These are found in the ServiceNow Store. They are " certified " integrations built to work with specific third-party vendors (like SCCM or Jamf) with minimal setup.

ServiceNow Discovery: The classic agentless method. It probes the network and uses patterns to identify and map CIs without needing software installed on every machine.