ServiceNow Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) (CIS-DF) CIS-DF Questions 226–272 | Page 4/4

226

MCQmedium

An auditor requests evidence that all critical databases have an identified support group. Which built-in CMDB feature allows an administrator to quickly run an on-demand check for this specific completeness rule without waiting for scheduled dashboard refreshes?

A.Run a background script using GlideRecord

B.Export the cmdb_ci table to Excel and filter manually

C.Run Policy evaluation from CMDB Data Governance

D.Execute a Full Discovery Scan

AnswerC

Running policy evaluation from CMDB Data Governance executes the completeness policy on demand, immediately returning compliance results for the critical-database support-group rule. This provides the auditor with current evidence without waiting for scheduled dashboard refreshes.

Why this answer

The CMDB Data Governance module includes a Policy evaluation feature that allows administrators to run on-demand checks against defined policies, such as ensuring all critical databases have an identified support group. This bypasses the need to wait for scheduled dashboard refreshes, providing immediate compliance evidence.

Exam trap

CIS-DF often tests the distinction between on-demand policy evaluation and scheduled health jobs, causing candidates to overlook the built-in governance feature and choose custom scripting or manual methods.

How to eliminate wrong answers

Option A is wrong because a background script using GlideRecord is a custom, manual approach that requires scripting and does not leverage built-in governance features. Option B is wrong because exporting to Excel and filtering manually is a time-consuming, error-prone process that does not provide an automated check. Option D is wrong because a Full Discovery Scan is used to discover CIs and their attributes, not to validate governance rules like support group assignment.

Full explanation →

227

MCQhard

During a review of the CMDB class hierarchy, an architect notices that a custom class extending cmdb_ci_hardware was created without a corresponding identification rule in the Identification and Reconciliation Engine (IRE). What is the primary risk of this configuration?

A.The CMDB Health dashboard will automatically delete all records in this custom table.

B.Business rules on the base cmdb table will prevent any inserts into the custom table.

C.CIs belonging to this class cannot be viewed in Dependency Views.

D.Inbound discovery payloads may create duplicate records because the IRE falls back to out-of-the-box system-level rules or creates new records without matching.

AnswerD

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

Why this answer

The IRE relies on identification rules to match incoming discovery payloads to existing CIs. Without a class-specific identification rule, the engine falls back to inherited or system-level rules, which may not match the custom class's unique attributes, resulting in duplicate CI records or unintended new inserts. This undermines CMDB data integrity and can cascade into incorrect relationship mapping and reporting.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →

228

MCQeasy

What is the primary role of the 'Walk' phase in CSDM maturity?

A.To achieve full automated AI cloud optimization.

B.To maintain basic foundation user tables only.

C.To introduce service portfolios and basic service mapping.

D.To replace the CMDB with external flat files.

AnswerC

Correct. Walk focuses on service portfolios and basic mapping.

Why this answer

The Walk phase in CSDM maturity is where organizations introduce service portfolios and basic service mapping, moving beyond the foundational Crawl phase. It establishes structured service definitions and begins linking services to CIs, enabling better service visibility. This phase is about building on the foundation, not full automation.

Exam trap

CIS-DF often tests the distinction between Crawl, Walk, and Run phases, with candidates confusing Walk's service portfolio focus with Run's automation focus.

How to eliminate wrong answers

Option A is wrong because full automated AI cloud optimization is not a CSDM maturity phase goal; CSDM focuses on data modeling, not AI optimization. Option B is wrong because maintaining basic foundation user tables only describes the Crawl phase, not Walk. Option D is wrong because replacing the CMDB with external flat files contradicts CSDM principles, which rely on the CMDB as the system of record.

Full explanation →

229

MCQhard

An enterprise configuration manager needs to audit all manual relationship modifications made to production servers over the last 30 days to ensure compliance with automated discovery policies. Which native audit mechanism tracks this?

A.CMDB Query Builder execution logs

B.Service Mapping traffic log table

C.Audit history on the Configuration Item Relationship [cmdb_rel_ci] table

D.Reconciliation Definition audit table

AnswerC

Audit history on the Configuration Item Relationship [cmdb_rel_ci] table records field-level changes to relationship records, capturing who manually altered each CI relationship and when. This directly satisfies the 30-day audit requirement for manual relationship modifications on production servers, since relationship edits are stored against that table rather than the CI records themselves.

Why this answer

The Configuration Item Relationship [cmdb_rel_ci] table stores every parent-child relationship between CIs in the CMDB, and ServiceNow automatically maintains an audit history on this table. Any manual insert, update, or delete of a relationship record is captured with the user, timestamp, and old/new values. Auditing this table's history is therefore the native way to identify manual relationship modifications over a defined window such as 30 days.

Exam trap

CIS-DF often tests whether candidates confuse query/execution logs with record-level audit history — the trap is picking a reporting or mapping tool when the question specifically asks for change tracking on relationship records.

How to eliminate wrong answers

Option A is wrong because CMDB Query Builder execution logs only record when and by whom a query was run — they do not track changes to relationship records themselves. Option B is wrong because the Service Mapping traffic log table captures discovery traffic and connection data used to build maps, not manual edits to cmdb_rel_ci records. Option D is wrong because Reconciliation Definition audit tables track reconciliation rule execution and precedence outcomes, not individual manual relationship modifications made by users.

Full explanation →

230

MCQmedium

A CMDB administrator is building an IntegrationHub ETL import that ingests Linux servers from an external discovery tool. The source payload contains a field named 'host_name', but the CMDB CI Class Manager mapping must populate the 'Name' attribute, and the source also provides 'os_version' that must land in 'OS Version'. After running the import, the administrator sees that the CI records are created but the 'Name' field is blank while 'OS Version' is populated correctly. Which action should the administrator take to resolve the blank 'Name' field?

A.Configure an Identification and Reconciliation Engine (IRE) identification rule that uses the 'host_name' field as a search criterion for the Linux server class.

B.Verify in the IntegrationHub ETL transform mapping that the 'host_name' source field is mapped to the 'Name' target attribute and that the mapping is not marked as a coalesce-only field.

C.Enable the 'Coalesce' option on the import set and set 'host_name' as the coalesce field so the value is copied automatically into the 'Name' attribute.

D.Add a Data Source Precedence rule that ranks the discovery source above all other sources for the Linux server class, then rerun the import.

AnswerB

In IntegrationHub ETL, the transform map between the source payload and the CMDB target class must explicitly map each source column to a target attribute. If 'host_name' is not mapped, or is mapped only as a coalesce field, the target 'Name' attribute will not be populated even though the record is created, while a correctly mapped 'OS Version' will populate.

Why this answer

The blank 'Name' attribute combined with a correctly populated 'OS Version' points to a transform mapping gap rather than an identification or precedence issue. In IntegrationHub ETL, each source column must be explicitly mapped to the desired target attribute; unmapped columns are simply not written. Coalesce settings and IRE identification rules affect matching, not field population, so the mapping must be corrected.

Exam trap

The trap here is assuming that fields not explicitly mapped in the ETL transform are automatically copied to same-named target attributes.

Full explanation →

231

MCQmedium

A company notices that hundreds of stale server records are polluting the CMDB, negatively affecting health scores. Rather than deleting them manually, what is the best practice governance workflow to handle stale CIs?

A.Initiate a review campaign or automated retirement workflow via CMDB health remediation

B.Delete all records where sys_updated_on is older than 90 days using a background script

C.Run Discovery against the entire IP range daily to force updates

D.Turn off the Stale CI metric so the score improves without action

AnswerA

CMDB health remediation drives stale CIs through a governed review campaign or automated retirement workflow, so hundreds of records are retired in bulk with auditability rather than manually deleted. This satisfies the stem's requirement for a best-practice governance workflow that fixes health scores without manual deletion.

Why this answer

The best-practice governance workflow for stale CIs is to initiate a review campaign or automated retirement workflow through CMDB Health remediation, which routes stale CIs to data owners for validation before retirement. This preserves auditability, respects data ownership, and prevents accidental deletion of CIs that may still be relevant. It also feeds back into the health score legitimately rather than masking the problem.

Exam trap

CIS-DF often tests governance best practices versus quick fixes, baiting candidates with options that delete records or disable metrics instead of following the proper remediation and review workflow.

How to eliminate wrong answers

Option B is wrong because bulk-deleting records older than 90 days via a background script bypasses governance, risks removing valid CIs, and leaves no audit trail — it also violates the principle of data-owner accountability. Option C is wrong because running Discovery daily against the entire IP range does not address stale records that are no longer discoverable; it wastes resources and may not update CIs that are genuinely decommissioned. Option D is wrong because turning off the Stale CI metric is data manipulation that hides the problem instead of remediating it, and it undermines the integrity of the CMDB health score.

Full explanation →

232

MCQhard

An organization wants to ensure that no duplicate CIs are ever inserted into the cmdb_ci table by API integrations or manual imports. Which ServiceNow engine natively enforces this governance rule?

A.Identification and Reconciliation Engine (IRE)

B.Data Policy Enforcement Engine

C.CMDB Health Duplicate Engine

D.Transform Map Unique Key matching

AnswerA

The IRE applies identification rules and reconciliation to every insert, whether from API integrations or imports, matching incoming payloads against existing CIs and preventing duplicates. It is the native engine enforcing that governance rule on cmdb_ci.

Why this answer

The Identification and Reconciliation Engine (IRE) is a native ServiceNow engine that enforces data governance by identifying and reconciling duplicate CIs before they are inserted into the CMDB. It uses identification rules and reconciliation rules to ensure that only unique CIs are created, even from multiple sources.

Exam trap

CIS-DF often tests the role of IRE in preventing duplicates, and candidates may confuse it with import set transform maps or data policies, which do not provide comprehensive duplicate prevention across all data sources.

How to eliminate wrong answers

Option B is wrong because Data Policy Enforcement Engine is not a real ServiceNow engine; data policies are used for validation but do not prevent duplicates. Option C is wrong because CMDB Health Duplicate Engine is not a native engine; CMDB Health includes duplicate metrics but does not enforce prevention. Option D is wrong because Transform Map Unique Key matching is a feature of import sets that can help avoid duplicates during imports, but it is not a comprehensive engine that covers API integrations and manual inserts; IRE is the centralized solution.

Full explanation →

233

MCQhard

When configuring custom indicators in Dependency Views, an organization wants to display a warning badge on any server CI whose CPU utilization exceeds 90% based on recent Performance Analytics or metric data. Where are custom widget indicators and map decorators configured for Dependency Views?

A.Dependency View Indicators configuration

B.CMDB Data Manager policy conditions

C.Service Mapping pattern extension script

D.CI Class Manager identifier rules

AnswerA

Custom widget indicators and map decorators for Dependency Views are defined in the Dependency View Indicators configuration, where each indicator's condition, such as CPU utilisation above 90 per cent, and its warning badge are set.

Why this answer

Dependency Views map indicators and status badges are configured via Dependency View Indicators [sys_dependency_indicator] or custom formatters.

Full explanation →

234

Multi-Selectmedium

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

Select 2 answers

A.Inherited classes ensure proper compatibility with CMDB Health, IRE, and Dependency Views.

B.Child classes automatically inherit standard attributes and behaviors from their parent class.

C.Independent base tables provide better integration with out-of-the-box Service Graph Connectors automatically.

D.Extending base tables allows CIs to bypass mandatory access control lists (ACLs).

E.Creating independent tables eliminates the need for any identification rules.

AnswersA, B

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

Why this answer

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

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

Exam trap

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

Full explanation →

235

MCQeasy

An implementer is reviewing the base tables of the CMDB. Which table serves as the ultimate parent class for virtually all Configuration Item classes in ServiceNow?

A.cmdb

B.task

C.cmdb_ci

D.cmdb_rel_ci

AnswerC

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

Why this answer

The cmdb_ci table is the ultimate parent class for virtually all Configuration Item classes in ServiceNow. Every CI class (e.g., cmdb_ci_server, cmdb_ci_appl) extends cmdb_ci through table inheritance, making it the root of the CMDB class hierarchy. This allows common attributes and relationships to be defined once at the top.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →

236

MCQhard

Your enterprise has implemented CSDM, but incident managers report that problem investigation is slowed because problem records are linked to Business Applications instead of Application Services. Why does linking problems to Application Services improve investigation efficiency?

A.Problem records cannot be saved unless an Application Service is populated.

B.Application Services provide the specific deployment and runtime infrastructure context needed to trace hardware and software component failures.

C.Application Services automatically generate patch scripts for problem analysts.

D.Business Applications automatically reject problem records that lack an assigned change advisory board.

AnswerB

Application Services map to the specific deployment and runtime infrastructure, so problems linked there expose the hardware and software components involved. Business Applications lack that granularity, forcing investigators to trace components manually and slowing root-cause analysis.

Why this answer

Application Services provide the specific deployment and runtime infrastructure context — the servers, databases, middleware, and network components — that a problem analyst needs to trace hardware and software component failures. Business Applications are logical groupings that do not carry this low-level infrastructure detail, so linking problems to Application Services gives investigators a direct path to the failing components. This is why CSDM recommends associating problems with Application Services rather than Business Applications.

Exam trap

CIS-DF often tests the misconception that Business Applications carry infrastructure detail — candidates confuse the logical business layer with the operational service layer that actually maps to CIs.

How to eliminate wrong answers

Option A is wrong because Problem records can be saved without an Application Service — there is no mandatory field enforcement that requires it. Option C is wrong because Application Services do not automatically generate patch scripts; patching is handled by Change Management and orchestration tools, not by the service record itself. Option D is wrong because Business Applications do not reject problem records based on change advisory board assignment — there is no such validation logic in the platform.

Full explanation →

237

MCQeasy

What is the primary purpose of the CSDM framework in ServiceNow?

A.To replace standard ITIL v4 processes with automated scripts.

B.To automatically configure Discovery credentials across network routers.

C.To enforce strict password complexity rules for end users.

D.To provide a standardized product-agnostic data model for mapping services, applications, and infrastructure in the CMDB.

AnswerD

The Common Service Data Model supplies a product-agnostic taxonomy that structures CMDB records into domains, service offerings and business services, satisfying the stem's requirement for a standardised model. It governs how services, applications and infrastructure relate, rather than describing a single product's schema, so mapping stays consistent across the enterprise.

Why this answer

The Common Service Data Model (CSDM) is a standardized, product-agnostic data model that defines how services, applications, business capabilities, and infrastructure are represented and related in the CMDB. It provides prescriptive tables, relationships, and domain separation so that ServiceNow products (ITSM, ITOM, CSM, etc.) share a consistent foundation. Its purpose is data consistency and interoperability, not process replacement or credential automation.

Exam trap

CIS-DF often tests the confusion between CSDM as a data model versus a process framework — candidates incorrectly assume CSDM automates ITIL processes or configures Discovery, when it only standardizes CMDB structure.

How to eliminate wrong answers

Option A is wrong because CSDM does not replace ITIL v4 processes — it is a data model that supports them, not a process automation engine. Option B is wrong because Discovery credential configuration is handled by Discovery schedules and credential records, not by CSDM, which only defines data structures. Option C is wrong because password complexity is enforced by authentication policies and password policies, entirely unrelated to the CMDB data model.

Full explanation →

238

Multi-Selecthard

Which THREE factors should an administrator consider when configuring CMDB Health Inclusion Rules? (Choose three.)

Select 3 answers

A.Operational State (e.g., excluding retired or non-operational CIs)

B.MID Server cluster membership

C.Environment (e.g., separating production from test/lab assets)

D.Email notification retry intervals

E.CI Class (targeting specific tables like servers or databases)

AnswersA, C, E

Retired or non-operational CIs skew health scores because they are no longer actively managed, so inclusion rules must filter on operational state. Excluding them ensures the CMDB Health dashboard reports only on CIs that genuinely require data completeness and compliance validation.

Why this answer

Option A is correct because CMDB Health Inclusion Rules commonly filter CIs by Operational State, allowing administrators to exclude retired, non-operational, or otherwise inactive CIs so they are not counted in health metrics. Option C is correct because Environment is a standard inclusion criterion, letting administrators scope health calculations to production assets and exclude test or lab CIs that would otherwise skew compliance and completeness scores. Option E is correct because CI Class is a fundamental inclusion factor, enabling rules to target specific tables such as servers or databases so health metrics apply only to the relevant CI types.

Option B is not correct because MID Server cluster membership relates to discovery and data collection infrastructure, not to which CIs are included in CMDB Health calculations. Option D is not correct because email notification retry intervals are an alerting or notification setting and have no bearing on CMDB Health Inclusion Rules.

Exam trap

CIS-DF often tests the factors for inclusion rules, and candidates may incorrectly include unrelated options like MID Server membership or notification settings.

Full explanation →

239

Multi-Selectmedium

When reviewing data ingestion methods for the ServiceNow CMDB, which TWO methods natively invoke the Identification and Reconciliation Engine (IRE) out of the box? (Choose two.)

Select 2 answers

A.Service Graph Connectors

B.Direct manual table inserts via background scripts using GlideRecord

C.Standard Email Inbound Actions creating incident records

D.Legacy Transform Maps with standard Coalesce settings

E.ServiceNow Discovery

AnswersA, E

Service Graph Connectors write through the Identification and Reconciliation Engine by design, so ingested records are deduplicated and reconciled against existing CIs. This native IRE invocation satisfies the stem's requirement for ingestion methods that call IRE out of the box, without custom transform scripts.

Why this answer

Service Graph Connectors (A) are built on the Identification and Reconciliation Engine and call IRE natively to deduplicate and reconcile incoming third-party data into the CMDB. ServiceNow Discovery (E) also natively invokes IRE when it creates or updates CIs, ensuring discovered data is identified and reconciled against existing records. Direct GlideRecord inserts (B) bypass IRE unless explicitly called, so they do not natively invoke it.

Email Inbound Actions creating incident records (C) operate on the task/incident tables, not the CMDB, and never touch IRE. Legacy Transform Maps with standard Coalesce settings (D) use coalesce-based matching rather than IRE, so they do not natively invoke the engine.

Full explanation →

240

Multi-Selecthard

Which THREE of the following maturity phases are recognized in the CSDM framework lifecycle?

Select 3 answers

A.Run

B.Crawl

C.Deploy

D.Sprint

E.Walk

AnswersA, B, E

Run is one of the CSDM lifecycle maturity phases, alongside Plan, Design, Build/Integrate, and Manage. It covers day-to-day operational activities, ensuring services and configuration items remain available and performant after deployment, satisfying the framework's operational maturity stage.

Why this answer

The CSDM (Common Service Data Model) framework lifecycle recognizes three maturity phases: Crawl (B), Walk (E), and Run (A). Crawl is the initial phase where organizations establish foundational data elements and basic relationships, Walk is the intermediate phase where the model is expanded and refined across domains, and Run is the mature phase where the CSDM is fully adopted, governed, and integrated into operational processes. These three phases describe progressive levels of data-model maturity and adoption, not project or delivery methodologies.

Deploy (C) is not a CSDM maturity phase; it is a general ITIL/ITSM release or implementation activity. Sprint (D) is not a CSDM phase either; it is an Agile/Scrum time-boxed iteration term unrelated to the CSDM lifecycle.

Exam trap

CIS-DF often tests the exact names of the CSDM phases, and candidates may mistakenly include Agile or ITIL terms like Deploy or Sprint.

Full explanation →

241

Multi-Selectmedium

An organization wants to ingest data into the CMDB using the Robust Transform Engine (RTE). Which TWO of the following capabilities are provided by RTE? (Choose two.)

Select 2 answers

A.Managing user authentication sessions for inbound REST API calls.

B.Replacing the underlying relational database management system with an in-memory graph store.

C.Transforming complex hierarchical JSON or XML payloads into structured tabular data for IRE processing.

D.Automatically generating ITSM Change Requests for every ingested CI.

E.Executing field transformations such as string trimming, concatenation, and regex mapping during ingestion.

AnswersC, E

RTE parses nested JSON and XML hierarchies and flattens them into the tabular rows that the Identification and Reconciliation Engine requires, satisfying the constraint that complex payloads must be normalised before IRE can identify and reconcile CIs.

Why this answer

The Robust Transform Engine (RTE) is ServiceNow's data-transformation framework used by CMDB integrations and Import Sets to normalize incoming payloads before they reach the Identification and Reconciliation Engine (IRE). Option C is correct because RTE is specifically designed to parse and flatten complex hierarchical JSON or XML structures into the structured, tabular rows that IRE requires for CI identification and reconciliation. Option E is correct because RTE provides a library of transform functions — including string trimming, concatenation, splitting, and regex-based mapping — that can be applied to fields during ingestion to standardize values.

Option A is incorrect because authentication and session management for inbound REST calls are handled by the REST API framework, OAuth, and authentication policies, not by RTE. Option B is incorrect because RTE is a transformation layer and does not replace the underlying relational database with an in-memory graph store. Option D is incorrect because RTE only transforms data; it does not create ITSM Change Requests, which would require separate workflow or business-rule logic.

Full explanation →

242

MCQhard

An administrator notices that a manual update made to a server's 'Asset tag' attribute by an IT agent is constantly overwritten during the nightly Discovery run, even though Discovery does not directly scan the asset tag. How is this behavior controlled and how should it be resolved?

A.Configure Data Source Precedence to give 'Manual' or a higher-ranking source precedence over 'ServiceNow' for the 'Asset tag' attribute.

B.Check the 'No-Delete' flag on the Discovery Schedule record.

C.Disable the 'Asset tag' field mapping in the IRE payload processor script.

D.Set the cmdb_ci table to read-only for the Discovery integration user via ACLs.

AnswerA

Data Source Precedence governs which source wins when multiple sources populate the same attribute. Because Discovery's ServiceNow source outranks Manual, it overwrites the agent's edit even without scanning the tag directly. Raising Manual's precedence for 'Asset tag' stops the nightly overwrite, satisfying the requirement to preserve manual updates.

Why this answer

Data Source Precedence in ServiceNow CMDB determines which data source wins when multiple sources update the same CI attribute. By default, 'ServiceNow' (Discovery) may have higher precedence than 'Manual' for certain attributes, causing manual edits to be overwritten. Configuring Data Source Precedence to rank 'Manual' higher than 'ServiceNow' for the 'Asset tag' attribute ensures manual updates persist.

Exam trap

CIS-DF often tests the difference between Data Source Precedence and Reconciliation Rules — candidates confuse the two, but precedence determines which source wins, while reconciliation rules define the action (update, ignore, etc.).

How to eliminate wrong answers

Option B is wrong because the 'No-Delete' flag on a Discovery Schedule prevents CIs from being deleted when not found, not from being updated with new attribute values. Option C is wrong because disabling the 'Asset tag' field mapping in the IRE payload processor script would stop Discovery from updating that field at all, but the question states Discovery does not directly scan the asset tag — the overwrite comes from reconciliation, not direct mapping. Option D is wrong because setting the cmdb_ci table to read-only for the Discovery integration user would block all Discovery updates, not just the asset tag, and would break Discovery functionality.

Full explanation →

243

MCQhard

A CMDB administrator for a large enterprise notices that the CMDB Health Dashboard's Completeness KPI for the 'Business Application' class has been degrading over the past quarter, even though discovery and integrations are running successfully. The administrator needs to identify which specific CI attributes are most frequently left blank so that data stewards can be tasked with remediation. Which action should the administrator take to obtain this insight?

A.Open the Configuration Item form for a sample Business Application and use the related 'Audit' history to identify which fields have never been populated since the CI was created.

B.Open the CMDB Health Dashboard and drill into the Completeness KPI for Business Application, then review the attribute-level breakdown showing the percentage of CIs missing each required attribute.

C.Navigate to the CMDB Data Manager and create a new expiration policy for the Business Application class that retires records with missing attributes, then monitor the policy results.

D.Run a CMDB Query Builder query joining Business Application to the cmdb_ci table and filter for records where the 'owned_by' field is empty, then export the results for review.

AnswerB

The CMDB Health Dashboard's Completeness KPI can be configured with a list of attributes that are considered required for a class. Drilling into the KPI reveals an attribute-by-attribute breakdown, showing exactly which fields are missing and on how many CIs, which directly supports tasking data stewards with targeted remediation.

Why this answer

The CMDB Health Dashboard's Completeness KPI tracks required attributes per class and provides a drill-down that breaks down missing data by attribute. This attribute-level view is the only mechanism listed that aggregates blanks across all Business Application CIs, allowing the administrator to see which fields are most often empty and assign remediation to data stewards.

Exam trap

The trap here is assuming that any query or report listing CIs with a blank field provides the same insight as the Completeness KPI's attribute breakdown, when only the KPI aggregates missing data across all required attributes for the class.

Full explanation →

244

MCQeasy

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

A.Correctness Duplicate Widget

B.Orphaned CI Widget

C.Completeness Score Widget

D.Compliance Audit Widget

AnswerC

The Completeness Score Widget reports the proportion of CIs holding all mandatory attributes, directly surfacing records with missing required values. It satisfies the requirement to display that ratio, letting administrators target remediation at incomplete CIs affecting overall CMDB health.

Why this answer

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

Exam trap

The trap is confusing Completeness with Correctness or Compliance; candidates may select the Duplicate Widget thinking it covers missing data, but Completeness specifically addresses missing mandatory attributes.

How to eliminate wrong answers

Option A is wrong because the Correctness Duplicate Widget focuses on duplicate CIs, not missing attributes. Option B is wrong because the Orphaned CI Widget shows CIs without relationships, not missing mandatory attributes. Option D is wrong because the Compliance Audit Widget tracks audit compliance, not completeness of mandatory attributes.

Full explanation →

245

MCQmedium

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

A.CI Class Manager

B.Configuration Item Relationship (cmdb_rel_ci)

C.Identification and Reconciliation Engine (IRE)

D.Discovery Schedule

AnswerB

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

Why this answer

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

Full explanation →

246

MCQmedium

An administrator needs to create a logical representation of a deployed software stack in a specific environment (e.g., QA, Production) for a Business Application. Which table should be used to store this representation according to CSDM guidelines?

A.Application Service [cmdb_ci_service_calculated]

B.Technical Service [cmdb_ci_service]

C.Business Application [cmdb_ci_business_app]

D.Dynamic CI Group [cmdb_ci_query_based_service]

AnswerA

Application Service [cmdb_ci_service_calculated] satisfies the CSDM requirement for a logical, environment-specific representation of a deployed software stack tied to a Business Application. Its calculated service model maps technical components across QA or Production, distinguishing it from the physical Application Service instance table.

Why this answer

Per CSDM guidelines, an Application Service [cmdb_ci_service_calculated] is the logical representation of a deployed software stack in a specific environment (e.g., QA, Production) for a Business Application. It is the runtime, environment-specific instantiation that ties together the technical components serving the business capability. Business Applications represent the logical 'what the business cares about' across environments, while Application Services represent the 'how it's deployed' in each environment.

Exam trap

CIS-DF often tests the confusion between Business Application (logical, environment-agnostic) and Application Service (environment-specific deployed stack) — candidates frequently pick Business Application because it sounds more 'official.'

How to eliminate wrong answers

Option B is wrong because Technical Service [cmdb_ci_service] represents a technology-focused service (like a database service or messaging service) that supports application services, not the environment-specific logical stack for a business app. Option C is wrong because Business Application [cmdb_ci_business_app] is the logical, environment-agnostic representation of a business capability — it is not tied to a specific environment like QA or Production. Option D is wrong because Dynamic CI Group [cmdb_ci_query_based_service] is a query-based grouping of CIs used for reporting/grouping, not a CSDM-defined logical service representation of a deployed stack.

Full explanation →

247

MCQhard

An administrator notices that the CMDB Health background jobs are running during peak business hours and impacting performance. Where can the schedule for CMDB Health metric calculations be modified?

A.Discovery Schedules > CMDB Health

B.System Definition > Scheduled Jobs (searching for CMDB Health jobs)

C.CMDB Health Dashboard > Schedule Settings

D.Data Governance > Job Execution

AnswerB

CMDB Health metric calculations run as scheduled jobs, so their timing is altered via System Definition > Scheduled Jobs, where the relevant CMDB Health jobs are located and their run schedule adjusted away from peak hours.

Why this answer

CMDB Health metric calculations are executed by scheduled jobs, which can be modified in the System Definition > Scheduled Jobs module. Administrators can search for CMDB Health-related jobs and adjust their schedules to run during off-peak hours, reducing performance impact.

Exam trap

CIS-DF often tests the location of scheduled jobs, and candidates may incorrectly assume that CMDB Health schedules are managed within the CMDB Health Dashboard or Data Governance modules.

How to eliminate wrong answers

Option A is wrong because Discovery Schedules are used to schedule discovery runs, not CMDB Health metric calculations. Option C is wrong because the CMDB Health Dashboard does not provide schedule settings; it displays health results. Option D is wrong because Data Governance > Job Execution is not a standard location for scheduling CMDB Health jobs; it may relate to policy evaluations but not the core health metrics.

Full explanation →

248

MCQmedium

An enterprise has a custom application built on a Platform-as-a-Service (PaaS) environment. How should the PaaS infrastructure be represented relative to the Application Service in CSDM?

A.Replaced entirely by the Business Application record.

B.Connected to the Application Service via 'Depends on / Used by'.

C.Nested inside the Business Application table as a child record.

D.Converted into Service Offerings in the Sell/Consume domain.

AnswerB

CSDM models the PaaS infrastructure as a separate CI connected to the Application Service through a 'Depends on / Used by' relationship, since the service consumes the platform rather than containing it. This satisfies the stem's requirement to represent the PaaS relative to the Application Service.

Why this answer

In CSDM, a PaaS environment hosting a custom application is modeled as infrastructure that the Application Service depends on. The correct representation is to connect the PaaS infrastructure (as a technical service or infrastructure CI) to the Application Service using 'Depends on / Used by' relationships. This preserves the layered CSDM model where Application Services consume technical services.

Exam trap

The trap is treating CSDM as a containment hierarchy (nesting records) rather than a relationship model — candidates pick 'nested inside' or 'replaced by' instead of the correct 'Depends on / Used by' relationship.

How to eliminate wrong answers

Option A is wrong because the Business Application record represents the business-facing application, not the underlying PaaS infrastructure — replacing it would erase the technical layer. Option C is wrong because CSDM does not nest infrastructure CIs as child records inside the Business Application table; relationships, not containment, model dependencies. Option D is wrong because Service Offerings in the Sell/Consume domain represent what is offered to consumers, not the PaaS runtime that supports an Application Service.

Full explanation →

249

MCQhard

You are auditing a ServiceNow instance and notice that an Application Service record has been created directly on the Business Application table rather than the Application Service table. What corrective action must be taken?

A.Convert the record into a Technical Service Offering.

B.Delete the incorrect record and create a new record on the Application Service table [cmdb_ci_service_calculated], linking it to the correct Business Application.

C.Leave the record as-is, because Business Application and Application Service tables are interchangeable in newer ServiceNow releases.

D.Change the table attribute in Dictionary Overrides so that Business Applications act as Application Services.

AnswerB

Application Service records must reside on the Application Service table, not the Business Application table, because CSDM class hierarchy and dependency mapping rely on correct class placement. Deleting the misplaced record and recreating it on cmdb_ci_service_calculated, linked to its Business Application, restores the mandated CSDM relationship structure.

Why this answer

The correct action is to delete the misclassified record and recreate it on the Application Service table [cmdb_ci_service_calculated], linking it to the correct Business Application. Application Service and Business Application are distinct CSDM classes with different semantics; a record created on the wrong table breaks the model's integrity and reporting. Recreating on the correct table ensures proper relationships and downstream CSDM compliance.

Exam trap

The trap is assuming the tables are interchangeable or that a simple field/dictionary change can fix the misclassification; CSDM requires the record to exist on the correct class with proper relationships.

How to eliminate wrong answers

Option A is wrong because converting the record into a Technical Service Offering does not address the misclassification — it moves the record to yet another incorrect class and still violates CSDM. Option C is wrong because Business Application and Application Service tables are not interchangeable; they represent different concepts (business-facing vs. calculated technical grouping) and merging them breaks CSDM reporting and service mapping. Option D is wrong because Dictionary Overrides cannot make one table act as another for CSDM purposes; they only alter field behavior, not class semantics or relationships.

Full explanation →

250

MCQhard

An enterprise is audited for CSDM compliance. The CSDM Data Foundations Dashboard indicates that application services are not properly connected to technical services. What is the governance impact of this structural gap?

A.Hardware assets will automatically be marked as deprecated

B.Database replication lag will increase across MID servers

C.Discovery will fail to run network scans on IP subnets

D.Inability to accurately perform impact analysis during outages and incorrect service portfolio visibility

AnswerD

Missing technical-service relationships break the CSDM dependency chain, so application services cannot be traced to the infrastructure they consume. That gap directly prevents accurate impact analysis during outages and corrupts service portfolio visibility, satisfying the stem's requirement to identify the governance consequence of the structural disconnect.

Why this answer

In CSDM, application services must be connected to technical services to provide a complete service model. If this linkage is missing, the organization cannot accurately trace the impact of an outage from the business application down to the underlying technical components, and service portfolio visibility becomes fragmented. This directly undermines impact analysis and service health reporting, which are core governance outcomes of CSDM.

Exam trap

CIS-DF often tests the misconception that CSDM gaps affect infrastructure operations like discovery or replication; the real impact is on service visibility and impact analysis, which are governance outcomes.

How to eliminate wrong answers

Option A is wrong because hardware asset deprecation is governed by asset lifecycle policies, not by application-to-technical service relationships; a structural gap in CSDM does not automatically deprecate hardware. Option B is wrong because database replication lag is a database/infrastructure performance issue, unrelated to CSDM service modeling relationships. Option C is wrong because Discovery network scans are configured via discovery schedules and IP ranges, not by application service to technical service connections; CSDM gaps do not prevent network scanning.

Full explanation →

251

Multi-Selectmedium

Which TWO actions can be performed directly from the CMDB Health Dashboard when investigating health metrics? (Choose two.)

Select 2 answers

A.Directly modify core IRE Identification Rules for hardware classes

B.Permanently delete all duplicate CIs across the entire enterprise with a single click

C.View remediation tasks associated with data health failures

D.Drill down into specific failing CIs contributing to poor completeness scores

E.Modify MID Server cluster configurations

AnswersC, D

Remediation tasks surface directly from the dashboard's health metric drill-down, letting you trace failed data health checks to their assigned fixes without leaving the CMDB Health Dashboard. This satisfies the stem's requirement for actions performed directly from the dashboard, since remediation records are linked to the failing metric itself.

Why this answer

Option C is correct because the CMDB Health Dashboard provides access to remediation tasks that are generated for failed health checks, allowing administrators to view and act on the tasks associated with data health failures directly from the dashboard. Option D is correct because the dashboard supports drill-down navigation, enabling users to click into a failing metric (such as completeness) and see the specific CIs that are contributing to the poor score. Option A is incorrect because IRE Identification Rules are configured in the Identification and Reconciliation engine settings, not modified from the CMDB Health Dashboard.

Option B is incorrect because bulk permanent deletion of all duplicate CIs across the enterprise is not a one-click action available from the dashboard and would require de-duplication processes and careful review. Option E is incorrect because MID Server cluster configuration is managed in MID Server properties and settings, not from the CMDB Health Dashboard.

Exam trap

CIS-DF often tests whether candidates confuse dashboard investigative actions (view/drill down) with administrative configuration actions (edit IRE rules, delete duplicates) — the exam expects you to know the dashboard is read/investigate-oriented, not a bulk-admin console.

Full explanation →

252

MCQmedium

An organization wants to establish a baseline snapshot of their critical infrastructure CIs to compare against future configuration changes. Which native feature allows creating and viewing these configuration baselines?

A.CI Class Manager Version Control

B.CMDB Baselines and Baseline Diff Viewer

C.CMDB Query Builder Snapshot Tool

D.Service Mapping Baseline Generator

AnswerB

CMDB Baselines capture point-in-time snapshots of configuration items, and the Baseline Diff Viewer compares them against later states, satisfying the requirement to detect drift in critical infrastructure CIs. Both are native ServiceNow capabilities, so no custom development or external tooling is needed to establish the baseline.

Why this answer

The CMDB Baselines and Baseline Diff Viewer feature allows administrators to create snapshots of CIs and their relationships, and then compare them over time to identify configuration changes. This is a native feature for establishing baselines and viewing differences.

Exam trap

CIS-DF often tests the name of the baseline feature, and candidates may confuse it with other CMDB tools like Query Builder or Service Mapping.

How to eliminate wrong answers

Option A is wrong because CI Class Manager Version Control is not a standard feature for creating baselines; it may refer to versioning of CI class definitions, not CI data. Option C is wrong because CMDB Query Builder Snapshot Tool is not a native feature; Query Builder is for querying, not baselines. Option D is wrong because Service Mapping Baseline Generator is not a native feature; Service Mapping is for mapping services, not baselines.

Full explanation →

253

MCQhard

An organization uses Service Mapping to visualize an e-commerce application. A user notices that a specific entry point shows a 'Partial' map status. What does this Insight indicator specifically communicate?

A.Service Mapping encountered errors, missing credentials, or unmapped traffic during discovery of the service topology.

B.The Discovery schedule is currently paused by an administrator.

C.The underlying infrastructure has not been updated within the last 90 days.

D.The business service record lacks mandatory CSDM technical service offerings.

AnswerA

A Partial status means Service Mapping could not complete the topology: discovery hit errors, lacked credentials for some devices, or saw traffic it could not map to a CI. The entry point is therefore only partially traced.

Why this answer

A 'Partial' map status in Service Mapping indicates that the discovery of the service topology was incomplete — typically due to errors, missing credentials, or unmapped traffic that prevented Service Mapping from fully tracing all connections. This status signals that the map is usable but not complete, and administrators should investigate the discovery errors to resolve the gaps.

Exam trap

CIS-DF often tests the meaning of Service Mapping map statuses — candidates confuse 'Partial' with schedule issues or data staleness, but it specifically indicates incomplete discovery due to errors, credentials, or unmapped traffic.

How to eliminate wrong answers

Option B is wrong because a paused Discovery schedule would halt discovery entirely, not produce a 'Partial' map status — the map status reflects the completeness of the discovered topology, not the schedule state. Option C is wrong because infrastructure staleness is a CMDB Health metric, not a Service Mapping map status — 'Partial' is about discovery completeness, not data age. Option D is wrong because missing CSDM technical service offerings is a data model compliance issue, not a Service Mapping map status indicator.

Full explanation →

254

MCQhard

An administrator is configuring a Robust Transform Engine (RTE) definition for a complex CMDB data import. They need to ensure that if an incoming record fails identification or has missing mandatory attributes, the entire batch does not fail, but instead logs an error for that specific row. Where is this error handling behavior managed in RTE?

A.Set the Import Set transform map property to 'Ignore Errors' globally.

B.Modify the IRE engine configuration property 'glide.cmdb.ire.abort_on_error' to false.

C.Write a global Business Rule on sys_import_set_row to catch exceptions.

D.Configure error handling options within the Robust Transform Engine Data Stream Definition and field processors to capture row-level exceptions.

AnswerD

Row-level exception capture is configured in the RTE Data Stream Definition, where field processors log failures for individual records without aborting the batch. This satisfies the stem's constraint that a single record failing identification or missing mandatory attributes must not fail the entire import, isolating errors per row instead.

Why this answer

In RTE, error handling is configured within the Data Stream Definition and field processors. This allows row-level error capture, so if a record fails identification or has missing mandatory attributes, the error is logged for that specific row without failing the entire batch.

Exam trap

CIS-DF often tests RTE error handling; candidates may confuse it with IRE or traditional transform map error handling, but RTE has its own configuration in Data Stream Definitions.

How to eliminate wrong answers

Option A is wrong because the Import Set transform map property 'Ignore Errors' is a global setting for traditional transforms, not RTE, and it would ignore all errors, not log them per row. Option B is wrong because the IRE engine property 'glide.cmdb.ire.abort_on_error' controls IRE behavior, not RTE, and setting it to false would prevent aborting on error but does not provide row-level logging. Option C is wrong because a global Business Rule on sys_import_set_row is a custom workaround, not the built-in RTE error handling mechanism.

Full explanation →

255

Multi-Selecthard

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

Select 3 answers

A.Configuring Identification and Reconciliation Engine (IRE) identification rules for the class.

B.Setting up reconciliation definitions to control data source update priorities.

C.Viewing and managing class attributes and inheritance hierarchy.

D.Creating custom database views across unrelated application tables.

E.Writing custom JavaScript business logic to execute during Discovery credential checks.

AnswersA, B, C

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

Why this answer

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

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

Exam trap

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

Full explanation →

256

MCQeasy

Which CSDM domain contains the 'Business Application' table [cmdb_ci_business_app]?

A.Manage Technical Services

B.Foundation

C.Design

D.Sell/Consume

AnswerC

The Design domain holds the Business Application table, which models logical applications independently of deployed infrastructure. This satisfies the stem's requirement by placing business-facing application records within the design layer rather than the Foundation or Manage Technical Service domains, where physical CIs and service offerings respectively reside.

Why this answer

The Design domain contains the Business Application table, representing applications from a portfolio and architecture perspective.

Full explanation →

257

Multi-Selectmedium

Which TWO of the following indicators or statuses can be viewed on a Service Mapping map? (Choose two.)

Select 2 answers

A.CMDB Data Manager archival policy execution logs

B.Individual user session password expiration alerts

C.Traffic connections showing active network communication flows between nodes

D.Partial map status indicating incomplete discovery traversal

E.Financial asset depreciation schedules and contract end dates

AnswersC, D

Traffic connections appear as directional lines between nodes, revealing live communication flows that satisfy the requirement to view active network relationships on the map. Service Mapping derives these from discovered TCP connections, so the map displays actual traffic paths rather than inferred dependencies, directly meeting the indicator-visibility constraint.

Why this answer

Option C is correct because Service Mapping maps display traffic-based connections between CIs, showing active network communication flows (such as TCP connections) that were discovered between nodes. Option D is correct because Service Mapping maps can show a partial map status when discovery traversal is incomplete, indicating that some connections or CIs could not be fully mapped. Option A is incorrect because CMDB Data Manager archival policy execution logs are viewed in the CMDB Data Manager, not on a Service Mapping map.

Option B is incorrect because individual user session password expiration alerts are not a Service Mapping map indicator. Option E is incorrect because financial asset depreciation schedules and contract end dates belong to asset and contract management, not Service Mapping maps.

Full explanation →

258

Multi-Selecteasy

Which TWO metrics are primary components of the CMDB Health framework? (Choose two.)

Select 2 answers

A.Correctness

B.Network latency

C.Storage capacity

D.Completeness

E.License compliance count

AnswersA, D

Correctness is one of the CMDB Health framework's primary pillars, alongside Completeness and Compliance. It measures whether CI records accurately reflect reality, covering duplicates, orphans and stale data, making it a foundational component of the health scoring model.

Why this answer

In the ServiceNow CMDB Health framework, Correctness (A) is a primary metric because it evaluates whether CIs have the required attributes populated with valid, accurate values (e.g., checking that mandatory fields are not empty and that values conform to expected formats or reference data). Completeness (D) is also a primary metric because it measures whether required CIs and their mandatory attributes exist and are populated, ensuring the CMDB contains all expected records and relationships. These two, along with Compliance and Duplicates, form the core CMDB Health KPIs used to score and remediate CMDB data quality.

Network latency (B) and storage capacity (C) are infrastructure performance metrics, not CMDB data-health indicators. License compliance count (E) relates to software license management or SAM, not to the CMDB Health framework's primary metrics.

Full explanation →

259

MCQeasy

Which CSDM domain covers the definition and management of Technical Services that support internal IT operations?

A.Design

B.Foundation

C.Manage Technical Services

D.Sell/Consume

AnswerC

The Manage Technical Services domain in the CSDM framework covers Technical Services and their offerings that support internal IT operations. It defines how infrastructure components are grouped into services consumed by other technical services rather than directly by business users.

Why this answer

The Manage Technical Services domain in the CSDM (Common Service Data Model) framework covers the definition and management of Technical Services that support internal IT operations. It sits between the Design and Sell/Consume domains and provides the operational layer for how IT services are delivered and maintained. This domain includes Technical Service, Technical Service Offering, and related CIs used by IT operations.

Exam trap

The trap is confusing the CSDM domains — candidates often pick Design or Foundation because they sound foundational, but the question specifically asks about the operational management of Technical Services, which is the Manage Technical Services domain.

How to eliminate wrong answers

Option A is wrong because the Design domain covers the conceptual and logical design of business and technical services (e.g., Business Service, Service Offering design), not the operational management of Technical Services. Option B is wrong because the Foundation domain provides the base data elements (Company, Location, User, etc.) that underpin all other domains, not the management of Technical Services. Option D is wrong because the Sell/Consume domain focuses on the customer-facing catalog and request fulfillment (e.g., Service Catalog, Request), not internal IT operational Technical Services.

Full explanation →

260

MCQhard

Your enterprise has multiple regions deploying the same ERP software. You want to map incident and change metrics separately for the North American Production instance versus the European Production instance of the ERP. How should you structure this in the CSDM framework?

A.Create two Technical Services and map them directly to the Business Application record.

B.Create two separate Business Application records and point them to a single Application Service record.

C.Create a single Application Service record and use dynamic tags on incident forms to separate the regions.

D.Create one Business Application record and link two distinct Application Service records to it.

AnswerD

Separate Application Service records let each regional ERP production instance carry its own incident and change metrics, while one Business Application preserves the shared ERP identity. This satisfies the stem's requirement to report metrics separately per region.

Why this answer

In the CSDM framework, a Business Application represents the logical software product (the ERP), while Application Services represent the specific deployed instances of that application that provide business functionality. To separate metrics for North American Production versus European Production, you need two distinct Application Service records—one per regional instance—both linked to the single Business Application record for the ERP. This structure allows incident and change metrics to be tracked independently at the Application Service level while maintaining a unified view of the Business Application.

Exam trap

CIS-DF often tests the distinction between Business Applications and Application Services, and candidates frequently confuse the two by either duplicating Business Applications for each instance or skipping the Application Service layer entirely.

How to eliminate wrong answers

Option A is wrong because Technical Services represent the underlying infrastructure or technology components (e.g., servers, databases) that support applications, not the business-facing application instances themselves; mapping them directly to the Business Application bypasses the Application Service layer and breaks CSDM's logical hierarchy. Option B is wrong because creating two separate Business Application records would incorrectly duplicate the logical software product, fragmenting reporting and violating the principle that a Business Application is a single logical entity; pointing them to a single Application Service also inverts the correct relationship. Option C is wrong because using dynamic tags on incident forms is a workaround that does not create the necessary CSDM structure; it lacks the formal relationships needed for consistent metric separation and reporting, and tags are not a substitute for proper Application Service records.

Full explanation →

261

MCQmedium

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

A.Discovery Source Exclusion rules

B.Reconciliation Definitions

C.CI Class Manager attribute properties

D.Access Control Lists (ACLs) on the cmdb_ci table

AnswerB

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →

262

MCQhard

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

A.Disable all discovery sources to prevent further duplicates.

B.Increase the CMDB Health Dashboard's duplicate threshold to improve the score.

C.Merge all duplicate CIs manually using the CI Class Manager.

D.Run the CMDB Health Dashboard's 'Duplicate CIs' report to list all duplicates.

AnswerD

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

Why this answer

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

Exam trap

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

Full explanation →

263

MCQmedium

An administrator is setting up a ServiceNow Discovery schedule for a subnet in a restricted data center. The Discovery schedule runs successfully, but no new CIs are populated in the CMDB. Upon checking the Discovery status, the probes completed, but the horizontal discovery pattern logs indicate a 'Permission Denied' on WMI/SSH commands. Where should the administrator verify the credentials used for this ingestion?

A.In CI Class Manager under Discovery Source Precedence.

B.In the CMDB Health Dashboard under Audit Rules.

C.In the Credentials table (discovery_credentials) or Credential Aliases, ensuring the correct protocol credentials are mapped to the IP range.

D.In the Robust Transform Engine source properties.

AnswerC

Discovery probes authenticated with credentials stored in the Credentials table and mapped via Credential Aliases to the target IP range. The 'Permission Denied' errors confirm the mapped WMI or SSH credential lacks rights, so verifying that mapping resolves the missing CI population.

Why this answer

Discovery and ingestion via credentials are managed through Credential Aliases and the Credentials table.

Full explanation →

264

MCQeasy

Which role is typically required to manage and configure CMDB Data Governance policies and remediation definitions?

A.asset

B.itil

C.discovery_admin

D.cmdb_datagovernance_admin

AnswerD

The cmdb_datagovernance_admin role grants the privileges needed to create and maintain CMDB Data Governance policies, remediation definitions and related rule configurations. It satisfies the requirement to manage governance policy setup without granting broader platform administrative rights.

Why this answer

The cmdb_datagovernance_admin role is specifically designed to manage and configure CMDB Data Governance policies and remediation definitions. This role grants the necessary permissions to define governance rules, set up remediation workflows, and oversee data integrity within the CMDB. Unlike other roles, it is purpose-built for data governance tasks, ensuring that only authorized users can modify critical governance settings.

Exam trap

CIS-DF often tests the distinction between general CMDB administration roles and specialized data governance roles, causing candidates to confuse the cmdb_datagovernance_admin with broader roles like itil or discovery_admin.

How to eliminate wrong answers

Option A is wrong because the 'asset' role is intended for asset management tasks, such as tracking and managing assets, not for configuring CMDB data governance policies. Option B is wrong because the 'itil' role is a general ITIL role that provides access to ITIL processes like incident, problem, and change management, but does not include the specific permissions required for CMDB data governance. Option C is wrong because the 'discovery_admin' role is focused on configuring and managing discovery schedules, credentials, and related settings, not on data governance policies or remediation definitions.

Full explanation →

265

Multi-Selecteasy

Which TWO core benefits does the CSDM Data Foundations Dashboard provide to an organization? (Choose two.)

Select 2 answers

A.Direct control over firewall security policies

B.Identification of orphaned relationships and missing foundational CIs

C.Visibility into CSDM compliance and maturity stages

D.Automated network switch configuration backups

E.Real-time patch management compliance scoring

AnswersB, C

The dashboard scans the CMDB for configuration items lacking mandatory relationships or required foundational data, surfacing orphans and gaps that break dependency mapping. This directly satisfies the stem's demand for a core benefit: proactive identification of data integrity failures, enabling remediation before downstream CSDM processes and reporting are compromised.

Why this answer

Option B is correct because the CSDM Data Foundations Dashboard surfaces data-quality gaps in the CMDB, specifically orphaned relationships (CIs whose relationships point to missing or decommissioned records) and missing foundational CIs that the CSDM framework requires as prerequisites for higher-level modeling. Option C is correct because the dashboard reports on CSDM compliance and shows which maturity stages (e.g., Foundation, Crawl, Walk, Run, Fly) the organization has achieved, letting teams track adoption progress against the CSDM framework. The remaining options do not belong: A (firewall security policy control) is a network security management function, D (automated network switch configuration backups) is a network configuration/backup tool capability, and E (real-time patch management compliance scoring) is a vulnerability/patch management function — none of these are provided by the CSDM Data Foundations Dashboard, which is focused on CMDB data quality and CSDM adoption.

Exam trap

The trap is picking operational capabilities (firewall control, patch scoring, switch backups) that sound like governance but belong to other ITOM/security modules, not the CSDM Data Foundations Dashboard.

Full explanation →

266

MCQeasy

A team wants to exclude test and lab servers from being evaluated by strict production CMDB Health completeness rules. What is the best practice method to handle this in ServiceNow?

A.Modify the baseline system properties to ignore completeness globally

B.Delete the test server CIs from the CMDB

C.Configure CMDB Health Inclusion Rules

D.Turn off Discovery for the test network

AnswerC

CMDB Health Inclusion Rules let administrators scope which CIs health calculations evaluate, so test and lab servers can be excluded from strict production completeness rules without altering the rules themselves. This directly satisfies the exclusion requirement.

Why this answer

The best practice to exclude test and lab servers from strict production CMDB Health completeness rules is to configure CMDB Health Inclusion Rules. These rules allow administrators to define conditions that determine which CIs are included in health evaluations, so test servers can be filtered out based on attributes like environment or CI class. This avoids modifying global settings or deleting CIs.

Exam trap

The trap is thinking that global system properties or deletion are viable solutions; the exam expects knowledge that CMDB Health Inclusion Rules provide a scoped, best-practice way to exclude specific CIs from health evaluations.

How to eliminate wrong answers

Option A is wrong because modifying baseline system properties to ignore completeness globally would disable completeness checks for all CIs, not just test servers, which is not a best practice. Option B is wrong because deleting test server CIs from the CMDB removes valuable data and is not a sustainable approach. Option D is wrong because turning off Discovery for the test network would stop data collection but would not exclude existing test CIs from health rules, and it could impact other discovery needs.

Full explanation →

267

MCQmedium

An administrator is setting up an import using Robust Transform Engine (RTE). They need to ensure that incoming records are only processed if a specific status field equals 'Active'. Where should this conditional filtering be configured within RTE?

A.Write an On-Load Client Script on the staging table.

B.Modify the identification rule criteria to ignore inactive records.

C.Configure data stream filters or conditional field processors within the Robust Transform Engine definition.

D.Set the Coalesce checkbox on the Transform Map to 'Active'.

AnswerC

Data stream filters and conditional field processors evaluate each incoming record against expressions such as status equals 'Active', discarding non-matching rows before transformation. This satisfies the stem's requirement that only Active records proceed, since filtering is applied inside the Robust Transform Engine definition itself rather than downstream.

Why this answer

In RTE, conditional filtering to process only records with a specific status (e.g., 'Active') is configured using data stream filters or conditional field processors within the RTE definition. These allow administrators to define conditions that records must meet to be processed further.

Exam trap

CIS-DF often tests the confusion between RTE-level filtering and other mechanisms like Transform Map coalesce or Business Rules, leading candidates to choose options that are not part of RTE.

How to eliminate wrong answers

Option A is wrong because an On-Load Client Script on the staging table runs in the browser and is not part of RTE processing; it cannot reliably filter records for RTE. Option B is wrong because identification rule criteria are used by the IRE to match CIs, not to filter incoming records before transformation. Option D is wrong because the Coalesce checkbox on a Transform Map is for updating existing records based on matching fields, not for conditional filtering based on a status field.

Full explanation →

268

Multi-Selectmedium

An administrator is configuring Data Source Precedence rules in the CMDB. Which TWO of the following statements regarding Data Source Precedence are true? (Choose two.)

Select 2 answers

A.Data Source Precedence only applies to data ingested via legacy Import Sets without Transform Maps.

B.Administrators can configure Data Source Precedence rules at both the global CMDB level and granularly per CI class.

C.Data Source Precedence automatically deletes CIs that have not been updated by a high-priority source within 30 days.

D.Data Source Precedence rules dictate which discovery source wins control of specific CI attributes when multiple sources attempt updates.

E.Data Source Precedence rules replace the need for Identification Rules in the IRE.

AnswersB, D

Data Source Precedence supports rules defined globally across the CMDB and also scoped granularly to individual CI classes, letting class-specific overrides take effect. This dual-level configuration is precisely the statement the question asks you to confirm as true.

Why this answer

Option B is correct because Data Source Precedence in the CMDB can be configured at the global level (applying to all CI classes) as well as at the individual CI class level, allowing administrators to tailor precedence granularly where needed. Option D is correct because the core purpose of Data Source Precedence rules is to determine which discovery source (e.g., ServiceNow Discovery, SCCM, manual entry) is authoritative for specific CI attributes when multiple sources attempt to update the same CI, resolving conflicts by source priority. Option A is incorrect because Data Source Precedence applies to data processed through the Identification and Reconciliation Engine (IRE), not just legacy Import Sets without Transform Maps.

Option C is incorrect because Data Source Precedence does not perform automatic deletion or aging of CIs; it only governs which source's data wins during updates. Option E is incorrect because Data Source Precedence works alongside Identification Rules within the IRE—it does not replace them, as Identification Rules are still required to determine CI uniqueness and matching.

Full explanation →

269

MCQhard

During a CSDM audit, you notice that incidents are being logged directly against Business Applications instead of Application Services. What is the operational impact of this misconfiguration?

A.It prevents targeted impact analysis because Business Applications do not track specific runtime infrastructure or environment details.

B.Users will be unable to view the Business Application in the Service Portal.

C.Discovery will fail to update the Business Application record during daily scheduled runs.

D.Service Level Agreements (SLAs) will automatically fail to attach to incident records.

AnswerA

Business Applications sit at the conceptual layer and carry no runtime or environment detail, so incidents logged against them cannot be traced to specific infrastructure. Application Services hold that deployment context, enabling targeted impact analysis; logging against Business Applications severs that linkage.

Why this answer

Business Applications represent logical groupings of application services and do not track specific runtime infrastructure or environment details. Incidents logged directly against them lack the granular context needed for targeted impact analysis, which requires mapping to Application Services that are tied to actual CIs and their relationships.

Exam trap

CIS-DF often tests the distinction between Business Applications and Application Services, trapping candidates who assume that logging incidents against either yields the same operational insight.

How to eliminate wrong answers

Option B is wrong because users can still view Business Applications in the Service Portal; the issue is not visibility but the lack of infrastructure detail. Option C is wrong because Discovery updates CIs, not Business Applications directly, and mislogging incidents does not affect Discovery's ability to update records. Option D is wrong because SLAs attach based on conditions on the incident record, not on the CI it is logged against, so SLAs would still attach if conditions are met.

Full explanation →

270

Multi-Selecthard

When configuring and troubleshooting Dependency Views in ServiceNow, which TWO factors directly affect how relationship lines and nodes are displayed between CIs? (Choose two.)

Select 2 answers

A.Presence of valid records in the cmdb_rel_ci table

B.Client-side form layout (UI policies)

C.The local browser cache size of the end user

D.Discovery schedule polling intervals

E.Active relationship filters applied to the view

AnswersA, E

The map relies entirely on relationship records stored in the cmdb_rel_ci table to draw connections.

Why this answer

Option A is correct because Dependency Views are built from the actual relationship records stored in the cmdb_rel_ci table; without valid parent/child CI relationship records there, no connecting lines or linked nodes can be rendered between CIs. Option E is correct because active relationship filters applied to the view determine which relationship types and directions are included, directly controlling which lines and nodes appear in the dependency map. Options B, C, and D do not belong: client-side form layout/UI policies affect form field behavior, not dependency map rendering; browser cache size only affects local performance, not the logical display of nodes and relationships; and Discovery schedule polling intervals govern when discovery runs, not how existing relationships are drawn in a Dependency View.

Exam trap

CIS-DF often tests the distinction between data-layer factors (cmdb_rel_ci records, relationship filters) and presentation-layer factors (UI policies, browser cache) — candidates incorrectly pick UI-related options.

Full explanation →

271

MCQeasy

Which module provides a centralized reporting interface specifically for monitoring CMDB data quality scores across Completeness, Correctness, and Compliance?

A.CMDB Health Dashboard

B.CSDM Workspace

C.Performance Analytics Hub

D.CMDB Dashboard in Service Operations Workspace

AnswerA

The CMDB Health Dashboard aggregates quality scores across the three prescribed axes — Completeness, Correctness, and Compliance — into one centralised view, directly satisfying the stem's requirement for a single reporting interface monitoring CMDB data quality. No other module consolidates all three metrics together.

Why this answer

The CMDB Health Dashboard is the centralized reporting interface specifically designed to monitor CMDB data quality scores across Completeness, Correctness, and Compliance. It provides widgets and scores that aggregate health metrics, allowing administrators to track data quality trends and identify areas needing remediation. This dashboard is the primary tool for CMDB health monitoring.

Exam trap

The trap is confusing the CMDB Health Dashboard with other dashboards like CSDM or Performance Analytics; candidates must remember that CMDB Health Dashboard is the specific tool for Completeness, Correctness, and Compliance scores.

How to eliminate wrong answers

Option B is wrong because CSDM Workspace focuses on the Common Service Data Model and its adoption, not specifically on CMDB health scores. Option C is wrong because Performance Analytics Hub is a general analytics platform, not a CMDB-specific health dashboard. Option D is wrong because the CMDB Dashboard in Service Operations Workspace is a different view, but the question asks for the centralized reporting interface for CMDB data quality scores, which is the CMDB Health Dashboard.

Full explanation →

272

MCQeasy

Which ServiceNow module provides a centralized dashboard view of CMDB data quality metrics, including completeness, correctness, and compliance?

A.Transform Map Metrics

B.CMDB Health Dashboard

C.Discovery Status Dashboard

D.Service Mapping Workbench

AnswerB

The CMDB Health Dashboard aggregates completeness, correctness, and compliance scores into a single centralised view, directly satisfying the stem's requirement for a dashboard of CMDB data quality metrics. Unlike the CMDB Data Manager, which governs lifecycle tasks, it specifically surfaces health KPIs for monitoring and remediation prioritisation.

Why this answer

The CMDB Health Dashboard provides health calculations across completeness, correctness, and compliance.

Full explanation →

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