CIS-DF Configuration Practice Test 3 — 15 Questions

Question 1

An administrator wants to ensure that all database instance CIs have a populated 'Assigned to' field. Which CMDB Health metric configuration should be updated to track this requirement?

Accepted Answer

Completeness Audit Rules. Completeness Audit Rules in CMDB Health are specifically designed to check whether required fields on CI records are populated. By configuring a completeness rule that targets the 'Assigned to' attribute on the database instance class, the administrator can flag any CI missing that value and track it on the CMDB Health Dashboard. This directly addresses the requirement to ensure the field is filled.

Answer

Compliance Audit Policies

Answer

Correctness Audit Rules

Answer

Identification Rules

Question 2

An administrator is configuring a Robust Transform Engine (RTE) integration to populate the CMDB from a third-party asset management system. Why is RTE recommended over a standard Transform Map for CMDB data loads?

Accepted Answer

RTE processes data through the Identification and Reconciliation Engine (IRE), preventing duplicates and enforcing data integrity.. RTE is recommended for CMDB loads because it routes incoming data through the Identification and Reconciliation Engine (IRE), which applies identification rules, reconciliation rules, and deduplication logic to ensure that only one authoritative CI record is created or updated. This prevents duplicate CIs and enforces data integrity across multiple data sources. A standard Transform Map writes directly to the target table without IRE, so it cannot guarantee deduplication or reconciliation.

Answer

RTE automatically translates foreign languages in source data payloads.

Answer

RTE eliminates the need for staging tables during data imports.

Answer

RTE bypasses all access control lists to accelerate import times.

Question 3

Your organization has deployed multiple datacenters, and engineers want to restrict visibility of specific server CIs so that regional support teams only see their local hardware. Which mechanism should be used to achieve class-level or record-level data segregation in the CMDB?

Accepted Answer

Access Control Lists (ACLs) combined with location or company attributes. Access Control Lists (ACLs) in ServiceNow can be configured with conditions based on CI attributes such as location or company, enabling record-level and class-level segregation. By combining ACLs with these attributes, regional support teams can be restricted to only see CIs that match their region. This is the standard mechanism for data segregation in the CMDB.

Answer

CI Class Manager hiding classes from navigation

Answer

Modifying Discovery Schedule target IP ranges

Answer

Disabling Dependency Views for non-admin users

Question 4

When reviewing relationship data in your CMDB, you notice a large number of 'Orphan' CIs reported on the CMDB Health Dashboard. What does an orphan CI represent?

Accepted Answer

A CI that has no parent or child relationships defined in the cmdb_rel_ci table.. An orphan CI in CMDB Health is defined as a CI that has no relationships in the cmdb_rel_ci table — meaning it is not connected to any parent or child CI. This lack of relationship context makes the CI 'orphaned' in the CMDB graph. The CMDB Health Dashboard specifically reports orphan CIs to highlight missing relationship data.

Answer

A CI whose primary discovery source has been deleted.

Answer

A CI assigned to an inactive user group.

Answer

A CI that has not been scanned by Discovery in over 60 days.

Question 5

Which TWO of the following actions can be performed directly within the CI Class Manager? (Choose two.)

Accepted Answer

Create and modify identification rules for a CI class. The CI Class Manager is the ServiceNow module used to define and maintain the CMDB class model, so option B is correct because it lets you create and modify identification rules (including CI identifiers and reconciliation rules) for a specific CI class directly in that interface. Option C is also correct because the CI Class Manager allows you to add new attributes/fields to a CI class, extending its schema without leaving the class definition UI. Option A is not correct because SLAs for incident resolution are configured in the SLA module (SLA definitions/Workflow), not in CI Class Manager. Option D is not correct because Discovery schedules and network scans are managed in Discovery Schedule/Discovery, not in CI Class Manager. Option E is not correct because graphical multi-table CMDB queries are built with Query Builder/CMDB Query Builder, not within CI Class Manager.

Answer

Configure Service Level Agreements (SLAs) for incident resolution

Answer

Schedule and execute Discovery network scans

Answer

Build graphical multi-table CMDB queries

Question 6

When configuring the Identification and Reconciliation Engine (IRE) for a complex multi-source data environment, which THREE components or concepts are critical to understand and configure properly? (Choose three.)

Accepted Answer

Identification Rules. Identification Rules (C) are critical because they define the independent and dependent match criteria (e.g., serial number, MAC address, or name plus IP) that IRE uses to decide whether an incoming record matches an existing CMDB CI or must create a new one. Reconciliation Definitions (D) are equally essential because they specify, per CI class and data source, the precedence and reconciliation actions (e.g., which source wins, or whether to create/update/ignore) that resolve conflicting attribute values across multiple sources. The Payload format (E) matters because IRE consumes data through the Identification and Reconciliation API, which requires a structured payload with 'items' and 'relations' arrays so that CIs and their relationships are correctly identified and reconciled in a single transaction. By contrast, Standard Legacy Transform Maps without RTE (A) are not part of IRE configuration, since IRE relies on the Robust Transform Engine (RTE) and IRE-specific rules rather than legacy transform maps. Dependency View graphical layout settings (B) only affect how the Dependency View map is rendered visually and have no bearing on identification or reconciliation logic.

Answer

Standard Legacy Transform Maps without RTE

Answer

Dependency View graphical layout settings

Question 7

When designing class hierarchy extensions in the CMDB, which THREE best practices should an implementation specialist follow? (Choose three.)

Accepted Answer

Avoid excessively deep class hierarchies unless justified by distinct identification or attribute requirements.. Option A is correct because keeping class hierarchies shallow avoids unnecessary complexity, reduces inheritance overhead, and prevents fragmentation of CIs across too many tables; a deeper subclass should only be created when it has genuinely distinct identification (e.g., a unique identifier entry) or attribute requirements. Option C is correct because subclassing from the most specific existing parent that already shares the same attributes and behaviors maximizes attribute and behavior reuse, keeps the model normalized, and avoids duplicating fields that already exist higher in the hierarchy. Option E is correct because checking for existing out-of-the-box attributes before adding custom ones prevents redundant or conflicting fields, keeps reporting and CMDB health clean, and avoids breaking baseline functionality that depends on those OOB attributes. Option B is wrong because CI classes must be created and extended through the CI Class Manager, not by manually creating database tables in System Definition, which bypasses the metadata model and breaks identification, reconciliation, and CMDB health. Option D is wrong because creating a brand new base table directly under cmdb for every hardware vendor produces a flat, unnormalized model that duplicates attributes and behaviors instead of leveraging existing classes such as cmdb_ci_hardware or vendor-specific subclasses where appropriate.

Answer

Bypass the CI Class Manager and create database tables directly in System Definition.

Answer

Create a brand new base table directly under cmdb for every new hardware vendor.

Question 8

Which TWO statements are true regarding Configuration Item (CI) relationships in ServiceNow? (Choose two.)

Accepted Answer

Relationships are directional, typically defined between a parent CI and a child CI.. Option B is correct because CI relationships in ServiceNow are directional, defined with a parent-child structure (for example, a server 'Contains' an application, or a database 'Depends on' a server), where the relationship type specifies the direction and nature of the link. Option E is correct because all CI-to-CI relationships are stored as records in the cmdb_rel_ci table, which holds the parent, child, and relationship type fields that define each connection. Option A is incorrect because creating a relationship does not delete CIs; relationships are independent records that can be created or removed without affecting the existence of the CIs themselves. Option C is incorrect because a CI can participate in many relationships simultaneously (for example, a server can contain multiple applications and depend on multiple databases). Option D is incorrect because relationships are stored in the cmdb_rel_ci table as separate records linking two CIs, whereas reference fields such as 'Assigned to' are simple field references on a single record and do not create CI-to-CI relationship records.

Answer

Creating a relationship automatically deletes both CIs if one is updated.

Answer

A CI can only participate in a single relationship across the entire CMDB.

Answer

Relationships and reference fields (like 'Assigned to') function in the exact same manner.

Question 9

An architect is reviewing data ingestion methods for the CMDB. Which THREE integration mechanisms natively support or integrate with the Identification and Reconciliation Engine (IRE)? (Choose three.)

Accepted Answer

ServiceNow Discovery. ServiceNow Discovery (A) is correct because it is one of the primary native data sources that feeds the CMDB through the Identification and Reconciliation Engine, sending discovered CIs to IRE for identification and reconciliation. ServiceGraph Connectors (B) are correct because they are built specifically to push third-party data into the CMDB via IRE, using the IRE API to identify and reconcile records. IntegrationHub ETL (C) is correct because it is the recommended ETL framework for CMDB data ingestion and natively invokes IRE to identify and reconcile incoming records. Manual CSV import via standard System Import Sets (D) is not correct because it relies on transform maps and does not natively invoke IRE unless specifically configured with an IRE-based transform, so it is not a native IRE integration mechanism. Standard Legacy Transform Maps without RTE (E) are not correct because they bypass the Robust Transform Engine and IRE, writing directly to CMDB tables without identification and reconciliation processing.

Answer

Manual CSV file import via standard System Import Sets

Answer

Standard Legacy Transform Maps without RTE

Question 10

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 11

An administrator is planning a custom CMDB extension project. Which THREE factors should be evaluated when deciding whether to create a new CI class or add attributes to an existing class? (Choose three.)

Accepted Answer

Whether specialized relationships or lifecycle workflows apply specifically to these items. Option A is correct because a new CI class is justified when the items need their own specialized relationship types or lifecycle workflows that do not apply to the existing parent class, since class-specific relationships and workflows cannot be cleanly modeled as attributes. Option B is correct because if the items require unique attributes that do not apply to the parent class, adding them to the parent would pollute the parent schema and force irrelevant fields onto other CIs, so a subclass is the proper design. Option E is correct because distinct identification rules (for example, different reconciliation keys or discovery source identifiers) must be defined at the class level, and items needing their own identification logic warrant a separate CI class rather than attributes on an existing one. Option C is incorrect because ITIL user license counts are a commercial/administrative concern and have no bearing on CMDB class modeling decisions. Option D is incorrect because table form background color is a cosmetic UI preference and is irrelevant to the data model design choice between a new class and added attributes.

Answer

The number of ITIL user licenses assigned to the platform

Answer

The preferred background color of the table form layout

Question 12

An administrator needs to create a new custom Configuration Item class to track specialized network routers. Where should this class be created within the ServiceNow platform?

Accepted Answer

Configuration > CI Class Manager. Custom CI classes should be created using the CI Class Manager (Configuration > CI Class Manager) in ServiceNow. This tool provides a guided interface to define the class hierarchy, attributes, and relationships, ensuring proper integration with the CMDB and CSDM. It also allows you to extend existing classes and apply class-specific configurations.

Answer

System Definition > Tables

Answer

System Dictionary > New Class

Answer

Configuration > CMDB Properties

Question 13

A project team wants to establish a parent-child relationship between a Business Application CI and several Server CIs to represent hosting dependencies. Which relationship type should they configure?

Accepted Answer

Hosted on::Hosts. The 'Hosted on::Hosts' relationship type is the correct CSDM relationship to represent that a Business Application (or Application Service) is hosted on a Server CI. It establishes a parent-child dependency where the application is 'Hosted on' the server, and the server 'Hosts' the application. This accurately models the hosting dependency the project team wants to represent.

Answer

Depends on::Used by

Answer

Runs on::Runs

Answer

Connected by::Connected by

Question 14

During a review of the CMDB class hierarchy, an architect notices that a custom class extending cmdb_ci_hardware was created without a corresponding identification rule in the Identification and Reconciliation Engine (IRE). What is the primary risk of this configuration?

Accepted Answer

Inbound discovery payloads may create duplicate records because the IRE falls back to out-of-the-box system-level rules or creates new records without matching.. The IRE relies on identification rules to match incoming discovery payloads to existing CIs. Without a class-specific identification rule, the engine falls back to inherited or system-level rules, which may not match the custom class's unique attributes, resulting in duplicate CI records or unintended new inserts. This undermines CMDB data integrity and can cascade into incorrect relationship mapping and reporting.

Answer

The CMDB Health dashboard will automatically delete all records in this custom table.

Answer

Business rules on the base cmdb table will prevent any inserts into the custom table.

Answer

CIs belonging to this class cannot be viewed in Dependency Views.

Question 15

An implementer is reviewing the base tables of the CMDB. Which table serves as the ultimate parent class for virtually all Configuration Item classes in ServiceNow?

Accepted Answer

cmdb_ci. The cmdb_ci table is the ultimate parent class for virtually all Configuration Item classes in ServiceNow. Every CI class (e.g., cmdb_ci_server, cmdb_ci_appl) extends cmdb_ci through table inheritance, making it the root of the CMDB class hierarchy. This allows common attributes and relationships to be defined once at the top.

Answer

cmdb

Answer

task

Answer

cmdb_rel_ci