CIS-DF Configuration Practice Test 4 — 15 Questions

Question 1

A company needs to store custom serial number attributes for specific physical storage devices. Where should an administrator add these custom attributes to ensure they are properly managed and tracked?

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

Accepted Answer

Using the CI Class Manager by selecting the target storage CI class and adding the attribute under the Attributes tab. The CI Class Manager is the correct place to add custom attributes to a specific CI class. An administrator selects the target storage CI class (e.g., cmdb_ci_storage_device or a more specific subclass), navigates to the Attributes tab, and adds the new attribute there. This ensures the attribute is properly associated with the class, inheritable by subclasses, and managed within the CMDB schema.

Answer

By editing the cmdb_ci_hardware form layout directly

Answer

Through the Discovery Definition > CI Attributes module

Answer

Directly in the Data Dictionary via System Definition > Dictionary by modifying the base cmdb table

Question 2

Which module allows an administrator to visualize the relationships between CIs in a graphical node-and-link format?

Accepted Answer

Dependency Views. Dependency Views is the ServiceNow CMDB module that renders CIs and their relationships as an interactive node-and-link graph, letting administrators visually trace upstream and downstream dependencies. It pulls relationship data from the cmdb_rel_ci table and displays it in a hierarchical, graphical format. This is the standard tool for impact analysis and relationship visualization in the CMDB.

Answer

CI Class Manager

Answer

Map Canvas

Answer

CMDB Dashboard

Question 3

An administrator needs to deprecate an old custom CI class that is no longer in use. What is the recommended best practice in the CI Class Manager?

Accepted Answer

Use the CI Class Manager to deprecate or safely review dependent records and rules before taking action.. The CI Class Manager provides a safe, guided way to deprecate or delete a custom CI class, including checks for dependent records, identification rules, and relationships before action is taken. Best practice is to use this tool to review dependencies and deprecate the class rather than deleting it outright, preserving data integrity and audit history.

Answer

Delete the table directly from the Tables and Columns module without checking for records.

Answer

Deactivate all identification rules and leave the table orphaned.

Answer

Rename the table name prefix to 'z_deprecated_' directly in the dictionary.

Question 4

When configuring identification rules for a custom CI class via the CI Class Manager, an administrator includes multiple criteria attributes. How does the Identification and Reconciliation Engine (IRE) process these criteria?

Accepted Answer

The IRE evaluates criteria attributes as an AND condition within the criterion, requiring all specified attributes to match.. In ServiceNow's Identification and Reconciliation Engine (IRE), a criterion within an identification rule contains multiple attributes that are evaluated together as an AND condition — all specified attributes must match the incoming payload for the CI to be identified. This ensures precise matching and prevents false positives from partial attribute matches.

Answer

Criteria attributes are ignored unless a Discovery source is explicitly named in the payload.

Answer

The IRE randomly selects one attribute to perform the lookup based on payload weight.

Answer

The IRE evaluates attributes as an OR condition, matching on any single attribute present in the payload.

Question 5

A team is importing legacy server data into the CMDB using an Import Set. To ensure that relationships between servers and switches are created accurately alongside the CI imports, which feature should they leverage?

Accepted Answer

IntegrationHub ETL or Robust Transform Engine (RTE) relationship processors. IntegrationHub ETL and the Robust Transform Engine (RTE) provide relationship processors that can create or update CI relationships during the transform of an Import Set, ensuring servers and switches are linked correctly as part of the same import. These processors handle the lookup and creation of related CIs and their cmdb_rel_ci entries in a single pass. This is the recommended approach for accurate, scalable relationship creation during bulk imports.

Answer

Standard Transform Maps without script writing

Answer

Database Views joining the sys_user and cmdb_ci tables

Answer

Manual entry via Dependency Views after import completion

Question 6

Where can an administrator view overall metrics regarding CMDB data quality, including completeness, correctness, and compliance?

Accepted Answer

Configuration > CMDB Health Dashboard. The CMDB Health Dashboard, accessed via Configuration > CMDB Health Dashboard, is the dedicated ServiceNow interface that aggregates CMDB data quality metrics across the three core pillars: completeness, correctness, and compliance (plus relationship health and duplicate metrics). It provides KPI scores, drill-downs to failing CIs, and trend visualization specifically for CMDB health.

Answer

System Diagnostics > Stats

Answer

Performance Analytics > Dashboards > CI Quality

Answer

Reports > View/Run > CMDB Quality

Question 7

An administrator needs to ensure that specific critical attributes of a Server CI cannot be overwritten by low-priority discovery sources, while higher-priority integrations can update them. Where is this behavior configured?

Accepted Answer

Reconciliation Definitions. Reconciliation Definitions in ServiceNow specify, per CI class and attribute, which discovery source has precedence and whether lower-priority sources can overwrite values. Configuring a reconciliation definition for the Server class with the critical attributes set to be updated only by higher-priority sources enforces the required behavior.

Answer

Discovery Source Exclusion rules

Answer

CI Class Manager attribute properties

Answer

Access Control Lists (ACLs) on the cmdb_ci table

Question 8

A company deploys a multi-tenant cloud environment. They need to ensure that CIs belonging to Tenant A are logically segregated and cannot be viewed or modified by users belonging to Tenant B, while utilizing a single shared CMDB. Which ServiceNow feature should be configured?

Accepted Answer

Domain Separation. Domain Separation is the ServiceNow feature designed to logically segregate data, processes, and users across multiple tenants within a single instance. By assigning CIs and users to domains, you ensure that Tenant A's users cannot see or modify Tenant B's CIs, even though both reside in the same CMDB tables. This is the only option that provides true multi-tenant isolation at the data level.

Answer

Data Policies enforced on the cmdb_ci table

Answer

Row-level Security via standard ACLs only

Answer

CMDB Baseline auditing

Question 9

Which table stores the actual relationship records connecting configuration items in the ServiceNow CMDB?

Accepted Answer

cmdb_rel_ci. In ServiceNow, the cmdb_rel_ci table stores the actual relationship instances between configuration items — each row represents one directed relationship (parent, child, type) linking two CIs. The relationship type itself is defined in cmdb_rel_type, but the concrete records connecting CIs live in cmdb_rel_ci.

Answer

cmdb_ci_rel

Answer

task_cmdb_ci_rel

Answer

sys_m2m_cmdb

Question 10

An administrator is troubleshooting an issue where duplicate CIs are being created by an external data feed despite having an identification rule configured. Upon inspecting the payload, they notice the payload uses a custom identifier field not included in the IRE rule. What is the correct way to resolve this?

Accepted Answer

Update the identification rule in the CI Class Manager to include the new attribute as part of the identification criteria.. The correct fix is to update the identification rule in the CI Class Manager to include the custom identifier field as part of the identification criteria. The IRE uses identification rules to match incoming CIs to existing ones; if the payload's unique identifier isn't in the rule, IRE cannot match and creates duplicates. Adding the attribute ensures IRE recognizes the custom identifier and reconciles correctly.

Answer

Modify the transform map script to delete duplicate records after insertion.

Answer

Write a Business Rule on cmdb_rel_ci to merge records with matching names.

Answer

Disable the Identification and Reconciliation Engine for external feeds.

Question 11

A ServiceNow architect is designing a CMDB architecture where CIs from multiple disparate discovery tools need to be ingested. To prevent race conditions and conflicting updates between tools updating the same CIs simultaneously, what mechanism should be utilized?

Accepted Answer

The Identification and Reconciliation Engine (IRE) processing queue and source precedence rules. The Identification and Reconciliation Engine (IRE) processes incoming CI data through a queue and applies source precedence rules to resolve conflicts when multiple discovery sources update the same CI. This prevents race conditions by serializing updates and ensuring a deterministic winner based on configured precedence. It is the standard mechanism for multi-source CMDB ingestion.

Answer

Manual approval workflows for every inbound payload

Answer

Asynchronous business rules triggered on insert to pause payloads

Answer

Database locks enforced via Table Administration settings

Question 12

An administrator is preparing to create a new custom CI class hierarchy. Which TWO actions should be performed as best practice during this process? (Choose two.)

Accepted Answer

Extend the most specific existing parent class (e.g., cmdb_ci_hardware) rather than the base cmdb_ci table.. Option C is correct because best practice when building a custom CI class hierarchy is to extend the most specific existing parent class (for example, cmdb_ci_hardware or cmdb_ci_server) so the new class inherits relevant attributes, relationships, and behaviors instead of duplicating them; extending the base cmdb_ci table directly is discouraged because it produces an overly generic class with unnecessary attributes. Option D is correct because every CI class must have identification rules defined in the CI Class Manager so that discovery sources and imports can correctly match and reconcile CIs (using identifiers such as serial number, name, or MAC address) rather than creating duplicates. Option A is wrong because CMDB Health audits should not be disabled globally; they are used to monitor data quality and can be scoped or tuned, but turning them off undermines governance. Option B is wrong because extending the root cmdb table directly is explicitly discouraged as it maximizes irrelevant inherited attributes and breaks class modeling best practices. Option E is wrong because custom relationships should be created as relationship types in the CI Class Manager or via the relationship type dictionary, not by directly editing the cmdb table dictionary, which risks upgrade and integrity issues.

Answer

Disable CMDB Health audits globally before creating the class table.

Answer

Always extend the root cmdb table directly to maximize attribute availability.

Answer

Create custom relationships directly on the cmdb table dictionary.

Question 13

Which TWO metrics are tracked out-of-the-box as part of the CMDB Health Dashboard? (Choose two.)

Accepted Answer

Completeness. The CMDB Health Dashboard in ServiceNow tracks three out-of-the-box health metrics: Completeness, Correctness, and Compliance. Option B (Completeness) is correct because the dashboard measures whether required CI attributes and related fields are populated, flagging CIs that are missing mandatory data. Option C (Correctness) is correct because the dashboard evaluates data accuracy by checking for orphan CIs, duplicate CIs, and CIs that fail audit or staleness rules. Options A (Availability), D (Performance), and E (Bandwidth) are not CMDB health metrics; they are operational or infrastructure monitoring metrics tracked by tools such as monitoring agents or network management systems, not by the CMDB Health Dashboard.

Answer

Availability

Answer

Performance

Answer

Bandwidth

Question 14

An architect is troubleshooting relationship cardinality and integrity issues in the CMDB. Which THREE mechanisms or tools help maintain relationship health? (Choose three.)

Accepted Answer

Suggested Relationships configurations. Option B (Suggested Relationships configurations) is correct because Suggested Relationships define the allowed parent-child relationship types between CI classes, enforcing valid cardinality and preventing invalid relationship types from being created in the CMDB. Option C (IRE relationship processing during payload ingestion) is correct because the Identification and Reconciliation Engine applies relationship rules and dependent/containment logic during ingestion, ensuring relationships are correctly matched, deduplicated, and reconciled rather than duplicated or orphaned. Option D (Orphan and Stale audits in CMDB Health Correctness) is correct because these CMDB Health Correctness KPIs detect CIs with missing required relationships (orphans) and outdated relationships (stale), surfacing integrity problems so they can be remediated. Option A is wrong because disabling index generation on cmdb_rel_ci degrades query performance and does not improve relationship health. Option E is wrong because direct SQL updates on cmdb_rel_ci bypass IRE, business rules, and audit logic, risking data corruption and unsupported configurations.

Answer

Disabling the cmdb_rel_ci table index generation

Answer

Manual SQL direct database updates on the cmdb_rel_ci table

Question 15

Which TWO methods can be used to add a custom attribute to a CI class in ServiceNow? (Choose two.)

Accepted Answer

Using the CI Class Manager by selecting the class and adding the attribute in the Attributes tab.. Option C is correct because the CI Class Manager is the purpose-built ServiceNow interface for extending the CMDB schema: after selecting the target CI class, the Attributes tab lets you add a new attribute (field) to that class, which creates the underlying column on the class table and inherits it to child classes. Option E is correct because adding a column directly to the target class table via System Definition > Tables (the sys_db_object/sys_dictionary mechanism) also creates a valid custom attribute on the CI class, and ServiceNow supports this as an alternative schema-editing method. Option A is not correct because Discovery patterns and Pattern Designer populate CI data during discovery; they do not define persistent custom attributes on a CI class. Option B is not correct because a Business Rule with a setDisplayValue script only manipulates how a value is displayed at runtime and does not add an attribute to the class schema. Option D is not correct because Form Designer only changes the layout of fields on a form; it cannot create a new attribute on the CI class.

Answer

Modifying Discovery patterns via Pattern Designer to store attributes in transient memory.

Answer

Creating a Business Rule with a setDisplayValue script.

Answer

Editing the Form Designer layout for the hardware form.