CIS-DF Practice Test 8 — 10 Questions

Question 1

A CMDB administrator notices that multiple CIs have duplicate records with identical serial numbers due to conflicting integration sources. Which CMDB Health metric evaluates this specific condition?

Accepted Answer

Correctness. The CMDB Health Correctness metric evaluates the accuracy of CI data by checking for duplicates, orphans, and other data quality issues. Duplicate CIs with identical serial numbers are specifically flagged under the Correctness metric, which includes duplicate checks.

Answer

Freshness

Answer

Completeness

Answer

Compliance

Question 2

Which dashboard component in the CMDB Health Dashboard displays the ratio of CIs that have missing mandatory attributes?

Accepted Answer

Completeness Score Widget. The Completeness Score Widget on the CMDB Health Dashboard displays the ratio of CIs that have missing mandatory attributes. Completeness measures whether required fields are populated, and the widget visualizes the percentage of CIs that meet completeness criteria versus those that do not. This directly answers the question about missing mandatory attributes.

Answer

Correctness Duplicate Widget

Answer

Orphaned CI Widget

Answer

Compliance Audit Widget

Question 3

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 4

Which THREE of the following statements are true regarding Dependency Views visualization? (Choose three.)

Accepted Answer

Users can filter displayed relationships by specific relationship types.. Option A is correct because Dependency Views provides filtering controls that let users narrow the displayed relationships by specific relationship types, so only the relevant dependency links are shown. Option C is correct because the core purpose of Dependency Views is to render a graphical map of CIs along with their upstream and downstream relationships and dependencies. Option E is correct because CI nodes in the map can be decorated with alert indicators and status badges reflecting health, alerts, and operational state. Option B is not correct because CSDM technical service offerings and portfolios are configured in the CSDM/Service Portfolio data model, not through the Dependency Views visualization. Option D is not correct because Dependency Views renders relationships from CMDB data and does not automatically execute network ping commands against every node during map rendering.

Answer

It is used to configure CSDM technical service offerings and portfolios.

Answer

It automatically executes network ping commands on every node during map rendering.

Question 5

A security audit reveals that unauthorized users are modifying critical CI attributes directly on form views. Which ServiceNow platform governance feature can restrict write access to specific CI attributes based on user roles and data classification?

Accepted Answer

Access Control Lists (ACLs) on cmdb_ci fields. Access Control Lists (ACLs) on cmdb_ci fields are the platform's native mechanism for restricting read and write access to specific CI attributes based on user roles, conditions, and data classification. By creating field-level ACLs with write rules tied to roles, administrators can prevent unauthorized users from modifying critical CI attributes directly on form views. This is the standard governance control for attribute-level write protection in the CMDB.

Answer

Data Certification read restrictions

Answer

Discovery credential filters

Answer

CMDB Data Governance read-only policies

Question 6

An administrator is setting up an IntegrationHub REST step to ingest server data into the CMDB via the IRE. Which TWO components must be properly configured within the IntegrationHub action or script? (Choose two.)

Accepted Answer

Invocation of the IRE API (such as `sn_cmdb.IdentificationEngine`) within the script step.. Option B is correct because ingesting data through the Identification and Reconciliation Engine (IRE) requires the IntegrationHub action or script step to explicitly call the IRE API, typically via the sn_cmdb.IdentificationEngine script include, so the payload is processed by IRE rather than inserted directly. Option E is correct because the IRE expects a properly structured JSON payload containing valid CI class names, identification attributes (such as serial_number, name, or sys_class_name), and related item entries so it can identify, reconcile, and create or update CIs correctly. Option A is not needed because Service Mapping horizontal patterns are used for service discovery topology mapping, not for REST-based CMDB ingestion via IRE. Option C is not needed because Discovery schedules and IP ranges apply to Discovery, not to an IntegrationHub REST step. Option D is not needed because legacy Transform Maps are bypassed when using the IRE API for identification and reconciliation.

Answer

Service Mapping horizontal pattern criteria.

Answer

Discovery schedule IP ranges matching the REST server IP.

Answer

Legacy Transform Map record definitions linked to the REST endpoint.

Question 7

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 8

An organization wants to categorize its applications based on whether they are mission-critical, business-operational, or administrative. Where should this classification be recorded according to CSDM best practices?

Accepted Answer

Business Application [cmdb_ci_business_app]. In CSDM, the Business Application [cmdb_ci_business_app] record is the correct place to capture business-criticality classification (mission-critical, business-operational, administrative) because it represents the logical application from a business perspective. This classification drives prioritization, reporting, and governance decisions tied to the application's business value.

Answer

Incident [incident]

Answer

User [sys_user]

Answer

Application Service [cmdb_ci_service_calculated]

Question 9

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 10

An administrator is troubleshooting a scenario where relationships created between Application Service CIs and underlying Server CIs are disappearing after a Discovery scheduled job runs. Upon reviewing CI class manager settings, which feature or setting most likely caused this behavior due to incorrect payload identification?

Accepted Answer

Identification and Reconciliation Engine (IRE) identification rules and dependent relationship definitions. The Identification and Reconciliation Engine (IRE) uses identification rules to determine which CI a payload corresponds to. If the identification rules are misconfigured, a discovery payload might be incorrectly identified as a different CI, causing existing relationships to be deleted or recreated. Dependent relationship definitions in IRE also control how relationships are maintained during reconciliation; incorrect settings can lead to relationships being removed when they should be preserved.

Answer

Data Dictionary cascade delete settings on the sys_dictionary table

Answer

CMDB Health dashboard completeness scorecards

Answer

Discovery Schedule exclude rules