CIS-DF Exam Dumps - Certified Implementation Specialist - Data Foundations (CMDB and CSDM)

In Data Foundations, “Insight” focuses on turning configuration data into actionable visibility. CMDB 360 (often associated with Multisource CMDB capabilities) provides a guided experience in CMDB Workspace for exploring CI data and running queries across sources. Within this experience, Saved Queries are managed directly under the CMDB 360 area of CMDB Workspace because they are part of the CMDB 360 query-and-analysis workflow.

A CMDB 360 Saved Query is not the same as a generic CMDB Query Builder query created from classic navigation modules. The CMDB 360 experience typically uses a tile/window approach where users can view existing saved queries, create new queries, modify them, and run them to retrieve CMDB 360 data aligned to multisource reporting and analysis. Keeping saved queries on the CMDB 360 tab makes them easy to discover and reuse for repeatable insights (for example, coverage and source comparisons, CI data quality checks by source, and targeted investigation of records).

The Insights tab in CMDB Workspace is generally used to understand adoption and health-related insights about CMDB features, not as the primary location for creating CMDB 360 multisource saved queries. “Coverage” is a specific lens/view and does not represent the saved-query creation workspace. “CMDB Query Builder” is a related capability, but the question explicitly asks where CMDB 360/Multisource Saved Queries are viewed and created in CMDB Workspace , which is the Saved queries window on the CMDB 360 tab.

The CMDB Health Dashboard organizes data quality into practical, action-oriented metrics:

Audits validate correctness by comparing CI values against defined expectations (rules, policies, certifications).

Duplicate CIs represent redundant records and should be reduced to improve trust and reporting accuracy.

Orphan CIs lack required relationships or key context, limiting impact analysis and service visibility.

Recommended fields are not mandatory but add diagnostic value during incidents and problem investigations.

Required fields are enforced by the platform and closely tied to Identification & Reconciliation remediation.

Stale CIs signal aging data that no longer reflects the current environment.

This mapping aligns with CMDB Data Foundations best practices and how the Health Dashboard is designed to guide prioritization and remediation.

Enhancing Incident Management in ServiceNow often involves integrating complementary products that enrich context, prioritization, and decision-making.

Discovery strengthens incident resolution by automatically populating accurate CI data and relationships, allowing responders to quickly understand affected infrastructure and applications.

Hardware Asset Management (HAM) adds visibility into asset lifecycle, ownership, and maintenance actions, which is especially valuable when incidents involve physical devices or failures.

Risk Management (part of IRM) provides insight into business and financial risk exposure, helping teams prioritize incidents based on potential regulatory, safety, or financial impact.

Service Portfolio Management (SPM) connects incidents to the service lifecycle, enabling better understanding of whether an incident affects a live, retiring, or planned service—and improving communication with stakeholders.

Together, these integrations transform Incident Management from a reactive process into a context-rich, business-aligned capability.

In Data Foundations, “Govern” includes maintaining consistency between closely related data domains so that operational and asset lifecycle processes remain trustworthy. For hardware endpoints (and other asset-backed items), Asset and CI records often represent the same real-world item from two perspectives: financial/lifecycle management (Asset) and operational/service context (CI). Automatic synchronization prevents drift such as different owners, locations, or statuses appearing in Asset vs CI, which can cause reporting errors, incorrect fulfillment decisions, and audit issues.

The platform supports synchronization through out-of-box synchronization logic (commonly implemented as business rules and related configuration) that updates the CI when an Asset changes, and updates the Asset when a CI changes—so the records stay aligned regardless of which team updates which record. Therefore, ensuring the Asset-to-CI update logic is active (A) and the CI-to-Asset update logic is active (B) is the right way to keep data synchronized automatically.

Option C is not required for synchronization; the intent is near real-time consistency driven by record changes, not batch jobs that run later. Scheduled jobs might exist for other maintenance activities, but they are not the primary mechanism for keeping Asset/CI synchronized. Option D is important as a data quality principle—ideally one Asset maps to one CI for physical items—but “ensuring one-to-one mapping” is not the automation mechanism itself. Automation is achieved through the active synchronization logic, which is why A and B are the correct answers.

In ServiceNow, CMDB 360 / Multisource CMDB extends the Identification and Reconciliation Engine (IRE) to support multi-source visibility, reconciliation, and confidence scoring. Configuration is controlled through system properties, each enabling a specific capability.

glide.identification_engine.multisource_enabled is the master switch that activates CMDB 360 functionality.

glide.identification_engine.multisource_cmdb_ci_enabled allows CMDB 360 to collect and evaluate data specifically from CMDB CI classes.

glide.cmdb.logger.source.cmdb_multisource enables detailed logging for troubleshooting multisource ingestion and reconciliation.

glide.identification_engine.multisource_recompute.max_ci_limit protects performance by limiting how many CIs can be processed during a recompute operation.

Capturing CMDB 360 data from non-CMDB classes is not supported, which is why no property applies to that option.

This mapping aligns with Data Foundations and CMDB governance best practices, ensuring CMDB 360 is enabled safely, transparently, and at scale.