Important ServiceNow CIS-DF Exam Questions

Answer: A, C

Explanation:

The CMDB aligns to business processes by giving the organization a trusted operational data foundation. First, it enhances decision-making and operational efficiency because Incident, Problem, Change, Risk, Security, and Service Management teams can assess impact, ownership, dependency, and priority using reliable CI and relationship data. Second, it provides a centralized view of configuration items and relationships, which is the core function of the CMDB. That centralized relationship model is what makes service impact analysis, change risk assessment, outage analysis, and operational routing possible. Tracking software licenses is primarily an IT Asset Management and Software Asset Management concern, not the main CMDB business-process alignment value. Extending service delivery management to all enterprise departments is too broad and belongs more to enterprise service management strategy than core CMDB alignment. Therefore, A and C are correct.

=========

Answer: C

Explanation:

In a mature CMDB implementation within ServiceNow, CI operational attributes are leveraged to automate ITSM workflows. One of the most important outcomes of accurate Configuration Management is automatic incident routing.

When a CI is selected on an Incident record, ServiceNow evaluates the CI's Support Group attribute. If populated correctly, the platform automatically copies this value into the Assignment Group field on the Incident. This ensures incidents are routed to the correct resolver group without manual triage, reducing mean time to resolution (MTTR).

The Support Group is a CI attribute, not an incident field that drives workflow directly. The Assignment Group is the operational field used by Incident Management to assign ownership. Managed by Group, Approval Group, and Change Group are used in other governance and lifecycle contexts and are not auto-populated during incident creation.

This behavior is a direct result of Data Foundations best practices: maintaining accurate CI-to-support-group relationships to enable automation and consistency across ITSM processes.

Therefore, the correct answer is C -- Assignment Group.

Answer: B, C

Explanation:

The CMDB Data Foundations Dashboard helps administrators assess whether important CMDB data is valid, properly configured, and aligned with expected data quality practices. It is designed to surface actionable gaps and risks, then guide remediation through playbooks. Therefore, B and C are correct. The dashboard does not automatically remediate all risks by itself; it guides administrators and data owners toward corrective actions through structured playbooks. It also is not primarily a custom metric development framework. Its purpose is to provide curated, ServiceNow-aligned metrics and remediation guidance for CMDB and CSDM maturity. This makes it useful for improving data health, identifying configuration issues, and supporting governance without requiring custom reporting or manual analysis from scratch.

=========

Answer: D, E

Explanation:

Archive and Retire are the correct CMDB Data Manager end-of-life policy types from the listed options. End-of-life governance in CMDB focuses on handling CI records that are no longer operationally active or no longer required in the active CMDB. A Retire policy is used when CIs should be moved out of active operational status while preserving lifecycle accuracy. An Archive policy is used when records should be removed from active operational use but retained for recovery, audit, or compliance purposes. Disposed and Lost are typically lifecycle status values used in asset or CI lifecycle tracking, not CMDB Data Manager policy types in this context. Decommission describes an operational lifecycle action or state transition, but it is not the Data Manager policy type being tested here. Therefore, the valid end-of-life policy types are Archive and Retire.

Answer: B

Explanation:

When the Identification and Reconciliation Engine encounters multiple existing records that satisfy the applicable identification criteria, it must select a record for processing while identifying the duplicate condition for later remediation. For this automatic IRE processing behaviour, the record with the most recent update date is selected for the incoming update.

This should not be confused with the Duplicate CI Remediator's guided selection of a Main CI. During manual remediation, factors such as the oldest creation date, number of related records, historical task references, and business relationships can influence which CI should ultimately be retained. That is a separate governance process from the IRE's immediate handling of incoming data.

Option A incorrectly selects the newest-created record, while Option C applies a main-record retention principle to the wrong stage of processing. IRE first identifies incoming records using identification rules and then applies reconciliation rules to control authorized updates and source precedence. This governed processing is what prevents uncontrolled insertion and overwriting of CI records.

=========