CIS-DF Practice Test 16 — 15 Questions

Question 1

An administrator is reviewing Discovery results and notices that network switches are successfully discovered, but their associated switch ports are missing. Which TWO factors are most likely responsible for this ingestion gap? (Choose two.)

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The dependent relationship payload structure for switch ports failed IRE validation or was omitted.. Option A is correct because switch ports are ingested as dependent CI records tied to the parent switch via the IRE (Identification and Reconciliation Engine); if the dependent relationship payload is malformed, fails IRE validation, or is omitted entirely, the parent switch is created but its port CIs are dropped. Option D is correct because the discovery pattern (e.g., the SNMP-based network switch pattern) is what parses and populates the switch port table; if that port-parsing step is removed or excluded from the pattern, switches still get discovered while ports never get created. Option B is not relevant because cmdb_ci_ip_address read-only access affects IP address CI writes, not switch port ingestion. Option C is not relevant because Data Source Precedence rules resolve conflicts between data sources for existing records; they do not cause ports to be marked deprecated or prevent their initial discovery. Option E is not relevant because running discovery outside business hours only affects timing, not whether switch port data is parsed and ingested.

Answer

The cmdb_ci_ip_address table has read-only access enabled for all users.

Answer

Data Source Precedence rules marked switch ports as deprecated.

Answer

Discovery schedules were run outside of business hours.

Question 2

Which TWO tools or features in ServiceNow allow you to investigate and visualize relationships between configuration items? (Choose two.)

Accepted Answer

CMDB Query Builder. CMDB Query Builder (C) is correct because it lets you build and run queries across CMDB classes and their relationships, then visualize the resulting CI relationship graph, making it a primary tool for investigating how configuration items connect. Dependency Views (E) is correct because it renders an interactive map of a CI and its upstream/downstream dependencies based on CMDB relationship data, which is exactly the visualization of CI relationships the question asks for. CI Class Manager (A) is for administering the class hierarchy, identifiers, and reconciliation rules of CI classes, not for querying or visualizing relationships between existing CIs. Discovery Schedule configuration (B) only defines when and what Discovery scans, so it creates/updates CIs but does not investigate or visualize their relationships. System Definition > Tables (D) is a low-level schema administration area for viewing table definitions and fields, not a relationship investigation or visualization feature.

Answer

CI Class Manager

Answer

Discovery Schedule configuration

Answer

System Definition > Tables

Question 3

An enterprise is designing a multi-source data ingestion architecture for their CMDB, combining Discovery, Service Graph Connectors, and manual spreadsheet imports. Which THREE governance practices should be implemented to ensure data integrity? (Choose three.)

Accepted Answer

Ensure robust identification rules are configured in CI Class Manager to prevent duplicate CI creation.. Option A is correct because the Identification and Reconciliation Engine (IRE) relies on identification rules configured in CI Class Manager to match incoming records to existing CIs; without robust rules, Discovery, Service Graph Connectors, and spreadsheet imports would create duplicate CIs instead of updating the correct record. Option C is correct because each integration and manual import must write a unique, standardized discovery source string (e.g., 'ServiceNow Discovery', 'SGC-Azure', 'Manual-Import-Finance') so the IRE can track provenance, apply source-specific precedence, and enable auditing or rollback per source. Option E is correct because Data Source Precedence rules determine which source wins when multiple sources update the same CI attribute, which is essential when Discovery, connectors, and manual imports supply conflicting values. Option B is incorrect because collapsing all sources into the default 'Discovery' string destroys provenance and makes precedence, auditing, and troubleshooting impossible. Option D is incorrect because bypassing the IRE for spreadsheet imports allows unrestricted, unreconciled inserts and updates that create duplicates and corrupt CI relationships, defeating data integrity.

Answer

Allow all data sources to use the default 'Discovery' source string to simplify configuration.

Answer

Bypass the IRE for manual spreadsheet imports to allow unrestricted table updates.

Question 4

When planning a CMDB Governance strategy, which THREE key stakeholder groups should be actively involved in defining data ownership and data quality rules? (Choose three.)

Accepted Answer

CMDB / Platform Administrators. Option A (CMDB / Platform Administrators) is correct because these administrators own the technical implementation of the CMDB, including the CI class model, attribute definitions, reconciliation and normalization rules, and health dashboards, so they must help define enforceable data quality rules and ownership workflows. Option B (Compliance and Audit Officers) is correct because they translate regulatory and internal control requirements (e.g., SOX, ISO 27001, ITIL audit criteria) into data retention, accuracy, and evidence standards that the governance strategy must satisfy. Option D (Data Owners / CI Stewards) is correct because they are accountable for the accuracy, completeness, and lifecycle of specific CI classes and attributes, making them the primary parties who assign ownership and approve data quality thresholds. Option C is not correct because end-users submitting self-service catalog requests are consumers of CMDB data, not stakeholders responsible for defining ownership or quality rules. Option E is not correct because external hardware manufacturers supply component data but have no governance authority over the organization's CMDB data ownership or quality standards.

Answer

End-users submitting self-service catalog requests

Answer

External third-party hardware component manufacturers

Question 5

When setting up CMDB Data Governance, which THREE elements must be defined for a custom data policy or rule? (Choose three.)

Accepted Answer

Evaluation Criteria (the condition or completeness check). In ServiceNow CMDB Data Governance, a custom data policy or rule requires three core elements: the Target CI Class (option E, e.g., cmdb_ci_appl), which scopes the rule to the specific class of CIs it governs; the Evaluation Criteria (option A), which defines the condition or completeness check that determines whether a CI passes or fails the policy; and the Remediation Configuration (option D), which specifies the task creation and assignment rules that fire when a CI violates the policy. These three together form the complete policy definition — what to check, against which CIs, and what to do when the check fails. Option B (MID Server IP address binding range) is unrelated, as MID Server binding is a discovery/connectivity concern, not a data governance policy element. Option C (SLA response time threshold for incident escalation) belongs to SLA and incident management configuration, not CMDB data governance.

Answer

MID Server IP address binding range

Answer

Service-Level Agreement response time threshold for incident escalation

Question 6

When configuring Identification Rules in CI Class Manager, administrators can specify multiple criteria entries. Which TWO behaviors apply when multiple identification rule entries are defined for a single class? (Choose two.)

Accepted Answer

The IRE evaluates the identification rule entries in sequential order based on their priority ranking.. Option B is correct because the Identification and Reconciliation Engine (IRE) processes multiple identification rule entries in a defined sequence governed by their priority ranking, so administrators control which criteria are attempted first. Option E is correct because identification entries act as a fallback chain: when the first entry's criteria do not match any existing CI, the IRE proceeds to evaluate the next entry until a match is found or all entries are exhausted. Options A, C, and D are incorrect: the IRE does not automatically merge all matching records into one (A), identification rules are not limited to legacy Import Sets and apply to all IRE-based ingestion sources (C), and entries are evaluated sequentially rather than requiring all criteria to match at once (D).

Answer

Defining multiple entries automatically merges all matching records into a single record.

Answer

Identification rule entries only apply when ingestion is performed via legacy Import Sets.

Answer

All identification rule entries must match simultaneously for a CI to be identified.

Question 7

When designing an integration using Robust Transform Engine (RTE), which TWO components must be configured to successfully ingest data into the CMDB? (Choose two.)

Accepted Answer

Robust Transform Engine Data Stream Definition and field maps. Option A is correct because the RTE Data Stream Definition and its field maps define how incoming source records are parsed and mapped into the target CMDB schema, which is the essential first stage of any RTE-based ingestion. Option C is correct because the IRE Payload structure or CI class mapping definition determines how the transformed data is classified and identified as the proper CMDB CI class, which is required for the Identification and Reconciliation Engine to create or update CIs correctly. Option B is not required because Discovery schedules and IP ranges only control how Discovery probes collect data, not how RTE ingests and maps it into the CMDB. Option D is not required because Service Mapping application pattern criteria are used to build service models, not to ingest CI data into the CMDB. Option E is not required because Legacy Transform Map Coalesce scripts belong to the older transform-map approach, not the RTE/IRE ingestion path.

Answer

Discovery schedule IP address ranges

Answer

Service Mapping application pattern criteria

Answer

Legacy Transform Map Coalesce scripts

Question 8

When reviewing data ingestion methods for the ServiceNow CMDB, which TWO methods natively invoke the Identification and Reconciliation Engine (IRE) out of the box? (Choose two.)

Accepted Answer

Service Graph Connectors. Service Graph Connectors (A) are built on the Identification and Reconciliation Engine and call IRE natively to deduplicate and reconcile incoming third-party data into the CMDB. ServiceNow Discovery (E) also natively invokes IRE when it creates or updates CIs, ensuring discovered data is identified and reconciled against existing records. Direct GlideRecord inserts (B) bypass IRE unless explicitly called, so they do not natively invoke it. Email Inbound Actions creating incident records (C) operate on the task/incident tables, not the CMDB, and never touch IRE. Legacy Transform Maps with standard Coalesce settings (D) use coalesce-based matching rather than IRE, so they do not natively invoke the engine.

Answer

Direct manual table inserts via background scripts using GlideRecord

Answer

Standard Email Inbound Actions creating incident records

Answer

Legacy Transform Maps with standard Coalesce settings

Question 9

An architect is troubleshooting an integration payload processed by the Identification and Reconciliation Engine (IRE) that resulted in an error. Which THREE of the following scenarios commonly trigger IRE processing errors? (Choose three.)

Accepted Answer

The incoming payload is missing attributes required by the class's identification rule criteria.. Option A is correct because IRE identification rules depend on specific attributes (such as serial number, name, or IP address) being present in the payload; if those required attributes are missing, the engine cannot match the incoming data to an existing CI and raises a processing error. Option D is correct because the discovery source value drives precedence and reconciliation logic in IRE; an unregistered or malformed discovery source string prevents the engine from evaluating precedence correctly and results in an error. Option E is correct because when a payload references a parent CI (for example via a relation or lookup), IRE must resolve that parent to a valid CI record; if the parent cannot be identified, the dependent CI cannot be processed and an error occurs. Option B is not relevant because UI Policies affect form behavior in the platform UI, not IRE payload processing. Option C is not relevant because IRE does not impose a 1,000-record-per-batch limit as a common error trigger; batch size is a general import consideration, not an IRE identification/reconciliation failure cause.

Answer

The target table does not have any UI Policies defined on its form view.

Answer

The import set table row count exceeds 1,000 records per batch.

Question 10

Your enterprise has acquired a company that uses custom naming conventions, causing duplicate CIs to be created during discovery. Which tool should you use to examine and adjust how incoming CIs are matched against existing records in the CMDB?

Accepted Answer

CI Class Manager. The CI Class Manager is the centralized interface for configuring identification and reconciliation rules, including how incoming CIs are matched to existing records. It allows you to define identification rules based on attributes (e.g., serial number, name) and reconciliation rules to handle duplicates. This is the correct tool to examine and adjust matching behavior when acquisitions introduce conflicting naming conventions.

Answer

Data Normalization Engine

Answer

CMDB Health Dashboard

Answer

Dependency View

Question 11

What is the primary visual benefit of using Dependency Views during change management planning?

Accepted Answer

Identifying upstream and downstream CIs that could be impacted by a change on a target CI.. Dependency Views helps change managers identify downstream infrastructure and upstream services that might be affected by a planned change on a CI.

Answer

Executing automated software deployments to target servers.

Answer

Calculating financial depreciation schedules for hardware assets.

Answer

Running vulnerability scans against network endpoints.

Question 12

An IT director wants to identify all business applications that do not have an assigned owner or support group in the CMDB. Which ServiceNow reporting or dashboard feature is best suited to highlight this specific completeness gap?

Accepted Answer

CMDB Health Dashboard - Completeness metric. The CMDB Health Dashboard's Completeness metric is purpose-built to measure whether required CMDB fields (such as 'Owned by' and 'Support group') are populated on configuration items. It runs scheduled completeness audits against CI classes and flags records missing mandatory attributes, which is exactly the 'no owner / no support group' gap the director wants surfaced. Because it aggregates results into KPIs and drill-down reports, it directly highlights the specific completeness deficiency rather than showing discovery or mapping activity.

Answer

Discovery Identification Engine log

Answer

Service Mapping Entry Point report

Answer

CSDM Data Foundations Dashboard - Sell/Consume stage

Question 13

An enterprise wants to ensure that data stewards are automatically notified when duplicate CIs are detected by the Identification and Reconciliation Engine (IRE). How can this governance requirement be streamlined?

Accepted Answer

Configure CMDB Duplicate Remediation rules. Configuring CMDB Duplicate Remediation rules allows the system to automatically detect duplicate CIs and notify data stewards based on predefined conditions. These rules can trigger notifications, assign tasks, or even merge duplicates, streamlining governance. This approach leverages out-of-the-box functionality rather than custom scripting, ensuring maintainability and scalability.

Answer

Set up a scheduled data import transform map script

Answer

Modify the Identification Engine processor script directly

Answer

Write a custom Business Rule on the sys_object_source table

Question 14

An organization is troubleshooting duplicate CIs appearing in the CMDB after running a new integration. Which TWO administrative actions should be taken to investigate and resolve this issue? (Choose two.)

Accepted Answer

Inspect CI Class Manager identification rules for the affected class to ensure unique attributes are correctly defined.. Option A is correct because CI Class Manager identification rules define which attributes (such as serial number, name, or IP address) are used to uniquely identify a CI; if these rules are misconfigured or missing for the affected class, incoming records will not match existing CIs and duplicates will be created. Option D is correct because the Identification and Reconciliation Engine (IRE) processing logs and payload results show exactly how each incoming record was evaluated, including which identification rules were applied and why a match failed, which is essential for diagnosing the root cause of duplicate CIs. Option B is incorrect because hiding duplicates via ACLs only masks the symptom and does not resolve the underlying identification problem. Option C is incorrect because REST Message timeout limits affect outbound request performance, not CI matching or deduplication. Option E is incorrect because deleting and recreating Discovery schedules is a destructive, unrelated action that would not address duplicate CI creation from an integration.

Answer

Modify Access Control Lists to hide duplicate CIs from users.

Answer

Increase the timeout limit on all REST Message records.

Answer

Delete all Discovery schedules and recreate them from scratch.

Question 15

When defining a Reconciliation Definition in ServiceNow to manage attribute precedence, which THREE configurations or behaviors apply? (Choose three.)

Accepted Answer

Rules can target specific CI classes or apply globally across the entire cmdb hierarchy.. Option A is correct because a reconciliation rule can be scoped to a specific CI class (for example, cmdb_ci_server) or defined globally so it applies across the entire CMDB class hierarchy, giving administrators flexible control over where precedence logic is enforced. Option C is correct because global precedence rules are the baseline that applies to all CMDB classes, and class-specific rules take priority over them when both exist, which is exactly how ServiceNow resolves attribute precedence conflicts. Option D is correct because reconciliation definitions let you designate which discovery sources (such as ServiceNow Discovery, SCCM, or a specific MID Server source) are authoritative for particular attributes, so the winning value comes from the trusted source. Option B is incorrect because reconciliation definitions are built specifically for CMDB CI classes (cmdb_ci and its children), not for transactional tables like task. Option E is incorrect because sources not listed in a precedence rule are not globally denied; they simply do not win precedence for the attributes covered by that rule, and may still update other attributes or be handled by other rules.

Answer

Reconciliation definitions only apply to transactional tables like task, never to cmdb_ci classes.

Answer

Discovery sources not explicitly listed in a precedence rule are denied any ability to update the CMDB entirely.