ServiceNow CIS-DF Practice Test Questions Answers

The Unified Map in ServiceNow provides a consolidated view of services and their underlying components, integrating Discovery and Service Mapping data. To make this view actionable, Service Owners can apply filters to focus on relevant elements and reduce visual noise.

Filtering by CI type (Option A) is a core capability. It allows the Service Owner to show or hide categories such as servers, databases, load balancers, or applications—making it easier to analyze specific layers of the service.

Filtering by Business Criticality (Option D) is also available and highly valuable. This enables Service Owners to prioritize views around high-impact components, ensuring attention is focused on CIs that pose the greatest risk to service delivery.

Option B (Discovery source) is not typically exposed as a Unified Map filter because the map focuses on operational and service context, not ingestion provenance. Option C (Managed by group) is a governance attribute and is not a standard visual filter within the Unified Map.

Thus, the correct filter options are A – CI type and D – Business criticality.

Within Data Foundations, “Configuration” includes designing the CMDB data model in a way that supports operational usability—especially for ITSM processes like Incident and Change. One common usability challenge is that CI reference fields (such as the Incident “Configuration item” field) can become cluttered and confusing if they allow selection from every CI class, including highly technical or rarely used classes. To address this, ServiceNow uses the concept of Principal Classes: a curated subset of CI classes that are considered primary for operational selection and reporting.

Principal Classes are designated in the CI Class Manager, because this is where administrators configure and manage CI class behaviors and class-level settings. Defining Principal Classes at the class-management layer ensures that the platform can consistently apply this constraint across CI reference fields and related experiences. This aligns with Data Foundations goals: improving data quality and process outcomes by making it easier for users to select the correct CI, which in turn increases accuracy for assignment, routing, impact analysis, and analytics.

The other options do not fit the responsibility. CMDB Workspace is primarily used for exploring and analyzing CMDB data, not configuring class-level constraints. CMDB Data Manager focuses on governance automation (like lifecycle policies and bulk remediation operations), not CI class designation rules. System Properties may influence global behaviors, but Principal Class designation is a modeling configuration handled through CI class configuration, which is why CI Class Manager is the correct location.

IRE applies identification logic to determine whether incoming data represents an existing record or requires the creation of a new record. This makes Option A correct: properly configured identifiers reduce duplicate creation by matching incoming data to existing records before insertion.

IRE also applies reconciliation controls after identification. Reconciliation rules establish which data sources are authorized to update particular classes or attributes and define source precedence when multiple sources provide competing values. Therefore, Option D is correct because an unauthorized or lower-priority source can be prevented from overwriting controlled data.

IRE does not generally prevent an authorized ingestion source from inserting a genuinely new record when no match exists, so Option B is too broad. Option C is incorrect because identification is based on identifier attributes and identification rules, not simply on whether relationships exist.

The guide describes IRE as the mechanism that uniquely identifies records, reduces duplicate creation, applies source precedence, and protects records from unauthorized overwrites.

=========

The Desired State audit type is included in the CMDB Health Compliance calculation. A desired-state audit compares the actual values stored on a CI against the values or conditions that the organization expects the CI to meet.

In this scenario, the organization’s desired state is that every server must have the current approved patch level. A Certification Template can define the server population and attributes to be evaluated. The resulting audit identifies servers that do not satisfy the expected patch condition, and those results contribute to the Compliance KPI.

“Compliance” is the name of the overall CMDB Health scorecard, not the audit type selected for this check. “Architecture Compliance” is not the applicable audit type for validating server patch-level attributes.

The Compliance scorecard uses audit results to determine whether CIs conform to defined organizational standards. Therefore, the correct audit type is Desired State .

=========

In ServiceNow, Dynamic CI Groups are a core Data Foundations capability used to automatically manage CI membership based on rules rather than manual maintenance. When Technology Management Service Offerings (Technical Service Offerings) are related to Dynamic CI Groups, ServiceNow uses those relationships to synchronize operational support attributes to the member CIs.

The two CI attributes that are intentionally designed to sync in this model are the Managed by Group and the Support Group. These groups directly influence operational ownership and support routing, which is why they are automatically aligned when Dynamic CI Groups are used. This ensures that incidents, changes, problems, and operational tasks are routed consistently as CI membership changes over time.

The Support Group defines who provides day-to-day operational support and is critical for Incident and Request Management workflows. The Managed by Group represents the team responsible for the technical lifecycle and operational health of the CI. Synchronizing these attributes eliminates manual updates and reduces misrouted tickets, which is a key goal of Configuration Management maturity.

The Approval Group (Option A) is not synced because approvals are process-driven and often context-specific rather than CI-driven. Similarly, the Owned by Group (Option C) represents accountability or financial ownership, which is intentionally decoupled from dynamic operational grouping to avoid unintended governance changes.

Therefore, the correct answers are B (Managed by Group) and D (Support Group).