Courseiva

ServiceNow Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) (CIS-DF) (CIS-DF) — Questions 1–75

272 questions total · 4 pages · All types, answers revealed

Take a mock examExam hub

Page 1 of 4

Page 2
1
Multi-Selecthard

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

Select 3 answers
A.Users can filter displayed relationships by specific relationship types.
B.It is used to configure CSDM technical service offerings and portfolios.
C.It graphically displays upstream and downstream CI relationships and dependencies.
D.It automatically executes network ping commands on every node during map rendering.
E.It can display alert indicators and status badges on CI nodes.
AnswersA, C, E

Dependency Views supports filtering by relationship type, letting users isolate specific connection categories within the displayed map. This satisfies the scenario's requirement to narrow visualised relationships, since the view renders multiple relationship types simultaneously and filtering reduces noise without altering the underlying dependency data.

Why this answer

Option A is correct because Dependency Views provides filtering controls that let users narrow the displayed relationships by specific relationship types, so only the relevant dependency links are shown. Option C is correct because the core purpose of Dependency Views is to render a graphical map of CIs along with their upstream and downstream relationships and dependencies. Option E is correct because CI nodes in the map can be decorated with alert indicators and status badges reflecting health, alerts, and operational state.

Option B is not correct because CSDM technical service offerings and portfolios are configured in the CSDM/Service Portfolio data model, not through the Dependency Views visualization. Option D is not correct because Dependency Views renders relationships from CMDB data and does not automatically execute network ping commands against every node during map rendering.

Full explanation →
2
Multi-Selecthard

An architect is troubleshooting an integration payload processed by the Identification and Reconciliation Engine (IRE) that resulted in an error. Which THREE of the following scenarios commonly trigger IRE processing errors? (Choose three.)

Select 3 answers
A.The incoming payload is missing attributes required by the class's identification rule criteria.
B.The target table does not have any UI Policies defined on its form view.
C.The import set table row count exceeds 1,000 records per batch.
D.The discovery source string specified in the payload is not registered or formatted correctly for precedence evaluation.
E.A referenced parent CI in the payload cannot be identified or resolved.
AnswersA, D, E

Identification rules match incoming CIs against specified attributes; when the payload omits any attribute those criteria require, the IRE cannot resolve a match and returns a processing error. This directly satisfies the scenario of payloads failing IRE identification.

Why this answer

Option A is correct because IRE identification rules depend on specific attributes (such as serial number, name, or IP address) being present in the payload; if those required attributes are missing, the engine cannot match the incoming data to an existing CI and raises a processing error. Option D is correct because the discovery source value drives precedence and reconciliation logic in IRE; an unregistered or malformed discovery source string prevents the engine from evaluating precedence correctly and results in an error. Option E is correct because when a payload references a parent CI (for example via a relation or lookup), IRE must resolve that parent to a valid CI record; if the parent cannot be identified, the dependent CI cannot be processed and an error occurs.

Option B is not relevant because UI Policies affect form behavior in the platform UI, not IRE payload processing. Option C is not relevant because IRE does not impose a 1,000-record-per-batch limit as a common error trigger; batch size is a general import consideration, not an IRE identification/reconciliation failure cause.

Full explanation →
3
MCQeasy

What is the primary visual benefit of using Dependency Views during change management planning?

A.Executing automated software deployments to target servers.
B.Calculating financial depreciation schedules for hardware assets.
C.Identifying upstream and downstream CIs that could be impacted by a change on a target CI.
D.Running vulnerability scans against network endpoints.
AnswerC

Dependency Views render the CMDB relationship map around a target CI, exposing upstream and downstream dependencies. During change planning this reveals which services and CIs could be impacted, satisfying the stem's requirement for a primary visual benefit when assessing change risk.

Why this answer

Dependency Views helps change managers identify downstream infrastructure and upstream services that might be affected by a planned change on a CI.

Full explanation →
4
MCQmedium

An enterprise wants to ensure that data stewards are automatically notified when duplicate CIs are detected by the Identification and Reconciliation Engine (IRE). How can this governance requirement be streamlined?

A.Set up a scheduled data import transform map script
B.Modify the Identification Engine processor script directly
C.Configure CMDB Duplicate Remediation rules
D.Write a custom Business Rule on the sys_object_source table
AnswerC

CMDB Duplicate Remediation rules generate tasks automatically when IRE detects duplicate CIs, assigning them to the relevant data stewards. This satisfies the governance requirement for automatic notification without manual monitoring, since the rules run as part of the duplicate remediation workflow.

Why this answer

Configuring CMDB Duplicate Remediation rules allows the system to automatically detect duplicate CIs and notify data stewards based on predefined conditions. These rules can trigger notifications, assign tasks, or even merge duplicates, streamlining governance. This approach leverages out-of-the-box functionality rather than custom scripting, ensuring maintainability and scalability.

Exam trap

CIS-DF often tests the misconception that custom scripts or direct modifications are needed for governance, but the correct answer is to use built-in CMDB Duplicate Remediation rules.

How to eliminate wrong answers

Option A is wrong because a scheduled data import transform map script is for data loading, not for duplicate detection and notification. Option B is wrong because modifying the Identification Engine processor script directly is risky, unsupported, and not a streamlined governance approach; it could break IRE functionality. Option D is wrong because writing a custom Business Rule on the sys_object_source table is a custom solution that may not be triggered by IRE duplicate detection and is not the recommended streamlined method.

Full explanation →
5
MCQmedium

An IT director wants to identify all business applications that do not have an assigned owner or support group in the CMDB. Which ServiceNow reporting or dashboard feature is best suited to highlight this specific completeness gap?

A.Discovery Identification Engine log
B.Service Mapping Entry Point report
C.CSDM Data Foundations Dashboard - Sell/Consume stage
D.CMDB Health Dashboard - Completeness metric
AnswerD

The CMDB Health Dashboard's Completeness metric specifically scores CIs against required fields, including owner and support group, and surfaces those failing the check. This directly highlights the applications missing assigned ownership, satisfying the director's need to isolate that completeness gap rather than broader data quality issues.

Why this answer

The CMDB Health Dashboard's Completeness metric is purpose-built to measure whether required CMDB fields (such as 'Owned by' and 'Support group') are populated on configuration items. It runs scheduled completeness audits against CI classes and flags records missing mandatory attributes, which is exactly the 'no owner / no support group' gap the director wants surfaced. Because it aggregates results into KPIs and drill-down reports, it directly highlights the specific completeness deficiency rather than showing discovery or mapping activity.

Exam trap

CIS-DF often tests the confusion between CMDB Health completeness (missing required field values on CIs) and CSDM Data Foundations dashboards (domain/relationship maturity), so candidates pick the CSDM dashboard when the question is really about missing attribute values.

How to eliminate wrong answers

Option A is wrong because the Discovery Identification Engine log records how discovery probes matched or failed to match CIs during identification and reconciliation — it reports discovery processing errors, not missing ownership attributes on existing CIs. Option B is wrong because a Service Mapping Entry Point report shows which entry points (e.g., load balancers, URLs) were used to build service maps and whether mapping succeeded; it has nothing to do with CI ownership completeness. Option C is wrong because the CSDM Data Foundations Dashboard's Sell/Consume stage tracks CSDM domain alignment for products, offerings, and service consumption relationships — it is a maturity/adoption view, not a field-level completeness audit for owner and support group.

Full explanation →
6
MCQmedium

An administrator is configuring a Service Graph Connector for AWS. They need to ensure that the connector only ingests EC2 instances that are currently running, and ignores terminated instances. Which configuration should they apply?

A.Modify the IRE identification rule to exclude instances with state 'terminated'.
B.Enable 'Absence detection' to mark terminated instances as absent.
C.Use a post-import script to delete terminated instances from the CMDB.
D.Set a filter in the connector's data source to only include instances with state 'running'.
AnswerD

Service Graph Connectors allow you to define filters on the data source to limit which records are retrieved from the external system. By filtering for instances with state 'running', the connector will only ingest those CIs, effectively ignoring terminated instances. This is the correct and efficient way to meet the requirement.

Why this answer

Filtering the data source in the Service Graph Connector ensures that only EC2 instances with state 'running' are retrieved from AWS. This prevents terminated instances from being ingested at all, which is efficient and aligns with the requirement. The filter is applied at the source query level, reducing data volume and processing.

Exam trap

The trap here is thinking that absence detection or post-import scripts can prevent ingestion, but only a source filter stops data from being fetched.

Full explanation →
7
MCQmedium

An enterprise wants to offer a standard email service to its employees through the Service Catalog. Which entity in the Sell/Consume domain should be linked to the Catalog Item?

A.Business Application
B.Application Service
C.Service Offering
D.Dynamic CI Group
AnswerC

A Service Offering represents a specific commitment of a service to a consumer group, so linking it to the Catalog Item connects the requestable item to the Sell/Consume domain. This satisfies the requirement to offer a standard email service to employees.

Why this answer

In the CSDM Sell/Consume domain, a Service Offering represents a specific offering of a service to a specific audience (e.g., 'Standard Email Service for Employees'), and it is the entity that catalog items are linked to. This linkage connects the consumer-facing catalog item to the service being delivered.

Exam trap

The trap is picking a technical entity like Application Service or Business Application — candidates must remember that catalog items link to Service Offerings in the Sell/Consume domain, not to operational or design-domain entities.

How to eliminate wrong answers

Option A is wrong because a Business Application is a logical grouping of application functionality in the Design/Plan domain, not a consumer-facing offering. Option B is wrong because an Application Service is the technical runtime view of an application in the Manage/Operate domain, not the offering presented to employees. Option D is wrong because a Dynamic CI Group is a query-based grouping of CIs used for reporting and health, not a service offering that catalog items link to.

Full explanation →
8
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.

Full explanation →
9
MCQhard

A large enterprise uses CSDM to model its services. The CMDB administrator notices that many Business Applications are not linked to any Application Service, causing a gap in the service hierarchy. The administrator needs to identify these unlinked Business Applications and understand which CSDM domain they belong to. Which CSDM domain should the administrator focus on to resolve this issue?

A.Design and Planning
B.Service Consumption
C.Foundation
D.Service Delivery
AnswerD

The Service Delivery domain in CSDM includes Business Applications, Application Services, and Technical Services, and defines how they relate. The linkage between Business Applications and Application Services is a key relationship within this domain, so the administrator should focus here to identify and resolve unlinked Business Applications.

Why this answer

The CSDM Service Delivery domain encompasses Business Applications, Application Services, and Technical Services, and defines their interrelationships. To find Business Applications not linked to Application Services, the administrator must work within this domain. The other domains serve different purposes: Design and Planning focuses on design, Service Consumption on user-facing offerings, and Foundation on base data.

Exam trap

The trap here is confusing the Design and Planning domain with Service Delivery, as both involve Business Applications, but only Service Delivery defines the linkage to Application Services.

Full explanation →
10
Multi-Selectmedium

An organization is troubleshooting duplicate CIs appearing in the CMDB after running a new integration. Which TWO administrative actions should be taken to investigate and resolve this issue? (Choose two.)

Select 2 answers
A.Inspect CI Class Manager identification rules for the affected class to ensure unique attributes are correctly defined.
B.Modify Access Control Lists to hide duplicate CIs from users.
C.Increase the timeout limit on all REST Message records.
D.Review IRE processing logs and payload results to determine why incoming records failed to match existing CIs.
E.Delete all Discovery schedules and recreate them from scratch.
AnswersA, D

Identification rules define which attributes the Identification and Reconciliation Engine uses to uniquely match incoming records. Inspecting CI Class Manager for the affected class confirms whether those unique attributes are correctly defined, directly addressing the duplicate CIs created when the new integration's payloads failed to match existing entries.

Why this answer

Option A is correct because CI Class Manager identification rules define which attributes (such as serial number, name, or IP address) are used to uniquely identify a CI; if these rules are misconfigured or missing for the affected class, incoming records will not match existing CIs and duplicates will be created. Option D is correct because the Identification and Reconciliation Engine (IRE) processing logs and payload results show exactly how each incoming record was evaluated, including which identification rules were applied and why a match failed, which is essential for diagnosing the root cause of duplicate CIs. Option B is incorrect because hiding duplicates via ACLs only masks the symptom and does not resolve the underlying identification problem.

Option C is incorrect because REST Message timeout limits affect outbound request performance, not CI matching or deduplication. Option E is incorrect because deleting and recreating Discovery schedules is a destructive, unrelated action that would not address duplicate CI creation from an integration.

Full explanation →
11
MCQhard

An organization wants to configure remediation rules so that when a CMDB Health Correctness anomaly (such as a duplicate CI) is identified, a remediation task is automatically generated and assigned to the correct data owner. Where are these remediation rules configured?

A.Inside Data Certification definition forms
B.In the CMDB Health Dashboard configuration settings
C.Through Data Policies on the cmdb_ci table
D.In the CI Class Manager under the Remediation tab
AnswerB

Remediation rules live within the CMDB Health Dashboard configuration, where each health metric's task generation and assignment logic is defined. Configuring them there lets a detected correctness anomaly, such as a duplicate CI, automatically spawn a remediation task routed to the appropriate data owner.

Why this answer

CMDB Health remediation rules are configured within the CMDB Health Dashboard configuration, where administrators define which health failures (correctness, completeness, compliance, duplicate) trigger remediation tasks and how those tasks are assigned. This is the centralized location for mapping a health anomaly to a task generation and assignment policy. The rules reference the CI's support group or owner to route the task to the correct data owner.

Exam trap

The trap is confusing Data Certification (periodic attestation campaigns) with CMDB Health remediation (event-driven task generation) — both involve 'data quality tasks' but live in different configuration areas.

How to eliminate wrong answers

Option A is wrong because Data Certification definitions are used to schedule certification campaigns where CI owners attest to data accuracy — they do not generate remediation tasks for CMDB Health anomalies. Option C is wrong because Data Policies enforce attribute-level validation on insert/update (e.g., mandatory fields, regex) but do not create remediation tasks for health scan findings like duplicates. Option D is wrong because the CI Class Manager manages class schema, attributes, and identification rules — it has no Remediation tab for health-based task generation.

Full explanation →
12
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.

Full explanation →
13
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.

Full explanation →
14
MCQhard

A healthcare enterprise uses both ServiceNow Discovery and a third-party asset management tool to update server records in the CMDB. The third-party tool frequently populates stale operational status data. Using Data Source Precedence rules, how can the administrator ensure that ServiceNow Discovery always overrides the third-party tool for the 'Operational status' attribute on Linux servers?

A.Add a Business Rule on cmdb_ci that checks the sys_updated_by field and aborts updates from the third-party source.
B.Modify the Discovery schedule to run after the third-party integration job completes.
C.Navigate to CI Class Manager, select cmdb_ci_linux_server, and configure Data Source Precedence to assign a higher priority to 'ServiceNow' than the third-party source for 'Operational status'.
D.Create an Access Control List (ACL) that restricts write access on the cmdb_ci_linux_server table for the third-party integration user.
AnswerC

Data Source Precedence is configured per CI class and per attribute, so setting 'ServiceNow' above the third-party source for 'Operational status' on cmdb_ci_linux_server makes Discovery's value win. This directly satisfies the stem's constraint that Discovery must always override stale third-party operational status data.

Why this answer

Data Source Precedence rules in ServiceNow allow administrators to define which data source wins when multiple sources update the same CI attribute. By navigating to CI Class Manager, selecting the cmdb_ci_linux_server class, and configuring Data Source Precedence for the 'Operational status' attribute, the administrator can assign a higher priority to 'ServiceNow' (Discovery) than the third-party source. This ensures that when both sources provide data, Discovery's value is authoritative, overriding the stale third-party data.

Exam trap

CIS-DF often tests the misconception that scheduling or access controls can enforce data precedence, when in fact ServiceNow provides a dedicated Data Source Precedence feature within CI Class Manager that must be configured at the attribute level.

How to eliminate wrong answers

Option A is wrong because a Business Rule that aborts updates based on sys_updated_by is a blunt approach that would block all updates from the third-party source, not just for 'Operational status', and it bypasses the built-in precedence mechanism, potentially causing data inconsistencies. Option B is wrong because scheduling Discovery to run after the third-party job does not guarantee precedence; if the third-party job runs again later, it could still overwrite Discovery's data, and it doesn't address attribute-level control. Option D is wrong because an ACL restricting write access would prevent the third-party tool from updating any attributes on Linux servers, which is overly restrictive and does not selectively enforce precedence for 'Operational status' only.

Full explanation →
15
MCQmedium

An IT team wants to create a report that lists all Business Services that depend on a specific database instance, traversing up to three relationship hops away. Which native feature can accomplish this multi-hop relationship extraction?

A.Standard List Report with parent filter
B.CMDB Health Dashboard audit rule
C.Service Mapping Traffic Connection report
D.CMDB Query Builder with multi-node relationship steps
AnswerD

CMDB Query Builder supports multi-node relationship steps, letting you chain hops between CI classes in a single query. That directly satisfies the requirement to traverse up to three relationship hops from the database instance to dependent Business Services.

Why this answer

CMDB Query Builder is the native tool designed for multi-hop relationship traversal across CMDB classes. It lets you define a starting CI class, add relationship steps (hops) between classes, and filter results — exactly what is needed to find Business Services three hops from a database instance. Standard reports cannot traverse arbitrary relationship depths.

Exam trap

The trap is assuming any report can traverse relationships — candidates forget that only CMDB Query Builder supports arbitrary multi-hop traversal, while standard reports are limited to direct parent-child filters.

How to eliminate wrong answers

Option A is wrong because a Standard List Report with a parent filter only shows direct parent-child relationships and cannot traverse multiple relationship hops across classes. Option B is wrong because CMDB Health Dashboard audit rules evaluate completeness, correctness, and compliance metrics — they do not extract multi-hop dependency chains. Option C is wrong because the Service Mapping Traffic Connection report shows discovered traffic-based connections for a mapped service, not an ad-hoc multi-hop query from an arbitrary starting CI.

Full explanation →
16
MCQeasy

Which CSDM domain represents the core conceptual view of applications before they are deployed into specific environments?

A.Design
B.Manage Technical Services
C.Foundation
D.Sell/Consume
AnswerA

The Design domain holds conceptual application models before environment-specific deployment, satisfying the stem's requirement for a pre-deployment view. It captures logical structure and relationships independently of runtime instances, unlike the Manage Technical Service domain, which records deployed services tied to actual environments.

Why this answer

The Design domain in the Common Service Data Model (CSDM) represents the conceptual view of applications and services before they are deployed into specific environments. It includes layers such as Business Capabilities, Business Applications, and Application Services, which define what the application is intended to do and how it is structured logically. This domain is distinct from the Manage Technical Services domain, which deals with the actual deployed instances and their operational management.

Therefore, Design is the correct answer as it captures the pre-deployment, conceptual perspective.

Exam trap

CIS-DF often tests the distinction between the Design domain (conceptual, pre-deployment) and the Manage Technical Services domain (operational, deployed), so candidates must not confuse the two when asked about pre-deployment views.

How to eliminate wrong answers

Option B is wrong because Manage Technical Services represents the operational view of deployed technical services, including their runtime instances and relationships, not the conceptual pre-deployment view. Option C is wrong because Foundation is the lowest CSDM layer that provides the base data model for all other domains, not a specific domain representing conceptual applications. Option D is wrong because Sell/Consume focuses on the commercial aspects of services, such as ordering and consumption, rather than the design-time conceptual view of applications.

Full explanation →
17
MCQhard

An enterprise has multiple child domains. An administrator needs to generate a CMDB Query Builder report that aggregates CIs across all domains while respecting domain separation rules. How does Query Builder handle domain separation?

A.Query Builder automatically evaluates records based on standard domain separation runtime rules and user session visibility.
B.Query Builder requires manual SQL joins on the sys_domain table for every query.
C.Domain separation is ignored by Query Builder; all queries execute globally against root domain data only.
D.Queries fail immediately if domain separation is enabled on the cmdb_ci table.
AnswerA

Query Builder inherits the platform's standard domain separation runtime logic, so an administrator's session visibility determines which child-domain CIs appear in the aggregated report. No separate Query Builder-specific domain filter exists; the report therefore respects domain separation rules automatically across all domains.

Why this answer

CMDB Query Builder respects domain separation rules based on the user's active session domain and domain path settings when querying and returning results.

Full explanation →
18
MCQmedium

An administrator needs to ensure that historical changes to data governance remediation tasks are easily tracked. Which platform feature automatically tracks changes to task work notes, state transitions, and assignments?

A.CMDB Health Audit Table
B.Discovery History Table
C.Task Activity Stream and Audit Log
D.Data Certification Log
AnswerC

The Task Activity Stream records field-level changes and work note additions chronologically on the task record, while the Audit Log captures state transitions and assignment changes, together providing the automatic historical traceability the administrator requires without manual logging.

Why this answer

The Task Activity Stream and Audit Log is the platform feature that automatically records field-level changes, work note additions, state transitions, and assignment changes on task records, including governance remediation tasks. It provides a chronological, filterable history without any custom configuration. This is the native mechanism for tracking who changed what and when on a task.

Exam trap

The trap is confusing CMDB health or certification logs with task-level audit history — candidates pick the 'audit-sounding' option without checking whether it actually tracks task field changes.

How to eliminate wrong answers

Option A is wrong because the CMDB Health Audit Table stores results of CMDB health audits (completeness, correctness, compliance), not task-level change history. Option B is wrong because the Discovery History Table logs discovery runs and their outcomes, not changes to task records. Option D is wrong because the Data Certification Log tracks certification task outcomes and attestation results, not the granular field-level change history of remediation tasks.

Full explanation →
19
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.

Full explanation →
20
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.

Full explanation →
21
Multi-Selecthard

An administrator is troubleshooting missing relationship data after running a custom data integration. Which THREE of the following factors should be investigated? (Choose three.)

Select 3 answers
A.Whether the payload structure correctly formats the related items or relationship blocks required by the IRE.
B.Whether the target CI table has active client scripts blocking the relationship field.
C.Whether the source and target CIs in the relationship payload successfully passed identification.
D.Whether the relationship type (e.g., 'Runs on::Runs') is active and correctly defined in the cmdb_rel_type table.
E.Whether the Discovery status schedule is set to 'Quick Discovery'.
AnswersA, C, D

The IRE parses relationship blocks from the payload; if related items are not formatted as the IRE expects, relationships are silently dropped. Correct payload structure is therefore a primary factor when relationship data goes missing after a custom integration.

Why this answer

Option A is correct because the Identification and Reconciliation Engine (IRE) requires the payload to include properly formatted related items or relationship blocks; if the structure is malformed, the IRE cannot create the relationships. Option C is correct because both the source and target CIs in a relationship payload must successfully pass identification; if either CI fails to identify or be created, the relationship cannot be established. Option D is correct because the relationship type (for example, 'Runs on::Runs') must exist and be active in the cmdb_rel_type table, otherwise the IRE will reject or skip the relationship.

Option B is not correct because client scripts on the target CI table do not block IRE relationship processing, which operates at the server/API level. Option E is not correct because the Discovery status schedule setting is unrelated to custom data integration relationship handling.

Full explanation →
22
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.

Full explanation →
23
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.

Full explanation →
24
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.

Full explanation →
25
MCQmedium

Which CMDB Health metric category evaluates whether CIs have mandatory fields populated, such as Assigned to, Managed by, and Support Group?

A.Freshness
B.Completeness
C.Correctness
D.Compliance
AnswerB

Completeness evaluates whether mandatory fields such as Assigned to, Managed by and Support Group are populated on CIs. It therefore directly satisfies the scenario's requirement to measure missing required attribute values in the CMDB health assessment.

Why this answer

Completeness is the CMDB Health metric category that specifically checks whether mandatory fields on a CI are populated — such as Assigned to, Managed by, and Support Group. It measures the presence of required attribute values rather than their accuracy or timeliness. This is distinct from Correctness (which validates values against expected patterns) and Freshness (which checks update recency).

Exam trap

CIS-DF often tests the distinction between Completeness (fields are populated) and Correctness (fields contain valid values) — candidates frequently swap these two because both sound like 'data quality' checks.

How to eliminate wrong answers

Option A is wrong because Freshness measures how recently a CI was updated or discovered, not whether mandatory fields are populated. Option C is wrong because Correctness evaluates whether populated values are valid/accurate (e.g., matching expected formats or reference data), not whether fields are filled. Option D is wrong because Compliance in CMDB Health refers to adherence to defined audit/validation rules and policy checks, not the presence of mandatory field values.

Full explanation →
26
Multi-Selectmedium

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

Select 2 answers
A.Service Mapping horizontal pattern criteria.
B.Invocation of the IRE API (such as `sn_cmdb.IdentificationEngine`) within the script step.
C.Discovery schedule IP ranges matching the REST server IP.
D.Legacy Transform Map record definitions linked to the REST endpoint.
E.The JSON payload formatted with valid CI classes, identification attributes, and related items.
AnswersB, E

The IntegrationHub action must call the IdentificationEngine scriptable API to submit the payload for identification and reconciliation; without this invocation no IRE processing occurs. This satisfies the requirement that the script step invoke IRE correctly.

Why this answer

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

Option C is not needed because Discovery schedules and IP ranges apply to Discovery, not to an IntegrationHub REST step. Option D is not needed because legacy Transform Maps are bypassed when using the IRE API for identification and reconciliation.

Full explanation →
27
MCQhard

An auditor requires proof that all discovered Linux servers have a validated business justification attribute. The team uses CMDB Data Governance to enforce this. How can the administrator prove to the auditor that the policy is actively running and enforcing this rule?

A.Show the CMDB Data Governance Policy execution history and generated remediation task metrics
B.Provide a screenshot of the Discovery Schedule configuration
C.Export the entire sys_audit table to CSV
D.Display the baseline CI Class Manager JSON payload definition
AnswerA

Policy execution history records each governance run, showing which CIs were evaluated and which failed the business justification rule. Remediation task metrics evidence that non-compliant records generated enforcement actions, giving the auditor verifiable proof the policy actively runs rather than existing as documentation only.

Why this answer

CMDB Data Governance policies maintain execution history and generate remediation task metrics that serve as auditable evidence. By showing the policy's execution history (when it ran, what it evaluated) and the generated remediation tasks (with timestamps, assignees, and statuses), the administrator can prove the policy is actively running and enforcing the business justification rule. This is the direct, purpose-built evidence an auditor needs.

Exam trap

CIS-DF often tests the difference between configuration evidence (screenshots of schedules or schemas) and operational evidence (execution history and task metrics), so candidates who pick Discovery Schedule or CI Class Manager miss that auditors require proof of active enforcement.

How to eliminate wrong answers

Option B is wrong because a Discovery Schedule screenshot only proves discovery is configured — it says nothing about whether the business justification policy is running or enforcing. Option C is wrong because exporting the entire sys_audit table is overbroad, noisy, and does not specifically demonstrate policy execution or enforcement of the business justification attribute. Option D is wrong because the baseline CI Class Manager JSON payload defines the class schema — it shows the attribute exists but not that the policy is actively enforcing it.

Full explanation →
28
Multi-Selectmedium

Which TWO of the following features are associated with Service Mapping visualization and insights? (Choose two.)

Select 2 answers
A.Traffic connection views showing live network communication flows
B.CMDB Health Dashboard compliance staleness scorecards
C.Application service maps showing entry points and dependent infrastructure
D.Automated CMDB duplicate CI merging wizards
E.CMDB Baseline configuration diff snapshots
AnswersA, C

Traffic connection views satisfy the live network communication flows requirement by rendering discovered TCP connections between configuration items, mapping each service's actual runtime dependencies rather than static records. This visualisation exposes communication paths and traffic direction across the estate, which is precisely the insight Service Mapping provides.

Why this answer

Service Mapping provides application topology maps and traffic connection views.

Full explanation →
29
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.

Full explanation →
30
MCQmedium

An architect is designing an integration to ingest virtual machines from a custom cloud provider into the CMDB using Robust Transform Engine (RTE). The payload contains nested objects representing datastores attached to each VM. How should the RTE be configured to handle these related child objects?

A.Set the coalesce field on the Transform Map to point to the datastore ID.
B.Flatten the JSON payload in a Business Rule before it reaches the Import Set table.
C.Configure RTE Related Item Processors to define the relationship and map fields from the nested datastore object to the target relationship table.
D.Create two separate import set tables and link them using a standard GlideRecord script in a Transform Map.
AnswerC

Related Item Processors are the RTE mechanism that parses nested child objects and writes them to relationship tables, mapping datastore fields to the target. Without them the nested datastores would be ignored or flattened, so this satisfies the requirement to ingest related child objects.

Why this answer

RTE (Robust Transform Engine) handles nested JSON objects through Related Item Processors, which are configured on the Transform Map to define the relationship between the parent record and child records, and to map fields from the nested object to the target relationship table. This is the native RTE mechanism for parsing hierarchical payloads without pre-flattening.

Exam trap

CIS-DF often tests whether candidates know that RTE has a built-in Related Item Processor feature for nested objects, rather than assuming they must flatten JSON or write custom scripts — a common misconception among engineers familiar only with the legacy transform engine.

How to eliminate wrong answers

Option A is wrong because setting a coalesce field on the Transform Map only controls deduplication of the parent record — it does nothing to parse or create related child records from nested objects. Option B is wrong because flattening the JSON in a Business Rule before it reaches the Import Set table bypasses RTE's native nested-object handling and adds unnecessary custom code, defeating the purpose of using RTE. Option D is wrong because creating two separate import set tables and linking them with a GlideRecord script in a Transform Map is a manual, brittle workaround that RTE's Related Item Processors are specifically designed to replace.

Full explanation →
31
MCQmedium

An administrator is configuring a Service Graph Connector. They notice that the integration is failing because the inbound payload uses a custom field name for the serial number instead of the standard IRE attribute name `serial_number`. How should this mapping discrepancy be resolved without altering the external source system?

A.Modify the target CI table dictionary to rename the `serial_number` column to match the external system's custom field name.
B.Configure an RTE field mapping to translate the custom source field name to the standard `serial_number` attribute expected by the IRE payload.
C.Create a Business Rule on the staging table to drop the custom field.
D.Update the CI Class Manager identification rule to use the custom field name.
AnswerB

RTE field mappings translate the source's custom serial number field into the IRE's expected serial_number attribute during ingestion, so the external system stays untouched. This directly resolves the mapping discrepancy without altering the source payload.

Why this answer

RTE field mappings are designed to translate source field names to target IRE payload attributes. By configuring an RTE field mapping, the custom source field name is mapped to the standard `serial_number` attribute expected by the IRE, allowing the integration to succeed without modifying the external system. This is the intended use of RTE's mapping layer.

Exam trap

CIS-DF often tests the misconception that identification rules or dictionary changes can resolve field name mismatches, when in fact RTE field mappings are the correct layer for translating source field names to IRE attributes.

How to eliminate wrong answers

Option A is wrong because renaming the `serial_number` column in the target CI table dictionary would break the CMDB schema and all other integrations relying on the standard attribute name. Option C is wrong because a Business Rule on the staging table that drops the custom field would discard data, not map it, and would not resolve the mapping discrepancy. Option D is wrong because the CI Class Manager identification rule defines how CIs are identified (e.g., by serial number, name), but it does not translate source field names to IRE payload attributes; that is the role of RTE field mappings.

Full explanation →
32
MCQhard

An organization wants to track performance metrics for Service Mapping, specifically measuring the average time taken to complete full discovery maps across all critical business services. Which reporting feature provides this analytics capability?

A.Discovery Schedule Log export
B.Performance Analytics widgets and dashboards for Service Mapping
C.CMDB Health Dashboard Completeness scores
D.CMDB Query Builder execution statistics
AnswerB

Performance Analytics pulls time-series data from Service Mapping discovery runs, letting you aggregate mean completion duration across every critical business service. Standard reporting cannot compute this rolling average, so the widgets and dashboards satisfy the stem's requirement for average full-map discovery time analytics.

Why this answer

Performance Analytics combined with Service Mapping execution logs or out-of-the-box PA widgets for Service Mapping track duration and map completion performance.

Full explanation →
33
Multi-Selecthard

An administrator is reviewing the CMDB IRE execution logs and notices numerous warnings regarding payloads that skipped attribute updates. Which THREE of the following reasons would cause the IRE to skip updating an attribute on an existing CI? (Choose three.)

Select 3 answers
A.The attribute is configured to be ignored when incoming values are empty, and the incoming payload provided a blank value.
B.The target CI table has an active Business Rule that aborts all updates.
C.The incoming data source has a lower Data Source Precedence than the source that last populated that attribute.
D.The incoming attribute value is identical to the existing attribute value already stored in the CI record.
E.The user executing the integration does not have read access to the sys_user table.
AnswersA, C, D

IRE honours per-attribute ignore rules for empty incoming values, so a blank payload field is skipped rather than written. This protects existing CI data from being cleared by integrations that omit or null out attributes.

Why this answer

Option A is correct because the Identification and Reconciliation Engine honors the 'ignore empty values' setting on an attribute; when the incoming payload supplies a blank value and that flag is enabled, the IRE skips the update rather than overwriting the existing value. Option C is correct because Data Source Precedence determines which source is authoritative for a given attribute; if the incoming data source has lower precedence than the source that last populated the attribute, the IRE will not overwrite the existing value. Option D is correct because the IRE performs a value comparison and skips the write when the incoming value is identical to the value already stored, avoiding a no-op update.

Option B is not a valid reason because IRE processing does not evaluate table-level Business Rules to decide whether to update an attribute; Business Rules run on record operations, not on the IRE's attribute-level reconciliation logic. Option E is not a valid reason because read access to sys_user is unrelated to attribute-level update decisions in the IRE; the IRE's skip logic is driven by attribute configuration, data source precedence, and value comparison, not by the executing user's access to an unrelated table.

Full explanation →
34
MCQhard

An administrator needs to configure score weightings on the CMDB Health Dashboard so that Correctness carries 50% weight, Completeness carries 30%, and Compliance carries 20%. Where is this configured?

A.Performance Analytics > Widgets
B.CI Class Manager > Health Properties
C.CMDB Health Dashboard > Metric Settings / Weightings
D.System Properties > CMDB > Governance
AnswerC

Weightings are set under CMDB Health Dashboard metric settings, where each health metric — Correctness, Completeness, Compliance — receives a percentage that must total 100. This satisfies the stem's exact 50/30/20 split, since the dashboard reads those configured values when calculating the aggregate health score.

Why this answer

Score weightings for CMDB Health (Correctness, Completeness, Compliance, and Relationship) are configured in the CMDB Health Dashboard under Metric Settings / Weightings. This is where administrators set the percentage contribution each health metric makes to the overall health score. Setting Correctness to 50%, Completeness to 30%, and Compliance to 20% is done there.

Exam trap

The trap is confusing class-level Health Properties (which metrics apply to a class) with global Metric Settings/Weightings (how much each metric counts) — candidates often pick CI Class Manager when the question asks about weighting percentages.

How to eliminate wrong answers

Option A is wrong because Performance Analytics > Widgets is for building and configuring PA dashboards and widgets, not for CMDB Health score weighting. Option B is wrong because CI Class Manager > Health Properties controls which health metrics and KPIs apply to a specific CI class, not the global weighting percentages across metrics. Option D is wrong because System Properties > CMDB > Governance holds governance-related properties (e.g., task creation behavior), not the health score weighting configuration.

Full explanation →
35
MCQmedium

An administrator is troubleshooting a Scheduled Data Import that uses an IntegrationHub REST step to pull server data. The import completes, but no CIs are created or updated in the CMDB, and the import set rows show a status of 'Processed'. Where should the administrator check to see if the IRE rejected the payload?

A.Check the System Log (syslog) for standard warning messages tagged with 'TransformMap'.
B.Check the CMDB Integration Results (cmdb_integration_log) or IRE processing logs for detailed payload error messages.
C.Review the Email Notifications table for failed ingestion alerts.
D.Inspect the Discovery Status dashboard.
AnswerB

The CMDB Integration Results table and IRE processing logs capture per-payload rejection reasons, satisfying the need to confirm whether IRE discarded the payload. Import set rows showing 'Processed' only confirm transform completion, not IRE acceptance, so these logs reveal the actual error.

Why this answer

The Identification and Reconciliation Engine (IRE) processes import set rows after they are marked 'Processed' by the transform. When IRE rejects a payload—due to missing required attributes, duplicate detection conflicts, or failed reconciliation rules—it does not create or update CIs, but the import set row status remains 'Processed' because the transform itself succeeded. Detailed rejection reasons, including the specific payload and rule that failed, are written to the CMDB Integration Results table (cmdb_integration_log) and IRE processing logs, not to the standard transform warnings.

Therefore, option B is the correct place to investigate IRE rejections.

Exam trap

CIS-DF often tests the misconception that a 'Processed' import set row means the CI was successfully created or updated, leading candidates to overlook IRE-specific logs and instead check generic system logs or dashboards.

How to eliminate wrong answers

Option A is wrong because the System Log (syslog) with 'TransformMap' warnings only captures transform-level issues (e.g., script errors, field mapping problems), not IRE rejection details; IRE operates after the transform and logs to its own tables. Option C is wrong because Email Notifications are not automatically generated for IRE rejections; they require custom business rules or notifications to be configured, and they do not contain the detailed payload error messages needed for troubleshooting. Option D is wrong because the Discovery Status dashboard is used for Discovery schedules and probes, not for IntegrationHub REST step imports or IRE processing; it would not show IRE rejection details.

Full explanation →
36
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.

Full explanation →
37
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.

Full explanation →
38
MCQmedium

An IT manager wants to track software license compliance and installations for a commercial database product. Which table in the Manage Technical Services or Foundation domain represents the installed software instance?

A.Installed Software / Software Instance [cmdb_ci_spkg or cmdb_install_sw]
B.Business Application [cmdb_ci_business_app]
C.Application Service [cmdb_ci_service_calculated]
D.Service Offering [service_offering]
AnswerA

Installed software instances are stored as cmdb_ci_spkg records (software package) or cmdb_install_sw, which capture the product, version and host CI. This table represents the actual installed instance, satisfying the requirement to track licence compliance and installations for the commercial database.

Why this answer

The Installed Software / Software Instance table (cmdb_ci_spkg for software packages and cmdb_install_sw for installed instances) is the CMDB table that represents a specific installation of software on a device. It captures the software product, version, install date, and the host CI it runs on, which is exactly what is needed to track license compliance and installation counts for a commercial database product. Business Applications, Application Services, and Service Offerings are logical/architectural constructs and do not represent installed binaries on a server.

Exam trap

CIS-DF often tests the distinction between logical CSDM constructs (Business Application, Application Service, Service Offering) and the physical installed software CI tables — candidates pick the logical layer because it sounds more 'governance-oriented'.

How to eliminate wrong answers

Option B is wrong because Business Application (cmdb_ci_business_app) represents a logical business application used by the enterprise, not a specific installed software instance on a host — it cannot tell you how many copies of a database are installed. Option C is wrong because Application Service (cmdb_ci_service_calculated) is a CSDM construct representing a service delivered by a combination of CIs, not an installed software package. Option D is wrong because Service Offering (service_offering) is a CSDM/Service Portfolio construct describing what is offered to consumers, not what is installed on a server.

Full explanation →
39
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.

Full explanation →
40
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.

Full explanation →
41
Multi-Selecthard

An administrator is troubleshooting an issue where records ingested via Robust Transform Engine (RTE) are failing to populate the CMDB. Upon inspecting the Robust Transform Engine execution logs, they see errors related to payload identification. Which THREE of the following troubleshooting steps should they perform? (Choose three.)

Select 3 answers
A.Restart all MID Servers across the enterprise network.
B.Inspect CI Class Manager identification rules for the target class to ensure the mapped attributes match rule criteria.
C.Check the CMDB Integration Results and IRE execution logs for detailed error descriptions.
D.Modify the instance web server memory allocation via system properties.
E.Verify that source fields are correctly mapped to mandatory identification attributes in the RTE field map.
AnswersB, C, E

Identification rules in CI Class Manager define which attributes IRE uses to match incoming payloads to existing CIs. If mapped attributes do not align with rule criteria, identification fails, so verifying these rules directly addresses the payload identification errors logged by RTE.

Why this answer

Option B is correct because payload identification failures often stem from the target class's identification rules in CI Class Manager not matching the attributes being sent, so verifying that the mapped attributes satisfy the rule criteria is essential. Option C is correct because the CMDB Integration Results and Identification and Reconciliation Engine (IRE) execution logs provide the detailed error descriptions needed to pinpoint why identification is failing after RTE processing. Option E is correct because RTE relies on the field map to translate source payload fields into the mandatory identification attributes (such as serial number, name, or sys_class_name) required by the identification rules, and a mis-mapping directly causes payload identification errors.

Option A is not appropriate because restarting MID Servers does not address identification logic or field mapping issues and would only disrupt data collection. Option D is not appropriate because modifying web server memory allocation via system properties is unrelated to RTE payload identification and would not resolve mapping or identification rule mismatches.

Full explanation →
42
MCQeasy

A configuration manager is setting up a new data import using an Excel file. They want the import to automatically create or update CIs in the CMDB while ensuring that duplicates are not created. Which method should they use to achieve this?

A.Service Graph Connector
B.Direct table insert via background script
C.CMDB API with custom matching logic
D.Import Set with Transform Map and Coalesce
AnswerD

Using an Import Set with a Transform Map and configuring coalesce fields allows the import to match incoming records to existing CIs based on specified fields. If a match is found, the record is updated; otherwise, a new CI is created. This prevents duplicates and is the standard approach for importing data into the CMDB.

Why this answer

Import Sets with Transform Maps and coalesce fields are the standard way to import data into ServiceNow while preventing duplicates. The coalesce fields define which fields must match for an existing record to be updated instead of creating a new one. This leverages the platform's built-in identification logic and is ideal for Excel-based imports.

Exam trap

The trap here is assuming that any import method automatically prevents duplicates, but only those that use coalesce or IRE do so.

Full explanation →
43
Multi-Selectmedium

Which TWO actions can be taken from the CMDB Data Governance application interface? (Choose two.)

Select 2 answers
A.Defining and editing data quality policies
B.Writing custom web server Apache configurations
C.Managing ITIL change request CAB approval boards
D.Monitoring and reviewing generated remediation tasks
E.Configuring MID Server SSL encryption keys
AnswersA, D

Defining and editing data quality policies is performed directly within the CMDB Data Governance application interface, satisfying the stem's requirement for actions available there. This interface governs data quality rules centrally, letting administrators create and modify policies without leaving the application, which matches the scenario's constraint of interface-native actions.

Why this answer

Option A is correct because the CMDB Data Governance application provides the interface for creating, defining, and editing data quality policies that specify the rules and thresholds used to evaluate CMDB data health. Option D is correct because the same application lets administrators monitor data quality results and review the remediation tasks that are generated when policy violations are detected, so owners can act on them. The other options do not belong: writing custom Apache web server configurations (B) is a web-tier administration task unrelated to CMDB governance, managing ITIL change request CAB approval boards (C) is done in Change Management, and configuring MID Server SSL encryption keys (E) is handled through MID Server and certificate/key management, not the CMDB Data Governance interface.

Full explanation →
44
MCQhard

An administrator is troubleshooting a Service Mapping map where a load balancer is mapped correctly, but the backend web servers are missing from the topology. Upon checking the traffic connections, the traffic is visible, but the map traversal stopped. What is the most common reason for this behavior in Service Mapping?

A.The CMDB Query Builder cache expired during the scan.
B.The discovery pattern lacks the specific extension or credentials to traverse from the load balancer to the backend nodes.
C.The cmdb_rel_ci table has exceeded maximum indexing thresholds.
D.The CMDB Health Correctness rule flagged the load balancer as a duplicate.
AnswerB

Traversal halts when the pattern cannot authenticate or lacks a step to query the load balancer's backend pool members. Since traffic is visible but the map stops, the missing extension or credentials prevent discovering the web servers, satisfying the requirement to explain why backend nodes never appear.

Why this answer

Service Mapping requires discovery credentials and patterns to traverse from load balancers to backend nodes; if credentials fail or patterns aren't assigned, mapping stops.

Full explanation →
45
MCQeasy

An administrator wants to view the hierarchical relationship and physical connections between a Business Application and its underlying database infrastructure in the CMDB. Which feature should they open from the Configuration Item form?

A.Service Portfolio Management
B.Dependency Views
C.Map Builder
D.CMDB Query Builder
AnswerB

Dependency Views renders a hierarchical, connection-aware map of CIs and their relationships, letting administrators trace a Business Application down to its underlying database infrastructure. This satisfies the requirement to view hierarchical and physical connections from the CI form.

Why this answer

Dependency Views is the ServiceNow feature that renders a hierarchical, graphical map of a CI and its relationships, including physical and logical connections. Opening Dependency Views from a CI form (via the related links or UI action) shows the Business Application, its underlying database, and the infrastructure path between them, making it the correct tool for visualizing application-to-infrastructure relationships.

Exam trap

CIS-DF often tests the confusion between Dependency Views (interactive CI relationship visualization) and CMDB Query Builder (multi-class query/reporting) — candidates pick Query Builder because it also deals with CMDB data, but it does not provide the hierarchical dependency map.

How to eliminate wrong answers

Option A is wrong because Service Portfolio Management is for managing the portfolio of services (demand, planning, costing), not for visualizing CI relationships. Option C is wrong because Map Builder is a tool for creating custom relationship maps and is not the standard feature opened from a CI form to view dependencies — Dependency Views is the native visualization. Option D is wrong because CMDB Query Builder is for building multi-class queries and reports, not for interactive hierarchical dependency visualization.

Full explanation →
46
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.

Full explanation →
47
MCQhard

When implementing the CSDM framework, your project team must decide where to attach Business Service Offerings. According to CSDM specifications, what is the primary parent of a Service Offering?

A.Business Application [cmdb_ci_business_app]
B.Application Service [cmdb_ci_service_calculated]
C.Service [cmdb_ci_service]
D.User Group [sys_user_group]
AnswerC

In CSDM, a Service Offering's parent is the Service [cmdb_ci_service] record it belongs to. Offerings represent consumable variants of that service, so they hang beneath the service rather than beneath Business Application or Technical Service.

Why this answer

According to CSDM, a Service Offering's primary parent is the Service [cmdb_ci_service] record. Service Offerings represent the consumable commitments (SLAs, pricing, availability) attached to a Service, and the Service is the top-level logical entity in the Sell/Consume domain.

Exam trap

CIS-DF often tests CSDM hierarchy by tempting candidates to attach Service Offerings to Business Applications or Application Services, when the correct primary parent is the Service [cmdb_ci_service] record in the Sell/Consume domain.

How to eliminate wrong answers

Option A is wrong because Business Application [cmdb_ci_business_app] is a Design-domain CI that groups capabilities and services; it is not the parent of a Service Offering. Option B is wrong because Application Service [cmdb_ci_service_calculated] is a technical realization of a service and sits below the Service in the CSDM hierarchy, not above Service Offerings. Option D is wrong because User Group [sys_user_group] represents people, not a service construct, and has no parent relationship to Service Offerings.

Full explanation →
48
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.

Full explanation →
49
MCQhard

When configuring Relationship Filters within Dependency Views, an administrator wants to ensure that only 'Runs on::Runs' and 'Hosted on::Hosts' relationships are rendered by default for all users. Where is this default view behavior configured?

A.CI Class Manager relationship definition tab
B.Service Mapping Properties table
C.CMDB Query Builder global settings
D.System Properties prefixed with glide.ui.dependency_view
AnswerD

System Properties prefixed with glide.ui.dependency_view define the default relationship filters rendered in Dependency Views, letting the administrator restrict rendering to 'Runs on::Runs' and 'Hosted on::Hosts' for all users without per-user configuration. This satisfies the stem's requirement for a global default.

Why this answer

Default Relationship Filters for Dependency Views are controlled by system properties prefixed with glide.ui.dependency_view. These properties define which relationship types are rendered by default when users open a Dependency View, allowing administrators to set global defaults such as 'Runs on::Runs' and 'Hosted on::Hosts'.

Exam trap

The trap is that candidates assume relationship display defaults are configured in CI Class Manager or Service Mapping settings, when in fact they are controlled by glide.ui.dependency_view system properties.

How to eliminate wrong answers

Option A is wrong because the CI Class Manager relationship definition tab defines relationship types and their rules, but does not control which relationships are displayed by default in Dependency Views. Option B is wrong because Service Mapping Properties govern service mapping behavior and topology generation, not the default relationship filters in Dependency Views. Option C is wrong because CMDB Query Builder global settings control query behavior and saved queries, not Dependency View rendering defaults.

Full explanation →
50
MCQeasy

Which CSDM domain contains entities such as Business Units, Companies, Locations, Departments, and Users?

A.Foundation
B.Manage Technical Services
C.Sell/Consume
D.Design
AnswerA

The Foundation domain holds shared reference data used across all other CSDM domains, including Business Units, Companies, Locations, Departments and Users. These entities underpin every other domain, which is why they are classified as Foundation rather than Design or Sell/Consume.

Why this answer

The Foundation domain in the CSDM (Common Service Data Model) houses the core 'who and where' entities — Business Units, Companies, Locations, Departments, and Users (via the User/Group tables). These are the base-level reference data that all other CSDM domains (Design, Sell/Consume, Manage Technical Services) build upon. Because these entities exist independently of any service or offering, they belong to Foundation rather than a service-oriented domain.

Exam trap

CIS-DF often tests whether candidates can distinguish the 'who/where' Foundation entities from the 'what we offer' Sell/Consume entities and the 'what we build' Design entities — the trap is picking Sell/Consume because 'Users' sound like consumers.

How to eliminate wrong answers

Option B is wrong because Manage Technical Services covers the technical service layer — Service Instances, Technical Services, and their CIs — not organizational entities like Business Units or Locations. Option C is wrong because Sell/Consume governs Service Offerings, Catalog Items, and Demand, which are commercial/consumption constructs, not foundational org data. Option D is wrong because Design covers Business Capabilities, Business Applications, Application Services, and Information Objects — the 'what we build' layer, not the 'who we are' layer.

Full explanation →
51
MCQmedium

A reporting analyst wants to create a report showing the distribution of CIs across different operational statuses (e.g., In Use, Maintenance, Retired). Which table and field should be used as the primary grouping?

A.cmdb_rel_ci table, Status field
B.cmdb_ci table, Operational Status field
C.ast_config_item table, State field
D.cmdb_ci table, Install Status field
AnswerB

The cmdb_ci table is the base CI class holding all configuration items, and its Operational Status field records lifecycle states such as In Use, Maintenance and Retired. Grouping on this field produces the required distribution of CIs across operational statuses.

Why this answer

The correct table and field for grouping CIs by operational status is the cmdb_ci table with the Operational Status field. The Operational Status field (operational_status) indicates the current state of a CI, such as In Use, Maintenance, or Retired, and is designed for this purpose.

Exam trap

The trap here is confusing Operational Status with Install Status; candidates might choose Install Status because it also sounds like a status field, but Operational Status specifically tracks the operational state (In Use, Maintenance, Retired) as described in the question.

How to eliminate wrong answers

Option A is wrong because the cmdb_rel_ci table stores relationships between CIs, not CI attributes, and it does not have a Status field for operational status. Option C is wrong because ast_config_item is not a standard table name in ServiceNow; the correct table is cmdb_ci. Option D is wrong because the Install Status field (install_status) indicates the installation state (e.g., Installed, On Order), not the operational status.

Full explanation →
52
MCQhard

An enterprise has multiple disjointed data sources feeding network gear into the CMDB. Source A provides high-accuracy IP data, while Source B provides high-accuracy serial numbers. However, their discovery source names differ slightly in casing and format across jobs. How does the IRE handle discovery source strings during reconciliation?

A.Discovery source strings are case-sensitive and must be standardized; inconsistent naming causes the IRE to treat them as distinct data sources, bypassing intended precedence rules.
B.The IRE maps discovery sources based on IP address ranges rather than the discovery source string.
C.The IRE automatically normalizes all discovery source strings to lowercase and strips special characters.
D.Discovery source names only affect reporting and have no impact on IRE reconciliation behavior.
AnswerA

IRE compares discovery source strings as case-sensitive values, so 'SourceA' and 'sourcea' register as separate sources. Precedence rules keyed to the intended source name are then bypassed, letting the lower-accuracy source overwrite data. Standardising casing and format across all discovery jobs is therefore required.

Why this answer

The IRE (Identification and Reconciliation Engine) treats discovery source strings as case-sensitive identifiers. If Source A is named 'SourceA' and Source B is named 'sourcea', the IRE considers them distinct data sources, which means precedence rules configured for one will not apply to the other. This can cause the IRE to bypass intended source precedence and produce inconsistent reconciliation results, so administrators must standardize discovery source naming.

Exam trap

CIS-DF often tests the assumption that the IRE auto-normalizes discovery source strings; the trap is that candidates believe case-insensitive matching is applied, but the IRE is strictly case-sensitive.

How to eliminate wrong answers

Option B is wrong because the IRE does not map discovery sources by IP address ranges; discovery source is a string attribute used for precedence and reconciliation rules. Option C is wrong because the IRE does not automatically normalize case or strip special characters from discovery source strings; normalization must be done manually or via data policies. Option D is wrong because discovery source names directly affect IRE reconciliation and precedence, not just reporting.

Full explanation →
53
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.

Full explanation →
54
MCQmedium

A governance team wants to ensure that CIs without valid IP addresses or MAC addresses are flagged in network-connected classes. Where can this specific validation rule be configured?

A.Discovery Definition > Behaviors
B.CI Class Manager > Identifiers
C.CMDB Data Governance > Policies
D.System Properties > Network Settings
AnswerC

CMDB Data Governance > Policies holds configurable data policies, including validation rules that flag CIs missing required attributes such as IP or MAC addresses in network-connected classes. This is the specific location where such attribute validation is defined and enforced.

Why this answer

CMDB Data Governance > Policies allows administrators to define validation rules that flag CIs with missing or invalid attributes, such as IP addresses or MAC addresses for network-connected classes. These policies can be configured to run on-demand or on schedule, providing governance over data quality.

Exam trap

CIS-DF often tests the location of data governance policy configuration, and candidates may confuse it with identification rules or discovery behaviors.

How to eliminate wrong answers

Option A is wrong because Discovery Definition > Behaviors is used to configure discovery behavior, not data validation rules. Option B is wrong because CI Class Manager > Identifiers is used to define identification rules for IRE, not for flagging invalid attributes. Option D is wrong because System Properties > Network Settings contains system-wide network configurations, not CI-specific validation rules.

Full explanation →
55
MCQhard

An enterprise has implemented strict identification rules requiring serial numbers for all hardware. However, a batch of legacy network hubs has no serial numbers encoded in firmware. When ingested via import sets, the IRE rejects every record due to missing identification attributes. The business wants these records ingested into the CMDB anyway, using their MAC address as the unique identifier. What is the correct way to accommodate this?

A.Change the target table to cmdb_ci_appl.
B.Disable the identification rule entirely for the hardware class.
C.Write a Business Rule to insert fake serial numbers starting with 'UNKNOWN' into every record.
D.Add a second identification rule entry for the hardware class in CI Class Manager where the identification criteria uses MAC address.
AnswerD

CI Class Manager supports multiple identification rule entries per class, each evaluated in order. Adding a second entry using MAC address lets legacy hubs lacking serial numbers be identified and ingested, satisfying the business requirement without weakening the existing serial-number rule.

Why this answer

Adding a secondary identification rule entry using MAC address allows devices without serial numbers to be correctly identified and ingested.

Full explanation →
56
MCQmedium

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

A.Business Capabilities are mapped directly to Hardware CIs.
B.Business Capabilities are children of Application Services.
C.Business Capabilities replace the need for Business Applications entirely.
D.Business Applications realize Business Capabilities.
AnswerD

In the CSDM Design domain, Business Applications are mapped to the Business Capabilities they enable, establishing a realisation relationship. This satisfies the question's requirement by placing Business Applications as the realising entity and Business Capabilities as the realised abstraction.

Why this answer

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

Exam trap

CIS-DF often tests the direction of the capability-application relationship — the trap is reversing it (thinking capabilities are children of applications or application services) instead of recognizing that applications realize capabilities.

How to eliminate wrong answers

Option A is wrong because Business Capabilities are logical business constructs, not mapped to Hardware CIs — hardware belongs to the Manage Technical Services domain and is several layers below capabilities. Option B is wrong because Application Services are deployed instances of applications (Manage Technical Services domain), and capabilities are not their children; the relationship runs capability → application, not capability → application service. Option C is wrong because capabilities and applications are complementary — capabilities define intent, applications deliver it; removing applications would leave capabilities unrealized.

Full explanation →
57
MCQeasy

An organization is beginning its CSDM journey and wants to populate basic foundational organizational and user data before linking any technical infrastructure. Which CSDM domain does this activity belong to?

A.Foundation
B.Design
C.Sell/Consume
D.Manage Technical Services
AnswerA

Foundation data covers the organisational and user entities — companies, business units, departments, users and groups — that underpin every other CSDM domain. Populating these before any infrastructure linkage matches the stem's requirement to establish basic foundational organisational and user data first, with no technical CIs involved.

Why this answer

The Foundation domain of the CSDM (Common Service Data Model) covers foundational data such as company, user, group, location, and other organizational reference data that underpins all other domains. Populating basic organizational and user data before linking technical infrastructure is precisely the Foundation domain's purpose.

Exam trap

CIS-DF often tests domain sequencing — candidates confuse Foundation (org/user reference data) with Design or Technical Services and pick a domain that assumes foundational data already exists.

How to eliminate wrong answers

Option B is wrong because the Design domain covers design-time artifacts like business services, service offerings, and their relationships — not foundational org/user data. Option C is wrong because Sell/Consume covers customer-facing and consumption constructs (e.g., sold products, service offerings to customers), which come after foundational data. Option D is wrong because Manage Technical Services covers technical services, CIs, and infrastructure management — the very technical layer the organization is deliberately deferring.

Full explanation →
58
MCQhard

Your organization is experiencing reporting discrepancies where incidents logged against an Application Service are not rolling up correctly into the parent Business Application dashboard. Upon inspection, you find that the Application Service is missing its link to the Business Application. Which field must be populated to resolve this reporting rollup issue?

A.Assigned group field on the Business Capability record.
B.Parent CI field on the Incident record.
C.Service portfolio field on the Technical Service record.
D.Business application field on the Application Service record.
AnswerD

The Business application field on the Application Service record establishes the parent-child relationship that dashboards traverse when rolling up incidents. Without this reference populated, the Application Service remains orphaned and its incidents never aggregate into the Business Application view.

Why this answer

The Business Application field on the Application Service record establishes the parent-child link that allows incidents and metrics on the Application Service to roll up into the Business Application dashboard. Without this reference, the reporting hierarchy is broken and rollups fail.

Exam trap

CIS-DF often tests whether candidates confuse the Incident's Parent CI field (impact analysis) with the Application Service's Business Application field (reporting hierarchy), or pick a field on the wrong record type entirely.

How to eliminate wrong answers

Option A is wrong because the Assigned group field on a Business Capability record relates to ownership of a capability, not to the Application Service-to-Business Application rollup path. Option B is wrong because the Parent CI field on an Incident record links an incident to a parent CI for impact analysis, but it does not establish the Application Service-to-Business Application relationship needed for dashboard rollup. Option C is wrong because the Service portfolio field on a Technical Service record relates to portfolio categorization, not to the Application Service-to-Business Application hierarchy.

Full explanation →
59
MCQeasy

When configuring a Service Graph Connector, where does an administrator typically test and execute the data ingestion process to verify that source data maps correctly to staging tables and the CMDB?

A.Discovery Status -> Run Quick Discovery
B.Service Mapping Workbench -> Test Map
C.Data Sources module -> Select the Data Source -> Click 'Test Load 20 Records' or 'Execute Now'
D.CI Class Manager -> Test Ingestion
AnswerC

The Data Sources module exposes Test Load 20 Records and Execute Now, which run the connector against staging tables so mapping to the CMDB can be verified before full ingestion. This is the standard validation point in Service Graph Connector configuration.

Why this answer

In ServiceNow, after configuring a Service Graph Connector, the data ingestion process is tested and executed from the Data Sources module. Selecting the relevant Data Source and clicking 'Test Load 20 Records' or 'Execute Now' allows the administrator to verify that source data maps correctly to staging tables and the CMDB. This is the standard testing procedure.

Exam trap

CIS-DF often tests the location for testing Service Graph Connectors, and candidates may confuse it with Discovery or Service Mapping testing areas.

How to eliminate wrong answers

Option A is wrong because Discovery Status -> Run Quick Discovery is for Discovery, not for testing Service Graph Connectors. Option B is wrong because Service Mapping Workbench -> Test Map is for service mapping, not data ingestion testing. Option D is wrong because CI Class Manager -> Test Ingestion is not a standard feature; ingestion testing is done via Data Sources.

Full explanation →
60
MCQeasy

What is the primary purpose of the 'Audit' functionality within ServiceNow Asset and CMDB management?

A.To verify physical or logical existence and accuracy of CI data through scheduled campaigns
B.To scan network ports for security vulnerabilities
C.To automatically approve emergency change requests
D.To track user login attempts and password resets
AnswerA

Audit campaigns schedule verification of CI records against physical or logical reality, reconciling discovered data with the CMDB. This satisfies the stem's requirement to confirm existence and accuracy of CI data through scheduled campaigns rather than ad hoc checks.

Why this answer

The Audit functionality in ServiceNow Asset and CMDB management is designed to verify the physical or logical existence and accuracy of CI data through scheduled audit campaigns. Auditors are assigned CIs to confirm, and results feed back into the CMDB to correct discrepancies, mark missing assets, or validate data quality. This directly supports CMDB governance and compliance.

Exam trap

The trap is confusing the CMDB Audit module with security auditing or change auditing — candidates see 'Audit' and think of vulnerability scans or login logs, but in ServiceNow Asset/CMDB context, Audit specifically means scheduled CI verification campaigns.

How to eliminate wrong answers

Option B is wrong because network port scanning for vulnerabilities is performed by security tools (e.g., Vulnerability Response, third-party scanners), not by the CMDB Audit module — Audit is about data verification, not security scanning. Option C is wrong because emergency change request approval is handled by the Change Management workflow and CAB/ECAB processes, not by Audit. Option D is wrong because tracking user login attempts and password resets is a platform security/authentication function (login audit records, password policy logs), not the Asset/CMDB Audit module.

Full explanation →
61
MCQmedium

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

A.Freshness
B.Completeness
C.Compliance
D.Correctness
AnswerD

Correctness evaluates whether CI records contain accurate, non-duplicate data, including conflicting values from multiple sources. Duplicate records sharing identical serial numbers from clashing integrations are precisely the data integrity defect this metric detects and reports.

Why this answer

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

Exam trap

CIS-DF often tests the distinction between CMDB Health metrics, and candidates may incorrectly associate duplicates with Completeness or Compliance instead of Correctness.

How to eliminate wrong answers

Option A is wrong because Freshness measures how recently CIs were updated, not duplicates. Option B is wrong because Completeness checks for missing required attributes, not duplicates. Option C is wrong because Compliance checks adherence to defined policies, which may include duplicates but is broader; the specific duplicate condition is part of Correctness.

Full explanation →
62
MCQmedium

An organization is ingesting printer CIs from a legacy asset system via Import Sets. Some incoming records contain a serial number with leading/trailing whitespace, causing the IRE to treat them as distinct CIs rather than matching existing ones. Where can data normalization be applied to clean this data before it reaches the IRE?

A.Modify the IRE Identification Rule to automatically ignore whitespace.
B.Use Robust Transform Engine (RTE) field transformations (such as Trim or Regex) during the data ingestion mapping phase.
C.Write a Client Script on the target cmdb_ci table to strip whitespace upon insert.
D.Configure a Data Policy to reject records containing whitespace.
AnswerB

RTE field transformations apply operations such as Trim or Regex during the mapping phase, before records reach the IRE. Cleaning leading and trailing whitespace here ensures serial numbers match existing CIs instead of creating duplicates.

Why this answer

The Robust Transform Engine (RTE) is the ServiceNow data transformation framework that runs during the Import Set transform mapping phase, before records are handed to the IRE. RTE field transformations such as Trim, Regex, or custom transform functions can strip leading/trailing whitespace from the serial number field so the cleaned value is what the IRE evaluates against identification rules. Because normalization happens upstream of identification, existing CIs match correctly and no duplicates are created.

Exam trap

CIS-DF often tests the misconception that the IRE itself normalizes or 'cleans' incoming data — candidates pick the Identification Rule option, not realizing normalization must happen upstream in the RTE during the transform mapping phase.

How to eliminate wrong answers

Option A is wrong because Identification Rules in the IRE match on the values they receive — they do not perform string normalization like trimming whitespace, so modifying the rule cannot fix dirty input data. Option C is wrong because a Client Script on cmdb_ci runs in the browser on the target table after the record is already being inserted, which is too late to influence IRE matching and is also the wrong execution context for server-side import processing. Option D is wrong because a Data Policy enforces validation/auditing rules and would reject or flag records rather than clean them, and rejecting records does not solve the matching problem.

Full explanation →
63
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.

Full explanation →
64
Multi-Selecthard

Which THREE actions occur when a Data Certification task is assigned to a CI owner? (Choose three.)

Select 3 answers
A.The CI is automatically retired from the database immediately
B.The reviewer can update incorrect attribute values directly from the task interface
C.A high-priority incident is automatically created for the IT service desk
D.The reviewer submits the certification response, completing the task
E.The reviewer is asked to verify if the CI data is accurate and up to date
AnswersB, D, E

Reviewers can correct inaccurate attribute values inline from the certification task, satisfying the requirement that remediation happens without leaving the task. This direct edit capability distinguishes certification tasks from read-only access reviews, letting the CI owner fix data quality issues during review rather than raising a separate change request.

Why this answer

Option B is correct because the Data Certification task interface lets the assigned CI owner (reviewer) correct inaccurate attribute values directly on the CI record while performing the certification. Option D is correct because the reviewer must submit a certification response (for example, certified or not certified), and that submission completes the task. Option E is correct because the core purpose of assigning a Data Certification task to a CI owner is to have that reviewer verify whether the CI's data is accurate and up to date.

Option A is incorrect because certification does not automatically retire a CI; retirement is a separate lifecycle action. Option C is incorrect because Data Certification does not automatically generate a high-priority incident for the service desk.

Exam trap

The trap here is assuming that Data Certification triggers automatic lifecycle changes or incident creation; candidates may confuse it with other CMDB processes like retirement workflows or incident management, but certification is strictly about verifying and updating CI data.

Full explanation →
65
Multi-Selectmedium

An administrator is reviewing Discovery results and notices that network switches are successfully discovered, but their associated switch ports are missing. Which TWO factors are most likely responsible for this ingestion gap? (Choose two.)

Select 2 answers
A.The dependent relationship payload structure for switch ports failed IRE validation or was omitted.
B.The cmdb_ci_ip_address table has read-only access enabled for all users.
C.Data Source Precedence rules marked switch ports as deprecated.
D.The discovery pattern for network switches was modified to exclude port table parsing.
E.Discovery schedules were run outside of business hours.
AnswersA, D

Switch ports are dependent CIs, so they only persist if the relationship payload passes IRE validation. If that dependent structure is malformed or omitted, the ports are dropped while the parent switch still ingests, matching the stem's gap of missing switch ports.

Why this answer

Option A is correct because switch ports are ingested as dependent CI records tied to the parent switch via the IRE (Identification and Reconciliation Engine); if the dependent relationship payload is malformed, fails IRE validation, or is omitted entirely, the parent switch is created but its port CIs are dropped. Option D is correct because the discovery pattern (e.g., the SNMP-based network switch pattern) is what parses and populates the switch port table; if that port-parsing step is removed or excluded from the pattern, switches still get discovered while ports never get created. Option B is not relevant because cmdb_ci_ip_address read-only access affects IP address CI writes, not switch port ingestion.

Option C is not relevant because Data Source Precedence rules resolve conflicts between data sources for existing records; they do not cause ports to be marked deprecated or prevent their initial discovery. Option E is not relevant because running discovery outside business hours only affects timing, not whether switch port data is parsed and ingested.

Exam trap

CIS-DF often tests the misconception that discovery automatically captures all dependent components, but pattern modifications or IRE validation failures can silently omit them.

Full explanation →
66
Multi-Selectmedium

Which TWO types of metrics are evaluated under the CMDB Health framework? (Choose two.)

Select 2 answers
A.Availability
B.Scalability
C.Correctness
D.Completeness
E.Performance
AnswersC, D

Correctness is one of the two metric types evaluated under the CMDB Health framework, alongside completeness. It measures whether configuration item attributes hold accurate, valid values, satisfying the stem's requirement for a metric type assessed by the framework rather than a compliance or audit score.

Why this answer

Under the CMDB Health framework, Correctness (C) is evaluated because it measures whether CI records contain accurate and valid data, such as ensuring required fields have valid values and that CIs conform to their class definitions. Completeness (D) is also evaluated because it measures whether required attributes and relationships are populated for each CI, identifying records that are missing mandatory data. These two metrics are part of the standard CMDB Health KPIs, along with compliance and duplicate metrics.

Availability (A), Scalability (B), and Performance (E) are not CMDB Health metric types; they are operational or infrastructure characteristics rather than data-quality dimensions assessed by the CMDB Health framework.

Full explanation →
67
MCQeasy

An implementer is setting up a new integration using IntegrationHub to ingest network switch data into the CMDB. Which API should be utilized within the script or action to ensure that the payload passes through deduplication and reconciliation checks?

A.SNC.IdentificationEngine.createOrUpdate()
B.RestMessageV2.execute()
C.CMDBAPI.ingest()
D.GlideRecord.insert()
AnswerA

SNC.IdentificationEngine.createOrUpdate() invokes the Identification and Reconciliation Engine directly, so the payload passes through deduplication and reconciliation. Satisfying the stem's constraint, it applies identification rules and reconciliation rules, unlike Table API inserts, which bypass the IRE entirely.

Why this answer

SNC.IdentificationEngine.createOrUpdate() is the JavaScript API that submits a payload to the Identification and Reconciliation Engine (IRE), which applies identification rules, deduplication, and reconciliation before inserting or updating CIs. This is the correct way to ensure ingested data respects CMDB governance. Direct inserts bypass IRE entirely.

Exam trap

The trap is picking a familiar-looking API like GlideRecord.insert() or a fabricated name like CMDBAPI.ingest() — candidates must remember that only the IdentificationEngine API routes payloads through IRE.

How to eliminate wrong answers

Option B is wrong because RestMessageV2.execute() only sends an outbound REST call — it has no awareness of IRE and does not trigger deduplication or reconciliation. Option C is wrong because CMDBAPI.ingest() is not a real ServiceNow API; it is a fabricated name that sounds plausible. Option D is wrong because GlideRecord.insert() writes directly to the table, bypassing identification rules, deduplication, and reconciliation, which is exactly what causes duplicate CIs and orphaned relationships.

Full explanation →
68
MCQmedium

An administrator is configuring a new Import Set to ingest third-party server data into the cmdb_ci_server table. During testing, they notice that records are being inserted as duplicates rather than updating existing CIs because the incoming payload lacks a unique identifier match. Which component should be configured to ensure the Identification and Reconciliation Engine (IRE) correctly identifies the existing CI?

A.Configure an Identification Rule in CI Class Manager for cmdb_ci_server.
B.Modify the coalesce setting on the Transform Map to use serial number.
C.Enable 'Robust Transform Engine' on the data source properties.
D.Create a Data Source Precedence rule for the import set.
AnswerA

Configuring an Identification Rule in CI Class Manager supplies the IRE with the attribute criteria it uses to match incoming payloads against existing cmdb_ci_server records. Without a matching rule, the IRE cannot correlate the third-party data, so it inserts duplicates. The rule directly satisfies the stem's requirement for correct identification during import.

Why this answer

The Identification and Reconciliation Engine uses Identification Rules defined per CI class in CI Class Manager to determine whether an incoming record matches an existing CI. If no Identification Rule is configured for cmdb_ci_server (or the rule's identifier entries don't match the incoming payload), the IRE cannot find a match and inserts a new record, producing duplicates. Configuring the appropriate Identification Rule — for example, using serial number, name, or a combination — allows the IRE to correctly match and update the existing CI.

Exam trap

CIS-DF often tests the confusion between Transform Map coalesce (legacy Import Set dedup) and IRE Identification Rules — candidates pick coalesce because it sounds like 'matching,' but IRE identification is a separate, class-specific configuration in CI Class Manager.

How to eliminate wrong answers

Option B is wrong because the Transform Map coalesce setting is a legacy Import Set mechanism that only prevents duplicate Import Set rows or performs simple coalescing on the target table; it does not participate in the IRE's identification logic and is bypassed when IRE is enabled. Option C is wrong because RTE is a data transformation framework, not an identification mechanism — enabling it does not tell the IRE how to match CIs. Option D is wrong because Data Source Precedence rules only resolve conflicts when multiple data sources update the same CI attribute; they do not perform identification and cannot match an incoming record to an existing CI.

Full explanation →
69
Multi-Selectmedium

Which TWO of the following are characteristics of the 'Fly' maturity phase in CSDM?

Select 2 answers
A.Advanced optimization and business value realization.
B.Configuring standard Foundation company records.
C.Continuous enterprise transformation and innovation across domains.
D.Initial data cleansing of user and department tables.
E.Setting up basic service portfolios for the first time.
AnswersA, C

The Fly phase is characterised by advanced optimisation and business value realisation, where CMDB data drives automated service management and measurable outcomes. This contrasts with Crawl's foundational data and baseline population and Walk's incremental expansion of scope.

Why this answer

In the CSDM (Common Service Data Model) maturity model, the 'Fly' phase represents the highest level of maturity, where organizations achieve advanced optimization and business value realization (option A) — meaning the data model is fully adopted, automated, and directly tied to measurable business outcomes. It also entails continuous enterprise transformation and innovation across domains (option C), because at this stage CSDM data is used to drive ongoing cross-domain improvement, not just operational stability. Options B, D, and E describe foundational or 'Crawl'-level activities — configuring standard Foundation company records, initial data cleansing of user and department tables, and setting up basic service portfolios for the first time — which belong to earlier maturity phases, not the advanced 'Fly' phase.

Exam trap

CIS-DF often tests the distinction between the Crawl, Walk, and Fly phases. Candidates might confuse activities from different phases, such as thinking that setting up basic service portfolios is part of Fly, when it is actually an early phase activity. It's important to remember that Fly is about advanced optimization and transformation.

Full explanation →
70
MCQeasy

What is the primary purpose of the CMDB Query Builder when generating insights?

A.To configure CI class identification and reconciliation rules.
B.To manage CSDM lifecycle policies and archival rules.
C.To execute automated discovery scans across IP networks.
D.To visually build and execute complex multi-class CI relationship queries and export results.
AnswerD

CMDB Query Builder provides a graphical interface for constructing multi-class CI relationship queries, then executing and exporting the results. This satisfies the requirement to generate insights by visually assembling complex relationship queries without writing code manually.

Why this answer

CMDB Query Builder allows users to construct visual, multi-class queries to find specific CI relationships and subsets across the CMDB.

Full explanation →
71
MCQmedium

An administrator is setting up a new technical service for internal server backup management. Where should this technical service be classified according to CSDM?

A.Design domain as a Business Application
B.Manage Technical Services domain
C.Sell/Consume domain as a public Catalog Item
D.Foundation domain as a User Group
AnswerB

Technical services that support infrastructure rather than directly serving customers belong in the Manage Technical Services domain. Internal server backup management is an infrastructure-facing technical service, so this domain satisfies the classification requirement rather than Design or Sell/Consume.

Why this answer

In the Common Service Data Model (CSDM), a technical service represents a service that is delivered by technical components (e.g., servers, applications) and consumed by other technical services or business services, not directly by end-users. Internal server backup management is an infrastructure-level service that supports IT operations, so it belongs in the Manage Technical Services domain. This domain is specifically designed for services that are managed by IT and have a technical focus, such as backup, monitoring, or patching.

Exam trap

CIS-DF often tests the confusion between technical services and business applications, where candidates incorrectly assume any IT service is a business application, ignoring the consumption perspective that defines CSDM domains.

How to eliminate wrong answers

Option A is wrong because a Business Application in the Design domain represents a logical grouping of application functionality that supports business processes, not an infrastructure service like backup management. Option C is wrong because a public Catalog Item in the Sell/Consume domain is an end-user-facing offering that can be requested, whereas internal server backup management is not sold or consumed by business users. Option D is wrong because a User Group in the Foundation domain is an organizational grouping of users, not a technical service classification.

Full explanation →
72
MCQeasy

When setting up CMDB data ownership, which field on a CI record is typically used to designate the individual accountable for the physical or logical asset's data quality?

A.Managed by
B.Caller ID
C.Reported by
D.Opened by
AnswerA

Managed by designates the person accountable for the CI's data quality, satisfying the ownership requirement. Owned by denotes the group responsible for support, and Supported by is operational, so Managed by is the field that maps to individual accountability for the physical or logical asset.

Why this answer

The 'Managed by' field on a CI record designates the individual accountable for the physical or logical asset's data quality. It is used to assign ownership and responsibility for maintaining accurate information about the CI. This field is typically populated with a user reference and is distinct from fields like 'Caller ID' or 'Reported by', which are used in incident or request contexts.

Exam trap

CIS-DF often tests the confusion between fields used for CI ownership versus those used in incident management, leading candidates to select 'Caller ID' or 'Reported by' incorrectly.

How to eliminate wrong answers

Option B is wrong because 'Caller ID' is used in incident, problem, or change records to identify the person who reported the issue, not for CI ownership. Option C is wrong because 'Reported by' is similar to 'Caller ID' and is used in task-based records, not for CI data stewardship. Option D is wrong because 'Opened by' is used in records like incidents or changes to indicate who created the record, not for CI accountability.

Full explanation →
73
Multi-Selecthard

An administrator is designing identification rules for a custom CI class in the CMDB. Which THREE ofg the following best practices should be followed when configuring identification rules? (Choose three.)

Select 3 answers
A.Use attributes that are guaranteed to be unique and immutable, such as serial numbers or hardware asset tags.
B.Order identification criteria logically, putting the most reliable and specific rules first.
C.Ensure that identification rules are created on custom tables without inheriting from cmdb_ci.
D.Avoid using volatile attributes like IP address or hostname alone as primary identifiers if devices frequently change networks.
E.Configure every single attribute of the CI class into a single compound identification rule entry to ensure maximum security.
AnswersA, B, D

Identification rules must rely on attributes that never change and uniquely distinguish one CI from another, otherwise reconciliation creates duplicates or merges distinct devices. Serial numbers and asset tags satisfy this because they remain stable and unique across the CI lifecycle.

Why this answer

Option A is correct because identification rules must rely on attributes that are unique and immutable, such as serial numbers or hardware asset tags, so the same CI is consistently matched rather than duplicated or misidentified when other fields change. Option B is correct because identification rules are evaluated in order, so placing the most reliable and specific criteria first ensures the strongest match is attempted before broader, less precise rules are considered. Option D is correct because volatile attributes like IP address or hostname alone can change when devices move networks, causing false matches or duplicate CIs; they should be combined with stable identifiers or avoided as sole primary identifiers.

Option C is incorrect because custom CI classes should extend cmdb_ci (or an appropriate CMDB base class) to inherit the identification engine behavior and required fields, not be created on unrelated custom tables. Option E is incorrect because cramming every attribute into one compound rule makes identification overly restrictive and brittle, so any single changed attribute breaks the match and creates duplicates.

Full explanation →
74
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.

Full explanation →
75
Multi-Selectmedium

Which TWO of the following methods can be used to view relationship-based insights for a configuration item in ServiceNow? (Choose two.)

Select 2 answers
A.Relationships related list on the CI form
B.CI Class Manager identifier rules
C.CMDB Health Dashboard completeness scorecards
D.Dependency Views map on the CI record
E.Discovery Schedule execution log
AnswersA, D

The Relationships related list on the CI form directly satisfies the requirement to view relationship-based insights, displaying all inbound and outbound dependencies for that configuration item. It queries the cmdb_rel_ci table, rendering parent-child and peer connections inline, so no separate reporting module or dashboard configuration is needed.

Why this answer

Option A is correct because the Relationships related list on a CI form directly displays the CI's relationship records (parent/child, depends on, etc.), giving relationship-based insight into how that configuration item connects to other CIs. Option D is correct because Dependency Views map, accessible from the CI record, renders a graphical, relationship-based visualization of the CI and its connected infrastructure, letting you explore upstream and downstream dependencies. Option B is not correct because CI Class Manager identifier rules define how CIs are uniquely identified and reconciled, not how relationships are viewed.

Option C is not correct because CMDB Health Dashboard completeness scorecards measure data completeness of CI attributes, not relationships. Option E is not correct because a Discovery Schedule execution log records discovery run activity and errors, not CI relationship insights.

Full explanation →

Page 1 of 4

Page 2

All pages

1234

Practice CIS-DF by domain

Target a specific domain to shore up weak areas.

CSDM FundamentalsConfigurationGovernanceIngestInsight
See all domains with question counts →