Pass the ServiceNow CIS-Data Foundations (CMDB and CSDM) CIS-DF Questions and answers with CertsForce

Custom CMDB class tables should begin with u_cmdb_ci . The u_ portion identifies a customer-created table, while cmdb_ci preserves the standard CMDB naming convention and clearly indicates that the table extends the Configuration Item hierarchy.

For example, appropriate custom class names may resemble u_cmdb_ci_custom_router or u_cmdb_ci_special_switch. The uploaded guide uses these exact naming patterns when discussing custom-class consolidation and the technical debt created by unnecessary custom classes.

Using only cmdb_ci would incorrectly suggest an out-of-box ServiceNow table. Prefixes such as u_ci_cmdb and ci_cmdb do not follow the standard hierarchy convention. Before creating any custom class, the administrator should still verify that a suitable supported class is not already available through the CMDB CI Class Models application.

=========

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.

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.

A Technology Management Service Offering associated with the applicable Dynamic CI Group synchronizes operational group information to its member CIs. The fields designed for this synchronization include Managed by Group and Support Group .

Therefore, Linux Server CIs included in the offering’s CI population receive Enterprise IT Services as their Managed by Group. The CI Class Manager value can provide class-level ownership or governance context, but the service-offering alignment actively maintains the operational group value on the related member CIs.

The conflicting values do not cause Discovery or ingestion to fail. ServiceNow applies the configured group-synchronization mechanism rather than leaving the field empty. Change Management Team is assigned to the Change Group field, not the Managed by Group field, so Option D does not answer the question.

Consequently, the Managed by Group assigned to the discovered Linux Server instances is Enterprise IT Services.

The Crawl stage addresses the Foundation and Design domains. The Foundation domain establishes shared reference data and fundamental structures required by the rest of the service model, including organizations, locations, users, groups, products, and core CI information.

The Design domain introduces planning-level constructs such as Business Applications, Business Capabilities, Business Processes, and Information Objects. These records provide ownership, lifecycle, architecture, and portfolio context before the organization develops more advanced operational service models.

Manage Technical Services is addressed as the organization progresses into more mature technical service-delivery modelling, including Technical Services, Technical Service Offerings, Application Services, and their supporting CIs. Sell/Consume is associated with business-facing services, offerings, consumers, subscriptions, and service consumption.

Beginning with Foundation and Design ensures that the organization establishes trusted reference and planning data before implementing more complex operational and consumer-facing models.

=========

Archive and Retire are the correct CMDB Data Manager end-of-life policy types from the listed options. End-of-life governance in CMDB focuses on handling CI records that are no longer operationally active or no longer required in the active CMDB. A Retire policy is used when CIs should be moved out of active operational status while preserving lifecycle accuracy. An Archive policy is used when records should be removed from active operational use but retained for recovery, audit, or compliance purposes. Disposed and Lost are typically lifecycle status values used in asset or CI lifecycle tracking, not CMDB Data Manager policy types in this context. Decommission describes an operational lifecycle action or state transition, but it is not the Data Manager policy type being tested here. Therefore, the valid end-of-life policy types are Archive and Retire.

CMDB Data Manager supports multiple governance policy types because CMDB lifecycle management is broader than simply deleting or certifying records. The complete set represented here is Retire, Archive, Attestation, Certification, and Delete. Retire policies support lifecycle transition of CIs that should no longer be active. Archive policies remove records from active operational use while preserving them according to retention requirements. Delete policies permanently remove records when they no longer need to be retained. Attestation policies validate that a CI still exists or is still relevant. Certification policies require users to validate and potentially correct specific CI attribute values. Options B, C, and D are incomplete because each omits at least one major CMDB Data Manager policy type. Option A is therefore the best answer because it includes both lifecycle/removal policy types and validation-focused policy types.

Identification rules are configured through CMDB CI Class Manager . These rules define how the Identification and Reconciliation Engine determines whether an incoming CI already exists or whether a new CI record should be created. For server records, identification rules usually rely on attributes such as serial number, name, hostname, hardware identifiers, or other class-specific criteria. If these rules are weak or missing, duplicate server records can be created during Discovery, Service Graph Connector imports, or other integrations. The CMDB Health Dashboard detects health issues such as duplicates, but it is not where identification rules are configured. CMDB Workspace provides operational access to CMDB capabilities, but CI Class Manager is the correct configuration location. CMDB Data Manager governs lifecycle policies, not IRE identification logic. Therefore, the correct answer is B.

=========

The correct answer is C . In CSDM and Application Portfolio Management, a platform should be modeled as a Business Application with the architecture type Platform Host . Applications that run on or are provided by that platform should be modeled as Platform Applications and should reference the platform host. In this scenario, the ServiceNow Platform is the platform host, while Incident and Change are platform applications because they are capabilities delivered on the ServiceNow Platform. The relationship is not best represented by making all three applications generic web-based applications. That would lose the platform/application distinction. The preferred model is also not simply a Depends On relationship, because CSDM provides a more specific platform host reference model for this use case. Therefore, ServiceNow Platform should be Platform Host, and Incident and Change should be Platform Applications referencing ServiceNow Platform.

=========