CIS-DF Ingest Practice Test 2 — 15 Questions

Question 1

When reviewing the Identification and Reconciliation Engine (IRE) payload processing results, an administrator notices an error stating 'Mandatory attributes missing for identification'. What does this error signify?

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

Accepted Answer

The incoming payload lacks one or more attributes specified in the identification rule criteria for that class.. The error 'Mandatory attributes missing for identification' means the incoming payload does not contain one or more attributes that the identification rule for that CI class requires to match against existing records. Without those attributes, IRE cannot determine whether the CI already exists, so it rejects the identification attempt.

Answer

The Transform Map is missing mandatory field mappings.

Answer

The target CI table has mandatory dictionary fields that are not populated by the form layout.

Answer

The Discovery source name is invalid.

Question 2

An organization uses Service Mapping to map a critical e-commerce application. During mapping, a custom web server process is discovered on a host, but it fails to establish a relationship with the underlying software installation. Where should the administrator verify or configure the identification rules for process classification and mapping?

Accepted Answer

In Service Mapping Configuration, review and adjust Process Classifiers and Application Patterns.. Process classification and identification for Service Mapping are configured via Application Patterns and Process Classifiers within Service Mapping configuration.

Answer

In Robust Transform Engine (RTE) definitions, map the process table to the software installation table.

Answer

In CI Class Manager, modify the Identification Rule for cmdb_ci_appl.

Answer

In Data Source Precedence rules, set Discovery as the primary source for process tables.

Question 3

Which ServiceNow utility should an administrator use to view and test identification rules, simulated payloads, and payload processing results for troubleshooting CI ingestion issues?

Accepted Answer

IRE Test Payload module (or Debug IRE). The IRE Test Payload module (or Debug IRE) is specifically designed to test identification rules, simulate payloads, and view processing results, making it the correct tool for troubleshooting CI ingestion issues. It allows administrators to validate how the Identification and Reconciliation Engine will process incoming data without affecting the production CMDB. This utility provides detailed logs and outcomes for each payload, helping diagnose why CIs are not being identified or reconciled correctly.

Answer

Discovery Log Analyzer

Answer

Transform Map Simulator

Answer

Service Mapping Workbench

Question 4

An organization is ingesting printer CIs from a legacy asset system via Import Sets. Some incoming records contain a serial number with leading/trailing whitespace, causing the IRE to treat them as distinct CIs rather than matching existing ones. Where can data normalization be applied to clean this data before it reaches the IRE?

Accepted Answer

Use Robust Transform Engine (RTE) field transformations (such as Trim or Regex) during the data ingestion mapping phase.. The Robust Transform Engine (RTE) is the ServiceNow data transformation framework that runs during the Import Set transform mapping phase, before records are handed to the IRE. RTE field transformations such as Trim, Regex, or custom transform functions can strip leading/trailing whitespace from the serial number field so the cleaned value is what the IRE evaluates against identification rules. Because normalization happens upstream of identification, existing CIs match correctly and no duplicates are created.

Answer

Modify the IRE Identification Rule to automatically ignore whitespace.

Answer

Write a Client Script on the target cmdb_ci table to strip whitespace upon insert.

Answer

Configure a Data Policy to reject records containing whitespace.

Question 5

An enterprise has multiple disjointed data sources feeding network gear into the CMDB. Source A provides high-accuracy IP data, while Source B provides high-accuracy serial numbers. However, their discovery source names differ slightly in casing and format across jobs. How does the IRE handle discovery source strings during reconciliation?

Accepted Answer

Discovery source strings are case-sensitive and must be standardized; inconsistent naming causes the IRE to treat them as distinct data sources, bypassing intended precedence rules.. The IRE (Identification and Reconciliation Engine) treats discovery source strings as case-sensitive identifiers. If Source A is named 'SourceA' and Source B is named 'sourcea', the IRE considers them distinct data sources, which means precedence rules configured for one will not apply to the other. This can cause the IRE to bypass intended source precedence and produce inconsistent reconciliation results, so administrators must standardize discovery source naming.

Answer

The IRE maps discovery sources based on IP address ranges rather than the discovery source string.

Answer

The IRE automatically normalizes all discovery source strings to lowercase and strips special characters.

Answer

Discovery source names only affect reporting and have no impact on IRE reconciliation behavior.

Question 6

An administrator is troubleshooting a Scheduled Data Import that uses an IntegrationHub REST step to pull server data. The import completes, but no CIs are created or updated in the CMDB, and the import set rows show a status of 'Processed'. Where should the administrator check to see if the IRE rejected the payload?

Accepted Answer

Check the CMDB Integration Results (cmdb_integration_log) or IRE processing logs for detailed payload error messages.. The Identification and Reconciliation Engine (IRE) processes import set rows after they are marked 'Processed' by the transform. When IRE rejects a payload—due to missing required attributes, duplicate detection conflicts, or failed reconciliation rules—it does not create or update CIs, but the import set row status remains 'Processed' because the transform itself succeeded. Detailed rejection reasons, including the specific payload and rule that failed, are written to the CMDB Integration Results table (cmdb_integration_log) and IRE processing logs, not to the standard transform warnings. Therefore, option B is the correct place to investigate IRE rejections.

Answer

Check the System Log (syslog) for standard warning messages tagged with 'TransformMap'.

Answer

Review the Email Notifications table for failed ingestion alerts.

Answer

Inspect the Discovery Status dashboard.

Question 7

When configuring an identification rule for a custom hardware CI class, an administrator can select multiple attributes to form a compound identification rule. What is the operational significance of selecting multiple attributes within a single rule entry?

Accepted Answer

All specified attributes in the rule entry must match an existing CI record for the IRE to identify it as a match.. In a compound identification rule, all specified attributes must match an existing CI for the IRE to consider it a match.

Answer

The IRE will consider it a match if any single attribute matches the incoming payload.

Answer

The IRE will automatically merge records if any two attributes match.

Answer

Multiple attributes are only used for reporting and have no effect on CI identification.

Question 8

An organization implements CSDM and wants to ingest business applications and their hosting environments. They receive a payload containing a Business Application CI that references a non-existent Application Service CI. How does the IRE handle references to related CIs that do not yet exist in the CMDB?

Accepted Answer

If the payload includes nested identification blocks for the related CI, the IRE will create the missing CI first and then establish the relationship.. The IRE can handle references to non-existent CIs if the payload includes nested identification blocks for those related CIs. In that case, the IRE will create the missing CI first (using the nested identification block) and then establish the relationship. This allows for the ingestion of complex CI hierarchies in a single payload.

Answer

References to non-existent CIs are automatically converted into Incident records in IT Service Management.

Answer

The IRE automatically creates dummy placeholder records for any unresolving reference.

Answer

The entire payload is always aborted if any single related reference cannot be resolved immediately.

Question 9

An administrator is setting up a ServiceNow Discovery schedule for a subnet in a restricted data center. The Discovery schedule runs successfully, but no new CIs are populated in the CMDB. Upon checking the Discovery status, the probes completed, but the horizontal discovery pattern logs indicate a 'Permission Denied' on WMI/SSH commands. Where should the administrator verify the credentials used for this ingestion?

Accepted Answer

In the Credentials table (discovery_credentials) or Credential Aliases, ensuring the correct protocol credentials are mapped to the IP range.. Discovery and ingestion via credentials are managed through Credential Aliases and the Credentials table.

Answer

In CI Class Manager under Discovery Source Precedence.

Answer

In the CMDB Health Dashboard under Audit Rules.

Answer

In the Robust Transform Engine source properties.

Question 10

An organization is migrating from a legacy configuration management database to ServiceNow. They load initial server records using custom import sets without the IRE. Later, they enable ServiceNow Discovery. They notice that every discovered server creates a duplicate CI right alongside the imported record. What caused this duplicate creation?

Accepted Answer

The legacy import bypassed the IRE, failing to populate the sys_object_source tracking table with the correct native keys and discovery source identifiers.. Records ingested without the IRE lack the proper sys_object_source tracking and native identifier linkage expected by Discovery and the IRE, resulting in failure to recognize existing records.

Answer

Discovery is hardcoded to ignore any records created by Transform Maps.

Answer

The cmdb_ci table has a business rule that forces duplicate insertion for security purposes.

Answer

Data Source Precedence rules were not set to 'Manual' before running Discovery.

Question 11

An administrator is configuring a Robust Transform Engine (RTE) definition for a complex CMDB data import. They need to ensure that if an incoming record fails identification or has missing mandatory attributes, the entire batch does not fail, but instead logs an error for that specific row. Where is this error handling behavior managed in RTE?

Accepted Answer

Configure error handling options within the Robust Transform Engine Data Stream Definition and field processors to capture row-level exceptions.. In RTE, error handling is configured within the Data Stream Definition and field processors. This allows row-level error capture, so if a record fails identification or has missing mandatory attributes, the error is logged for that specific row without failing the entire batch.

Answer

Set the Import Set transform map property to 'Ignore Errors' globally.

Answer

Modify the IRE engine configuration property 'glide.cmdb.ire.abort_on_error' to false.

Answer

Write a global Business Rule on sys_import_set_row to catch exceptions.

Question 12

An administrator wants to check which identification rules are active for the `cmdb_ci_computer` class. Where in the ServiceNow user interface should they navigate?

Accepted Answer

CI Class Manager -> Select cmdb_ci_computer -> Identification Rule. The CI Class Manager is the central place to view and manage identification rules for a specific CI class. Navigating to CI Class Manager, selecting the cmdb_ci_computer class, and then viewing the Identification Rule tab shows the active rules. This is the correct path in the ServiceNow UI.

Answer

Discovery -> Identification -> Classes

Answer

Configuration -> CMDB Properties -> Rules

Answer

System Definition -> Identification Rules

Question 13

An implementer is configuring Service Graph Connectors to ingest infrastructure data into ServiceNow. Service Graph Connectors utilize the Robust Transform Engine (RTE) and the IRE. What is the primary benefit of using Service Graph Connectors over legacy Import Sets for third-party data ingestion?

Accepted Answer

They provide pre-built mapping, utilize the IRE for deduplication, and ensure data aligns with CSDM and CMDB data standards.. Service Graph Connectors provide pre-built mappings, leverage the IRE for deduplication and reconciliation, and ensure ingested data aligns with the Common Service Data Model (CSDM) and CMDB data standards. This reduces implementation effort, improves data quality, and ensures consistency across the CMDB compared to legacy Import Sets that require manual mapping and often bypass IRE.

Answer

They allow administrators to bypass CI Class Manager identification rules entirely.

Answer

They completely bypass the database and store CIs in memory for faster reporting.

Answer

They eliminate the need for any network connectivity between the third-party tool and ServiceNow.

Question 14

An administrator notices that when Discovery updates a virtual machine, the 'Environment' attribute populated by a manual spreadsheet import is overwritten, despite Data Source Precedence rules being configured. Upon investigation, they find that both sources are writing with the exact same discovery source string value. What is the correct way to resolve this conflict?

Accepted Answer

Configure the manual import to use a distinct discovery source string (e.g., 'Manual Import' or 'Spreadsheet') rather than sharing the default discovery source string.. Data Source Precedence rules rely on the discovery source string to differentiate sources. If both the manual import and Discovery use the same discovery source string, the system cannot distinguish between them, so precedence rules won't apply correctly. Assigning a distinct discovery source string to the manual import allows precedence rules to work as intended.

Answer

Enable 'Coalesce' on the spreadsheet import transform map.

Answer

Modify the CI Class Manager identification rule to exclude the Environment attribute.

Answer

Set the table to read-only for the discovery integration user.

Question 15

An administrator is troubleshooting a custom integration where incoming JSON payloads for routers contain an array of interfaces. When the payload is processed, the parent router updates successfully, but none of the interface CIs are created. Reviewing the IRE payload structure shows that the interface objects are nested inside a property named `network_interfaces`. What must be configured in the IRE payload mapping to successfully process these child items?

Accepted Answer

Define a related items block in the payload structure mapping `network_interfaces` to the corresponding child class and relationship type.. In IRE payload mapping, nested arrays of child items must be defined in a related items block. This block maps the array property (e.g., `network_interfaces`) to the appropriate child class and relationship type, enabling IRE to create the child CIs and establish relationships with the parent router.

Answer

Modify the Transform Map coalesce script to loop through the array.

Answer

Create a Business Rule to split the JSON array into individual rows on the import staging table.

Answer

Add 'network_interfaces' as a comma-separated string column in the base cmdb_ci table dictionary.