CIS-DF Exam Dumps - ServiceNow CIS-Data Foundations (CMDB and CSDM) Questions and Answers

A CMDB Data Foundations Dashboard playbook provides a Problem Overview and information about likely Root Causes . The Problem Overview explains the deficient metric, why the condition matters, and the operational or governance risks created by poor performance. The Root Cause material helps administrators identify why the condition exists, such as incomplete source data, incorrect transformations, missing ownership, inappropriate class usage, or weak governance controls.

The guide describes these playbooks as structured, prescriptive guidance for identifying root causes, assessing ingestion and governance gaps, and applying appropriate corrective actions.

Playbooks may recommend analysis, correction, reporting, and governance activities, but they do not normally provide fully automated remediation scripts that should be executed without review. “Problem Analysis” is not the named documentation component tested here; analysis is instead performed through the recommended remediation plays.

=========

The correct answer is Run. The Run stage of CSDM maturity focuses on operationalizing the service model so that it supports real ITSM and operational processes. Technology Management Services and Technical Service Offerings are used to represent technical services delivered by internal technology teams. When these offerings are connected to Dynamic CI Groups, operational ownership data such as Support Group and Managed By Group can be populated and maintained on associated CIs. This is beyond the basic Crawl and Walk stages, which focus on foundational CMDB data and initial service modeling. It is also not Fly, which represents more advanced optimization and enterprise-level maturity. Because the scenario is about using Technical Service Offerings to drive operational support alignment for CIs, it belongs to the Run stage.

=========

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.

The correct option is Allow fallback to parent’s rules . In CI identification, ServiceNow evaluates the configured identification rule for the target class first. If the Tomcat rule cannot find a match using its class-specific criterion attributes, fallback behavior allows the Identification and Reconciliation Engine to attempt matching against the parent class identification rule. Since Tomcat is a more specific application class, falling back to the parent Application identification rule helps prevent unnecessary duplicate records when a match cannot be made at the subclass level. “Applies to” defines the class or scope for the identifier entry. “Independent” controls whether a rule is evaluated independently rather than through parent inheritance. “Criterion attributes” are the fields used for matching, not the fallback setting. Therefore, the correct configuration is Allow fallback to parent’s rules .

=========

CMDB 360, also known as Multisource CMDB , provides attribute-level visibility into the data contributed by different discovery and integration sources. It enables an administrator to examine which source supplied a particular attribute, compare competing values, identify missing source contributions, and understand how reconciliation selected the final value stored on the CI.

The guide explains that CMDB 360 reveals gaps in attribute data and differing attribute values across sources. These insights help administrators diagnose reconciliation conflicts, inappropriate source precedence, incomplete integrations, and inconsistent discovery results.

CMDB 360 is not itself the mechanism used to ingest records. Service Graph Connectors, IntegrationHub ETL, Import Sets, and Discovery perform ingestion. CMDB 360 instead preserves and exposes the source- level contributions after ingestion so that data owners can investigate and improve multisource data quality.

=========

CMDB 360/Multisource CMDB retains information about the values contributed by individual data sources. When reconciliation logic is modified, the administrator can perform a recompute operation so the latest rules are applied to the stored source contributions without waiting for every external system to send the data again.

This enables administrators to test and refine source-precedence or dynamic reconciliation rules and then recalculate the resulting CI attribute values using the available historical source data. The capability is particularly useful when correcting an inappropriate source-priority rule or implementing dynamic rules such as Most Reported or Last Updated.

CMDB 360 does not eliminate identification rules, permanently lock records, or automatically archive records based on quarterly reporting behaviour. Identification remains necessary to match incoming data to the correct CI, while reconciliation determines which authorized source controls an attribute.

=========

The correct answer is C. Service Graph Connectors are ServiceNow-supported integrations when used as delivered or configured within supported boundaries. When an administrator customizes the mappings, the implementation moves away from the supported out-of-box connector behavior. This creates upgrade and support implications because ServiceNow cannot guarantee that customized mappings will remain compatible with future connector updates. The customer becomes responsible for validating, maintaining, and troubleshooting those customizations. Option A is not the primary consequence because customized fields are not simply protected by a special CMDB tag. Option B is incorrect because custom mapping does not automatically block connector execution pending approval. The key risk is supportability and technical debt, making C the correct answer.

=========

When building advanced CMDB queries using CMDB Query Builder in ServiceNow, the correct approach is to model CI scope, relationships, and task context explicitly on the canvas.

To limit results to databases in a specific location, the administrator must filter the Database CI node by the Location attribute. Therefore, Option C is required to scope the query to Database CIs where Location = Seattle.

To include Incidents related to those databases, the Incident table must be added from the Non-CMDB Tables list and linked through the task_ci relationship. This is exactly what Option A provides. CMDB Query Builder separates CMDB tables (CIs) from task and transactional tables, so incidents must be explicitly added from the Non-CMDB section.

Option B is incorrect because property columns on Application Services do not scope databases or incidents. Option D is unnecessary because relationship depth alone does not include non-CMDB task data and does not filter by location.

Thus, the correct actions are A (add Incident table) and C (filter Database by location).

In Data Foundations, “Ingest” is not limited to Discovery. It includes establishing reliable sources and mechanisms to populate and maintain CMDB attributes—especially those that Discovery cannot provide. Warranty expiration dates are a classic example of non-discoverable data: they typically come from procurement systems, asset repositories, vendors, or contract tools rather than from device interrogation.

The correct approach is to maintain these attributes via a scheduled data import from an authoritative external source. This ensures ongoing accuracy and consistency at scale. A scheduled import allows you to define a repeatable integration pattern, apply data quality checks, and keep warranty data current as vendors and procurement records change—without relying on manual updates that inevitably drift over time.

Option A is incorrect because the CMDB Reconciliation Engine resolves conflicts between multiple data sources and applies precedence rules; it does not create the warranty values out of thin air. Reconciliation helps decide which source wins when updates occur, but you still need a source feed providing the warranty attribute values. Option B is also not recommended because creating a new CI class just to hold non-discoverable attributes fragments the model and complicates reporting and processes. Best practice is to keep the attributes on the appropriate hardware CI classes (or related normalized structures, when applicable) and manage them through governed ingestion from authoritative systems. Therefore, C is the best method.

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.

=========