ServiceNow Updated CIS-DF Exam Questions and Answers by sunny

CMDB Query Builder provides purpose-built Export Query and Import Query functions for transferring saved query definitions between ServiceNow instances. The administrator selects the saved query, exports its definition as an XML file, and the receiving team imports that file using the Import Query function. The imported definition then appears in the destination instance’s Saved Queries tab.

Exporting the query as a report would transfer report configuration rather than the complete Query Builder canvas and relationship definition. A generic record-level XML export is not the prescribed Query Builder workflow.

ServiceNow also documents transfer through an update set, but identifies that process as an alternative maintained for backward compatibility. Because the question asks for the direct and recommended Query Builder approach, Option A is the best answer.

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.

=========

A web server is a software-based CI hosted on underlying server hardware or a virtual machine. The standard ServiceNow relationship is therefore Runs on::Runs . From the Web Server CI’s perspective, it runs on the Server CI. When the same relationship is viewed in the reverse direction, the Server runs the Web Server.

The reverse wording in Option B incorrectly changes the parent-to-child direction. “Uses::Used by” represents a dependency or consumption relationship, not the direct hosting relationship between installed software and its host. Option D reverses that unrelated relationship type.

ServiceNow documentation defines Runs on::Runs as the standard relationship between a software application CI and its hosting hardware or virtual machine, giving Tomcat running on a Linux server as an example. Discovery can automatically identify and load these CI relationships into the CMDB.

=========

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.