CIS-DF Configuration — Timed 15 Questions

Question 1

A team is designing a custom CMDB class for virtual storage arrays. They need to ensure that when a physical host is deleted, the dependent virtual storage array records are also cleaned up. Where should this cascading delete behavior be defined?

15 minute time limit — choose an answer to begin.

Accepted Answer

CI Class Manager under the relationship rules section. Cascading delete behavior for CMDB CIs is defined in CI Class Manager under the relationship rules section, where administrators configure how dependent CIs are handled when a parent CI is deleted. This is the supported, upgrade-safe location for defining cascade rules, rather than writing custom business rules or scripts.

Answer

Business Rules on the cmdb_ci table

Answer

Data Dictionary [sys_dictionary] attribute settings

Answer

IRE payload processor scripts

Question 2

An administrator is reviewing the CMDB class hierarchy and needs to modify attributes that apply to all types of servers (Linux, Windows, AIX). Which table should be updated to ensure all server sub-classes inherit the new attribute?

Accepted Answer

cmdb_ci_server. The correct table is cmdb_ci_server because it is the parent class for all server types (Linux, Windows, AIX) in the CMDB class hierarchy. Modifying attributes at this level ensures that all sub-classes (e.g., cmdb_ci_win_server, cmdb_ci_linux_server, cmdb_ci_aix_server) inherit the new attribute. This follows ServiceNow's CMDB class inheritance model, where child classes automatically inherit attributes from their parent. Thus, updating cmdb_ci_server applies the change to all server types without needing to modify each sub-class individually.

Answer

cmdb_ci

Answer

cmdb_ci_win_server

Answer

cmdb_ci_computer

Question 3

Your organization wants to ensure that all virtual machine CIs contain a mandatory 'Environment' tag attribute. Where should this attribute be added to ensure it is inherited by all virtual machine subclasses?

Accepted Answer

cmdb_ci_vm_instance table. Adding the 'Environment' attribute to the cmdb_ci_vm_instance table ensures it is inherited by all virtual machine subclasses, because cmdb_ci_vm_instance is the parent class for VM instance types (e.g., cmdb_ci_vmware_instance, cmdb_ci_ec2_instance). Attributes defined on a parent class are automatically available on child classes in ServiceNow's class hierarchy. This is the correct place to enforce a mandatory attribute across all VM CIs.

Answer

cmdb_ci_appl table

Answer

cmdb_rel_ci table

Answer

sys_user table

Question 4

Which ServiceNow table is designated as the universal base table from which all Configuration Item classes ultimately inherit?

Accepted Answer

cmdb. The cmdb table is the root table for all configuration items in ServiceNow.

Answer

cmdb_ci

Answer

cmdb_rel_ci

Answer

task

Question 5

An administrator needs to create a new relationship type between databases and storage volumes that does not exist out-of-the-box. Which table should be updated to define this new relationship type?

Accepted Answer

cmdb_rel_type. The cmdb_rel_type table stores the definitions of relationship types in the CMDB. To create a new relationship type between databases and storage volumes, you must add a new record to this table specifying the parent class, child class, and relationship type name. This is the correct table for defining relationship types.

Answer

cmdb_ci_rel_server

Answer

cmdb_rel_ci

Answer

sys_choice

Question 6

When analyzing CMDB data quality, you discover multiple records representing the exact same physical server, but they were created by different discovery tools with slightly different naming conventions. The IRE successfully merges them during updates, but initial creation still generates duplicates. What is the root cause?

Accepted Answer

Reconciliation definitions are set to allow multiple sources.. The root cause is twofold: the reconciliation definitions are configured to allow multiple sources (Option A), and the identification rules for the server class lack matching criteria that cover the unique attributes provided by both discovery tools (Option D). When reconciliation allows multiple sources, the IRE does not enforce a single authoritative source, so duplicates can persist if identification rules fail to uniquely match records. Additionally, if identification rules do not include attributes that are common to both tools (e.g., serial number, MAC address), the IRE cannot correlate the records during initial creation, resulting in duplicates. Both conditions together explain why merging occurs only during updates (when reconciliation runs) but not at creation.

Answer

The cmdb_rel_ci table is missing indexes.

Answer

The CMDB Health Dashboard needs to be restarted.

Question 7

A company has implemented strict data governance where CIs that have not been discovered or updated in over 90 days are considered stale. Where should this threshold be configured in ServiceNow?

Accepted Answer

CMDB Health Dashboard Correctness settings. Stale CI thresholds are configured within the Correctness settings of the CMDB Dashboard / CI Class Manager audit rules.

Answer

CI Class Manager relationship rule definitions

Answer

Discovery Schedule properties

Answer

Data Archiving rule definitions

Question 8

Which TWO metrics are part of the Correctness pillar in the CMDB Health Dashboard? (Choose two.)

Accepted Answer

Orphans. In the CMDB Health Dashboard, the Correctness pillar measures whether CIs are properly related and free of structural data problems, and its two metrics are Orphans (B) and Duplicates (E). Orphans (B) is correct because it counts CIs that have no relationships to any other CI, which is a correctness defect since a CI with no relations cannot be validated as part of the CMDB graph. Duplicates (E) is correct because it identifies multiple CIs that appear to represent the same real-world item, another correctness defect that undermines the integrity of the CMDB. The other options belong to different pillars: Software license audit compliance (A) relates to the Compliance pillar, while Required fields populated (C) and Recommended attributes filled (D) are Completeness pillar metrics, so they are not part of Correctness.

Answer

Software license audit compliance

Answer

Required fields populated

Answer

Recommended attributes filled

Question 9

Which TWO pillars comprise the standard CMDB Health Dashboard scoring model? (Choose two.)

Accepted Answer

Correctness. The CMDB Health Dashboard in ServiceNow scores CI data quality across three standard pillars: Correctness, Completeness, and Compliance. Correctness (A) is correct because it measures whether CI records contain accurate, valid data — for example, checking for duplicate CIs, orphan CIs, and CIs that fail audit or certification checks. Completeness (E) is correct because it measures whether required CI attributes and related records (such as relationships) are populated, flagging CIs with missing mandatory fields. Availability (B), Performance (C), and Scalability (D) are not part of the CMDB Health scoring model; those are operational or infrastructure characteristics, not data-quality pillars of the dashboard.

Answer

Availability

Answer

Performance

Answer

Scalability

Question 10

When configuring Identification Rules in the CI Class Manager, which THREE attributes or criteria types are commonly utilized as unique identifiers? (Choose three.)

Accepted Answer

Serial Number. In the CI Class Manager, Identification Rules use attributes that uniquely distinguish a Configuration Item within its class. Serial Number (A) is a canonical hardware identifier that manufacturers assign uniquely per device, making it a primary choice for identifying physical CIs. IP Address (B) is commonly used as a unique identifier for network devices and interfaces, since it uniquely locates a node on a network at a given time. MAC Address (C) is a globally unique hardware address burned into network interfaces, so it reliably identifies network-capable CIs. Cost Center (D) and Department (E) are organizational or financial attributes that many CIs can share, so they lack the uniqueness required for identification rules and are not used as unique identifiers.

Answer

Cost Center

Answer

Department

Question 11

An enterprise is designing a complex class hierarchy for IoT devices. They decide to create a multi-level extension: cmdb_ci > cmdb_ci_hardware > cmdb_ci_compute > cmdb_ci_iot. What happens to the table inheritance and record storage when a new record is inserted into cmdb_ci_iot?

Accepted Answer

The record is stored in the cmdb_ci_iot table, and database views or UNION queries allow parent tables to display the record.. ServiceNow CMDB uses true table inheritance where each class is a physical database table. When a record is inserted into cmdb_ci_iot, it is stored in the cmdb_ci_iot table itself, and parent tables (cmdb_ci_compute, cmdb_ci_hardware, cmdb_ci) access it through database views or UNION-based queries that traverse the inheritance chain. This is the standard ServiceNow table-per-class inheritance model.

Answer

All attributes are stored in a single flat cmdb_ci table with discriminator columns.

Answer

The platform throws an error because more than two levels of extension are prohibited in the CMDB.

Answer

Records are stored exclusively in the cmdb_ci table, and child tables only store metadata.

Question 12

When designing a custom CI relationship between two new classes, an administrator needs to ensure that relationship suggestions appear correctly when using Dependency Views. Where are relationship rules defined to control valid parent-child pairings?

Accepted Answer

Suggested Relationships (Configuration > CI Relationships > Suggested Relationships). Suggested Relationships (Configuration > CI Relationships > Suggested Relationships) is the correct location because this module defines which parent-child class pairings are valid and therefore offered as relationship suggestions in Dependency Views and CI relationship editors. Each record specifies a parent class, child class, and relationship type, controlling what the UI proposes when users build dependency maps.

Answer

Dictionary Overrides on cmdb_rel_ci

Answer

CI Class Manager > Relationship Tab

Answer

Discovery Schedule filters

Question 13

When configuring Identification and Reconciliation Engine (IRE) rules for a specialized hardware class, an administrator needs to understand how identification entries and criteria work. Which THREE statements are true regarding IRE rules? (Choose three.)

Accepted Answer

Attributes listed within a single identification criterion are evaluated using AND logic.. Option C is correct because within a single identification criterion, all listed attributes are combined with AND logic, so a CI matches only when every attribute in that criterion agrees. Option D is correct because an identification rule is invalid without at least one criterion attribute; the IRE needs at least one attribute to compare against incoming data to identify or create a CI. Option E is correct because when a rule contains multiple criteria, the IRE evaluates them in order as fallback steps, effectively OR logic between criteria, so a match on any criterion satisfies the rule. Option A is wrong because IRE identification rules apply to data ingested through Discovery, Service Graph Connectors, and other CMDB integration sources, not only Service Graph Connectors. Option B is wrong because IRE does not automatically create custom relationship types for every identification rule; relationship types are defined separately and must already exist to be used.

Answer

Identification rules only apply when data is ingested via Service Graph Connectors, ignoring standard Discovery.

Answer

The IRE automatically creates custom relationship types for every identification rule created.

Question 14

An administrator needs to understand where a newly discovered database instance CI's attributes are stored across the CMDB table hierarchy. Which table represents the base class for all Configuration Items in ServiceNow?

Accepted Answer

cmdb. The base class for all CIs in the CMDB is cmdb, which contains core attributes inherited by all child classes.

Answer

cmdb_rel_ci

Answer

sys_object

Answer

cmdb_ci

Question 15

An administrator is reviewing the configuration of CI relationships within the platform. Which THREE characteristics apply to the cmdb_rel_ci table? (Choose three.)

Accepted Answer

It supports the Dependency Views map to visually display upstream and downstream impacts.. Option A is correct because the cmdb_rel_ci table is the underlying data source for Dependency Views, which traverse parent/child relationships to render upstream and downstream impact maps. Option C is correct because each relationship record references a relationship type record (sys_relationship_type) whose 'Type' field defines the nature of the link, such as 'Runs on :: Runs on' or 'Depends on :: Used by'. Option E is correct because cmdb_rel_ci stores the relationship directionally via the 'parent' and 'child' reference fields, each pointing to a Configuration Item record. Option B is incorrect because discovery updates do not purge relationship records; relationships are maintained or reconciled, not wholesale deleted on parent CI update. Option D is incorrect because CI attribute values such as IP address and serial number are stored on the CI's own class table (for example cmdb_ci_netgear), not on the cmdb_rel_ci relationship table.

Answer

It automatically purges all relationship records whenever a parent CI is updated by a discovery schedule.

Answer

It stores unique configuration item attribute values such as IP address and serial number for network gear.