CIS-DF Ingest Practice Test 3 — 15 Questions

Question 1

An administrator is setting up an integration that uses Robust Transform Engine (RTE). They need to combine two incoming fields—'First Name' and 'Last Name' from a user data source—into a single 'Managed By' reference field on the target CI. Which RTE feature should they use?

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

Accepted Answer

RTE Field Transformations / Operations (such as Concatenate). RTE field transformations and field copiers allow combining or transforming multiple source fields into a single target attribute.

Answer

CI Class Manager Identification Rule criteria

Answer

Discovery pattern preprocessing script

Answer

Standard Transform Map Coalesce script

Question 2

An organization discovers network gear using both SNMP Discovery and an external cloud management platform API. Both integrations populate the same physical switch CIs. The cloud platform sometimes sends an empty string for the serial number, which accidentally clears out valid serial numbers previously populated by SNMP Discovery. How can this be prevented using CMDB ingestion controls?

Accepted Answer

Configure IRE payload settings or Data Source Precedence rules to ignore empty or null attribute updates from specific data sources.. Configuring IRE payload settings or Data Source Precedence rules allows you to ignore empty or null attribute updates from specific data sources. This prevents the cloud platform's empty serial number from overwriting valid data from SNMP Discovery, as you can define that only non-empty values should be processed or that SNMP Discovery has higher precedence.

Answer

Delete the identification rule for serial number.

Answer

Write an Inbound Email Action to reject empty payloads.

Answer

Set the serial number field dictionary attribute to 'read-only'.

Question 3

When reviewing CI records ingested into the CMDB, an administrator notices a field labeled 'First discovered' and another labeled 'Last discovered'. Which component populates these lifecycle tracking fields automatically?

Accepted Answer

The Identification and Reconciliation Engine (IRE) and Discovery logging mechanisms. Discovery and the IRE automatically maintain discovery audit metadata, such as first and last discovered timestamps.

Answer

Standard Transform Map execution engine

Answer

CMDB Health Dashboard audit jobs

Answer

Data Policies on the cmdb_ci table

Question 4

An administrator is configuring Data Source Precedence rules in the CMDB. Which TWO of the following statements regarding Data Source Precedence are true? (Choose two.)

Accepted Answer

Administrators can configure Data Source Precedence rules at both the global CMDB level and granularly per CI class.. Option B is correct because Data Source Precedence in the CMDB can be configured at the global level (applying to all CI classes) as well as at the individual CI class level, allowing administrators to tailor precedence granularly where needed. Option D is correct because the core purpose of Data Source Precedence rules is to determine which discovery source (e.g., ServiceNow Discovery, SCCM, manual entry) is authoritative for specific CI attributes when multiple sources attempt to update the same CI, resolving conflicts by source priority. Option A is incorrect because Data Source Precedence applies to data processed through the Identification and Reconciliation Engine (IRE), not just legacy Import Sets without Transform Maps. Option C is incorrect because Data Source Precedence does not perform automatic deletion or aging of CIs; it only governs which source's data wins during updates. Option E is incorrect because Data Source Precedence works alongside Identification Rules within the IRE—it does not replace them, as Identification Rules are still required to determine CI uniqueness and matching.

Answer

Data Source Precedence only applies to data ingested via legacy Import Sets without Transform Maps.

Answer

Data Source Precedence automatically deletes CIs that have not been updated by a high-priority source within 30 days.

Answer

Data Source Precedence rules replace the need for Identification Rules in the IRE.

Question 5

An administrator is configuring a Service Graph Connector to ingest client workstations. During test runs, they notice that workstations with identical hostnames but different serial numbers are being incorrectly merged into a single CI. Where should the administrator check and modify the matching criteria to ensure serial number is prioritized over hostname?

Accepted Answer

CI Class Manager -> Select cmdb_ci_computer -> Identification Rule -> Adjust criteria precedence and attribute selection. The CI Class Manager is where identification rules for a CI class are configured. By selecting cmdb_ci_computer and navigating to the Identification Rule, the administrator can adjust the criteria precedence and attribute selection to prioritize serial number over hostname. This directly addresses the issue of workstations with identical hostnames but different serial numbers being merged.

Answer

Data Source Precedence rules for workstations

Answer

Robust Transform Map Coalesce order

Answer

Discovery Schedule IP range filters

Question 6

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 7

An administrator is designing identification rules for a custom CI class in the CMDB. Which THREE ofg the following best practices should be followed when configuring identification rules? (Choose three.)

Accepted Answer

Use attributes that are guaranteed to be unique and immutable, such as serial numbers or hardware asset tags.. Option A is correct because identification rules must rely on attributes that are unique and immutable, such as serial numbers or hardware asset tags, so the same CI is consistently matched rather than duplicated or misidentified when other fields change. Option B is correct because identification rules are evaluated in order, so placing the most reliable and specific criteria first ensures the strongest match is attempted before broader, less precise rules are considered. Option D is correct because volatile attributes like IP address or hostname alone can change when devices move networks, causing false matches or duplicate CIs; they should be combined with stable identifiers or avoided as sole primary identifiers. Option C is incorrect because custom CI classes should extend cmdb_ci (or an appropriate CMDB base class) to inherit the identification engine behavior and required fields, not be created on unrelated custom tables. Option E is incorrect because cramming every attribute into one compound rule makes identification overly restrictive and brittle, so any single changed attribute breaks the match and creates duplicates.

Answer

Ensure that identification rules are created on custom tables without inheriting from cmdb_ci.

Answer

Configure every single attribute of the CI class into a single compound identification rule entry to ensure maximum security.

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 organization wants to ingest data into the CMDB using the Robust Transform Engine (RTE). Which TWO of the following capabilities are provided by RTE? (Choose two.)

Accepted Answer

Transforming complex hierarchical JSON or XML payloads into structured tabular data for IRE processing.. The Robust Transform Engine (RTE) is ServiceNow's data-transformation framework used by CMDB integrations and Import Sets to normalize incoming payloads before they reach the Identification and Reconciliation Engine (IRE). Option C is correct because RTE is specifically designed to parse and flatten complex hierarchical JSON or XML structures into the structured, tabular rows that IRE requires for CI identification and reconciliation. Option E is correct because RTE provides a library of transform functions — including string trimming, concatenation, splitting, and regex-based mapping — that can be applied to fields during ingestion to standardize values. Option A is incorrect because authentication and session management for inbound REST calls are handled by the REST API framework, OAuth, and authentication policies, not by RTE. Option B is incorrect because RTE is a transformation layer and does not replace the underlying relational database with an in-memory graph store. Option D is incorrect because RTE only transforms data; it does not create ITSM Change Requests, which would require separate workflow or business-rule logic.

Answer

Managing user authentication sessions for inbound REST API calls.

Answer

Replacing the underlying relational database management system with an in-memory graph store.

Answer

Automatically generating ITSM Change Requests for every ingested CI.

Question 10

An administrator is troubleshooting missing relationship data after running a custom data integration. Which THREE of the following factors should be investigated? (Choose three.)

Accepted Answer

Whether the payload structure correctly formats the related items or relationship blocks required by the IRE.. Option A is correct because the Identification and Reconciliation Engine (IRE) requires the payload to include properly formatted related items or relationship blocks; if the structure is malformed, the IRE cannot create the relationships. Option C is correct because both the source and target CIs in a relationship payload must successfully pass identification; if either CI fails to identify or be created, the relationship cannot be established. Option D is correct because the relationship type (for example, 'Runs on::Runs') must exist and be active in the cmdb_rel_type table, otherwise the IRE will reject or skip the relationship. Option B is not correct because client scripts on the target CI table do not block IRE relationship processing, which operates at the server/API level. Option E is not correct because the Discovery status schedule setting is unrelated to custom data integration relationship handling.

Answer

Whether the target CI table has active client scripts blocking the relationship field.

Answer

Whether the Discovery status schedule is set to 'Quick Discovery'.

Question 11

An enterprise is planning a data ingestion strategy for their CSDM implementation. Which TWO principles should guide their approach to data ingestion and the CMDB? (Choose two.)

Accepted Answer

Always route automated integrations through the Identification and Reconciliation Engine (IRE) to maintain data hygiene.. Option B is correct because the Identification and Reconciliation Engine (IRE) is the ServiceNow mechanism that applies identification rules, reconciliation rules, and data source precedence to deduplicate and govern CI data as it is ingested, which is essential for maintaining CMDB data hygiene in a CSDM implementation. Option D is correct because clear data source ownership and precedence rules ensure that when multiple sources (e.g., discovery, imports, integrations) supply the same CI attribute, the authoritative value is deterministically chosen, which is a core CSDM data governance principle. Option A is incorrect because disabling identification rules on base classes would allow duplicate and conflicting records to proliferate, directly undermining CMDB integrity. Option C is incorrect because relying exclusively on weekly manual spreadsheet imports is neither scalable nor timely for enterprise infrastructure CIs and violates CSDM guidance favoring automated, near-real-time ingestion. Option E is incorrect because bypassing IRE with legacy transform maps and direct GlideRecord insertions skips identification and reconciliation, producing duplicates and inconsistent data despite any perceived performance gain.

Answer

Disable identification rules on all base classes to allow any data source to create records freely.

Answer

Rely exclusively on manual spreadsheet imports performed weekly for all infrastructure CIs.

Answer

Use legacy transform maps with direct GlideRecord insertions for all server ingestion to maximize performance.

Question 12

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 13

An administrator is reviewing the CMDB IRE execution logs and notices numerous warnings regarding payloads that skipped attribute updates. Which THREE of the following reasons would cause the IRE to skip updating an attribute on an existing CI? (Choose three.)

Accepted Answer

The attribute is configured to be ignored when incoming values are empty, and the incoming payload provided a blank value.. Option A is correct because the Identification and Reconciliation Engine honors the 'ignore empty values' setting on an attribute; when the incoming payload supplies a blank value and that flag is enabled, the IRE skips the update rather than overwriting the existing value. Option C is correct because Data Source Precedence determines which source is authoritative for a given attribute; if the incoming data source has lower precedence than the source that last populated the attribute, the IRE will not overwrite the existing value. Option D is correct because the IRE performs a value comparison and skips the write when the incoming value is identical to the value already stored, avoiding a no-op update. Option B is not a valid reason because IRE processing does not evaluate table-level Business Rules to decide whether to update an attribute; Business Rules run on record operations, not on the IRE's attribute-level reconciliation logic. Option E is not a valid reason because read access to sys_user is unrelated to attribute-level update decisions in the IRE; the IRE's skip logic is driven by attribute configuration, data source precedence, and value comparison, not by the executing user's access to an unrelated table.

Answer

The target CI table has an active Business Rule that aborts all updates.

Answer

The user executing the integration does not have read access to the sys_user table.

Question 14

An administrator is troubleshooting an integration that uses Robust Transform Engine (RTE) to ingest software licenses. During testing, records are inserted into staging tables, but the RTE fails to push them into the CMDB via the IRE. Which THREE areas should the administrator inspect to diagnose the failure? (Choose three.)

Accepted Answer

CMDB Integration Results / IRE Execution Logs to identify specific payload rejection reasons.. Option C is correct because the CMDB Integration Results and IRE Execution Logs record the exact outcome of each IRE payload, including rejection reasons such as missing required attributes, duplicate detection, or identification failures, which is the fastest way to see why records are not being inserted into the CMDB. Option D is correct because the IRE requires valid identification rules for the target CI class; if the software license class lacks an active identification rule (or the rule is not published), the IRE cannot uniquely identify or create the CI and will reject the payload. Option E is correct because RTE relies on field mappings and data stream definitions to transform source staging fields into the IRE payload attributes; if a mandatory target attribute is unmapped or mapped incorrectly, the IRE payload will be incomplete and the insert will fail. Option A is not relevant because SLA definitions govern task/response time tracking, not IRE payload processing or CMDB insertion. Option B is not relevant because UI Macros control form rendering and decorators, which have no bearing on RTE-to-IRE data flow or CMDB record creation.

Answer

The Service Level Agreement (SLA) definition table for expired response times.

Answer

The UI Macro table for broken form decorators.

Question 15

An enterprise is setting up automated server discovery across multiple VLANs. Which TWO configuration steps are essential for ensuring Discovery successfully ingests this infrastructure? (Choose two.)

Accepted Answer

Configure Discovery Schedules with target IP ranges and associate appropriate credentials.. Option A is correct because Discovery Schedules define the target IP ranges (or individual IPs) to probe and attach the credentials (Windows, SSH, SNMP, etc.) needed to authenticate and collect data from the discovered servers; without a schedule and valid credentials, Discovery cannot ingest anything. Option B is correct because MID Servers are the on-premises execution components that actually perform the probes and scans; they must have network reachability (routing/firewall rules) to each target VLAN, otherwise the schedules in A have no path to the devices. Option C is incorrect because transform maps typically coalesce on a unique identifier such as serial number, name, or asset tag, not sys_id, which is a system-generated GUID and not a meaningful match key for imported data. Option D is incorrect because Service Mapping uses its own patterns and topology discovery; custom Business Rules on cmdb_ci are not a Discovery ingestion requirement and do not simulate Service Mapping. Option E is incorrect because disabling the Identification and Reconciliation Engine (IRE) globally would break deduplication and CI creation/update, harming rather than helping Discovery ingestion.

Answer

Set all transform maps to coalesce on the sys_id field.

Answer

Create custom Business Rules on cmdb_ci to simulate Service Mapping.

Answer

Disable the Identification and Reconciliation Engine globally to speed up server creation.