The CMDB Health Dashboard allows for granular control over the scope of its metrics using Health Inclusion Rules. These rules define a specific subset of CIs within a class to be evaluated for a particular health test. The scenario shows the Duplicate metric evaluating all 60,000 servers, while the Orphan metric evaluates only 50,000. This indicates that a Health Inclusion Rule is applied specifically to the Orphan metric for the Server class, filtering the CIs included in its calculation based on defined conditions.

A. The Orphan metric has a CMDB Group configured for the Server class: CMDB Groups are for logical organization and reporting, not for defining the evaluation scope of a specific health metric.

C. The Duplicate metric has a Health Inclusion rule configured for the Server class: This would cause the Duplicate metric to evaluate fewer than 60,000 CIs, which contradicts the information provided.

D. The Duplicate metric has a CMDB Group configured for the Server class: CMDB Groups are not the mechanism used to scope individual health metric calculations.

1. ServiceNow Product Documentation, "Create a CMDB health inclusion rule," CMDB, Utah. "Use health inclusion rules to include only a specific set of CIs of a class in the health calculations of a health metric."

2. ServiceNow Product Documentation, "CMDB Health," CMDB, Utah. "You can create an inclusion rule for a specific health test, such as the duplicate CIs test, and for a specific CI class, such as the Server class."

The CMDB Health Dashboard assesses the quality of CMDB data across three main categories: Completeness, Compliance, and Correctness. The Correctness metric specifically includes tests to identify stale and duplicate CIs. Stale CIs are those that have not been updated within a configured time period, suggesting they may no longer be valid (D). Duplicate CIs are multiple records that represent the same physical or logical item, which can lead to confusion and process failures (E). Both are critical indicators of data correctness and overall CMDB health.

A. "Downgraded CIs" is not a standard metric in the CMDB Health Dashboard. This term is not typically used in the context of CMDB data quality assessment.

B. "Upgraded CIs" is not a standard health metric. While a CI's state can change, this is not a specific category of data quality measured by the dashboard.

C. The dashboard measures incompleteness (e.g., missing required fields) but does not have a metric for "Missing CIs," as it cannot know what CIs are absent.

- ServiceNow Product Documentation. (2024). CMDB Health dashboards and reports. Retrieved from docs.servicenow.com. This page details the health indicators, listing "Duplicate CIs" and "Stale CIs" under the Correctness health metric.

- ServiceNow Product Documentation. (2024). CMDB health metrics. Retrieved from docs.servicenow.com. This document provides a detailed list of the metrics, including cmdbhealthmetricstaleness and cmdbhealthmetricduplicate.

When a Technical Service Offering is associated with a Dynamic CI Group, ServiceNow can automatically synchronize key operational group information from the offering to all member CIs of that group. This feature automates the assignment of responsibility for CIs based on the service they support. The specific group fields on the service offering that are propagated to the corresponding fields on the CIs are the Managed by group and the Support group. This ensures that CIs are automatically assigned to the correct teams for operational management and incident support.

A. Approval Group: This field is not a standard CI attribute that is synchronized from a service offering; it is typically used within workflow processes like Change Management.

C. Owned by Group: The standard CI form has an Owned by field, which is a user reference, not a group. The Managed by group is the correct field for operational group ownership.

1. ServiceNow Product Documentation. (2023). Service Portfolio Management. "Populate support and managed by groups for CIs in a dynamic CI group," explicitly states, "The support group and managed by group from the service offering are populated in the respective fields for all the CIs in the dynamic CI group."

2. ServiceNow Product Documentation. (2023). Dynamic CI groups. "Use a dynamic CI group," describes how these groups are used in conjunction with service offerings to manage CI populations.

The Identification and Reconciliation Engine (IRE) is a core platform capability responsible for managing data consistency in the CMDB. It processes incoming data from various sources and uses reconciliation rules to prevent data duplication and maintain data integrity. While the Multisource CMDB feature (part of ITOM licensing) provides an enhanced user interface and specific features for managing source data, the underlying IRE functionality to apply reconciliation rules across multiple discovery sources is available without this specific license. Therefore, the Data Owner can configure and use IRE reconciliation rules for their five discovery sources on the base platform.

A. ITOM Discovery is not a mandatory prerequisite for using the IRE with multiple sources; IRE is a core CMDB function.

C. Multisource CMDB is not a base platform product; it requires a specific subscription, such as ITOM Visibility or Discovery, to be activated and used.

- ServiceNow Product Documentation, "CMDB Identification and Reconciliation," Doc ID: f268315553c3330034443754911c08e3. This document describes the IRE as a core CMDB feature for processing data from different sources.

- ServiceNow Product Documentation, "Multisource CMDB," Doc ID: 060a21115303330034443754911c08d3. This page notes that Multisource CMDB stores the entire history of discovery sources, a feature that requires specific licensing, but it doesn't state that the base IRE reconciliation is locked behind it.

The CSDM framework connects technical CIs to business context. For Vulnerability Response and Security Incident Response, understanding the business impact of a vulnerable CI is critical for prioritization. The relationship between an Application Service (the operational instance) and a Business Application (the business-facing entity) provides this essential context. The "Application Services with Business Application Relationships" Get Well Playbook specifically tracks and encourages the creation of these relationships, directly enabling security and operations teams to assess risk accurately and prioritize tasks based on business criticality.

A. Locations without a Parent Location: This playbook addresses data quality for physical locations, which is less critical for the business context needed for SecOps risk assessment.

C. Named Product Models without Product Owners: This focuses on asset management ownership. While useful, it does not provide the direct business service impact context needed for prioritization.

D. Percentage of Custom Status Values for CI Life Cycle Stages: This is a data governance metric for CI lifecycle states and does not provide the necessary business context for risk evaluation.

1. ServiceNow Product Documentation. (2023). CSDM Data Foundations dashboard. "Application Services with Business Application Relationships" indicator description.

2. ServiceNow White Paper. (2023). Common Service Data Model (CSDM) 4.0. Section: "CSDM domains and examples," illustrates the connection from infrastructure to Application Service to Business Application for providing context.

The Common Service Data Model (CSDM) provides a standardized framework that connects technical Configuration Items (CIs) to the business services they support. For Change Management, this provides two key benefits. First, it allows for accurate impact analysis by showing which business applications and services depend on a CI being changed (D). Second, by linking CIs to services which have defined ownership (e.g., Support Group, Approval Group), change requests can be dynamically and accurately routed to the correct teams for assessment and approval (C).

A. Blackout windows are scheduling constructs within Change Management to prevent changes during critical periods; they are not directly derived from the CSDM structural data.

B. Determining the root cause of an issue is a function of Problem Management (Root Cause Analysis), not a direct benefit to the Change Management process itself.

1. ServiceNow. (2022). CSDM 4.0 White Paper. Page 11, under "CSDM framework outcomes," lists "Improved change management" and specifies benefits including "Impact analysis of changes against services" and "Better change routing."

2. ServiceNow Product Documentation. (2024). Change Management and CSDM. Retrieved from ServiceNow Docs. This section details how CSDM improves change risk assessment by providing visibility into service dependencies.

3. ServiceNow Product Documentation. (2024). View CIs for a service in a change request. Retrieved from ServiceNow Docs. This page explains how the relationship data from CSDM is used to assess the impact of a change.

The Principal Class filter is controlled by the principalclassfilter dictionary attribute on the Configuration Item field. Modifying dictionary attributes requires the personalizedictionary role. The sncmdbadmin role is a comprehensive administrative role for the CMDB. It contains the personalizedictionary role, granting it the necessary permissions to perform this and other CMDB structural configurations, such as managing CI classes and their attributes. Therefore, a user with either of these roles can modify the Principal Class filter.

C. The sncsdmadmin role focuses on CSDM data governance, managing lifecycles, and ensuring model adherence, not low-level dictionary or table configuration.

D. The cmdbquerybuilder role grants permissions to create, edit, and run queries against the CMDB but does not include administrative configuration privileges.

1. ServiceNow Product Documentation. (2023). Dictionary attributes. Describes how attributes like principalclassfilter are used and that modifying them requires dictionary personalization rights.

2. ServiceNow Product Documentation. (2023). CMDB roles. The documentation for the sncmdbadmin role explicitly states it contains roles like personalizedictionary, granting it broad configuration capabilities for the CMDB.

Agent Client Collector (ACC) is an agent-based discovery method that excels where traditional agentless discovery is challenged. A primary use case is for devices in secure network zones (e.g., DMZ, PCI environments) where inbound network connections and credentials required for agentless discovery are blocked by firewalls. ACC initiates an outbound connection, which is more likely to be permitted. Another key use case is for devices that connect intermittently to the corporate network, such as laptops. The agent runs locally and can collect and cache data, sending it to the instance whenever a network connection is available, ensuring data is not missed.

A. Servers in a data center are typically always online and accessible on the corporate network, making them ideal candidates for traditional agentless discovery.

B. Network devices like routers and switches do not run a standard OS that can host an agent; they are discovered via agentless protocols like SNMP.

1. ServiceNow Product Documentation. Agent Client Collector. Section: "Agent Client Collector overview". The documentation states, "Agent Client Collector is ideal for discovering endpoints that are not easily accessible with agentless discovery, such as endpoints in a secure network or endpoints that are not always connected to the enterprise network."

2. ServiceNow Product Documentation. Agent Client Collector for Visibility. Section: "Agent Client Collector for Visibility use cases". This section explicitly lists "Discovering CIs in a secure network" and "Discovering CIs that are not always connected to the enterprise network" as key use cases.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/ServiceNow_CIS-DF/page_62_img_2.jpg 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.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/ServiceNow_CIS-DF/page_61_img_2.jpg When transitioning to CSDM-aligned lifecycle management, ServiceNow introduces a structured lifecycle framework that separates high-level intent from detailed operational state. Life Cycle Stage represents the macro phase of a CI’s existence (for example: Plan, Build, Deploy, Operate, Retire). Life Cycle Stage Status refines that phase with granular, sub-level states that vary by CI type. Life Cycle Object determines which lifecycle stages and statuses apply, based on what kind of CI is being managed (hardware, application, document, etc.). Life Cycle Mapping ensures a safe transition from legacy status fields by translating existing values into standardized CSDM lifecycle values—avoiding data loss or process disruption. Together, these objects enable consistent lifecycle governance, improve reporting accuracy, and support automation across ITSM, ITOM, and IRM use cases—while remaining backward compatible with legacy CMDB data.