CIS-DF Practice Exam 4 — 20 Questions

Question 1

When designing a custom CI class hierarchy, what is the primary benefit of inheriting from an existing parent class rather than creating an entirely independent base table?

Accepted Answer

It automatically inherits parent class attributes, identification rules, and relationship definitions.. Inheriting from an existing parent class in the CI class hierarchy allows the child class to automatically inherit attributes, identification rules, and relationship definitions from the parent. This promotes consistency, reduces configuration effort, and ensures that the child class adheres to the same data model and identification logic as the parent.

Answer

It bypasses the need for IRE processing.

Answer

It prevents the table from ever being deleted.

Answer

It automatically populates data from external discovery sources without mapping.

Question 2

A company discovers that multiple discovery sources are overwriting authoritative manual updates to server asset tags. Which governance mechanism should be configured to protect specific attributes from being updated by automated discovery?

Accepted Answer

Reconciliation Definition (Data Precedence). Reconciliation Definitions (Data Precedence) in the CMDB control which data source wins when multiple sources update the same CI attribute. By configuring a reconciliation rule that gives manual/authoritative sources higher precedence than discovery sources for specific attributes, you protect manual updates from being overwritten by automated discovery.

Answer

Discovery Schedule Exclude filters

Answer

Access Control Lists (ACLs)

Answer

Business Rules on the cmdb_ci table

Question 3

What is the primary objective of the 'Crawl' phase in the CSDM framework?

Accepted Answer

To establish foundational data and baseline CMDB population.. The Crawl phase in the CSDM framework is the initial stage where organizations establish foundational data and baseline CMDB population. It focuses on getting the core configuration management data into the CMDB accurately, setting the stage for later phases like Walk and Run. This phase is about creating a solid data foundation, not about retiring applications or achieving full financial optimization.

Answer

To retire all legacy applications across the enterprise.

Answer

To publish all service catalog offerings to external customers.

Answer

To achieve full enterprise financial cost allocation and automated AI optimization.

Question 4

Which TWO methods can be used to assign data ownership to configuration items in the CMDB to support governance and accountability? (Choose two.)

Accepted Answer

Populating the 'Owned by' or 'Managed by' fields on the CI record. Option C is correct because the 'Owned by' and 'Managed by' fields on a CI record are the standard ServiceNow reference fields used to designate the person or group accountable for a configuration item, directly supporting governance and accountability. Option E is correct because CMDB Data Manager policies let you define CI filter criteria and then automatically assign ownership fields (such as 'Owned by' or 'Managed by') in bulk, which is the scalable, policy-driven way to enforce ownership across the CMDB. Option A is not correct because ACL rules on cmdb_ci control read/write access to records, not the assignment of ownership data. Option B is not correct because Discovery behavior patterns are used to identify and classify CIs and their attributes during discovery, not to inject firewall rules or set ownership. Option D is not correct because adjusting Discovery schedule probe frequency only changes how often discovery runs and has no bearing on assigning CI ownership.

Answer

Editing ACL rules on the cmdb_ci table

Answer

Modifying Discovery behavior patterns to inject custom firewall rules

Answer

Adjusting Discovery schedule probe frequency

Question 5

An organization is setting up its CSDM framework and has defined several Business Capabilities. How do Business Capabilities relate to Business Applications in the Design domain?

Accepted Answer

Business Applications realize Business Capabilities.. In the CSDM Design domain, Business Applications are the technological realization of Business Capabilities — meaning each application exists to enable one or more capabilities. This is a many-to-many relationship modeled via the capability reference on the Business Application record. The Design domain intentionally separates the 'what' (capability) from the 'how' (application) so that capability maps remain stable even as applications change.

Answer

Business Capabilities are mapped directly to Hardware CIs.

Answer

Business Capabilities are children of Application Services.

Answer

Business Capabilities replace the need for Business Applications entirely.

Question 6

An organization is configuring ITSM processes to use CSDM data. When a user submits an incident, which CI field on the incident form should be populated to ensure proper service alignment according to CSDM?

Accepted Answer

Configuration Item [cmdb_ci] referencing an Application Service.. According to CSDM, when a user submits an incident, the Configuration Item [cmdb_ci] field on the incident form should be populated with a reference to an Application Service. This ensures that the incident is aligned with the service that is affected, enabling proper impact analysis and routing. The Application Service is a key CSDM entity that represents a service provided by applications, and it is the appropriate CI to link to incidents for service alignment.

Answer

Service Portfolio [service_portfolio] directly.

Answer

Business Application [cmdb_ci_business_app] directly.

Answer

Foundation Company [core_company] directly.

Question 7

An administrator is reviewing the CMDB Health Dashboard and notices high staleness scores across several server classes. Which TWO of the following data ingestion practices contribute to high CMDB staleness? (Choose two.)

Accepted Answer

Failing to run Discovery or integration updates regularly against active infrastructure.. Option D is correct because CMDB staleness measures how long CIs have gone without being refreshed by a trusted data source; if Discovery or integration jobs are not scheduled and run regularly against active infrastructure, the last-discovered timestamps age beyond the staleness thresholds defined in CMDB Health, driving up staleness scores. Option E is correct because decommissioned CIs that are never updated to a non-operational status or retired, and CIs whose source integrations have stopped feeding data, retain old last-updated values indefinitely, which the CMDB Health staleness metric flags as stale. Options A, B, and C do not contribute to staleness: the Identification and Reconciliation Engine (IRE) is the recommended mechanism for automated imports and actually improves data quality, certified Service Graph Connectors are the supported, continuously maintained ingestion path, and Data Source Precedence rules govern which source wins for an attribute rather than how frequently CIs are refreshed.

Answer

Using the Identification and Reconciliation Engine for all automated imports.

Answer

Ingesting data exclusively through certified Service Graph Connectors.

Answer

Configuring robust Data Source Precedence rules for all attributes.

Question 8

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 9

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 10

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 11

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 12

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 13

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 14

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 15

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 16

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 17

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 18

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 19

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 20

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