Courseiva

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

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

Take a mock examExam hub
Page 1

Page 2 of 4

Page 3
76
MCQeasy

An auditor needs to verify when a critical business application CI was last updated by an authorized discovery source versus a manual update. Which CMDB feature tracks the provenance and history of attribute updates for governance review?

A.CMDB Baseline
B.Reconciliation Engine Simulator
C.Audit Log and CI History
D.CMDB Data Manager
AnswerC

Audit Log and CI History retain each attribute change with its source, timestamp and user, distinguishing discovery-driven updates from manual edits. This provenance trail gives auditors the evidence needed to verify who last modified the application CI and through which channel.

Why this answer

The Audit Log and CI History feature in the CMDB records every change made to a configuration item, including the source of the update (e.g., discovery, manual, import) and the timestamp. This provides the provenance and historical record needed for governance and audit reviews. It allows auditors to distinguish between authorized discovery updates and manual modifications.

Exam trap

CIS-DF often tests the confusion between features that manage data quality (like CMDB Data Manager) and those that provide audit trails (like Audit Log and CI History). Candidates may mistakenly choose CMDB Data Manager thinking it tracks provenance, but it focuses on data certification and bulk updates, not historical audit.

How to eliminate wrong answers

Option A is wrong because CMDB Baseline is used to compare the current state of a CI against a known good baseline, not to track the history or source of individual attribute updates. Option B is wrong because Reconciliation Engine Simulator is a tool for testing reconciliation rules and does not store historical update data. Option D is wrong because CMDB Data Manager is used for bulk data operations and governance of data quality, but it does not provide the detailed audit trail of attribute-level changes with source information.

Full explanation →
77
MCQmedium

A CMDB administrator is configuring a Data Certification campaign to verify the accuracy of CI attributes. The administrator wants to ensure that only CIs that have not been certified in the last 6 months are included in the campaign. Which ServiceNow feature should be used to filter the CIs?

A.CMDB Data Manager policies
B.Data Certification filter conditions
C.CMDB Data Governance policies
D.CMDB Health Dashboard filters
AnswerB

When creating a Data Certification campaign, you can define filter conditions to specify which CIs are included. You can use conditions based on fields such as 'Last certified date' to exclude CIs certified within the last 6 months. This allows precise targeting of CIs that require re-certification.

Why this answer

Data Certification filter conditions allow the administrator to specify criteria for including CIs in a campaign. By setting a condition on the 'Last certified' field to be older than 6 months, only those CIs are included. Other options do not provide this filtering capability for certification campaigns.

Exam trap

The trap here is confusing governance policies with certification filters; only the certification campaign configuration includes filter conditions.

Full explanation →
78
MCQhard

A CMDB administrator is mapping the CSDM Service Delivery domain for a bank. The bank offers 'Mobile Banking' as a service to retail customers, and internally the IT group also provides 'Database Administration' to application teams. Which statement correctly distinguishes how these two offerings are modeled in CSDM?

A.Mobile Banking is modeled as a Business Service, while Database Administration is modeled as a Technical Service.
B.Both are modeled as Technical Services, because CSDM classifies all services by the technology that delivers them.
C.Mobile Banking is modeled as a Technical Service, while Database Administration is modeled as a Business Service.
D.Both are modeled as Business Services, because CSDM treats every service consumed by a user group as a Business Service.
AnswerA

In the CSDM Service Delivery domain, a Business Service is something offered to business or external consumers, so Mobile Banking fits that definition. A Technical Service is consumed by other services or IT teams rather than business users, so Database Administration belongs there. This separation preserves the consumer-based distinction and allows correct dependency mapping between business-facing and internally consumed services.

Why this answer

The CSDM Service Delivery domain separates services based on who consumes them. Mobile Banking is consumed by retail customers, so it is modeled as a Business Service. Database Administration is consumed by internal application teams, so it is modeled as a Technical Service.

Keeping these categories distinct preserves accurate dependency mapping and service portfolio reporting across business-facing and IT-facing offerings.

Exam trap

The trap here is assuming that any service with the word 'service' in its name must be a Business Service, instead of checking the consumer relationship that CSDM uses for classification.

Full explanation →
79
Multi-Selecthard

Which THREE of the following mechanisms can be used to populate or maintain Application Services in the CMDB?

Select 3 answers
A.Manual CI selection and list management
B.Dynamic CI Groups using query criteria
C.Direct import of incident ticket attachments
D.Automatic conversion of Foundation user records
E.Top-down Service Mapping
AnswersA, B, E

Manual CI selection and list management lets administrators explicitly choose which configuration items constitute an application service and curate that membership list. This satisfies the stem by providing a human-maintained mechanism that populates and sustains Application Services in the CMDB where automated discovery is unsuitable.

Why this answer

Option A (Manual CI selection and list management) is correct because Application Services in the CMDB can be populated by manually adding CIs to the service record, giving administrators direct control over which configuration items belong to the service. Option B (Dynamic CI Groups using query criteria) is correct because Application Services can be maintained dynamically through CI Groups whose membership is defined by query conditions, so CIs are automatically included or excluded as they match or fail the criteria. Option E (Top-down Service Mapping) is correct because Service Mapping discovers and builds Application Services by tracing traffic and dependencies top-down from an entry point, automatically creating and maintaining the service CIs and their relationships in the CMDB.

Option C is not correct because incident ticket attachments are unstructured data and are not a supported mechanism for populating CMDB Application Services. Option D is not correct because Foundation user records are identity/user data, not CI records, and are not automatically converted into Application Services.

Exam trap

CIS-DF often tests whether candidates confuse unrelated record types (users, incident attachments) with legitimate CI population mechanisms, or overlook that Dynamic CI Groups and Service Mapping are both valid automated approaches alongside manual management.

Full explanation →
80
MCQhard

An organization requires a custom report that extracts CIs that match a complex multi-class criteria: Linux servers running a specific Oracle version that connect to a Business Service via a downstream 'Depends on::Used by' relationship. What is the most efficient native way to generate this dataset?

A.Write a Database View joining cmdb_ci, cmdb_rel_ci, and cmdb_software_product.
B.Build a custom Service Mapping Traffic Connection report.
C.Use CMDB Query Builder to construct a multi-node relationship query and save it as a reporting source.
D.Create a standard ServiceNow List Report on the CI [cmdb_ci] table with multiple join conditions.
AnswerC

CMDB Query Builder supports multi-node relationship traversal, so you can join Linux server CIs, their Oracle software CIs, and the downstream 'Depends on::Used by' path to a Business Service in one query, then save it as a reporting source. This avoids scripting and satisfies the complex multi-class criteria natively.

Why this answer

CMDB Query Builder allows administrators to define multi-class, relationship-aware queries across multiple tables and export or report on the resulting dataset.

Full explanation →
81
MCQhard

An organization notices that custom application CIs are failing compliance checks because the governance policy checks standard fields that do not apply to custom apps. How should an administrator resolve this while maintaining governance standards?

A.Disable CMDB Data Governance globally
B.Create a class-specific governance policy targeting the custom application table
C.Add mandatory fields to the base configuration item table (cmdb_ci)
D.Ignore the failed tasks permanently
AnswerB

A class-specific governance policy applies audit criteria only to the custom application table, so standard fields irrelevant to custom apps are no longer enforced while governance remains intact for other classes. This resolves the failures without weakening overall standards.

Why this answer

ServiceNow CMDB Data Governance policies are applied per CI class, so the correct fix is to create a class-specific governance policy that targets the custom application table (a child of cmdb_ci_appl) and defines only the fields relevant to that class. This preserves governance for standard CIs while allowing custom apps to be evaluated against appropriate rules. It maintains compliance standards rather than bypassing them.

Exam trap

The trap is assuming governance is global and all-or-nothing — candidates pick 'disable globally' or 'add fields to base table' instead of recognizing that governance policies are class-scoped and should be tailored per CI class.

How to eliminate wrong answers

Option A is wrong because disabling CMDB Data Governance globally removes all compliance enforcement across every CI class, which destroys governance rather than fixing the custom-app mismatch. Option C is wrong because adding mandatory fields to the base cmdb_ci table would force those fields onto every CI class, causing widespread false failures and polluting the base schema. Option D is wrong because permanently ignoring failed tasks suppresses the symptom without resolving the policy mismatch, leaving the CMDB non-compliant and unauditable.

Full explanation →
82
MCQhard

An organization wants to configure CMDB Data Governance remediation tasks so that when a completeness policy fails for a high-priority server, a task is automatically assigned to the data owner. Where are these remediation workflows and task generation parameters configured?

A.CMDB Health > Dashboard Settings
B.Data Certification > Definitions
C.CMDB Data Governance > Policies
D.System Policy > Rules > Data Policy
AnswerC

Remediation workflows and task generation parameters are defined within CMDB Data Governance policies. Each policy specifies the task assignment and scheduling behaviour triggered on failure, so configuring the completeness policy there produces the automatic task for the data owner.

Why this answer

CMDB Data Governance > Policies is where administrators define the health policies (completeness, correctness, compliance, duplicates) and configure the remediation workflow, task assignment rules, and task generation parameters such as the assignee (data owner), priority, and due date. The policy record itself contains the 'Remediation' related list and task generation settings that drive automatic task creation when a high-priority server fails the completeness check.

Exam trap

CIS-DF often tests the confusion between CMDB Health dashboard configuration (display only) and CMDB Data Governance policies (which actually generate remediation tasks), so candidates who pick the dashboard option miss the task-generation capability.

How to eliminate wrong answers

Option A is wrong because CMDB Health > Dashboard Settings only controls which health KPIs and scores are displayed on the CMDB Health dashboard — it does not create remediation tasks or assign them. Option B is wrong because Data Certification > Definitions is used to schedule certification campaigns where CI owners attest to the accuracy of their CIs, not to auto-generate remediation tasks from health policy failures. Option D is wrong because System Policy > Rules > Data Policy governs field-level data policy rules (mandatory/read-only fields) at the platform level, not CMDB health remediation workflows.

Full explanation →
83
MCQeasy

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

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

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

Why this answer

The CMDB Health Dashboard, accessed via Configuration > CMDB Health Dashboard, is the dedicated ServiceNow interface that aggregates CMDB data quality metrics across the three core pillars: completeness, correctness, and compliance (plus relationship health and duplicate metrics). It provides KPI scores, drill-downs to failing CIs, and trend visualization specifically for CMDB health.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
84
Multi-Selectmedium

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

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

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

Why this answer

Option B is correct because CI relationships in ServiceNow are directional, defined with a parent-child structure (for example, a server 'Contains' an application, or a database 'Depends on' a server), where the relationship type specifies the direction and nature of the link. Option E is correct because all CI-to-CI relationships are stored as records in the cmdb_rel_ci table, which holds the parent, child, and relationship type fields that define each connection. Option A is incorrect because creating a relationship does not delete CIs; relationships are independent records that can be created or removed without affecting the existence of the CIs themselves.

Option C is incorrect because a CI can participate in many relationships simultaneously (for example, a server can contain multiple applications and depend on multiple databases). Option D is incorrect because relationships are stored in the cmdb_rel_ci table as separate records linking two CIs, whereas reference fields such as 'Assigned to' are simple field references on a single record and do not create CI-to-CI relationship records.

Exam trap

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

Full explanation →
85
MCQhard

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

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

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

Why this answer

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

Full explanation →
86
MCQmedium

An administrator needs to create a CMDB Query Builder definition to locate all Windows Servers that host a specific Business Application and have an open critical Incident. What capability does Query Builder provide to achieve this?

A.Real-time execution of automated remediation workflows on matching CIs
B.Visual graphical querying across multiple related CMDB tables and operational tables
C.Automatic conversion of query results into scheduled Discovery jobs
D.Enforcement of CI write-access restrictions during query execution
AnswerB

Visual graphical querying joins related CMDB tables with operational tables, letting you traverse the Business Application relationship to Windows Servers and correlate open critical Incidents in one definition. This satisfies the stem's requirement to combine configuration relationships with live incident data, which single-table filters cannot achieve.

Why this answer

Query Builder allows users to construct visual multi-table graph queries across the CMDB and related operational tables (such as Incidents) without writing complex SQL or scripted GlideRecord queries.

Full explanation →
87
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
88
MCQhard

An organization implements CSDM and wants to ingest business applications and their hosting environments. They receive a payload containing a Business Application CI that references a non-existent Application Service CI. How does the IRE handle references to related CIs that do not yet exist in the CMDB?

A.References to non-existent CIs are automatically converted into Incident records in IT Service Management.
B.The IRE automatically creates dummy placeholder records for any unresolving reference.
C.The entire payload is always aborted if any single related reference cannot be resolved immediately.
D.If the payload includes nested identification blocks for the related CI, the IRE will create the missing CI first and then establish the relationship.
AnswerD

When the payload includes the related Application Service as its own item with identifying attributes, the IRE can resolve it, creating it if it does not exist, and then create the relationship to the Business Application. This dependency handling lets one payload describe both CIs and their relationship. Without identifying data for the related CI, the IRE has nothing to match or create, and the relationship is reported as unresolved.

Why this answer

The IRE can handle references to non-existent CIs if the payload includes nested identification blocks for those related CIs. In that case, the IRE will create the missing CI first (using the nested identification block) and then establish the relationship. This allows for the ingestion of complex CI hierarchies in a single payload.

Exam trap

CIS-DF often tests the IRE's handling of missing references: candidates may think the IRE always creates placeholders or aborts, but it actually creates missing CIs only if nested identification blocks are provided.

How to eliminate wrong answers

Option A is wrong because references to non-existent CIs are not converted into Incident records; the IRE either creates the CI or rejects the payload, but it does not create Incidents. Option B is wrong because the IRE does not automatically create dummy placeholder records; it only creates CIs if proper identification information is provided. Option C is wrong because the entire payload is not always aborted; if nested identification blocks are present, the IRE can create the missing CIs and proceed.

Full explanation →
89
Multi-Selectmedium

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

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

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

Why this answer

CMDB Query Builder (C) is correct because it lets you build and run queries across CMDB classes and their relationships, then visualize the resulting CI relationship graph, making it a primary tool for investigating how configuration items connect. Dependency Views (E) is correct because it renders an interactive map of a CI and its upstream/downstream dependencies based on CMDB relationship data, which is exactly the visualization of CI relationships the question asks for. CI Class Manager (A) is for administering the class hierarchy, identifiers, and reconciliation rules of CI classes, not for querying or visualizing relationships between existing CIs.

Discovery Schedule configuration (B) only defines when and what Discovery scans, so it creates/updates CIs but does not investigate or visualize their relationships. System Definition > Tables (D) is a low-level schema administration area for viewing table definitions and fields, not a relationship investigation or visualization feature.

Full explanation →
90
MCQhard

Your team is troubleshooting a business service mapping issue where incident impact analysis fails to show downstream application outages. Upon reviewing the CMDB, you discover that the Application Service was created as a 'Manual' type, but its supporting infrastructure CIs were deleted during a data purge. What is the recommended way to restore the mapping?

A.Run a quick discovery scan to automatically regenerate the manual application service relationships.
B.Convert the manual Application Service into a Business Application record.
C.Re-establish the infrastructure CIs and manually re-add them to the Application Service via the Application Service Workbench.
D.Delete the Business Application and recreate it as a Technical Service.
AnswerC

Because the Application Service is Manual type, the engine will not auto-discover members, so infrastructure CIs must be recreated and manually re-added through the Application Service Workbench. This restores the downstream mapping impact analysis depends on.

Why this answer

Manual Application Services do not auto-populate relationships from discovery; their CIs must be added by hand. Once the supporting infrastructure CIs are restored in the CMDB, the correct remediation is to re-add them to the Application Service through the Application Service Workbench, which is the supported UI for managing manual service mappings. This restores the downstream dependency chain so incident impact analysis can traverse it again.

Exam trap

The trap here is assuming discovery can 'fix' any broken service mapping — candidates forget that Manual Application Services are explicitly excluded from automatic discovery-driven relationship generation.

How to eliminate wrong answers

Option A is wrong because discovery cannot regenerate relationships for a Manual Application Service — manual services are explicitly excluded from automatic mapping and require human-defined CIs. Option B is wrong because converting the record type to Business Application does not restore the deleted infrastructure CIs or their relationships, and Business Applications are populated by Service Mapping, not manual entry. Option D is wrong because deleting and recreating as a Technical Service changes the semantic layer entirely and still leaves the infrastructure CIs missing, so impact analysis would remain broken.

Full explanation →
91
MCQmedium

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

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

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

Why this answer

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

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

Exam trap

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

Full explanation →
92
MCQeasy

An administrator needs to track overall CMDB data quality using standardized metrics out of the box. Which specific dashboard should they access in ServiceNow to view scores for Completeness, Correctness, Compliance, and Freshness?

A.CSDM Framework Dashboard
B.CMDB Health Dashboard
C.Data Certification Dashboard
D.CI Class Manager Dashboard
AnswerB

The CMDB Health Dashboard provides out-of-the-box scores for Completeness, Correctness, Compliance, and Freshness, exactly the four standardised metrics the administrator must track. It aggregates these across the CMDB without custom reporting, satisfying the requirement for overall data quality visibility using standardised metrics.

Why this answer

The CMDB Health Dashboard provides out-of-the-box scores for Completeness, Correctness, Compliance, and Freshness to help administrators measure data quality.

Full explanation →
93
MCQhard

An organization ingests data from two different cloud providers into the CMDB. Provider A populates virtual machines with a serial number, while Provider B populates virtual machines with a BIOS UUID but no serial number. Both providers use the same identification rule which requires serial number. Consequently, Provider B records fail identification and create duplicates. How should the identification rules be configured to correctly handle both providers?

A.Disable identification rules and rely on legacy transform map coalescing.
B.Create a Business Rule to copy the BIOS UUID into the serial number field before ingestion.
C.Combine serial number and BIOS UUID into a single compound identification rule entry with an AND operator.
D.Configure multiple identification rule entries in CI Class Manager: Entry 1 using serial number, and Entry 2 using BIOS UUID.
AnswerD

Multiple identification rule entries are evaluated in order, so Entry 1 matches Provider A on serial number while Entry 2 falls back to BIOS UUID for Provider B. This satisfies both providers' differing unique identifiers, preventing failed identification and duplicate CIs.

Why this answer

The correct approach is to configure multiple identification rule entries in CI Class Manager, each with a different identifier attribute (serial number for Provider A, BIOS UUID for Provider B). The IRE evaluates entries in order and uses the first one that matches, so Provider B records will be identified by BIOS UUID even if serial number is missing. This ensures both providers' data are correctly identified without creating duplicates.

Exam trap

CIS-DF often tests the misconception that a single identification rule entry must contain all possible identifiers; candidates may think combining with AND is correct, but the IRE evaluates entries independently, so multiple entries are needed for alternative identifiers.

How to eliminate wrong answers

Option A is wrong because disabling identification rules and relying on transform map coalescing bypasses the IRE, which is the modern and recommended method for CI identification; it can lead to inconsistent identification and does not leverage the full capabilities of the CMDB. Option B is wrong because using a Business Rule to copy BIOS UUID into the serial number field is a data manipulation hack that pollutes the serial number field with non-serial data, causing data quality issues and potential conflicts if a real serial number appears later. Option C is wrong because combining serial number and BIOS UUID with an AND operator would require both attributes to be present and match, which would fail for Provider B (no serial number) and Provider A (no BIOS UUID), resulting in no identification at all.

Full explanation →
94
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
95
Multi-Selectmedium

Which THREE features are provided natively by the CMDB Query Builder tool? (Choose three.)

Select 3 answers
A.Real-time generation of automated remediation workflows
B.Direct packet capture analysis for discovered network switches
C.Exporting query results to JSON or CSV formats
D.Ability to filter nodes based on specific CI attributes and related task states
E.Visual construction of multi-class relationship queries
AnswersC, D, E

CMDB Query Builder natively exports results to JSON or CSV, satisfying the requirement for built-in data extraction without external tooling. This export capability lets administrators pull query output directly into reporting or integration pipelines, confirming it as one of the three native features the question demands.

Why this answer

Option C is correct because the CMDB Query Builder natively supports exporting query results to JSON or CSV formats, allowing administrators to extract and share CMDB data for reporting or external processing. Option D is correct because the tool lets users filter nodes by specific CI attributes and by related task states, enabling targeted queries that combine configuration item data with workflow/task context. Option E is correct because CMDB Query Builder provides a visual, drag-and-drop interface for constructing multi-class relationship queries, so users can traverse relationships across multiple CI classes without writing SQL.

Options A and B are not native features: the Query Builder is a querying and reporting tool and does not generate automated remediation workflows in real time, nor does it perform direct packet capture analysis for discovered network switches.

Full explanation →
96
Multi-Selecthard

An administrator is troubleshooting an integration that uses Robust Transform Engine (RTE) to ingest software licenses. During testing, records are inserted into staging tables, but the RTE fails to push them into the CMDB via the IRE. Which THREE areas should the administrator inspect to diagnose the failure? (Choose three.)

Select 3 answers
A.The Service Level Agreement (SLA) definition table for expired response times.
B.The UI Macro table for broken form decorators.
C.CMDB Integration Results / IRE Execution Logs to identify specific payload rejection reasons.
D.CI Class Manager to verify that valid identification rules exist for the target software license class.
E.RTE Field Mappings and Data Stream Definitions to verify that source fields are correctly mapped to target IRE payload attributes.
AnswersC, D, E

CMDB Integration Results and IRE execution logs record the precise payload rejection reasons when RTE output fails to reach the CMDB, satisfying the diagnostic requirement. They expose identification or reconciliation failures that staging table inspection alone cannot reveal.

Why this answer

Option C is correct because the CMDB Integration Results and IRE Execution Logs record the exact outcome of each IRE payload, including rejection reasons such as missing required attributes, duplicate detection, or identification failures, which is the fastest way to see why records are not being inserted into the CMDB. Option D is correct because the IRE requires valid identification rules for the target CI class; if the software license class lacks an active identification rule (or the rule is not published), the IRE cannot uniquely identify or create the CI and will reject the payload. Option E is correct because RTE relies on field mappings and data stream definitions to transform source staging fields into the IRE payload attributes; if a mandatory target attribute is unmapped or mapped incorrectly, the IRE payload will be incomplete and the insert will fail.

Option A is not relevant because SLA definitions govern task/response time tracking, not IRE payload processing or CMDB insertion. Option B is not relevant because UI Macros control form rendering and decorators, which have no bearing on RTE-to-IRE data flow or CMDB record creation.

Exam trap

CIS-DF often tests the tendency to overlook the IRE Execution Logs and instead focus on unrelated areas like SLAs or UI macros, or to forget that identification rules must exist for the target class.

Full explanation →
97
MCQmedium

An IT architect wants to map a Software-as-a-Service (SaaS) application (e.g., Workday) into the CSDM framework. Since there is no on-premise infrastructure to discover, how should Workday be modeled?

A.As a Technical Service with no portfolio parent.
B.As an unmapped Incident record.
C.As a Business Application record linked to an Application Service record representing the SaaS tenant, without requiring local infrastructure CIs.
D.As a Hardware Asset CI in the Foundation domain.
AnswerC

Modelling Workday as a Business Application linked to an Application Service representing the SaaS tenant captures the consumed service without fabricating infrastructure CIs. This satisfies the constraint that no on-premise infrastructure exists to discover, keeping the CSDM mapping accurate and complete.

Why this answer

A SaaS application like Workday has no on-premise infrastructure to discover, so CSDM models it as a Business Application (the logical application the business uses) linked to an Application Service that represents the SaaS tenant/instance. No local infrastructure CIs are required because the underlying infrastructure is owned by the SaaS provider and is out of scope for the CMDB. This is the standard CSDM pattern for SaaS in the Design domain.

Exam trap

The trap is assuming every application must have underlying infrastructure CIs — for SaaS, CSDM explicitly allows a Business Application + Application Service model with no local infrastructure CIs.

How to eliminate wrong answers

Option A is wrong because a Technical Service represents a technology-level service (e.g., database service) and is not the right abstraction for a business-facing SaaS application; also, having no portfolio parent breaks CSDM's requirement that services roll up to a business context. Option B is wrong because an unmapped Incident record is an operational artifact, not a CMDB model — it does not represent the application in CSDM at all. Option D is wrong because a Hardware Asset CI in the Foundation domain models physical hardware; a SaaS application has no hardware asset owned by the organization, so this is a category error.

Full explanation →
98
MCQmedium

An administrator is troubleshooting an issue where duplicate CIs are being created by an external data feed despite having an identification rule configured. Upon inspecting the payload, they notice the payload uses a custom identifier field not included in the IRE rule. What is the correct way to resolve this?

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

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

Why this answer

The correct fix is to update the identification rule in the CI Class Manager to include the custom identifier field as part of the identification criteria. The IRE uses identification rules to match incoming CIs to existing ones; if the payload's unique identifier isn't in the rule, IRE cannot match and creates duplicates. Adding the attribute ensures IRE recognizes the custom identifier and reconciles correctly.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
99
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
100
MCQhard

An organization uses ServiceNow Discovery to populate servers. They also have a security vulnerability scanner that ingests vulnerability records and associates them with CIs in the CMDB. The security tool frequently sends payloads containing stale IP addresses that match existing CIs incorrectly because the IP reuse policy in their network causes IP addresses to cycle rapidly. How can the administrator prevent the security tool from using IP address as an identification criterion while still allowing it to update vulnerability attributes?

A.Configure Data Source Precedence to block the security tool from updating IP addresses.
B.Write a Business Rule on cmdb_ci to delete IP records when IP churn occurs.
C.Review and refine the identification rules for the server class to remove volatile attributes like IP address, ensuring identification relies on stable unique keys like serial number or system ID.
D.Set the security tool's discovery source to 'Manual'.
AnswerC

Refining the server class identification rules to exclude volatile attributes such as IP address forces matching onto stable keys like serial number or system ID. The security tool can still update vulnerability attributes, but stale, rapidly recycled IPs can no longer cause incorrect CI matches.

Why this answer

The administrator should refine the identification rules for the server class to remove volatile attributes like IP address. By ensuring identification relies on stable unique keys such as serial number or system ID, the security tool can still update vulnerability attributes without incorrectly matching CIs based on IP.

Exam trap

CIS-DF often tests the misconception that Data Source Precedence can solve identification issues, but it only controls attribute-level updates, not CI matching.

How to eliminate wrong answers

Option A is wrong because Data Source Precedence controls which data source wins for specific attributes, but it does not prevent the security tool from using IP as an identification criterion; it only affects attribute updates. Option B is wrong because writing a Business Rule to delete IP records is a reactive and destructive approach that could cause data loss and does not address the root cause. Option D is wrong because setting the discovery source to 'Manual' would prevent the tool from updating CIs automatically, which is not desired.

Full explanation →
101
MCQeasy

An incident manager wants to see all upstream business services impacted by a failed network switch directly from the infrastructure alert. Where can they view this immediate impact path?

A.CMDB Baseline Diff Viewer
B.Event Management Alert Correlation Form
C.Dependency Views map on the switch CI record
D.CSDM Conceptual Diagram
AnswerC

The Dependency Views map on the switch CI record renders the CMDB relationship graph, showing upstream business services that depend on the failed switch. This gives the incident manager the immediate impact path directly from the infrastructure alert without manual correlation.

Why this answer

Dependency Views renders a graphical map of a CI and its upstream and downstream relationships directly from CMDB relationship data. Opening Dependency Views on the failed switch CI shows the business services and application services that depend on it, giving the incident manager an immediate impact path. This is the native, real-time way to trace impact from an infrastructure CI to business services.

Exam trap

CIS-DF often tests whether candidates know which tool provides live topology versus which provides historical comparison or alert grouping — the trap is selecting Baseline Diff or Alert Correlation when the question asks for an immediate impact path.

How to eliminate wrong answers

Option A is wrong because CMDB Baseline Diff Viewer compares snapshots of CI data over time to detect configuration drift — it does not display service impact paths. Option B is wrong because the Event Management Alert Correlation Form groups related alerts into a single actionable alert; it does not render the CI dependency topology. Option D is wrong because the CSDM Conceptual Diagram is a reference model illustrating CSDM domains and relationships, not a live map of a specific switch's upstream services.

Full explanation →
102
MCQmedium

A team needs to evaluate the overall health of their CSDM implementation by verifying if technical services are correctly linked to applications and infrastructure. Which built-in assessment tool provides this specific visibility?

A.Service Portfolio Workspace
B.CMDB Health Dashboard
C.Instance Security Center
D.CSDM Data Foundations Dashboard
AnswerD

The CSDM Data Foundations Dashboard assesses whether technical services are correctly linked to applications and infrastructure, exposing gaps in the Common Service Data Model. It provides the specific health visibility the team needs, unlike CMDB health dashboards that focus on data completeness rather than CSDM relationship integrity.

Why this answer

The CSDM Data Foundations Dashboard is a built-in assessment tool that provides visibility into the health of a CSDM implementation, including whether technical services are correctly linked to applications and infrastructure. It surfaces gaps, misalignments, and completeness metrics specific to the CSDM data model. This makes it the correct tool for evaluating overall CSDM health.

Exam trap

CIS-DF often tests the difference between the CMDB Health Dashboard (data quality) and the CSDM Data Foundations Dashboard (CSDM domain alignment) — candidates pick CMDB Health because it sounds broader, but the question specifically asks about CSDM linkage health.

How to eliminate wrong answers

Option A is wrong because the Service Portfolio Workspace is used for managing the service portfolio lifecycle, not for assessing CSDM data linkage health. Option B is wrong because the CMDB Health Dashboard focuses on CMDB data quality (completeness, correctness, compliance) but does not specifically assess CSDM domain alignment between technical services and applications/infrastructure. Option C is wrong because the Instance Security Center is a security hardening and compliance tool, unrelated to CSDM health assessment.

Full explanation →
103
MCQhard

An organization discovers network gear using both SNMP Discovery and an external cloud management platform API. Both integrations populate the same physical switch CIs. The cloud platform sometimes sends an empty string for the serial number, which accidentally clears out valid serial numbers previously populated by SNMP Discovery. How can this be prevented using CMDB ingestion controls?

A.Delete the identification rule for serial number.
B.Write an Inbound Email Action to reject empty payloads.
C.Set the serial number field dictionary attribute to 'read-only'.
D.Configure IRE payload settings or Data Source Precedence rules to ignore empty or null attribute updates from specific data sources.
AnswerD

Data Source Precedence and IRE payload settings let administrators suppress null or empty attribute values from a lower-trust source, preventing the cloud API from overwriting SNMP-populated serial numbers with blanks while still accepting genuine updates.

Why this answer

Configuring IRE payload settings or Data Source Precedence rules allows you to ignore empty or null attribute updates from specific data sources. This prevents the cloud platform's empty serial number from overwriting valid data from SNMP Discovery, as you can define that only non-empty values should be processed or that SNMP Discovery has higher precedence.

Exam trap

CIS-DF often tests IRE and Data Source Precedence; candidates may think making a field read-only solves the issue, but it blocks all updates, not just empty ones.

How to eliminate wrong answers

Option A is wrong because deleting the identification rule for serial number would break identification entirely, causing duplicates or failed CI creation. Option B is wrong because an Inbound Email Action is for processing incoming emails, not for controlling CMDB ingestion from APIs. Option C is wrong because setting the field to read-only would prevent all updates, including valid ones, and is not a granular control for specific data sources.

Full explanation →
104
MCQeasy

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

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

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

Why this answer

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

Full explanation →
105
MCQhard

An administrator is troubleshooting a custom integration where incoming JSON payloads for routers contain an array of interfaces. When the payload is processed, the parent router updates successfully, but none of the interface CIs are created. Reviewing the IRE payload structure shows that the interface objects are nested inside a property named `network_interfaces`. What must be configured in the IRE payload mapping to successfully process these child items?

A.Modify the Transform Map coalesce script to loop through the array.
B.Define a related items block in the payload structure mapping `network_interfaces` to the corresponding child class and relationship type.
C.Create a Business Rule to split the JSON array into individual rows on the import staging table.
D.Add 'network_interfaces' as a comma-separated string column in the base cmdb_ci table dictionary.
AnswerB

Nested child objects require a related items block in the payload structure mapping, which links the network_interfaces array to the child class and relationship type so the IRE creates interface CIs and their connections to the router.

Why this answer

In IRE payload mapping, nested arrays of child items must be defined in a related items block. This block maps the array property (e.g., `network_interfaces`) to the appropriate child class and relationship type, enabling IRE to create the child CIs and establish relationships with the parent router.

Exam trap

CIS-DF often tests IRE payload structure; candidates may try to use traditional transform maps or business rules, but IRE requires explicit related items blocks for nested arrays.

How to eliminate wrong answers

Option A is wrong because modifying the Transform Map coalesce script is not applicable when using IRE; IRE bypasses traditional transform maps for CI processing. Option C is wrong because creating a Business Rule to split the JSON array on the import staging table is unnecessary and would not integrate with IRE's payload structure. Option D is wrong because adding a column to the base cmdb_ci table dictionary is not how IRE handles nested arrays; it would not create child CIs.

Full explanation →
106
MCQeasy

An enterprise wants to establish clear data ownership and automate the lifecycle management tasks of archiving and retiring old hardware servers. Which native ServiceNow tool should be implemented to govern this process?

A.Service Graph Connector
B.CMDB Data Manager
C.Discovery Schedule
D.Identification and Reconciliation Engine (IRE)
AnswerB

CMDB Data Manager enforces ownership through CI class policies and automates lifecycle transitions, including archiving and retiring hardware CIs, directly satisfying the stem's requirement to govern ownership and automate archiving and retirement of old servers.

Why this answer

CMDB Data Manager is the native application designed to automate lifecycle operations such as backup, retire, delete, and attest for CIs based on policy rules.

Full explanation →
107
Multi-Selectmedium

Which TWO of the following tasks can be accomplished using the CMDB Data Manager? (Choose two.)

Select 2 answers
A.Scheduling automated archival of historical CIs
B.Creating automated policies to retire obsolete CIs
C.Visualizing service maps in Service Mapping
D.Configuring network IP discovery schedules
E.Defining CI identification and reconciliation rules
AnswersA, B

CMDB Data Manager provides lifecycle policies that automate archival of historical configuration items, satisfying the requirement to schedule archival without manual intervention. Policies define retention thresholds and target CI classes, then run on defined schedules to retire stale records, preserving database performance and accuracy.

Why this answer

CMDB Data Manager allows administrators to create policies for automating CI lifecycle states such as archival and retirement.

Full explanation →
108
MCQhard

An administrator is reviewing the Correctness score on the CMDB Health Dashboard and notices a low score caused by multiple CIs having no relationships to any business services. Which specific Correctness metric is flagging this issue?

A.Duplicate CIs
B.Orphans
C.Unassigned CIs
D.Stale CIs
AnswerB

Orphans are CIs lacking any relationship to a business service, so they directly reduce the Correctness score. This metric flags exactly the condition described, distinguishing it from duplicate or stale metrics that measure different correctness failures.

Why this answer

The Orphans metric under CMDB Health Correctness flags CIs that have no relationships to any business services or other CIs, indicating they are disconnected from the service model. A low Correctness score caused by CIs lacking business-service relationships is precisely what the Orphans KPI measures. This helps identify CIs that need to be related or retired.

Exam trap

CIS-DF often tests the specific definitions of Correctness KPIs, confusing candidates between Orphans (no relationships), Unassigned (no owner/group), Stale (no recent update), and Duplicate (multiple records).

How to eliminate wrong answers

Option A is wrong because Duplicate CIs measures CIs that appear more than once due to failed identification/reconciliation, not CIs lacking relationships. Option C is wrong because Unassigned CIs refers to CIs without an assigned support group or owner, not CIs missing business-service relationships. Option D is wrong because Stale CIs measures CIs that have not been updated or discovered within a threshold, which is a different correctness dimension than missing relationships.

Full explanation →
109
Multi-Selecthard

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

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

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

Why this answer

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

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

Exam trap

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

Full explanation →
110
MCQeasy

Which of the following domains is responsible for managing technical infrastructure, hardware, and software instances?

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

Correct. Manage Technical Services covers infrastructure and technical CIs.

Why this answer

The Manage Technical Services domain in the ServiceNow CIS-Data Foundation (CIS-DF) certification covers the operational management of technical infrastructure, including hardware, software instances, and configuration items (CIs). It focuses on the processes and tools used to monitor, maintain, and support the technical components that underpin IT services. This domain ensures that the technical foundation is effectively managed throughout its lifecycle, aligning with ITIL practices for technical service management.

Exam trap

CIS-DF often tests the distinction between the Design and Manage Technical Services domains, as candidates may confuse the planning of technical solutions with their operational management.

How to eliminate wrong answers

Option A is wrong because the Sell/Consume domain pertains to customer-facing activities such as sales, order management, and consumption of services, not the management of technical infrastructure. Option B is wrong because the Foundation domain deals with establishing the core data model and foundational data elements (e.g., CMDB, CSDM) rather than the ongoing management of technical services. Option C is wrong because the Design domain focuses on the planning and design of services and solutions, not their operational management.

Full explanation →
111
MCQmedium

An administrator needs to deprecate an old custom CI class that is no longer in use. What is the recommended best practice in the CI Class Manager?

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

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

Why this answer

The CI Class Manager provides a safe, guided way to deprecate or delete a custom CI class, including checks for dependent records, identification rules, and relationships before action is taken. Best practice is to use this tool to review dependencies and deprecate the class rather than deleting it outright, preserving data integrity and audit history.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
112
MCQhard

Your company acquires another firm and inherits two separate ServiceNow instances. You are consolidating them and need to merge overlapping Business Applications. When retiring a redundant Business Application record that has active Application Services attached to it, what must be done first according to CSDM data integrity standards?

A.Export all incident history to an external data lake and delete the CMDB table.
B.Convert the redundant Business Application into a Technical Service.
C.Delete all underlying infrastructure CIs associated with the application.
D.Reassign or re-map the active Application Services to the surviving Business Application record.
AnswerD

CSDM requires Application Services to reference a valid Business Application, so retiring the redundant record first would orphan them. Re-mapping the active Application Services to the surviving Business Application preserves the service hierarchy and referential integrity before the duplicate record is deleted.

Why this answer

According to CSDM data integrity standards, before retiring a Business Application that has active Application Services attached, you must reassign or re-map those Application Services to the surviving Business Application record. This preserves the service hierarchy and prevents orphaned Application Services that would break impact analysis and reporting.

Exam trap

The trap is thinking you can simply delete or retire the redundant Business Application — candidates overlook that active Application Services must be re-mapped first to maintain CSDM referential integrity and avoid orphaned records.

How to eliminate wrong answers

Option A is wrong because exporting incident history and deleting the CMDB table is destructive and violates data retention and referential integrity — it does not address the Application Services. Option B is wrong because converting a Business Application into a Technical Service misrepresents the CSDM layer — Business Applications and Technical Services are distinct classes with different purposes. Option C is wrong because deleting underlying infrastructure CIs would destroy valid configuration data and break relationships, rather than resolving the Business Application retirement.

Full explanation →
113
MCQmedium

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

A.Service Portfolio [service_portfolio] directly.
B.Business Application [cmdb_ci_business_app] directly.
C.Foundation Company [core_company] directly.
D.Configuration Item [cmdb_ci] referencing an Application Service.
AnswerD

Application Services represent the CSDM service layer that incidents align to, so populating cmdb_ci with an Application Service reference ties the incident to the correct service offering rather than a raw infrastructure CI, satisfying the requirement for proper service alignment.

Why this answer

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

Exam trap

CIS-DF often tests the distinction between different CI types on the incident form. Candidates might choose Business Application because it sounds business-oriented, but the correct CI for service alignment is the Application Service, which is more granular and directly tied to the service.

How to eliminate wrong answers

Option A is wrong because Service Portfolio is not a CI and is not used on the incident form for service alignment; it is a higher-level categorization. Option B is wrong because Business Application is a CI, but it is not the most granular service-level CI for incident alignment; incidents should be tied to the specific Application Service that is impacted. Option C is wrong because Foundation Company is an organizational entity, not a service-related CI, and is not used for service alignment on incidents.

Full explanation →
114
MCQmedium

A company needs to store custom serial number attributes for specific physical storage devices. Where should an administrator add these custom attributes to ensure they are properly managed and tracked?

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

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

Why this answer

The CI Class Manager is the correct place to add custom attributes to a specific CI class. An administrator selects the target storage CI class (e.g., cmdb_ci_storage_device or a more specific subclass), navigates to the Attributes tab, and adds the new attribute there. This ensures the attribute is properly associated with the class, inheritable by subclasses, and managed within the CMDB schema.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
115
Multi-Selecthard

A CMDB administrator is configuring CMDB Data Governance policies to enforce data quality. The administrator wants to define actions that occur when a policy is violated. Which two actions can be configured in a CMDB Data Governance policy? (Choose two.)

Select 2 answers
A.Block the CI from being saved
B.Assign the CI to a different class
C.Create a remediation task
D.Send an email notification
E.Automatically delete the CI
AnswersC, D

CMDB Data Governance policies can be configured to create a remediation task when a violation occurs. This task is assigned to a responsible user or group to correct the data. This action helps ensure that data quality issues are addressed in a timely manner.

Why this answer

CMDB Data Governance policies support actions such as creating remediation tasks and sending email notifications. These actions help enforce data quality by alerting and assigning work to correct issues. Other actions like deleting, blocking saves, or reclassifying are not native to Data Governance policies.

Exam trap

The trap here is assuming that Data Governance policies can delete or reclassify CIs, but those are outside its scope; it focuses on remediation and notification.

Full explanation →
116
Multi-Selecthard

Which THREE of the following actions help ensure accurate relationship-based insights in the CMDB? (Choose three.)

Select 3 answers
A.Disabling all manual relationship creation across the entire instance
B.Configuring proper IRE identification rules for relationships to prevent duplicate links
C.Utilizing Discovery and Service Mapping to automatically populate runtime relationships
D.Setting CMDB Query Builder cache timeouts to zero
E.Monitoring and remediating orphan CIs using the CMDB Health Dashboard
AnswersB, C, E

IRE relationship identification rules define the matching attributes that decide whether an incoming relationship is new or already exists. Without them, Discovery creates duplicate links between the same CIs, corrupting dependency maps and any relationship-based insight the CMDB reports.

Why this answer

Option B is correct because the Identification and Reconciliation Engine (IRE) uses relationship identification rules to determine whether a relationship already exists, so properly configured rules prevent duplicate or conflicting links that would distort relationship-based insights. Option C is correct because Discovery and Service Mapping automatically populate runtime relationships (for example, Service Mapping builds application service dependencies and Discovery populates CI-to-CI connections), giving the CMDB accurate, current topology data instead of relying on manual entry. Option E is correct because the CMDB Health Dashboard surfaces orphan CIs (CIs with no relationships), and monitoring and remediating them restores the missing links that relationship-based analytics depend on.

Option A is not appropriate because disabling all manual relationship creation instance-wide removes a legitimate data source and does not by itself improve accuracy. Option D is not appropriate because setting CMDB Query Builder cache timeouts to zero only affects query caching performance, not the accuracy of stored relationships.

Full explanation →
117
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

Full explanation →
118
MCQhard

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
119
MCQeasy

A CMDB manager wants to review the overall health of the CMDB across Completeness, Correctness, and Compliance. Which ServiceNow module should they navigate to first?

A.Configuration > Data Governance > Dashboard
B.Configuration > CMDB Health > Dashboard
C.System Definition > CMDB Dashboard
D.Reports > View > CMDB Health
AnswerB

The CMDB Health Dashboard aggregates Completeness, Correctness and Compliance scores into one view, letting the manager assess overall health across all three pillars simultaneously. Navigating there first satisfies the stem's requirement to review the combined health state before drilling into individual metrics.

Why this answer

The CMDB Health Dashboard is the dedicated ServiceNow module that aggregates the three health pillars — Completeness, Correctness, and Compliance — into a single view with scores, KPIs, and drill-downs. It is accessed via Configuration > CMDB Health > Dashboard, which is the standard navigation path in the CMDB Health plugin (com.snc.cmdb.health). This module is purpose-built for the exact review the manager needs.

Exam trap

CIS-DF often tests whether candidates know the exact navigation path for CMDB Health, baiting them with plausible-sounding but non-existent menu items like 'Data Governance Dashboard' or 'System Definition > CMDB Dashboard'.

How to eliminate wrong answers

Option A is wrong because 'Configuration > Data Governance > Dashboard' is not a real ServiceNow navigation path — Data Governance is a concept, not a module with its own dashboard under Configuration. Option C is wrong because 'System Definition > CMDB Dashboard' does not exist; System Definition contains tables, business rules, and scheduled jobs, not CMDB health dashboards. Option D is wrong because 'Reports > View > CMDB Health' is not a valid navigation; CMDB Health is not surfaced as a report view but as a dedicated dashboard module.

Full explanation →
120
MCQmedium

When analyzing a service map in Service Mapping, an administrator wants to see live network connections and traffic flows captured between application nodes. Which feature provides this insight?

A.Dependency Views baseline diff
B.CMDB Query Builder topology export
C.Traffic Connections view
D.Discovery Schedule Log
AnswerC

The Traffic Connections view displays live network connections and traffic flows between application nodes, satisfying the requirement for real-time connection insight in the service map. Unlike static dependency views, it captures actual observed traffic, letting the administrator analyse active communication paths directly within Service Mapping.

Why this answer

The Traffic Connections view in Service Mapping displays live network connections and traffic flows between application nodes, providing visibility into actual communication paths. It is the specific feature designed to show real-time traffic data captured by Service Mapping. This makes it the correct answer for analyzing live network connections.

Exam trap

CIS-DF often tests the distinction between static dependency data (Dependency Views, CMDB Query Builder) and dynamic traffic data (Traffic Connections view) — candidates pick Dependency Views because it sounds related, but it does not show live traffic flows.

How to eliminate wrong answers

Option A is wrong because Dependency Views baseline diff compares current dependency relationships against a baseline snapshot, not live traffic flows. Option B is wrong because CMDB Query Builder topology export is used to query and export CMDB relationship data, not to display live network traffic. Option D is wrong because Discovery Schedule Log records the execution history of discovery schedules, not network traffic between application nodes.

Full explanation →
121
Multi-Selecthard

Which THREE of the following are core goals or benefits of implementing the CSDM framework?

Select 3 answers
A.Automatically configuring network router firewall rules without admin approval.
B.Replacing the ServiceNow database with external spreadsheets.
C.Enabling accurate incident and change impact analysis via proper service mapping.
D.Providing a standard, product-agnostic data model for the CMDB.
E.Aligning business applications and capabilities with technical infrastructure.
AnswersC, D, E

CSDM's service mapping relationships let you trace which configuration items and services an incident or change affects, producing accurate impact analysis. Without that mapping, impact assessment relies on guesswork, so this capability directly fulfils the framework's goal of reliable incident and change impact determination.

Why this answer

Option C is correct because the CSDM (Common Service Data Model) establishes consistent relationships between services, applications, and infrastructure, which enables accurate impact analysis for incidents and changes through proper service mapping. Option D is correct because CSDM provides a standard, product-agnostic data model that normalizes how configuration items and services are represented in the CMDB, independent of any specific vendor product. Option E is correct because CSDM aligns business applications and business capabilities with the underlying technical infrastructure, creating traceability from business value down to technical components.

Option A is incorrect because CSDM is a data modeling framework, not an automation tool for configuring network firewall rules, and it does not bypass administrative approval processes. Option B is incorrect because CSDM strengthens the ServiceNow CMDB as the system of record; it does not replace the database with external spreadsheets, which would contradict its purpose of a unified, governed data model.

Exam trap

CIS-DF often tests the understanding of CSDM goals versus unrelated IT tasks. Candidates might be distracted by options that sound like automation or data management, but the core goals are specifically about service mapping, standard data model, and business-IT alignment.

Full explanation →
122
MCQhard

A CMDB administrator is using the CMDB Health Dashboard to analyze the Compliance KPI. The administrator notices that many CIs are failing compliance due to missing required relationships, such as a Server not being related to an Application Service. Which CMDB feature should the administrator use to define and enforce these required relationships?

A.CMDB Health Dashboard's Compliance KPI configuration
B.CMDB Data Manager to create a relationship policy
C.CMDB Query Builder to identify missing relationships
D.Service Mapping to automatically create relationships
AnswerA

The Compliance KPI configuration allows administrators to define required relationships and attributes for CI classes. By setting up compliance rules, the administrator can specify that a Server must be related to an Application Service, and the KPI will flag violations. This directly addresses the need to enforce required relationships.

Why this answer

The Compliance KPI in the CMDB Health Dashboard is configured with rules that define required relationships and attributes. By setting up compliance rules, the administrator can enforce that a Server must be related to an Application Service. The KPI will then flag CIs that violate these rules, enabling remediation.

Other tools like Query Builder or Service Mapping do not provide this policy enforcement.

Exam trap

The trap here is assuming that CMDB Query Builder or Service Mapping can enforce compliance, when in fact only the Compliance KPI configuration defines required relationships.

Full explanation →
123
Multi-Selecthard

Which THREE of the following are primary components evaluated under the CMDB Health Dashboard framework? (Choose three.)

Select 3 answers
A.Security
B.Performance
C.Correctness
D.Completeness
E.Compliance
AnswersC, D, E

Correctness is one of the three primary CMDB Health Dashboard components, alongside completeness and compliance. It measures the accuracy of configuration item attributes against expected values, satisfying the stem's requirement to identify components evaluated under the health framework rather than related metrics such as duplicate or orphan CIs.

Why this answer

The CMDB Health framework evaluates Completeness, Correctness, and Compliance.

Full explanation →
124
MCQeasy

What is the primary role of a 'Data Owner' in the context of ServiceNow CMDB governance?

A.Accountability for the accuracy, completeness, and quality of data within their assigned CI domain
B.Approving financial balance sheets for the enterprise
C.Configuring network switch routing tables
D.Writing custom Java code for MID server extensions
AnswerA

The Data Owner holds accountability for accuracy, completeness and quality of CIs within their assigned domain, approving governance decisions rather than performing daily data entry. This satisfies the stem's governance-role requirement by placing ownership at the domain level.

Why this answer

A Data Owner in ServiceNow CMDB governance is accountable for the accuracy, completeness, and quality of data within their assigned CI domain. They are responsible for validating CIs, approving remediation, and ensuring data meets governance standards. This role is central to the CMDB data governance framework.

Exam trap

CIS-DF often tests governance role definitions, baiting candidates with unrelated responsibilities like financial approvals or network configuration that do not belong to a Data Owner.

How to eliminate wrong answers

Option B is wrong because approving financial balance sheets is a finance function, not a CMDB data governance responsibility. Option C is wrong because configuring network switch routing tables is a network engineering task, not a data ownership role. Option D is wrong because writing custom Java code for MID server extensions is a development task, unrelated to data ownership and governance.

Full explanation →
125
MCQhard

Your company is preparing for an IT audit and needs to demonstrate which user groups are responsible for supporting specific Application Services. Where should the support group be specified on the Application Service record according to CSDM guidelines?

A.Assignment group field on all incoming Incident records automatically.
B.Managed by group field on the underlying Linux server CIs.
C.Support group field on the Application Service record.
D.Assigned group field on the parent Business Application record.
AnswerC

CSDM places accountability on the Application Service record itself via its support group field, which references a group in sys_user_group. This satisfies the audit requirement by tying each Application Service directly to its responsible support team.

Why this answer

Per CSDM guidelines, the Application Service record itself carries a 'Support group' field that identifies the group accountable for supporting that service. This is the authoritative location auditors will check to map responsibility for each Application Service. Placing it directly on the service record keeps ownership explicit and reportable without relying on downstream CI inheritance.

Exam trap

CIS-DF often tests the distinction between CI-level ownership fields (managed by, owned by) and the Application Service-level 'Support group' field, so candidates who default to infrastructure CI fields pick the wrong answer.

How to eliminate wrong answers

Option A is wrong because assignment groups on Incident records are transactional and vary per ticket; they do not define the accountable support group for a service. Option B is wrong because 'Managed by group' on a Linux server CI describes infrastructure ownership, not Application Service support responsibility, and CSDM separates these concerns. Option D is wrong because the Business Application record's 'Assigned group' does not represent the support group for the underlying Application Service; CSDM places support ownership at the Application Service layer.

Full explanation →
126
MCQeasy

When reviewing CI records ingested into the CMDB, an administrator notices a field labeled 'First discovered' and another labeled 'Last discovered'. Which component populates these lifecycle tracking fields automatically?

A.Standard Transform Map execution engine
B.The Identification and Reconciliation Engine (IRE) and Discovery logging mechanisms
C.CMDB Health Dashboard audit jobs
D.Data Policies on the cmdb_ci table
AnswerB

The IRE stamps first and last discovered values when it processes and reconciles incoming payloads, while Discovery logging records each discovery run. Together these mechanisms populate the lifecycle tracking fields automatically, reflecting when a CI was initially identified and most recently seen.

Why this answer

Discovery and the IRE automatically maintain discovery audit metadata, such as first and last discovered timestamps.

Full explanation →
127
Multi-Selectmedium

An enterprise is planning a data ingestion strategy for their CSDM implementation. Which TWO principles should guide their approach to data ingestion and the CMDB? (Choose two.)

Select 2 answers
A.Disable identification rules on all base classes to allow any data source to create records freely.
B.Always route automated integrations through the Identification and Reconciliation Engine (IRE) to maintain data hygiene.
C.Rely exclusively on manual spreadsheet imports performed weekly for all infrastructure CIs.
D.Establish clear data source ownership and precedence rules for critical CI attributes.
E.Use legacy transform maps with direct GlideRecord insertions for all server ingestion to maximize performance.
AnswersB, D

Routing automated integrations through the Identification and Reconciliation Engine ensures incoming records are identified against existing CIs and reconciled using class rules, preserving data hygiene. This prevents duplicate CIs and enforces consistent identification across all automated ingestion sources.

Why this answer

Option B is correct because the Identification and Reconciliation Engine (IRE) is the ServiceNow mechanism that applies identification rules, reconciliation rules, and data source precedence to deduplicate and govern CI data as it is ingested, which is essential for maintaining CMDB data hygiene in a CSDM implementation. Option D is correct because clear data source ownership and precedence rules ensure that when multiple sources (e.g., discovery, imports, integrations) supply the same CI attribute, the authoritative value is deterministically chosen, which is a core CSDM data governance principle. Option A is incorrect because disabling identification rules on base classes would allow duplicate and conflicting records to proliferate, directly undermining CMDB integrity.

Option C is incorrect because relying exclusively on weekly manual spreadsheet imports is neither scalable nor timely for enterprise infrastructure CIs and violates CSDM guidance favoring automated, near-real-time ingestion. Option E is incorrect because bypassing IRE with legacy transform maps and direct GlideRecord insertions skips identification and reconciliation, producing duplicates and inconsistent data despite any perceived performance gain.

Full explanation →
128
MCQmedium

An enterprise wants to ensure that change requests correctly assess risk by identifying which Application Services will experience downtime during a server patch. Which CSDM relationship makes this impact calculation possible?

A.The relationship between the Server CI and the Application Service ('Depends on / Used by').
B.The link between Foundation companies and Locations.
C.The assignment group field on the Incident table.
D.The direct mapping between User Groups and Business Capabilities.
AnswerA

The 'Depends on / Used by' relationship links a Server CI to the Application Services relying on it, letting change risk assessment traverse that dependency and enumerate affected services. This satisfies the stem's requirement to identify which Application Services suffer downtime during patching.

Why this answer

The 'Depends on / Used by' relationship between a Server CI and an Application Service is what allows ServiceNow to calculate which Application Services will be impacted when the server is patched. This relationship is part of the CSDM service modeling layer and is used by Change Management's impact analysis and the Service Mapping/CSDM dependency views. Without this relationship, the change request cannot determine downstream service impact.

Exam trap

CIS-DF often tests whether candidates understand that impact analysis depends on CMDB relationship types (Depends on/Used by), not on organizational fields like assignment group or company-location links.

How to eliminate wrong answers

Option B is wrong because the link between Foundation companies and Locations is an organizational/location hierarchy relationship and has no bearing on service impact calculation. Option C is wrong because the assignment group field on the Incident table is a routing attribute, not a CMDB relationship, and does not model service dependencies. Option D is wrong because mapping User Groups to Business Capabilities is not a CSDM relationship used for impact analysis — Business Capabilities are mapped to Business Applications, not directly to User Groups for downtime impact.

Full explanation →
129
MCQeasy

A CSDM implementation team is defining the foundational elements of the framework. They need to identify which domain is responsible for representing the logical design of business applications and application services, including their relationships and dependencies. Which CSDM domain fulfills this purpose?

A.Design domain
B.Service Delivery domain
C.Service Consumption domain
D.Service Management domain
AnswerA

The Design domain in CSDM is specifically intended for modeling the logical design of services and applications. It includes business applications, application services, and their relationships. This domain captures how services are architected and how they depend on each other, providing the blueprint for service delivery and management. It is the correct choice for representing logical design elements.

Why this answer

The CSDM Design domain is dedicated to the logical design of services and applications. It includes entities such as business applications, application services, and their relationships, which are essential for understanding how services are structured and how they depend on one another. This domain provides the architectural blueprint that informs other domains, making it the correct choice for representing logical design.

Exam trap

The trap here is mixing up the Design domain with the Service Management domain, which handles physical and technical CIs rather than logical design.

Full explanation →
130
Multi-Selectmedium

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

Select 2 answers
A.Using the Identification and Reconciliation Engine for all automated imports.
B.Ingesting data exclusively through certified Service Graph Connectors.
C.Configuring robust Data Source Precedence rules for all attributes.
D.Failing to run Discovery or integration updates regularly against active infrastructure.
E.Leaving decommissioned CIs in the CMDB without updating their operational status or removing them when source integrations cease.
AnswersD, E

Infrequent Discovery or integration runs leave CI records unrefreshed, so last_scan and updated timestamps age beyond the staleness threshold defined in CMDB Health. The stem's high staleness scores across active server classes directly reflect this gap, since active infrastructure keeps changing while the CMDB remains static.

Why this answer

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

Exam trap

CIS-DF often tests CMDB health contributors — candidates pick best practices (IRE, Service Graph Connectors, Data Source Precedence) as causes of staleness, reversing the logic that these practices actually reduce staleness.

Full explanation →
131
MCQeasy

What does a green health score indicator represent on the CMDB Health Dashboard?

A.The CI is currently part of an active Service Map.
B.The CI has active Discovery credentials.
C.The metric meets or exceeds the defined target threshold for data quality.
D.No changes have been made to the CI in 365 days.
AnswerC

The green indicator means the measured metric satisfies or surpasses the target threshold configured for that CMDB data-quality metric, confirming acceptable health. Amber and red denote approaching or breaching thresholds respectively, so green specifically signals the target is met or exceeded.

Why this answer

A green indicator on the CMDB Health Dashboard signifies that the compliance, completeness, or correctness metric meets or exceeds the defined target threshold.

Full explanation →
132
MCQmedium

An administrator needs to configure a Data Certification schedule to ensure that Application owners review their respective records quarterly. Which module is used to set up these recurring certification campaigns?

A.Configuration > Governance > Audits
B.CMDB Health > Certification Rules
C.Data Certification > Certification Definitions
D.Service Level Management > Certification
AnswerC

Certification Definitions holds the schedule, filter and scope that generate recurring certification tasks. Configuring it here satisfies the quarterly requirement, because the definition drives task creation for Application owners at the specified interval, unlike the Certification Tasks module, which only shows generated instances.

Why this answer

Data Certification campaigns are configured through the Data Certification module, where administrators create Certification Definitions that specify the target table, filter conditions, certification schedule (e.g., quarterly), and the certifier assignment (such as CI owner or application owner). The Certification Definition is the reusable template that drives each recurring campaign, so it is the correct place to set up quarterly reviews of Application owner records.

Exam trap

CIS-DF often tests the distinction between configuring certification definitions versus reviewing certification tasks, causing candidates to select audit or CMDB Health options that sound governance-related but do not schedule campaigns.

How to eliminate wrong answers

Option A is wrong because Configuration > Governance > Audits is used for audit records and attestation tracking, not for defining recurring certification campaigns. Option B is wrong because CMDB Health > Certification Rules does not exist as a certification scheduling module; CMDB Health focuses on completeness, correctness, and compliance metrics. Option D is wrong because Service Level Management deals with SLAs and OLAs, not data certification scheduling.

Full explanation →
133
Multi-Selecthard

When planning a CMDB Governance strategy, which THREE key stakeholder groups should be actively involved in defining data ownership and data quality rules? (Choose three.)

Select 3 answers
A.CMDB / Platform Administrators
B.Compliance and Audit Officers
C.End-users submitting self-service catalog requests
D.Data Owners / CI Stewards
E.External third-party hardware component manufacturers
AnswersA, B, D

CMDB and platform administrators hold technical ownership of the CMDB schema, identification rules and data ingestion pipelines, so they must define enforceable data quality rules and assign CI ownership consistent with platform capabilities and constraints.

Why this answer

Option A (CMDB / Platform Administrators) is correct because these administrators own the technical implementation of the CMDB, including the CI class model, attribute definitions, reconciliation and normalization rules, and health dashboards, so they must help define enforceable data quality rules and ownership workflows. Option B (Compliance and Audit Officers) is correct because they translate regulatory and internal control requirements (e.g., SOX, ISO 27001, ITIL audit criteria) into data retention, accuracy, and evidence standards that the governance strategy must satisfy. Option D (Data Owners / CI Stewards) is correct because they are accountable for the accuracy, completeness, and lifecycle of specific CI classes and attributes, making them the primary parties who assign ownership and approve data quality thresholds.

Option C is not correct because end-users submitting self-service catalog requests are consumers of CMDB data, not stakeholders responsible for defining ownership or quality rules. Option E is not correct because external hardware manufacturers supply component data but have no governance authority over the organization's CMDB data ownership or quality standards.

Full explanation →
134
Multi-Selecthard

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

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

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

Why this answer

Option B (Suggested Relationships configurations) is correct because Suggested Relationships define the allowed parent-child relationship types between CI classes, enforcing valid cardinality and preventing invalid relationship types from being created in the CMDB. Option C (IRE relationship processing during payload ingestion) is correct because the Identification and Reconciliation Engine applies relationship rules and dependent/containment logic during ingestion, ensuring relationships are correctly matched, deduplicated, and reconciled rather than duplicated or orphaned. Option D (Orphan and Stale audits in CMDB Health Correctness) is correct because these CMDB Health Correctness KPIs detect CIs with missing required relationships (orphans) and outdated relationships (stale), surfacing integrity problems so they can be remediated.

Option A is wrong because disabling index generation on cmdb_rel_ci degrades query performance and does not improve relationship health. Option E is wrong because direct SQL updates on cmdb_rel_ci bypass IRE, business rules, and audit logic, risking data corruption and unsupported configurations.

Exam trap

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

Full explanation →
135
Multi-Selectmedium

Which TWO configurations can be adjusted within CMDB Health Dashboard metric settings? (Choose two.)

Select 2 answers
A.Adjusting metric weightings to influence overall health scoring
B.Configuring SMTP email server relay settings
C.Enabling or disabling specific metric evaluations (e.g., toggling Stale CIs on or off)
D.Defining firewall zone routing rules
E.Modifying underlying hardware CPU core clock speeds
AnswersA, C

Metric weightings are configurable within CMDB Health Dashboard metric settings, letting administrators control how much each metric contributes to the composite health score. Adjusting them aligns scoring with business priorities without altering the underlying metric definitions or evaluation logic.

Why this answer

Option A is correct because the CMDB Health Dashboard metric settings allow administrators to adjust metric weightings, which determine how much each health metric (such as completeness, correctness, or compliance) contributes to the overall CMDB health score. Option C is correct because these settings also let you enable or disable individual metric evaluations, for example toggling the Stale CIs metric on or off, so you can control which checks run and affect the dashboard results. Options B, D, and E are not part of CMDB Health Dashboard metric configuration: SMTP relay settings belong to email/notification configuration, firewall zone routing rules are network security settings, and CPU core clock speeds are hardware/firmware parameters, none of which are adjustable within the CMDB Health metric settings.

Exam trap

The trap here is selecting options that sound like general system configurations but are unrelated to CMDB Health; candidates might pick SMTP settings because they are configurable elsewhere, but the question specifically asks about CMDB Health Dashboard metric settings.

Full explanation →
136
MCQhard

While reviewing the CMDB Dashboard, an administrator notices a high number of duplicate CIs flagged under the Correctness score. What mechanism should be reviewed and tuned to prevent these duplicate records from being continuously created by incoming integrations?

A.Data Certification filter criteria
B.Identification and Reconciliation Engine (IRE) identification rules
C.CI class manager inheritance settings
D.Dependency Views layout engines
AnswerB

Tuning IRE identification rules directly addresses the duplicate CIs flagged under Correctness. These rules define the attribute combinations (such as serial number or MAC address) that IRE uses to match incoming integration payloads against existing records; weak or missing criteria cause each payload to be inserted as a new CI rather than merged.

Why this answer

Duplicate CIs are typically caused by misconfigured IRE (Identification and Reconciliation Engine) identification rules or payload processing failures.

Full explanation →
137
MCQhard

An administrator notices that when Discovery updates a virtual machine, the 'Environment' attribute populated by a manual spreadsheet import is overwritten, despite Data Source Precedence rules being configured. Upon investigation, they find that both sources are writing with the exact same discovery source string value. What is the correct way to resolve this conflict?

A.Enable 'Coalesce' on the spreadsheet import transform map.
B.Configure the manual import to use a distinct discovery source string (e.g., 'Manual Import' or 'Spreadsheet') rather than sharing the default discovery source string.
C.Modify the CI Class Manager identification rule to exclude the Environment attribute.
D.Set the table to read-only for the discovery integration user.
AnswerB

Data Source Precedence only arbitrates between different discovery source strings; identical strings are treated as the same source, so precedence cannot apply. Giving the manual import its own distinct string lets precedence rules correctly rank it against Discovery.

Why this answer

Data Source Precedence rules rely on the discovery source string to differentiate sources. If both the manual import and Discovery use the same discovery source string, the system cannot distinguish between them, so precedence rules won't apply correctly. Assigning a distinct discovery source string to the manual import allows precedence rules to work as intended.

Exam trap

CIS-DF often tests Data Source Precedence; candidates may overlook that the discovery source string must be unique for precedence to work, leading to conflicts.

How to eliminate wrong answers

Option A is wrong because enabling 'Coalesce' on the transform map affects how records are merged during import, but does not address the conflict with Discovery's updates or the discovery source string issue. Option C is wrong because modifying the identification rule to exclude the Environment attribute would prevent the attribute from being used for identification, but does not resolve the overwrite conflict. Option D is wrong because setting the table to read-only for the discovery integration user would block all updates from that user, which is not the desired outcome and does not solve the precedence issue.

Full explanation →
138
MCQeasy

Where can an administrator view graphical relationship maps directly from an incident ticket to assess which business services might be affected by an attached configuration item?

A.CI Class Manager relationship tab
B.Dependency Views icon next to the Configuration Item field
C.Business Service Catalog
D.CMDB Data Manager policy list
AnswerB

The Dependency Views icon beside the Configuration Item field opens a graphical map showing the CI's upstream and downstream relationships, including business services. This satisfies the requirement to assess affected services directly from the incident ticket without leaving the record.

Why this answer

The CI field on an incident record includes a preview icon and link to open Dependency Views.

Full explanation →
139
MCQeasy

When reviewing the Identification and Reconciliation Engine (IRE) payload processing results, an administrator notices an error stating 'Mandatory attributes missing for identification'. What does this error signify?

A.The incoming payload lacks one or more attributes specified in the identification rule criteria for that class.
B.The Transform Map is missing mandatory field mappings.
C.The target CI table has mandatory dictionary fields that are not populated by the form layout.
D.The Discovery source name is invalid.
AnswerA

Identification rules define mandatory attributes per class; when an incoming payload omits any of those attributes, IRE cannot evaluate the rule and raises this error. The payload must be corrected or enriched before identification can proceed.

Why this answer

The error 'Mandatory attributes missing for identification' means the incoming payload does not contain one or more attributes that the identification rule for that CI class requires to match against existing records. Without those attributes, IRE cannot determine whether the CI already exists, so it rejects the identification attempt.

Exam trap

The trap is conflating IRE identification-rule requirements with table-level mandatory fields or transform map mappings — candidates must recognize the error is specifically about identification rule criteria.

How to eliminate wrong answers

Option B is wrong because Transform Map field mappings are a separate concern — they map source columns to target fields before IRE is invoked, and a missing mapping would produce a different error or empty values, not this specific IRE identification error. Option C is wrong because dictionary-level mandatory fields are enforced at the form/table layer, not by IRE's identification rules; the error is specifically about identification criteria. Option D is wrong because an invalid discovery source name would produce a source-related error, not a missing-attributes error.

Full explanation →
140
MCQhard

Your company uses Service Graph connectors and Discovery to populate CIs. A database administrator complains that their production database instance appears under multiple different Application Services in the CMDB. According to CSDM best practices, what does this multi-mapping indicate?

A.It is a critical CSDM violation; a database CI can never be associated with more than one Application Service.
B.It means the database must be converted into a Service Offering immediately.
C.It is a valid architectural scenario if the database is genuinely shared, but requires correct 'Depends on / Used by' relationships to each Application Service.
D.It indicates that Discovery has duplicated the database CI into the Business Application table.
AnswerC

CSDM permits a shared database to serve several Application Services, so multi-mapping is legitimate when the database genuinely underpins each one. Correct 'Depends on / Used by' relationships to every Application Service are required, otherwise the mapping reflects a data-quality defect.

Why this answer

In CSDM, a CI (like a database) can legitimately be shared by multiple Application Services when it genuinely serves more than one application. The correct modeling is to create 'Depends on::Used by' relationships from each Application Service to the shared database CI, which accurately reflects the many-to-many dependency without duplicating the CI. This is not a violation — it is a valid architectural pattern that CSDM explicitly supports through proper relationship modeling.

Exam trap

CIS-DF often tests the misconception that any CI appearing under multiple parents is a data quality violation, when in fact shared CIs with proper 'Depends on::Used by' relationships are a valid CSDM pattern.

How to eliminate wrong answers

Option A is wrong because CSDM does not prohibit a database CI from being associated with multiple Application Services; shared infrastructure is a common and valid pattern. Option B is wrong because a Service Offering represents a consumer-facing packaging of a service, not a remediation for shared CI relationships — converting a database to a Service Offering is a category error. Option D is wrong because Discovery does not duplicate CIs into the Business Application table; the Business Application table holds logical applications, not physical database instances, and multi-mapping is a relationship issue, not a duplication issue.

Full explanation →
141
MCQhard

An organization uses Service Mapping to map a critical e-commerce application. During mapping, a custom web server process is discovered on a host, but it fails to establish a relationship with the underlying software installation. Where should the administrator verify or configure the identification rules for process classification and mapping?

A.In Robust Transform Engine (RTE) definitions, map the process table to the software installation table.
B.In CI Class Manager, modify the Identification Rule for cmdb_ci_appl.
C.In Service Mapping Configuration, review and adjust Process Classifiers and Application Patterns.
D.In Data Source Precedence rules, set Discovery as the primary source for process tables.
AnswerC

Service Mapping Configuration holds the Process Classifiers and Application Patterns that govern how discovered processes are classified and related to software installations. Adjusting these rules lets the custom web server process be recognised and matched to its underlying installation, satisfying the requirement to establish the missing relationship.

Why this answer

Process classification and identification for Service Mapping are configured via Application Patterns and Process Classifiers within Service Mapping configuration.

Full explanation →
142
Multi-Selectmedium

Which TWO of the following fields are typically found on a Business Application record in the Design domain?

Select 2 answers
A.IP address [ip_address]
B.Vendor [vendor]
C.BIOS serial number [serial_number]
D.Business criticality [business_criticality]
E.MAC address [mac_address]
AnswersB, D

Vendor [vendor] is a standard field on the Business Application record, capturing the external supplier providing the software. This satisfies the stem's requirement for fields typically present in the Design domain, alongside details such as application owner and lifecycle status, supporting governance and ownership tracking.

Why this answer

Option B (Vendor) is correct because a Business Application record in the Design domain captures ownership and support information, including the software vendor or publisher that supplies the application. Option D (Business criticality) is correct because the Design domain records how important the application is to the business (for example, critical, high, medium, or low), which drives impact analysis and prioritization. Options A (IP address) and E (MAC address) are incorrect because these are network-layer identifiers that belong to infrastructure or configuration item records (such as servers or network devices), not to a business application definition.

Option C (BIOS serial number) is incorrect because it is a hardware asset identifier tied to a physical device, not an attribute of a business application.

Exam trap

CIS-DF often tests CSDM domain attribute placement — candidates see 'Business Application' and pick any familiar-sounding field, but IP address, serial number, and MAC address are infrastructure CI attributes, while only vendor and business criticality belong on the Design-domain Business Application record.

Full explanation →
143
MCQmedium

An implementer is configuring Service Graph Connectors to ingest infrastructure data into ServiceNow. Service Graph Connectors utilize the Robust Transform Engine (RTE) and the IRE. What is the primary benefit of using Service Graph Connectors over legacy Import Sets for third-party data ingestion?

A.They allow administrators to bypass CI Class Manager identification rules entirely.
B.They completely bypass the database and store CIs in memory for faster reporting.
C.They eliminate the need for any network connectivity between the third-party tool and ServiceNow.
D.They provide pre-built mapping, utilize the IRE for deduplication, and ensure data aligns with CSDM and CMDB data standards.
AnswerD

Pre-built mapping plus IRE deduplication directly satisfies the stem's ingestion requirement, while CSDM and CMDB alignment enforces the data standards legacy Import Sets leave to manual transform maps. Service Graph Connectors therefore reduce custom mapping effort and prevent duplicate CIs that Import Sets would create.

Why this answer

Service Graph Connectors provide pre-built mappings, leverage the IRE for deduplication and reconciliation, and ensure ingested data aligns with the Common Service Data Model (CSDM) and CMDB data standards. This reduces implementation effort, improves data quality, and ensures consistency across the CMDB compared to legacy Import Sets that require manual mapping and often bypass IRE.

Exam trap

CIS-DF often tests Service Graph Connector benefits — candidates pick answers that claim they bypass IRE or eliminate connectivity, misunderstanding that connectors depend on IRE and still require network paths.

How to eliminate wrong answers

Option A is wrong because Service Graph Connectors do not bypass CI Class Manager identification rules — they rely on the IRE, which uses those very identification rules to deduplicate and reconcile CIs. Option B is wrong because Service Graph Connectors write to the ServiceNow database like any other integration; they do not store CIs in memory, which would be impractical and non-persistent. Option C is wrong because Service Graph Connectors still require network connectivity (typically via MID Server or API endpoints) between the third-party tool and ServiceNow — they do not eliminate connectivity requirements.

Full explanation →
144
MCQhard

A ServiceNow architect is designing a CMDB architecture where CIs from multiple disparate discovery tools need to be ingested. To prevent race conditions and conflicting updates between tools updating the same CIs simultaneously, what mechanism should be utilized?

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

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

Why this answer

The Identification and Reconciliation Engine (IRE) processes incoming CI data through a queue and applies source precedence rules to resolve conflicts when multiple discovery sources update the same CI. This prevents race conditions by serializing updates and ensuring a deterministic winner based on configured precedence. It is the standard mechanism for multi-source CMDB ingestion.

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
145
Multi-Selectmedium

Which TWO metrics are categorized under CMDB Health Correctness? (Choose two.)

Select 2 answers
A.Unauthorized software installations
B.Mandatory fields missing
C.Orphans
D.Duplicates
E.Support group population status
AnswersC, D

Orphans counts configuration items lacking required relationships, directly measuring data correctness within the CMDB. Because correctness evaluates whether CI records hold valid, complete relationship data, orphaned CIs represent failed integrity checks, satisfying the stem's requirement for a correctness-categorised health metric alongside duplicate and stale metrics.

Why this answer

In ServiceNow CMDB Health, the Correctness KPI measures data quality problems that make CIs inaccurate or improperly related, and it includes the Orphans metric (C), which flags CIs that lack required relationships to other CIs, and the Duplicates metric (D), which flags multiple CI records that appear to represent the same real-world item. Both Orphans and Duplicates are scored under Correctness because they directly indicate incorrect or unreliable CMDB data rather than completeness or compliance issues. Unauthorized software installations (A) belong to CMDB Health compliance-type checks (e.g., unauthorized CI/software detection), not Correctness.

Mandatory fields missing (B) is a Completeness metric, since it measures whether required attributes are populated. Support group population status (E) is also a Completeness concern, because it checks whether the support group field is filled in, not whether the CI data is correct.

Full explanation →
146
MCQmedium

An administrator is configuring a Service Graph Connector to ingest client workstations. During test runs, they notice that workstations with identical hostnames but different serial numbers are being incorrectly merged into a single CI. Where should the administrator check and modify the matching criteria to ensure serial number is prioritized over hostname?

A.CI Class Manager -> Select cmdb_ci_computer -> Identification Rule -> Adjust criteria precedence and attribute selection
B.Data Source Precedence rules for workstations
C.Robust Transform Map Coalesce order
D.Discovery Schedule IP range filters
AnswerA

CI Class Manager hosts the identification rules that govern how the Service Graph Connector reconciles incoming records. Editing the cmdb_ci_computer identification rule lets the administrator reorder criteria so serial number is evaluated before hostname, preventing identical hostnames with differing serials from merging into one CI.

Why this answer

The CI Class Manager is where identification rules for a CI class are configured. By selecting cmdb_ci_computer and navigating to the Identification Rule, the administrator can adjust the criteria precedence and attribute selection to prioritize serial number over hostname. This directly addresses the issue of workstations with identical hostnames but different serial numbers being merged.

Exam trap

CIS-DF often tests the difference between identification rules and other matching mechanisms like data source precedence or coalesce, and candidates may confuse where to modify identification criteria.

How to eliminate wrong answers

Option B is wrong because Data Source Precedence rules determine which data source wins when multiple sources provide data for the same CI, but they do not control the matching criteria for identification. Option C is wrong because Robust Transform Map Coalesce order is used during transform to determine how to coalesce records, but it is not the primary place to modify identification rules for a CI class. Option D is wrong because Discovery Schedule IP range filters are used to limit discovery scope, not to modify matching criteria.

Full explanation →
147
MCQmedium

An administrator is setting up an integration that uses Robust Transform Engine (RTE). They need to combine two incoming fields—'First Name' and 'Last Name' from a user data source—into a single 'Managed By' reference field on the target CI. Which RTE feature should they use?

A.RTE Field Transformations / Operations (such as Concatenate)
B.CI Class Manager Identification Rule criteria
C.Discovery pattern preprocessing script
D.Standard Transform Map Coalesce script
AnswerA

RTE Field Transformations apply operations such as Concatenate to combine multiple source fields into one target value. Concatenating 'First Name' and 'Last Name' produces the full name string needed to populate the 'Managed By' reference field during transform execution.

Why this answer

RTE field transformations and field copiers allow combining or transforming multiple source fields into a single target attribute.

Full explanation →
148
Multi-Selecthard

Which THREE of the following actions are recommended when preparing an organization for CSDM adoption?

Select 3 answers
A.Disabling ServiceNow Discovery to rely solely on manual spreadsheets.
B.Securing cross-functional alignment between enterprise architects, ITSM managers, and CMDB administrators.
C.Deleting all existing incident and change history from the database.
D.Defining clear CSDM maturity goals and roadmap phases (Crawl, Walk, Run, Fly).
E.Cleansing baseline foundation data (users, companies, locations) before service mapping.
AnswersB, D, E

CSDM adoption spans architecture, service management and CMDB disciplines, so securing cross-functional alignment ensures each stakeholder group owns its domain layer. Without this shared governance, design decisions fragment and the Common Service Data Model cannot be applied consistently across the organisation.

Why this answer

Option B is correct because CSDM adoption spans multiple domains, so securing cross-functional alignment between enterprise architects, ITSM managers, and CMDB administrators ensures shared ownership of data models, governance, and service definitions across teams. Option D is correct because defining clear CSDM maturity goals and roadmap phases (Crawl, Walk, Run, Fly) gives the organization a structured, incremental path to adopt the Common Service Data Model without attempting a disruptive big-bang transformation. Option E is correct because cleansing baseline foundation data such as users, companies, and locations before service mapping ensures that the foundational CSDM layers are accurate, preventing downstream service and application mappings from inheriting bad reference data.

Option A is incorrect because disabling ServiceNow Discovery and relying on manual spreadsheets undermines the automated, authoritative data that CSDM depends on. Option C is incorrect because deleting all existing incident and change history destroys valuable data and audit trails rather than preparing the organization for CSDM adoption.

Exam trap

CIS-DF often tests the misconception that CSDM adoption is purely a technical configuration task, leading candidates to overlook the importance of cross-functional alignment and phased maturity goals.

Full explanation →
149
MCQhard

An enterprise uses Service Graph connectors to automatically populate infrastructure CIs. They want to ensure that these dynamically discovered CIs are automatically associated with the correct Application Service without manual mapping for every server addition. Which Application Service type should be deployed?

A.Static Business Application Service
B.Dynamic CI Group Application Service
C.Manual Application Service
D.Portfolio-linked Application Service
AnswerB

A Dynamic CI Group Application Service uses CMDB group query rules to automatically include matching CIs, so newly discovered servers join the correct Application Service without manual mapping. This satisfies the requirement for automatic association as servers are added.

Why this answer

A Dynamic CI Group Application Service automatically includes CIs based on a saved query or filter, so newly discovered servers matching the criteria are associated without manual mapping. This is exactly the requirement for dynamically discovered CIs from Service Graph connectors. Static and Manual Application Services require explicit CI membership, which would not scale.

Exam trap

CIS-DF often tests the difference between Manual/Static Application Services (explicit CI lists) and Dynamic CI Group Application Services (query-based membership) — candidates pick Static thinking it's simpler, but the 'automatically associated' requirement signals Dynamic.

How to eliminate wrong answers

Option A is wrong because a Static Business Application Service requires manually defining and maintaining the list of CIs, so new servers would not be automatically associated. Option C is wrong because a Manual Application Service also relies on manual association of CIs, defeating the automation goal. Option D is wrong because 'Portfolio-linked Application Service' is not a standard ServiceNow Application Service type for dynamic CI association; Application Services are typically categorized as Manual, Dynamic CI Group, or Tag-based, and portfolio linkage relates to APM/CSDM portfolio records, not dynamic membership.

Full explanation →
150
MCQhard

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

A.Access Control Lists (ACLs) on cmdb_ci fields
B.Data Certification read restrictions
C.Discovery credential filters
D.CMDB Data Governance read-only policies
AnswerA

ACLs on cmdb_ci fields enforce field-level write restrictions, checking the user's roles against the attribute's data classification before permitting edits. This directly blocks unauthorised modification of critical CI attributes on form views, satisfying the audit requirement for role- and classification-based write control.

Why this answer

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

Exam trap

CIS-DF often tests whether candidates confuse data quality processes (Data Certification) with access control mechanisms (ACLs), causing them to pick a governance process when the question asks for write-access restriction.

How to eliminate wrong answers

Option B is wrong because Data Certification is a process for attesting to the accuracy of CI data, not for restricting write access to attributes — it does not enforce field-level write permissions. Option C is wrong because Discovery credential filters control which credentials are used during discovery, not who can modify CI attributes on forms. Option D is wrong because 'CMDB Data Governance read-only policies' is not a real ServiceNow feature — while read-only policies exist conceptually, the actual enforcement mechanism for field-level write restriction is ACLs, not a governance policy module.

Full explanation →
Page 1

Page 2 of 4

Page 3

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 →