Courseiva

CCNA Configuration Questions

57 questions · Configuration · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQmedium

Your enterprise has acquired a company that uses custom naming conventions, causing duplicate CIs to be created during discovery. Which tool should you use to examine and adjust how incoming CIs are matched against existing records in the CMDB?

A.Data Normalization Engine
B.CI Class Manager
C.CMDB Health Dashboard
D.Dependency View
AnswerB

CI Class Manager provides the Identification and Reconciliation rules that govern how discovered CIs are matched against existing records, letting you adjust matching attributes to accommodate the acquired company's custom naming conventions and prevent duplicate CIs. This directly satisfies the requirement to examine and modify incoming CI matching behaviour in the CMDB.

Why this answer

The CI Class Manager is the centralized interface for configuring identification and reconciliation rules, including how incoming CIs are matched to existing records. It allows you to define identification rules based on attributes (e.g., serial number, name) and reconciliation rules to handle duplicates. This is the correct tool to examine and adjust matching behavior when acquisitions introduce conflicting naming conventions.

Exam trap

The trap is confusing data normalization (standardizing values) with identification and reconciliation (matching and merging records), which are distinct CMDB processes.

How to eliminate wrong answers

Option A is wrong because the Data Normalization Engine standardizes attribute values (e.g., manufacturer names) but does not control how CIs are matched against existing records. Option C is wrong because the CMDB Health Dashboard reports on data quality metrics like completeness and correctness; it does not configure matching logic. Option D is wrong because Dependency View visualizes relationships between CIs, not identification or reconciliation rules.

Practice this question →
2
MCQmedium

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?

A.Hosted on::Hosts
B.Depends on::Used by
C.Runs on::Runs
D.Connected by::Connected by
AnswerA

Hosted on::Hosts is the CI relationship type whose parent is the hosting entity and child the hosted one, so a Business Application hosting Server CIs maps correctly. It satisfies the stem's requirement to represent hosting dependencies as a parent-child relationship.

Why this answer

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.

Exam trap

CIS-DF often tests confusion between 'Hosted on::Hosts' (physical hosting) and 'Depends on::Used by' (logical dependency), catching candidates who pick the dependency relationship when the scenario describes hosting.

How to eliminate wrong answers

Option B is wrong because 'Depends on::Used by' represents a logical dependency between services or applications, not a physical hosting relationship between an application and a server. Option C is wrong because 'Runs on::Runs' is used for process-to-server or similar execution relationships, not the standard CSDM hosting relationship for applications. Option D is wrong because 'Connected by::Connected by' represents network connectivity between CIs, not a hosting or parent-child dependency.

Practice this question →
3
Multi-Selecthard

When defining a Reconciliation Definition in ServiceNow to manage attribute precedence, which THREE configurations or behaviors apply? (Choose three.)

Select 3 answers
A.Rules can target specific CI classes or apply globally across the entire cmdb hierarchy.
B.Reconciliation definitions only apply to transactional tables like task, never to cmdb_ci classes.
C.Global precedence rules apply across all CMDB classes unless overridden by class-specific rules.
D.Rules can specify which discovery sources have authority to update specific attributes.
E.Discovery sources not explicitly listed in a precedence rule are denied any ability to update the CMDB entirely.
AnswersA, C, D

Reconciliation rules can be scoped to individual CI classes or applied across the whole CMDB hierarchy, satisfying the requirement to manage precedence at differing granularities. This class-level targeting lets you resolve conflicting attribute values from multiple discovery sources precisely where needed, rather than enforcing one blanket rule everywhere.

Why this answer

Option A is correct because a reconciliation rule can be scoped to a specific CI class (for example, cmdb_ci_server) or defined globally so it applies across the entire CMDB class hierarchy, giving administrators flexible control over where precedence logic is enforced. Option C is correct because global precedence rules are the baseline that applies to all CMDB classes, and class-specific rules take priority over them when both exist, which is exactly how ServiceNow resolves attribute precedence conflicts. Option D is correct because reconciliation definitions let you designate which discovery sources (such as ServiceNow Discovery, SCCM, or a specific MID Server source) are authoritative for particular attributes, so the winning value comes from the trusted source.

Option B is incorrect because reconciliation definitions are built specifically for CMDB CI classes (cmdb_ci and its children), not for transactional tables like task. Option E is incorrect because sources not listed in a precedence rule are not globally denied; they simply do not win precedence for the attributes covered by that rule, and may still update other attributes or be handled by other rules.

Exam trap

CIS-DF often tests the misconception that reconciliation definitions apply to all tables or that unlisted sources are completely blocked, when in reality they are CMDB-specific and unlisted sources may still have default permissions.

Practice this question →
4
MCQmedium

You notice that a specific data source (e.g., SCCM) is overwriting critical configuration attributes that are manually maintained by your infrastructure team. How should you prevent this data source from updating those specific attributes?

A.Create a Business Rule on the cmdb_ci table to check the updated-by user.
B.Modify the Identification Rule to exclude the manual attributes.
C.Configure Reconciliation Definitions with attribute-level precedence rules.
D.Disable the data source integration entirely.
AnswerC

Reconciliation Definitions let you set attribute-level precedence, so the SCCM source can populate most fields while manually maintained attributes are excluded from its authority. This stops the source overwriting those specific values without disabling the whole connector.

Why this answer

Reconciliation Definitions in ServiceNow CMDB allow attribute-level precedence rules that determine which data source 'wins' when multiple sources update the same CI attribute. By configuring a reconciliation rule that assigns higher precedence to manually maintained attributes (or excludes the SCCM source from those specific attributes), the infrastructure team's manual edits are preserved while SCCM continues updating other fields. This is the designed mechanism for resolving multi-source attribute conflicts without disabling the integration.

Exam trap

CIS-DF often tests the misconception that Identification Rules control attribute updates, when in fact they only control CI matching — attribute-level precedence is the job of Reconciliation Definitions.

How to eliminate wrong answers

Option A is wrong because a Business Rule on cmdb_ci would be a custom code workaround that fires after the update and cannot cleanly arbitrate between multiple data sources — it also risks breaking other integrations and is not the supported conflict-resolution pattern. Option B is wrong because Identification Rules determine whether an incoming record matches an existing CI (creating/merging CIs), not which attributes get updated — they have no bearing on attribute-level overwrites. Option D is wrong because disabling the SCCM integration entirely stops all useful discovery/update data, which is a disproportionate action when only a few attributes need protection.

Practice this question →
5
MCQeasy

When configuring CMDB health metrics, which of the following represents one of the three core pillars measured by the CMDB Health Dashboard?

A.Security
B.Performance
C.Availability
D.Completeness
AnswerD

Completeness is one of the three core CMDB Health Dashboard pillars, alongside correctness and compliance. It measures whether required attributes and related records are populated, directly satisfying the stem's constraint that the metric be a core pillar rather than a derived or supplementary indicator.

Why this answer

The CMDB Health Dashboard in ServiceNow measures three core pillars: Completeness, Compliance, and Correctness. Completeness specifically evaluates whether required CI attributes and relationships are populated, ensuring the CMDB has the necessary data to support IT processes. This is a fundamental metric because incomplete CIs can lead to inaccurate impact analysis and service mapping.

The other options—Security, Performance, and Availability—are not part of the CMDB Health Dashboard's core pillars; they are operational metrics tracked elsewhere.

Exam trap

CIS-DF often tests the distinction between CMDB health pillars and general IT metrics, so candidates may mistakenly choose Security, Performance, or Availability because they are common IT concerns, but the CMDB Health Dashboard specifically measures Completeness, Compliance, and Correctness.

How to eliminate wrong answers

Option A is wrong because Security is not one of the three core pillars; while security is important, CMDB health focuses on data quality, not security posture. Option B is wrong because Performance is not a CMDB health pillar; performance metrics are typically monitored in APM or infrastructure monitoring tools. Option C is wrong because Availability is not a CMDB health pillar; availability is an operational metric, not a data quality dimension.

Option D is correct because Completeness is one of the three pillars (along with Compliance and Correctness) that assess CMDB data integrity.

Practice this question →
6
MCQeasy

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?

A.Configuration > CI Class Manager
B.System Definition > Tables
C.System Dictionary > New Class
D.Configuration > CMDB Properties
AnswerA

CI Class Manager is the dedicated console for creating and maintaining custom CI classes and their identification rules within the CMDB Class Hierarchy. It satisfies the need to define a new class for specialised network routers without altering base system tables.

Why this answer

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.

Exam trap

The trap here is confusing table creation with CI class creation; candidates might choose System Definition > Tables because it is a common way to create custom tables, but CI classes require the CMDB-specific CI Class Manager to ensure proper hierarchy and identification rules.

How to eliminate wrong answers

Option B is wrong because System Definition > Tables is used to create custom tables, but it does not provide the CMDB-specific context, class hierarchy management, or identification rules needed for CI classes. Option C is wrong because System Dictionary > New Class is not a valid navigation path; the dictionary manages table columns, not class creation. Option D is wrong because Configuration > CMDB Properties is for setting system properties related to CMDB behavior, not for creating classes.

Practice this question →
7
MCQeasy

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

A.cmdb_ci_rel
B.task_cmdb_ci_rel
C.sys_m2m_cmdb
D.cmdb_rel_ci
AnswerD

The cmdb_rel_ci table holds relationship instances, storing parent and child CI references plus the relationship type. It is the join table that connects configuration items, distinct from cmdb_ci itself and from the relationship type definition table.

Why this answer

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.

Exam trap

The trap is the near-identical distractor cmdb_ci_rel, which inverts the correct table name cmdb_rel_ci — candidates who don't memorize the exact table name pick the plausible-sounding wrong one.

How to eliminate wrong answers

Option A is wrong because cmdb_ci_rel is not the standard relationship-instance table in ServiceNow; the naming is a common distractor that inverts the correct table name. Option B is wrong because task_cmdb_ci_rel is a many-to-many (m2m) table linking tasks to CIs, not the table storing CI-to-CI relationships. Option C is wrong because sys_m2m_cmdb is not a real ServiceNow table — it is a fabricated name that mimics the sys_m2m_* naming convention used for many-to-many relationship tables.

Practice this question →
8
Multi-Selectmedium

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.)

Select 2 answers
A.Disable CMDB Health audits globally before creating the class table.
B.Always extend the root cmdb table directly to maximize attribute availability.
C.Extend the most specific existing parent class (e.g., cmdb_ci_hardware) rather than the base cmdb_ci table.
D.Define appropriate identification rules in the CI Class Manager for the new class.
E.Create custom relationships directly on the cmdb table dictionary.
AnswersC, D

Extending the most specific parent inherits relevant attributes, identification rules and relationships from that branch, avoiding the sparse base cmdb_ci table. This preserves class hierarchy integrity and lets the new class reuse existing CI data model behaviour.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that extending cmdb_ci directly gives 'more attributes,' when in fact it gives fewer inherited behaviors and breaks IRE identification patterns.

Practice this question →
9
Multi-Selecthard

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

Select 3 answers
A.Avoid excessively deep class hierarchies unless justified by distinct identification or attribute requirements.
B.Bypass the CI Class Manager and create database tables directly in System Definition.
C.Subclass from the most specific existing parent class that shares the same attributes and behaviors.
D.Create a brand new base table directly under cmdb for every new hardware vendor.
E.Check for existing out-of-the-box attributes before creating custom attributes to prevent redundancy.
AnswersA, C, E

Excessively deep hierarchies complicate inheritance, slow queries and obscure where attributes belong, so depth must be justified by genuinely distinct identification or attribute requirements. This satisfies the stem's design-practise constraint by keeping the CMDB class model shallow and maintainable, avoiding redundant child classes that add administrative overhead without functional benefit.

Why this answer

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.

Exam trap

CIS-DF often tests the temptation to create new base tables for each vendor or to modify system definitions directly; the correct approach is always to use the CI Class Manager and reuse existing structures.

Practice this question →
10
Multi-Selecthard

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.)

Select 3 answers
A.Standard Legacy Transform Maps without RTE
B.Dependency View graphical layout settings
C.Identification Rules
D.Reconciliation Definitions
E.Payload format (items and relations arrays)
AnswersC, D, E

Identification Rules define the attribute combinations IRE uses to detect whether an incoming record matches an existing CI. In a multi-source environment they prevent duplicate CIs by specifying, per class, which independent or dependent attributes must agree before records are merged.

Why this answer

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.

Exam trap

CIS-DF often tests whether candidates know that IRE requires Identification Rules, Reconciliation Definitions, and the items/relations payload — candidates sometimes pick legacy transform maps or unrelated visualization settings because they sound plausible.

Practice this question →
11
Multi-Selectmedium

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

Select 2 answers
A.Availability
B.Completeness
C.Correctness
D.Performance
E.Bandwidth
AnswersB, C

Completeness is one of the metrics tracked out-of-the-box by the CMDB Health Dashboard, satisfying the stem's requirement for native, no-configuration metrics. It measures the proportion of required fields populated on each configuration item, flagging records with missing mandatory attributes so data stewards can remediate gaps.

Why this answer

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.

Exam trap

The trap is selecting generic IT metrics like Availability or Performance, which sound plausible but are not part of the CMDB Health Dashboard's out-of-the-box KPIs.

Practice this question →
12
MCQhard

When configuring a new identification rule for a custom CI class using the CI Class Manager, you need to specify criteria that take precedence over other criteria. What element of the identification rule controls this priority?

A.Class Hierarchy Level
B.Identification Rule Priority Matrix
C.Identification Section Order
D.Reconciliation Definition Weight
AnswerC

Identification Section Order determines the sequence in which the identification rule's sections are evaluated, so criteria in an earlier section take precedence over later ones. Reordering sections therefore controls which matching criteria win when multiple entries could identify the same CI.

Why this answer

In ServiceNow's CI Class Manager, identification rules are composed of multiple identification sections (e.g., based on serial number, MAC address, or name). Each section is evaluated in a specific order, and the first section that matches an existing CI is used to identify the CI. The 'Identification Section Order' field within the rule allows you to define which section takes precedence over others.

This ordering is critical because it determines which criteria are applied first, ensuring that the most reliable identifiers are used before falling back to less specific ones.

Exam trap

CIS-DF often tests the distinction between identification rule priority (which rule runs first) and identification section order (which criteria within a rule take precedence), causing candidates to confuse the two.

How to eliminate wrong answers

Option A is wrong because Class Hierarchy Level refers to the position of a CI class within the class hierarchy (e.g., parent vs. child class) and does not control the priority of identification criteria within a rule. Option B is wrong because there is no 'Identification Rule Priority Matrix' in ServiceNow; identification rules themselves have a priority relative to other rules, but that is not the element that controls precedence of criteria within a single rule. Option D is wrong because Reconciliation Definition Weight is used in the reconciliation process to resolve conflicts when multiple CIs are identified, not to set the order of identification criteria.

Practice this question →
13
MCQeasy

You need to review the inheritance chain of a specific custom class called cmdb_ci_cloud_firewall. Which ServiceNow module provides a centralized UI to inspect class definitions, attributes, and relationships?

A.System Definition > Dictionary
B.Configuration > Relationships > Matrix
C.CMDB Workspace > Health Dashboard
D.Configuration > CI Class Manager
AnswerD

CI Class Manager is the centralised console for inspecting the class hierarchy, showing parent classes, inherited attributes, and relationships for a given table such as cmdb_ci_cloud_firewall. It directly satisfies the requirement to review the inheritance chain.

Why this answer

The CI Class Manager (Configuration > CI Class Manager) is the centralized ServiceNow UI for inspecting class definitions, attributes, inheritance chains, identification rules, and relationships. It provides a visual hierarchy view and lets administrators drill into any class, including custom ones like cmdb_ci_cloud_firewall.

Exam trap

The trap is confusing the Dictionary (which shows columns) with CI Class Manager (which shows class hierarchy and CMDB-specific metadata) — candidates often pick Dictionary because it 'shows class info' but it lacks the hierarchy and relationship view.

How to eliminate wrong answers

Option A is wrong because System Definition > Dictionary shows table columns and field definitions but does not present a class hierarchy or relationship view. Option B is wrong because the Relationship Matrix shows CI-to-CI relationship types, not class inheritance or attributes. Option C is wrong because the CMDB Workspace Health Dashboard reports data quality and health metrics, not class definitions or inheritance chains.

Practice this question →
14
MCQhard

Your team is troubleshooting a problem where discovery payloads for network gear are failing identification because multiple network devices share the same MAC address due to virtual routing and switching configurations. How can you resolve this in the CI Class Manager?

A.Create a Business Rule to merge duplicate records after discovery runs.
B.Modify the identification rule for the network gear class to include secondary unique identifiers like serial number or IP address in combination with MAC address.
C.Change the discovery schedule interval to prevent overlapping scans.
D.Disable the MAC address attribute from the cmdb_ci table entirely.
AnswerB

MAC address alone cannot uniquely identify devices when virtual routing and switching cause duplicates. Adding serial number or IP address as a secondary identifier creates a compound rule, so CI Class Manager distinguishes each device and discovery payloads identify correctly.

Why this answer

When multiple network devices share the same MAC address (common in virtual routing/switching or VRF scenarios), the default identification rule that relies solely on MAC address will fail or create duplicate/incorrect CIs. The correct fix is to modify the identification rule for the network gear class to use a combination of attributes — such as serial number or IP address combined with MAC — so that each device is uniquely identified. This ensures the IRE (Identification and Reconciliation Engine) can distinguish between devices that appear to have the same MAC.

Exam trap

CIS-DF often tests the misconception that merging duplicates or disabling attributes solves identification problems, when the correct approach is to refine the identification rule with additional unique attributes.

How to eliminate wrong answers

Option A is wrong because a Business Rule that merges duplicate records after discovery is a reactive workaround that does not fix the root cause of failed identification and can lead to data loss or incorrect merges. Option C is wrong because changing the discovery schedule interval only affects timing and does not address the fundamental issue of non-unique identifiers. Option D is wrong because disabling the MAC address attribute from the cmdb_ci table would break many other identification rules and is an overly broad, destructive change that does not solve the problem.

Practice this question →
15
MCQhard

Your team is planning to introduce a new class of CIs that will store sensitive cryptographic keys. These CIs should only be accessible and modifiable by a specific security team. In ServiceNow CMDB architecture, how are class-level access controls typically managed?

A.By configuring Discovery source rules to encrypt payloads before they reach the cmdb_rel_ci table.
B.By writing a Business Rule on cmdb_rel_ci that strips read access during query execution.
C.By utilizing standard ServiceNow Access Control Lists (ACLs) targeting the specific custom table name created for the class.
D.By modifying the CI Class Manager security tab to lock out standard roles automatically.
AnswerC

Class-level security in ServiceNow is enforced through standard Access Control Lists applied to the specific table created for the class. ACLs on that table name restrict read, write and delete operations to the designated security team, satisfying the sensitive cryptographic key constraint.

Why this answer

In ServiceNow, class-level access controls are managed through standard Access Control Lists (ACLs) that target the specific table created for the custom CI class. Each CI class is backed by its own table (e.g., u_crypto_key), and ACLs on that table control read, write, create, and delete access for roles. This is the native ServiceNow security model for restricting access to a class of CIs.

Exam trap

CIS-DF often tests the misconception that CI Class Manager or Discovery rules handle class-level security; candidates must recognize that standard ServiceNow ACLs on the class-specific table are the correct mechanism for restricting access to a CI class.

How to eliminate wrong answers

Option A is wrong because Discovery source rules control how Discovery identifies and populates CIs; they do not encrypt payloads or manage access to the cmdb_rel_ci table. Option B is wrong because Business Rules on cmdb_rel_ci manipulate relationship records, not read access to a custom CI class table, and stripping read access via a business rule is not the standard security mechanism. Option D is wrong because the CI Class Manager security tab does not automatically lock out standard roles; access control is enforced through ACLs, not through a class manager toggle.

Practice this question →
16
Multi-Selecthard

When designing a custom class hierarchy in the CMDB, an architect must adhere to best practices to ensure optimal performance and maintainability. Which TWO of the following practices are recommended when creating and configuring custom CI classes? (Choose two.)

Select 2 answers
A.Extend from an existing appropriate child class (such as cmdb_ci_server) if the new CI shares those attributes.
B.Extend from the cmdb table directly for every new hardware type to ensure clean table isolation.
C.Avoid creating custom classes when an existing class with customized attributes or identifiers can adequately represent the CI type.
D.Disable inheritance on all custom classes to improve database query execution speed.
E.Create a separate custom relationship table for each new custom CI class to maintain relationship integrity.
AnswersA, C

Extending from an appropriate existing child class inherits its attributes and relationships, preserving hierarchy integrity. This satisfies the stem's best-practice requirement by avoiding redundant attribute definitions and ensuring the new CI class integrates correctly with existing CMDB structures and queries.

Why this answer

Option A is correct because ServiceNow best practice is to extend a new custom CI class from the most specific existing class whose attributes it shares (for example, extending from cmdb_ci_server for a specialized server type), which inherits relevant fields, identifiers, and relationships instead of duplicating them. Option C is correct because reusing an existing class with customized attributes or identifiers avoids unnecessary class proliferation, keeping the CMDB model simpler, easier to maintain, and more performant. Option B is wrong because extending every new hardware type directly from the base cmdb table discards useful inherited attributes and relationships and creates a flat, hard-to-maintain hierarchy rather than clean isolation.

Option D is wrong because disabling inheritance is not a supported performance-tuning practice and would break the class model, identifier inheritance, and dependent relationships. Option E is wrong because creating a separate relationship table per CI class fragments the relationship model; relationships should use the shared relationship tables (such as cmdb_rel_ci) with appropriate relationship types.

Exam trap

CIS-DF often tests whether candidates understand that CMDB best practice favors inheritance from appropriate child classes and reuse of existing classes — the trap is picking options that promise 'clean isolation' or 'faster queries' by flattening the hierarchy or disabling inheritance.

Practice this question →
17
Multi-Selectmedium

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

Select 2 answers
A.Modifying Discovery patterns via Pattern Designer to store attributes in transient memory.
B.Creating a Business Rule with a setDisplayValue script.
C.Using the CI Class Manager by selecting the class and adding the attribute in the Attributes tab.
D.Editing the Form Designer layout for the hardware form.
E.Using System Definition > Tables to add a column directly to the target class table.
AnswersC, E

CI Class Manager adds the attribute through the class model's Attributes tab, writing to the underlying table while keeping the class hierarchy and CMDB model consistent. This satisfies the requirement to extend a CI class without manually editing table schema.

Why this answer

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.

Exam trap

The trap here is confusing presentation-layer changes (Form Designer, setDisplayValue Business Rules) with schema-layer changes — only the latter actually adds a custom attribute to a CI class.

Practice this question →
18
MCQmedium

During an audit of the cmdb_ci_computer table, you notice that several records lack standard manufacturer and model attributes that are present in the parent cmdb_ci_hardware table. What architectural feature of ServiceNow tables explains why these attributes exist across multiple hardware sub-classes?

A.Table inheritance through dictionary column extension
B.CMDB Data Manager policy enforcement
C.Dynamic CI Group membership rules
D.Database View joining
AnswerA

ServiceNow implements table inheritance by extending dictionary columns down the hierarchy, so attributes defined on cmdb_ci_hardware are physically available to sub-classes such as cmdb_ci_computer. Records missing manufacturer and model therefore reflect data gaps, not absent schema.

Why this answer

ServiceNow tables use inheritance: child tables (e.g., cmdb_ci_computer) inherit columns from parent tables (e.g., cmdb_ci_hardware). This means attributes like manufacturer and model are defined once in the parent and automatically available in all child tables, ensuring consistency and reducing redundancy.

Exam trap

CIS-DF often tests the concept of table inheritance and candidates may think attributes are duplicated in each table or that other features like database views are responsible.

How to eliminate wrong answers

Option B is wrong because CMDB Data Manager policies are used for data certification and lifecycle management, not for defining table schema. Option C is wrong because Dynamic CI Groups are used to group CIs based on queries, not to define attributes. Option D is wrong because Database Views are used to join tables for reporting, not for attribute inheritance.

Practice this question →
19
MCQeasy

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

A.System Diagnostics > Stats
B.Configuration > CMDB Health Dashboard
C.Performance Analytics > Dashboards > CI Quality
D.Reports > View/Run > CMDB Quality
AnswerB

The CMDB Health Dashboard aggregates completeness, correctness and compliance scores across all CIs, directly satisfying the requirement to view overall data-quality metrics. Configuration > CMDB Health Dashboard is the dedicated interface for these three health KPIs, unlike the CMDB home page or CI class manager, which show records rather than scored quality.

Why this answer

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.

Exam trap

The trap here is confusing general platform diagnostics or reporting modules with the purpose-built CMDB Health Dashboard — candidates who haven't navigated the CMDB Health module often pick a plausible-sounding but nonexistent report path like 'Reports > CMDB Quality.'

How to eliminate wrong answers

Option A is wrong because System Diagnostics > Stats provides platform-level performance and system statistics (transaction counts, memory, semaphores), not CMDB data quality metrics. Option C is wrong because Performance Analytics > Dashboards > CI Quality is not a standard out-of-box dashboard name — while PA can be used to build custom CMDB dashboards, the native CMDB health metrics live in the CMDB Health Dashboard, not a pre-built PA dashboard called 'CI Quality.' Option D is wrong because Reports > View/Run > CMDB Quality is not a valid navigation path — the Reports module does not contain a pre-built 'CMDB Quality' report category; CMDB health is surfaced through the dedicated Health Dashboard, not the generic reporting interface.

Practice this question →
20
Multi-Selectmedium

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

Select 2 answers
A.Creating a relationship automatically deletes both CIs if one is updated.
B.Relationships are directional, typically defined between a parent CI and a child CI.
C.A CI can only participate in a single relationship across the entire CMDB.
D.Relationships and reference fields (like 'Assigned to') function in the exact same manner.
E.CI relationships are stored in the cmdb_rel_ci table.
AnswersB, E

ServiceNow CI relationships carry a direction, recorded as parent-to-child, so traversal and dependency mapping depend on which CI is defined as parent versus child. This satisfies the stem's requirement for a true statement about relationship structure.

Why this answer

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.

Exam trap

CIS-DF often tests whether candidates conflate CI relationships (records in cmdb_rel_ci) with reference fields, or wrongly assume relationships are bidirectional or exclusive.

Practice this question →
21
MCQhard

An integration script is passing a complex payload containing multiple related CIs to the Identification and Reconciliation Engine (IRE) via the script include 'JSONUtils' or 'CmdbUtil'. Which payload structure is required for the IRE to correctly process related CIs in a single transaction?

A.Separate REST API calls for each CI followed by a manual relationship creation call.
B.A CSV file attached to a Data Source record processed exclusively by a Transform Map.
C.A flat array of CI records with parent and child reference ID fields embedded directly in each CI record.
D.A root object containing an 'items' array for the CIs and a 'relations' array specifying parent, child, and relationship type references.
AnswerD

The IRE requires a root object holding an 'items' array of CIs plus a 'relations' array defining parent, child, and relationship type, so all related CIs are identified, reconciled, and linked atomically within one transaction. Flat or separate payloads cannot express those relationships.

Why this answer

The IRE payload requires a structured JSON object containing an 'items' array for the CIs and a 'relations' array to define relationships between items in the payload.

Practice this question →
22
MCQmedium

Your organization is designing a custom subclass for specialized network appliances that require unique attributes not found in the standard cmdb_ci_netgear class. When creating a custom CI class extending cmdb_ci, what is the best practice recommendation regarding table extension?

A.Create a standalone table independent of the CMDB hierarchy and link it via business rules.
B.Extend from the most specific existing parent class that shares the common attributes of the new CI type.
C.Extend from cmdb_rel_ci to automatically inherit relationship capabilities.
D.Always extend directly from cmdb to avoid table bloat and performance degradation.
AnswerB

Extending from the most specific matching parent class inherits relevant attributes and relationships, avoiding duplication while preserving the appliance's unique fields. This satisfies the stem's requirement for specialised network appliances with attributes beyond cmdb_ci_netgear, since cmdb_ci itself is too generic and would force manual redefinition of inherited CI behaviour.

Why this answer

ServiceNow best practice for creating custom CI classes is to extend from the most specific existing parent class that already shares the common attributes of the new CI type. This maximizes inheritance of relevant fields, relationships, and behaviors while avoiding duplication, and keeps the custom class properly positioned within the CMDB class hierarchy for reporting and CSDM alignment.

Exam trap

CIS-DF often tests the misconception that extending from the base cmdb table is 'cleaner' or that standalone tables are acceptable for custom CIs — both violate ServiceNow's inheritance-based CMDB design and break CSDM alignment.

How to eliminate wrong answers

Option A is wrong because creating a standalone table outside the CMDB hierarchy breaks inheritance, prevents the class from participating in CMDB relationships and CSDM domains, and requires custom business rules to simulate what inheritance provides natively. Option C is wrong because cmdb_rel_ci is the relationship table that stores CI-to-CI relationships, not a CI class — extending from it would create a malformed class that cannot function as a CI. Option D is wrong because extending directly from cmdb (the base CI table) skips all intermediate classes like cmdb_ci_hardware or cmdb_ci_netgear, forcing you to redefine attributes that already exist and losing out on inherited behaviors and reports.

Practice this question →
23
Multi-Selectmedium

Which TWO tools or features in ServiceNow allow you to investigate and visualize relationships between configuration items? (Choose two.)

Select 2 answers
A.CI Class Manager
B.Discovery Schedule configuration
C.CMDB Query Builder
D.System Definition > Tables
E.Dependency Views
AnswersC, E

CMDB Query Builder lets administrators construct multi-table queries across CI classes and relationship tables, returning result sets that reveal how configuration items interconnect. This supports investigation of relationships, satisfying the question's requirement for a relationship-visualisation tool.

Why this answer

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.

Practice this question →
24
MCQmedium

A CMDB administrator needs to allow discovery sources to automatically create relationships between a server CI and its network adapter CI, but only when the network adapter's 'Installed on' relationship is explicitly provided by the discovery source. The administrator wants to enforce that a specific relationship type is used only for this class pair and that the relationship is not created if the parent CI is missing. Which feature in the CMDB Identification and Reconciliation Engine (IRE) should be configured to meet these requirements?

A.CMDB CI Class Manager
B.CMDB Health Dashboard relationship KPIs
C.CMDB Relationship Rules
D.CMDB Identification and Reconciliation Engine (IRE) identification rules
AnswerC

CMDB Relationship Rules in the IRE define which relationship types are allowed between specific CI class pairs and control whether relationships are created only when both parent and child CIs are resolved. They enforce the exact scenario: restricting the relationship type to the class pair and preventing creation when the parent is absent. This is the correct feature because it directly manages relationship creation during identification and reconciliation, ensuring data integrity and adherence to the CMDB model.

Why this answer

CMDB Relationship Rules are specifically designed to govern the creation of relationships during the identification and reconciliation process. They allow administrators to define which relationship types are permitted between certain CI class pairs and to enforce conditions such as requiring both parent and child CIs to be resolved before the relationship is created. This ensures that only valid relationships are added to the CMDB, preventing orphans and maintaining data integrity.

The other options either focus on identification, monitoring, or class definition without controlling relationship creation logic.

Exam trap

The trap here is confusing identification rules with relationship rules, assuming that identifying CIs automatically creates relationships according to the desired constraints.

Practice this question →
25
MCQeasy

A user wants to view the parent-child relationships and upstream/downstream dependencies of a core router in a graphical map format. Which ServiceNow feature should they open?

A.Dependency Views
B.CI Class Manager
C.CMDB Query Builder
D.CSDM Dashboard
AnswerA

Dependency Views renders a graphical map of configuration items, showing parent-child relationships and upstream/downstream dependencies, exactly matching the request for a core router's topology. It satisfies the stem's graphical-map constraint, unlike tabular CMDB lists or impact simulators that lack this visual dependency representation.

Why this answer

Dependency Views in ServiceNow provides a graphical map showing CI relationships, including parent-child hierarchies and upstream/downstream dependencies. It is specifically designed to visualize how CIs connect and impact each other, making it the correct feature for viewing a core router's relationships in map format.

Exam trap

CIS-DF often tests whether candidates confuse CMDB Query Builder (tabular queries) with Dependency Views (graphical relationship maps), leading them to pick the query tool when a visual map is requested.

How to eliminate wrong answers

Option B is wrong because CI Class Manager is used to configure CI class definitions, attributes, and identification rules — it does not visualize relationships. Option C is wrong because CMDB Query Builder is a reporting tool for querying CI data and relationships in tabular form, not a graphical dependency map. Option D is wrong because CSDM Dashboard displays CSDM compliance and domain-level metrics, not individual CI dependency graphs.

Practice this question →
26
MCQmedium

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?

A.Update the identification rule in the CI Class Manager to include the new attribute as part of the identification criteria.
B.Modify the transform map script to delete duplicate records after insertion.
C.Write a Business Rule on cmdb_rel_ci to merge records with matching names.
D.Disable the Identification and Reconciliation Engine for external feeds.
AnswerA

The IRE matches incoming payload attributes against configured identification criteria. Because the custom identifier is absent from the rule, no match occurs and duplicates are created. Adding that attribute to the CI Class Manager identification rule lets the IRE correlate the feed correctly.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that post-insertion scripts or business rules can fix duplicate CIs, when the real solution is updating IRE identification rules.

How to eliminate wrong answers

Option B is wrong because deleting duplicates after insertion via transform map script is a reactive workaround that doesn't prevent duplicates and can cause data loss or referential integrity issues. Option C is wrong because a Business Rule on cmdb_rel_ci only affects relationships, not CI creation, and merging by name is unreliable. Option D is wrong because disabling IRE for external feeds removes the very mechanism that prevents duplicates, making the problem worse.

Practice this question →
27
MCQmedium

An implementation specialist is configuring dependency relationships where a virtual machine must be marked as dependent on a physical ESXi host. When utilizing CI relationships, what is the significance of setting the 'Depends :: Used by' relationship direction correctly?

A.It enforces mandatory database indexing on the cmdb_rel_ci table for both records.
B.It determines the physical network routing path used by Discovery.
C.It automatically populates the asset tag field on the child CI from the parent CI.
D.It dictates how Business Service Management and Dependency Views calculate impact propagation.
AnswerD

Setting 'Depends :: Used by' correctly ensures the VM-to-ESXi-host dependency propagates impact in the right direction, so Business Service Management and Dependency Views trace outages from host to VM. Reversing it would misattribute impact, breaking the required dependency relationship the stem specifies.

Why this answer

In ServiceNow CMDB, the 'Depends :: Used by' relationship direction defines which CI depends on which, and this direction is what Business Service Management and Dependency Views use to calculate impact propagation. If a VM is set as dependent on an ESXi host, an outage on the host correctly propagates impact to the VM and any services above it. Setting the direction incorrectly reverses the impact tree, causing misleading outage analysis.

Exam trap

CIS-DF often tests the misconception that relationship direction is cosmetic or only affects display; candidates must recognize that direction is the semantic backbone of impact propagation in BSM and Dependency Views.

How to eliminate wrong answers

Option A is wrong because relationship direction has no bearing on database indexing of the cmdb_rel_ci table; indexing is a platform concern, not a relationship semantic. Option B is wrong because Discovery network routing is determined by network topology and MID Server configuration, not by CI relationship direction. Option C is wrong because asset tag population is handled by asset/CI synchronization rules or transform maps, not by the parent/child direction of a dependency relationship.

Practice this question →
28
MCQeasy

An administrator needs to create a new custom Configuration Item class for specialized industrial IoT gateways that inherit base attributes from the Hardware class. Which table should be the parent table for this new class?

A.cmdb_rel_ci
B.cmdb_ci
C.cmdb_ci_hardware
D.cmdb
AnswerC

Extending cmdb_ci_hardware inherits the Hardware class attributes the gateways require, satisfying the stem's inheritance constraint. Configuration Item classes must extend an existing CI table so the CMDB hierarchy and dependent relationships remain valid; cmdb_ci_hardware is the correct parent for physical device classes.

Why this answer

Custom CI classes representing physical hardware typically inherit from the cmdb_ci_hardware table to leverage existing hardware attributes and identification rules.

Practice this question →
29
Multi-Selecthard

An organization is utilizing CSDM (Common Service Data Model) and needs to relate technical CIs to business services and applications. Which THREE relationship types or foundational concepts are core to proper CSDM alignment in the CMDB? (Choose three.)

Select 3 answers
A.Storing all users, business applications, and servers in a single flat cmdb_ci table without differentiation.
B.Relating Business Applications to Application Services using the 'Consumes::Consumed by' or instance relationship mappings.
C.Establishing clear demarcations between the Design, Technical, and Sell/Consume domains of CSDM.
D.Connecting Infrastructure CIs to Application Services using 'Hosted on::Hosts' or 'Depends on::Used by'.
E.Using the task table to store direct relationships between hardware and software.
AnswersB, C, D

The 'Consumes::Consumed by' relationship links a Business Application to the Application Services it depends on, forming the traceable path from business capability down to technical components. This mapping is foundational for aligning technical CIs with business services in the CMDB.

Why this answer

Option B is correct because CSDM models the relationship between a Business Application and the Application Service(s) that realize it, typically via 'Consumes::Consumed by' or the application service instance relationship, which links the logical business-facing layer to the technical service layer. Option C is correct because CSDM is organized into distinct domains — Design (business/application models), Technical (infrastructure and technical services), and Sell/Consume (service offerings and subscriptions) — and clear demarcation between these domains is foundational to aligning CIs correctly. Option D is correct because infrastructure CIs (servers, databases, etc.) must be connected to Application Services through relationships such as 'Hosted on::Hosts' or 'Depends on::Used by' to trace technical components up to the services they support.

Option A is incorrect because CSDM requires differentiated CI classes (e.g., cmdb_ci_business_app, cmdb_ci_appl, cmdb_ci_server) rather than a single flat table, which would destroy class hierarchy and relationship semantics. Option E is incorrect because relationships in the CMDB are stored in dedicated relationship tables (e.g., cmdb_rel_ci) via CI Relationship [cmdb_rel_ci], not in the task table, which is used for work items like incidents, changes, and problems.

Exam trap

CIS-DF often tests the misconception that any table can store relationships, or that flat CI storage is acceptable, when CSDM mandates specific classes and relationship types.

Practice this question →
30
MCQmedium

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?

A.Delete the table directly from the Tables and Columns module without checking for records.
B.Deactivate all identification rules and leave the table orphaned.
C.Rename the table name prefix to 'z_deprecated_' directly in the dictionary.
D.Use the CI Class Manager to deprecate or safely review dependent records and rules before taking action.
AnswerD

Deprecating a class in CI Class Manager first surfaces dependent records, relationships and rules, satisfying the stem's requirement to retire an unused custom CI class safely. Reviewing these dependencies prevents orphaned references and broken reconciliation before the class is marked deprecated, preserving configuration item integrity.

Why this answer

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.

Exam trap

CIS-DF often tests the temptation to delete tables directly via Tables and Columns, when the correct practice is to use the CI Class Manager to review dependencies and deprecate safely.

How to eliminate wrong answers

Option A is wrong because deleting the table directly from Tables and Columns bypasses dependency checks and can orphan records, break references, and cause data loss. Option B is wrong because deactivating identification rules and leaving the table orphaned creates an unmanaged, confusing state with no governance. Option C is wrong because renaming the table prefix in the dictionary is a hack that does not properly deprecate the class and can break existing references and integrations.

Practice this question →
31
MCQmedium

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?

A.Using the CI Class Manager by selecting the target storage CI class and adding the attribute under the Attributes tab
B.By editing the cmdb_ci_hardware form layout directly
C.Through the Discovery Definition > CI Attributes module
D.Directly in the Data Dictionary via System Definition > Dictionary by modifying the base cmdb table
AnswerA

The CI Class Manager defines attributes at the class level, so adding the serial number attribute to the target storage CI class under the Attributes tab makes it available on every device instance of that class, ensuring consistent management and tracking.

Why this answer

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.

Exam trap

The trap is thinking that adding an attribute to a base table like cmdb_ci or cmdb_ci_hardware is acceptable — candidates who don't know the CI Class Manager pick the Data Dictionary option, not realizing it pollutes the entire CMDB schema.

How to eliminate wrong answers

Option B is wrong because editing the cmdb_ci_hardware form layout only changes the UI presentation — it does not create or manage a new attribute, and it applies to the wrong class (hardware, not the specific storage class). Option C is wrong because Discovery Definition > CI Attributes is not a valid module for adding custom CI attributes — Discovery definitions configure identification and reconciliation rules, not schema extensions. Option D is wrong because directly modifying the base cmdb table via the Data Dictionary is a dangerous anti-pattern: it adds the attribute to the root class, making it available to every CI in the CMDB, which pollutes the schema and violates proper class design.

Practice this question →
32
MCQeasy

A CMDB administrator needs to ensure that all new Configuration Items (CIs) of a certain class are automatically assigned a specific support group based on the CI's location. Which feature should be used to achieve this?

A.CMDB Health Dashboard
B.Transform Map
C.CI Class Manager
D.Business Rule
AnswerD

A Business Rule can execute server-side logic when a CI record is created or updated. It can evaluate the CI's location and assign the appropriate support group dynamically. This is the standard way to automate field population based on conditions in ServiceNow.

Why this answer

A Business Rule is the correct choice because it can run on CI insert or update, check the location, and set the support group accordingly. This provides dynamic, real-time assignment. CI Class Manager, CMDB Health Dashboard, and Transform Maps do not provide this automation for all CI creation paths.

Exam trap

The trap here is confusing data import tools like Transform Maps with automation tools like Business Rules, which can act on any record change.

Practice this question →
33
MCQhard

An enterprise is planning to deploy a complex multi-tier application architecture. They want to ensure that application services are mapped using the correct relationship types between technical CIs and logical service nodes. Which recommended relationship type represents the connection between a logical application service and its running software instance?

A.Contains / Contained by
B.Runs on / Runs
C.Used by / Uses
D.Connects to / Connected by
AnswerB

The Runs on / Runs relationship type links a logical application service CI to the software instance executing it, which is exactly the mapping the enterprise needs between logical service nodes and technical CIs in the multi-tier architecture.

Why this answer

The 'Runs on / Runs' relationship type represents the connection between a logical application service (or application) and the running software instance (e.g., a software instance running on a server). This is the standard CSDM relationship for mapping a logical service node to the technical CI that hosts or executes it. It captures the deployment/runtime dependency, which is exactly what the question describes.

Exam trap

CIS-DF often tests the confusion between 'Runs on' (execution/hosting) and 'Contains' (hierarchy) — candidates pick 'Contains' because it sounds like the service 'contains' its components, but the correct semantic for a logical service and its running instance is 'Runs on.'

How to eliminate wrong answers

Option A is wrong because 'Contains / Contained by' represents a hierarchical containment relationship (e.g., a service contains a CI), not the runtime execution relationship between a logical service and its software instance. Option C is wrong because 'Used by / Uses' represents a dependency where one CI uses another (e.g., an application uses a database), not the hosting/running relationship. Option D is wrong because 'Connects to / Connected by' represents network or communication connections between CIs, not the execution of a software instance by a logical service.

Practice this question →
34
Multi-Selecthard

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

Select 3 answers
A.Disabling the cmdb_rel_ci table index generation
B.Suggested Relationships configurations
C.IRE relationship processing during payload ingestion
D.Orphan and Stale audits in CMDB Health Correctness
E.Manual SQL direct database updates on the cmdb_rel_ci table
AnswersB, C, D

Suggested Relationships configurations let the CMDB infer and create connections automatically from discovery data and CI attributes, rather than relying on manual entry. This directly addresses the cardinality and integrity issues in the stem by enforcing consistent, rule-based relationship creation, reducing orphaned or duplicate links that manual maintenance introduces.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that manual database updates or disabling indexes are valid ways to manage relationships, when in fact they are harmful and not part of best practices.

Practice this question →
35
MCQhard

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?

A.Manual approval workflows for every inbound payload
B.The Identification and Reconciliation Engine (IRE) processing queue and source precedence rules
C.Asynchronous business rules triggered on insert to pause payloads
D.Database locks enforced via Table Administration settings
AnswerB

The IRE processing queue serialises incoming CI payloads, while source precedence rules resolve conflicts when multiple discovery tools update the same CI. This prevents race conditions and conflicting simultaneous updates, satisfying the stated ingestion constraint.

Why this answer

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.

Exam trap

The trap is thinking that database-level locking or custom business rules can solve multi-source concurrency, when ServiceNow provides IRE specifically for this purpose.

How to eliminate wrong answers

Option A is wrong because manual approval workflows for every payload do not scale and do not prevent race conditions; they only add human latency. Option C is wrong because asynchronous business rules on insert do not coordinate across sources and can themselves create race conditions. Option D is wrong because database locks are not a supported or practical mechanism in ServiceNow for CMDB ingestion; the platform uses IRE, not table-level locks, to manage concurrency.

Practice this question →
36
MCQmedium

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?

A.A CI that has no parent or child relationships defined in the cmdb_rel_ci table.
B.A CI whose primary discovery source has been deleted.
C.A CI assigned to an inactive user group.
D.A CI that has not been scanned by Discovery in over 60 days.
AnswerA

Orphan CIs are records absent from any entry in cmdb_rel_ci, meaning neither a parent nor a child relationship references them. They indicate incomplete relationship modelling rather than missing attributes, so remediation focuses on populating relationship records.

Why this answer

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.

Exam trap

CIS-DF often tests the definition of 'orphan' — candidates confuse it with stale CIs (not updated recently) or CIs with missing discovery sources, but orphan specifically means no relationships in cmdb_rel_ci.

How to eliminate wrong answers

Option B is wrong because a deleted discovery source does not define an orphan; it may affect data freshness but not relationship status. Option C is wrong because assignment to an inactive user group is a data quality issue but not the definition of an orphan CI. Option D is wrong because not being scanned in 60 days relates to staleness or 'age' metrics, not orphan status.

Practice this question →
37
MCQeasy

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?

A.It bypasses the need for IRE processing.
B.It automatically inherits parent class attributes, identification rules, and relationship definitions.
C.It prevents the table from ever being deleted.
D.It automatically populates data from external discovery sources without mapping.
AnswerB

Inheritance means the child class automatically receives the parent's attributes, identification rules and relationship definitions, so the custom CI class reuses proven schema and reconciliation logic rather than duplicating it in an independent base table.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that inheritance bypasses IRE or automatically populates data, when it actually provides schema and rule inheritance but still requires proper discovery mapping and IRE processing.

How to eliminate wrong answers

Option A is wrong because inheriting from a parent class does not bypass the need for IRE processing; IRE still runs to identify and reconcile CIs. Option C is wrong because inheritance does not prevent the table from being deleted; table deletion is governed by other constraints. Option D is wrong because inheritance does not automatically populate data from external discovery sources without mapping; discovery still requires mapping and identification rules.

Practice this question →
38
MCQmedium

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?

A.CI Class Manager hiding classes from navigation
B.Access Control Lists (ACLs) combined with location or company attributes
C.Modifying Discovery Schedule target IP ranges
D.Disabling Dependency Views for non-admin users
AnswerB

ACLs restrict read or write access to specific CI classes or records, and combining them with location or company attributes scopes visibility so each regional support team sees only its local hardware, achieving record-level segregation in the CMDB.

Why this answer

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.

Exam trap

The trap here is confusing UI-level hiding (navigation menu, module visibility) with true security enforcement — candidates often pick 'hide classes' thinking it restricts data access, but only ACLs enforce record-level security.

How to eliminate wrong answers

Option A is wrong because hiding classes from the navigation menu only affects UI visibility; users can still access records via search, reports, or APIs, so it does not enforce security. Option C is wrong because Discovery Schedule target IP ranges control what gets discovered, not who can see the resulting CIs. Option D is wrong because disabling Dependency Views only removes a visualization feature; it does not restrict access to CI records themselves.

Practice this question →
39
MCQmedium

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?

A.Completeness Audit Rules
B.Compliance Audit Policies
C.Correctness Audit Rules
D.Identification Rules
AnswerA

Completeness Audit Rules define which fields must be populated on a CI class and flag records missing them. Configuring the rule against the database instance class with 'Assigned to' as a required field directly tracks the stated requirement.

Why this answer

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.

Exam trap

CIS-DF often tests the distinction between the three CMDB Health KPIs — candidates confuse Completeness (field populated) with Correctness (field accurate) or Compliance (policy adherence).

How to eliminate wrong answers

Option B is wrong because Compliance Audit Policies check whether CIs conform to governance requirements such as approved software or lifecycle states, not whether a specific field is populated. Option C is wrong because Correctness Audit Rules validate data accuracy against authoritative sources (e.g., mismatched OS versions), not field presence. Option D is wrong because Identification Rules determine how discovery sources are matched and merged into a single CI; they do not enforce required field population.

Practice this question →
40
Multi-Selectmedium

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

Select 2 answers
A.Configure Service Level Agreements (SLAs) for incident resolution
B.Create and modify identification rules for a CI class
C.Add new attributes and fields to a specific CI class
D.Schedule and execute Discovery network scans
E.Build graphical multi-table CMDB queries
AnswersB, C

Identification rules define how incoming discovery data maps to a CI class, and CI Class Manager provides direct editing of these rules per class. This satisfies the stem's requirement for actions performed within the tool itself, rather than through separate modules such as Discovery or the CMDB health dashboard.

Why this answer

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.

Exam trap

CIS-DF often tests the scope of CI Class Manager — candidates may think it includes Discovery scheduling or SLA configuration, but it is limited to class definition, attributes, and identification/reconciliation rules.

Practice this question →
41
MCQmedium

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?

A.Standard Transform Maps without script writing
B.IntegrationHub ETL or Robust Transform Engine (RTE) relationship processors
C.Database Views joining the sys_user and cmdb_ci tables
D.Manual entry via Dependency Views after import completion
AnswerB

IntegrationHub ETL and Robust Transform Engine relationship processors build CI relationships during import by resolving dependent CIs and creating relation records in the same transform run. This satisfies the stem's requirement that server-to-switch relationships be created accurately alongside the CI imports, rather than through separate post-import reconciliation.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that standard Transform Maps can handle relationships out of the box, when in fact relationship creation requires RTE/IntegrationHub ETL relationship processors or custom script.

How to eliminate wrong answers

Option A is wrong because standard Transform Maps without scripting cannot resolve and create relationships between CIs — they only map fields on a single target table. Option C is wrong because Database Views are read-only joins used for reporting, not for creating or importing relationship records. Option D is wrong because manual entry via Dependency Views is error-prone, does not scale, and defeats the purpose of an automated import.

Practice this question →
42
Multi-Selecthard

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.)

Select 3 answers
A.ServiceNow Discovery
B.ServiceGraph Connectors
C.IntegrationHub ETL
D.Manual CSV file import via standard System Import Sets
E.Standard Legacy Transform Maps without RTE
AnswersA, B, C

ServiceNow Discovery natively feeds the Identification and Reconciliation Engine, passing discovered CIs through IRE for deduplication and reconciliation before insertion. This satisfies the stem's constraint that the mechanism must natively support or integrate with IRE.

Why this answer

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.

Exam trap

CIS-DF often tests the integration of various data sources with IRE, trapping candidates who assume all import methods use IRE, including legacy transform maps.

Practice this question →
43
MCQhard

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?

A.Criteria attributes are ignored unless a Discovery source is explicitly named in the payload.
B.The IRE randomly selects one attribute to perform the lookup based on payload weight.
C.The IRE evaluates attributes as an OR condition, matching on any single attribute present in the payload.
D.The IRE evaluates criteria attributes as an AND condition within the criterion, requiring all specified attributes to match.
AnswerD

Within a single criterion, IRE combines the listed attributes using AND logic, so a CI is only identified when every specified attribute value matches. This satisfies the stem's constraint of multiple criteria attributes in one criterion, ensuring precise identification rather than broad OR-based matching across unrelated records.

Why this answer

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.

Exam trap

CIS-DF often tests the confusion between identification criteria logic (AND within a criterion) and reconciliation precedence (source priority) — candidates incorrectly assume OR logic or that discovery source naming is required for identification.

How to eliminate wrong answers

Option A is wrong because criteria attributes are evaluated regardless of whether a Discovery source is named; the source is used for reconciliation precedence, not to gate identification. Option B is wrong because IRE does not randomly select attributes — it deterministically evaluates the full criterion set using AND logic. Option C is wrong because OR logic would match on any single attribute, which would cause incorrect CI identification (e.g., matching two different servers that share only a hostname pattern); IRE uses AND within a criterion and OR across multiple criteria.

Practice this question →
44
MCQhard

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?

A.RTE automatically translates foreign languages in source data payloads.
B.RTE eliminates the need for staging tables during data imports.
C.RTE bypasses all access control lists to accelerate import times.
D.RTE processes data through the Identification and Reconciliation Engine (IRE), preventing duplicates and enforcing data integrity.
AnswerD

RTE routes records through the Identification and Reconciliation Engine, which applies CI identification rules and reconciliation to deduplicate and enforce CMDB data integrity. A standard Transform Map writes directly to tables, bypassing IRE and risking duplicate CIs.

Why this answer

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.

Exam trap

CIS-DF often tests the difference between a standard Transform Map (direct table writes, no dedup) and RTE (IRE-driven, dedup and reconciliation), so candidates who assume 'transform map' and 'RTE' are interchangeable pick a wrong option.

How to eliminate wrong answers

Option A is wrong because RTE does not perform language translation — it is a data transformation and reconciliation engine, not a localization tool. Option B is wrong because RTE still relies on staging tables (import sets) to hold raw data before transformation; it does not eliminate them. Option C is wrong because RTE does not bypass ACLs — access controls still apply to the import process and to the resulting CI records, and bypassing ACLs would be a security violation, not a feature.

Practice this question →
45
MCQeasy

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

A.CI Class Manager
B.Map Canvas
C.Dependency Views
D.CMDB Dashboard
AnswerC

Dependency Views renders configuration items as interactive nodes joined by labelled links, mapping upstream and downstream relationships across the CMDB. This graphical topology directly satisfies the requirement to visualise CI relationships, unlike tabular lists or reports. It draws on service mapping data to expose the impact paths administrators need during incident and change analysis.

Why this answer

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.

Exam trap

CIS-DF often tests the confusion between CMDB data-quality dashboards (CMDB Dashboard) and relationship visualization tools (Dependency Views), or between custom UI builders (Map Canvas) and the out-of-box dependency graph.

How to eliminate wrong answers

Option A is wrong because CI Class Manager is used to define and manage CI class hierarchies, attributes, and identification rules — not to visualize relationships. Option B is wrong because Map Canvas is a ServiceNow UI Framework feature for building custom graphical interfaces (e.g., floor plans, network maps) and is not the out-of-box CMDB relationship visualizer. Option D is wrong because CMDB Dashboard provides metrics, health scores, and KPIs about CMDB data quality, not a node-and-link relationship graph.

Practice this question →
46
MCQhard

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?

A.Data Policies enforced on the cmdb_ci table
B.Row-level Security via standard ACLs only
C.Domain Separation
D.CMDB Baseline auditing
AnswerC

Domain Separation partitions a single ServiceNow instance so each tenant's CIs, users and processes are isolated by domain. Tenant B users cannot view or modify Tenant A records, satisfying the logical segregation requirement while retaining one shared CMDB.

Why this answer

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.

Exam trap

CIS-DF often tests the confusion between ACL-based row-level security and Domain Separation, leading candidates to pick ACLs when true multi-tenant logical segregation is required.

How to eliminate wrong answers

Option A is wrong because Data Policies enforce field-level mandatory/read-only rules, not row-level tenant isolation. Option B is wrong because standard ACLs alone can restrict access but do not provide the hierarchical, tenant-aware segregation that Domain Separation offers; ACLs would need to be manually maintained per tenant and are error-prone. Option D is wrong because CMDB Baseline auditing tracks changes to CI records for compliance, not access segregation.

Practice this question →
47
MCQhard

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?

A.Data Dictionary cascade delete settings on the sys_dictionary table
B.CMDB Health dashboard completeness scorecards
C.Identification and Reconciliation Engine (IRE) identification rules and dependent relationship definitions
D.Discovery Schedule exclude rules
AnswerC

IRE identification rules and dependent relationship definitions govern how discovered payloads map to existing CIs and their relationships. When payload identification is misconfigured, IRE treats the Application Service-to-Server relationship as unmatched, so reconciliation deletes it during the scheduled Discovery run — directly explaining the disappearing relationships described in the stem.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that discovery schedules or health dashboards directly modify relationships, when the root cause is usually IRE identification and reconciliation rules.

How to eliminate wrong answers

Option A is wrong because data dictionary cascade delete settings affect deletion of records when a parent is deleted, not relationship disappearance after discovery. Option B is wrong because CMDB Health dashboard completeness scorecards are for monitoring, not for causing relationship changes. Option D is wrong because Discovery Schedule exclude rules prevent discovery of certain IPs or ranges, but they do not directly cause relationships to disappear after a job runs; they would prevent discovery altogether.

Practice this question →
48
Multi-Selecthard

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.)

Select 3 answers
A.Whether specialized relationships or lifecycle workflows apply specifically to these items
B.Whether the items require unique attributes that do not apply to the parent class
C.The number of ITIL user licenses assigned to the platform
D.The preferred background color of the table form layout
E.Whether the new items require distinct identification rules compared to existing classes
AnswersA, B, E

Specialised relationships or lifecycle workflows that apply only to the new items justify a distinct CI class, because class-specific relationship types and lifecycle states cannot be expressed through attributes on an existing class. This is a valid factor when choosing between extension approaches.

Why this answer

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.

Exam trap

CIS-DF often tests the confusion between technical factors (attributes, relationships, identification) and irrelevant factors (licenses, UI preferences); candidates must focus on data modeling principles.

Practice this question →
49
MCQmedium

An administrator needs to create a query that pulls all virtual machines running on ESXi hosts where the host status is 'Maintenance'. Which tool is best suited for building this multi-table query visually without writing SQL or custom scripts?

A.Report Designer
B.CI Class Manager
C.CMDB Query Builder
D.Performance Analytics
AnswerC

CMDB Query Builder joins multiple CMDB tables visually, letting the administrator filter ESXi hosts by status 'Maintenance' and traverse relationships to their hosted virtual machines. This satisfies the no-SQL, no-scripting constraint, since its drag-and-drop interface generates the underlying query automatically.

Why this answer

CMDB Query Builder is the ServiceNow tool specifically designed for visually building multi-table queries across CMDB classes and relationships without writing SQL or scripts. It allows drag-and-drop selection of CI classes, relationship traversal, and filter conditions, making it ideal for queries like 'all VMs running on ESXi hosts with status Maintenance.' It is the recommended tool for ad-hoc CMDB relationship queries.

Exam trap

CIS-DF often tests the confusion between CMDB Query Builder (multi-table CI relationship queries) and Report Designer (reporting/dashboards) — candidates pick Report Designer because it sounds like it can 'query' data, but it cannot traverse CMDB relationships the way Query Builder does.

How to eliminate wrong answers

Option A is wrong because Report Designer is for building reports and dashboards, not for constructing complex multi-table CMDB relationship queries — it lacks the relationship traversal capability needed here. Option B is wrong because CI Class Manager is for managing CI class definitions, attributes, and class hierarchy, not for querying CI data. Option D is wrong because Performance Analytics is for time-series metric tracking and KPI dashboards, not for ad-hoc multi-table CI relationship queries.

Practice this question →
50
MCQeasy

Where in ServiceNow should an administrator navigate to inspect the current list of CMDB classes, review class attribute counts, and check identification rules?

A.System Definition > Tables
B.Configuration > CI Class Manager
C.System UI > Forms
D.Configuration > CMDB Health Dashboard
AnswerB

The CI Class Manager provides a hierarchical view of CMDB classes, showing attribute counts per class and the identification rules configured for each, giving administrators a single place to inspect class structure and reconciliation criteria.

Why this answer

The CI Class Manager (Configuration > CI Class Manager) is the dedicated ServiceNow interface for inspecting and managing CMDB classes, viewing class attributes and their counts, and configuring identification rules per class. It centralizes class hierarchy, attribute metadata, and identification/reconciliation settings in one place.

Exam trap

CIS-DF often tests the distinction between raw table administration (System Definition > Tables) and CMDB-specific tooling (CI Class Manager) — candidates pick the generic table view and miss the CMDB-aware interface.

How to eliminate wrong answers

Option A is wrong because System Definition > Tables shows raw table schema and dictionary entries, not the CMDB class hierarchy, attribute counts, or identification rules in a CMDB-aware view. Option C is wrong because System UI > Forms controls form layout and design, not CMDB class metadata. Option D is wrong because the CMDB Health Dashboard reports on health metrics (completeness, correctness, compliance) but does not let you inspect class attribute counts or edit identification rules.

Practice this question →
51
MCQhard

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?

A.The CMDB Health dashboard will automatically delete all records in this custom table.
B.Business rules on the base cmdb table will prevent any inserts into the custom table.
C.CIs belonging to this class cannot be viewed in Dependency Views.
D.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.
AnswerD

Without a class-specific identification rule, the IRE cannot match inbound payloads to existing records for that class. It falls back to out-of-the-box system rules or inserts new records, producing duplicates that corrupt CMDB integrity and require manual remediation.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that identification rules are optional metadata; in reality, missing rules cause the IRE to fall back to parent or system rules, producing duplicates rather than blocking inserts or breaking views.

How to eliminate wrong answers

Option A is wrong because the CMDB Health dashboard reports on data quality (duplicates, staleness, orphan CIs) but never auto-deletes records in any table. Option B is wrong because business rules on cmdb do not block inserts into child tables by default; inserts proceed unless a specific before-insert rule is authored to prevent them. Option C is wrong because Dependency Views render relationships from cmdb_rel_ci, which is independent of whether an identification rule exists — CIs can still appear in dependency maps.

Practice this question →
52
Multi-Selectmedium

An administrator is reviewing class hierarchy design principles in the CMDB. Which TWO statements describe the purpose of extending existing CI classes rather than creating independent base tables? (Choose two.)

Select 2 answers
A.Inherited classes ensure proper compatibility with CMDB Health, IRE, and Dependency Views.
B.Child classes automatically inherit standard attributes and behaviors from their parent class.
C.Independent base tables provide better integration with out-of-the-box Service Graph Connectors automatically.
D.Extending base tables allows CIs to bypass mandatory access control lists (ACLs).
E.Creating independent tables eliminates the need for any identification rules.
AnswersA, B

Extending an existing CI class means records inherit its schema and class lineage, so CMDB Health, IRE and Dependency Views recognise them correctly. This satisfies the stem's requirement for statements describing why inheritance is preferred over independent base tables.

Why this answer

Option A is correct because extending an existing CI class keeps the new class within the CMDB class hierarchy, so platform features such as CMDB Health, Identification and Reconciliation Engine (IRE), and Dependency Views continue to recognize and process the CIs correctly. Option B is correct because child classes inherit the parent class's attributes, fields, and behaviors, so administrators only add the extra attributes specific to the new CI type instead of redefining everything. Option C is incorrect because independent base tables are not automatically integrated with out-of-the-box Service Graph Connectors; those connectors target the standard CMDB class hierarchy.

Option D is incorrect because extending a base table does not bypass ACLs; access control is still enforced on the class and its records. Option E is incorrect because independent tables still require identification rules (or equivalent logic) to uniquely identify and reconcile CIs.

Exam trap

CIS-DF often tests the misconception that creating a new base table gives more flexibility — in reality it severs the CI from the platform's OOB identification, health, and dependency logic.

Practice this question →
53
MCQeasy

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?

A.cmdb
B.task
C.cmdb_ci
D.cmdb_rel_ci
AnswerC

The cmdb_ci table sits at the root of the CMDB class hierarchy, and virtually every CI class extends it directly or indirectly. Extending it inherits core fields such as name, sys_class_name and operational status, enabling consistent identification and reconciliation across all CI types.

Why this answer

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.

Exam trap

The trap is confusing the CMDB namespace prefix ('cmdb') or the relationship table (cmdb_rel_ci) with the actual root CI class (cmdb_ci); candidates must know that cmdb_ci is the base class.

How to eliminate wrong answers

Option A is wrong because 'cmdb' is not a table — it is a prefix/namespace used for CMDB tables, not a parent class. Option B is wrong because 'task' is the parent class for task-oriented records (incidents, changes, problems), not for CIs. Option D is wrong because cmdb_rel_ci is the table that stores relationships between CIs, not the parent class of CI types.

Practice this question →
54
MCQmedium

Your organization wants to understand the impact of a failing database server on dependent business applications. Which component of the CMDB architecture must be configured to establish this dependency link?

A.CI Class Manager
B.Configuration Item Relationship (cmdb_rel_ci)
C.Identification and Reconciliation Engine (IRE)
D.Discovery Schedule
AnswerB

The cmdb_rel_ci table stores parent-child relationships between configuration items, so linking the database server CI to dependent application CIs exposes the downstream business impact of its failure. Without these relationship records, no dependency mapping or impact analysis is possible.

Why this answer

Relationships between configuration items are stored in the Configuration Item Relationship table (cmdb_rel_ci), defining how CIs depend on or connect to one another.

Practice this question →
55
Multi-Selecthard

When designing class hierarchy relationships and investigating class behaviors in the CI Class Manager, which THREE options represent capabilities or configurations managed within the CI Class Manager? (Choose three.)

Select 3 answers
A.Configuring Identification and Reconciliation Engine (IRE) identification rules for the class.
B.Setting up reconciliation definitions to control data source update priorities.
C.Viewing and managing class attributes and inheritance hierarchy.
D.Creating custom database views across unrelated application tables.
E.Writing custom JavaScript business logic to execute during Discovery credential checks.
AnswersA, B, C

IRE identification rules are configured per class within the CI Class Manager, letting you define the attributes and precedence that determine how incoming records merge into existing CIs. This directly satisfies the stem's focus on class hierarchy relationships and behaviours, since identification rules govern how each class recognises and reconciles its own instances.

Why this answer

In the CI Class Manager, option A is correct because it is the interface where administrators create and edit Identification and Reconciliation Engine (IRE) identification rules that determine how CIs of a given class are uniquely identified from discovery and import sources. Option B is correct because reconciliation definitions (data source precedence/update priorities) are configured per class in the CI Class Manager to control which source wins when multiple sources update the same CI attribute. Option C is correct because the CI Class Manager provides the class hierarchy explorer where you view, create, and manage class attributes, inheritance, and parent-child relationships.

Option D is not correct because custom database views across unrelated tables are built with database tooling or reporting/performance analytics, not the CI Class Manager. Option E is not correct because custom JavaScript for Discovery credential checks is handled through Discovery patterns/sensors and MID Server scripting, not class hierarchy configuration.

Exam trap

CIS-DF often tests the misconception that CI Class Manager can create database views or write JavaScript, when its scope is limited to class configuration, IRE rules, and reconciliation.

Practice this question →
56
MCQmedium

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?

A.Discovery Source Exclusion rules
B.Reconciliation Definitions
C.CI Class Manager attribute properties
D.Access Control Lists (ACLs) on the cmdb_ci table
AnswerB

Reconciliation Definitions in Configuration Manager specify precedence rules per CI class, letting administrators lock critical attributes so low-priority discovery sources cannot overwrite them while higher-priority integrations still update them. This directly satisfies the requirement to protect specific attributes from lower-priority discovery data.

Why this answer

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.

Exam trap

CIS-DF often tests the confusion between reconciliation (source precedence per attribute) and exclusion (blocking a source entirely) — candidates pick Discovery Source Exclusion or ACLs when the requirement is selective, priority-based attribute updates.

How to eliminate wrong answers

Option A is wrong because Discovery Source Exclusion rules prevent a source from updating CIs entirely, which is too broad — it does not allow higher-priority sources to update while blocking lower-priority ones. Option C is wrong because CI Class Manager attribute properties control metadata like mandatory/read-only flags, not source-based precedence during reconciliation. Option D is wrong because ACLs on cmdb_ci control user/role access to records, not discovery source precedence — ACLs govern who can read/write, not which integration wins.

Practice this question →
57
MCQhard

A CMDB administrator is reviewing the CMDB Health Dashboard and notices a low score for 'Duplicate CIs'. They need to identify the root cause. Which action should they take first?

A.Disable all discovery sources to prevent further duplicates.
B.Increase the CMDB Health Dashboard's duplicate threshold to improve the score.
C.Merge all duplicate CIs manually using the CI Class Manager.
D.Run the CMDB Health Dashboard's 'Duplicate CIs' report to list all duplicates.
AnswerD

The CMDB Health Dashboard provides a 'Duplicate CIs' report that lists all duplicate CIs and their details. Running this report is the first step to identify which CIs are duplicated, their classes, and potential sources. This data is essential for diagnosing the root cause.

Why this answer

The first step is to run the 'Duplicate CIs' report from the CMDB Health Dashboard to get a list of duplicates. This provides the necessary information to analyze patterns, such as which discovery sources or identification rules are causing duplicates. Disabling discovery, manually merging, or changing thresholds do not address the root cause and may worsen the situation.

Exam trap

The trap here is jumping to remediation like merging or disabling discovery before diagnosing the cause, which can lead to recurring duplicates or data loss.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Configuration questions.

Start 20-question session