The Unified Map is a central feature of the CMDB Workspace. It provides an integrated and modern interface for visualizing Configuration Items (CIs) and their relationships. This tool combines functionalities from legacy dependency views and service mapping into a single, comprehensive map, allowing users to explore CI connections, service impacts, and overall infrastructure topology directly within the workspace environment. It is designed to be the primary tool for CI relationship visualization for Configuration Managers and other CMDB users.

A. CI Class Manager is used for managing the CMDB class hierarchy, including creating and editing CI classes and their attributes, not for visualizing CI relationships.

B. CMDB Data Manager is a tool for creating and managing data management policies and tasks to ensure the health and correctness of CMDB data, not for mapping.

- ServiceNow Product Documentation. (2023). CMDB Workspace. "The Unified Map in the CMDB Workspace provides a single map for visualizing CIs and their relationships."

- ServiceNow Product Documentation. (2023). Explore CIs and their relationships in the Unified Map. "Navigate to Configuration > CMDB Workspace. In the CMDB Workspace

on the CIs list view

select a CI to explore in the Unified Map."

According to the Common Service Data Model (CSDM), the Business Application [cmdbcibusinessapp] is the logical construct used to store business-level information for portfolio management, GRC, and audits. To address data classification requirements, the Information Object [cmdbciinformationobject] is used to define the type of data (e.g., PII, PCI) that the Business Application processes. Linking these two CIs provides a clear, auditable record of which applications handle sensitive data, directly satisfying the security and compliance requirements.

A. Technology Management Service Offerings (Technical Service Offerings) and Groups: Technical Service Offerings represent underlying technical capabilities (e.g., database hosting), not the business application or its data classification.

C. Customer Service Offerings and Databases: The business-level compliance and data classification information belongs on the Business Application, not the underlying database CI or a non-standard "Customer Service Offering" term.

1. ServiceNow White Paper

"CSDM 4.0 White Paper

" October 2022

Page 16 (Design Domain). This document defines Business Application as the record for "rationalization

GRC

and other business-related concerns."

2. ServiceNow Product Documentation

"Information object

" CSDM

Utah. "An information object represents the data that is exchanged or manipulated by the business application... Use information objects to track and manage sensitive data

such as PII or PCI."

The key difference lies in the scope and depth of verification. Attestation is a process to confirm that a CI still exists and that its ownership is correct. It is a high-level acknowledgement. Data Certification, conversely, is a more granular process that requires a user to validate the correctness of specific attributes (fields) on a CI record against a predefined template. It focuses on ensuring the accuracy of the data within the CI record itself, not just its existence.

A. This option incorrectly reverses the definitions of Attestation and Data Certification.

B. Both Attestation and Data Certification policies can be scheduled to run at regular intervals.

C. Both Attestation and Data Certification tasks can be assigned to either individual users or to groups.

1. ServiceNow Product Documentation. (2024). CMDB Attestation. ServiceNow. Retrieved from the ServiceNow Product Documentation site. It states

"Attestation is a process for verifying the existence and correctness of CIs."

2. ServiceNow Product Documentation. (2024). Data Certification. ServiceNow. Retrieved from the ServiceNow Product Documentation site. It explains

"Data Certification is a tool that enables you to verify the accuracy of your CMDB data... You can certify either an entire table or the records in a table that match a specific filter."

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 relationship is many-to-many. A single application server can host multiple applications (a one-to-many relationship from server to application). Conversely, a single application can be deployed across multiple application servers for reasons like load balancing, high availability, or scaling (a one-to-many relationship from application to server). When both conditions are true, the overall relationship between the two classes is defined as many-to-many. This is typically implemented in the CMDB using a separate relationship table (cmdbrelci) to link the records.

B. Many-to-one would imply many application servers host only one application, which contradicts the scenario.

C. One-to-one would mean each application server hosts exactly one application, and each application runs on only one server.

D. One-to-many would imply an application server can host many applications, but an application can only run on a single server.

- ServiceNow Product Documentation. (2023). Create a many-to-many relationship. "A many-to-many relationship is one in which many records in one table can relate to many records in another table."

- ServiceNow Product Documentation. (2023). Common Service Data Model (CSDM) product view. The CSDM framework illustrates how applications (Application Service CIs) are realized by infrastructure CIs

often showing a distributed architecture where one service relies on many servers.

The recommended action for managing the lifecycle of stale CIs, such as removing servers that have not been updated, is to use the CMDB Data Manager. This tool allows an administrator to create policies, including an archive policy. An archive policy can be configured with specific conditions (e.g., class is Linux Server, 'Updated' is more than six months ago) to automatically move matching records from primary tables to archive tables. This is the standard, out-of-the-box method for managing data retention and maintaining CMDB health, preferable to custom scripts.

A. A business rule is event-driven (e.g., runs on record update/insert) and is not the appropriate tool for a scheduled, proactive cleanup task based on a time condition.

C. While a scheduled job could execute a script to perform this task, it is a custom solution. The recommended best practice is to use the purpose-built CMDB Data Manager policies.

1. ServiceNow Product Documentation. (2024). CMDB Data Manager. Retrieved from ServiceNow Docs. The overview states

"Use CMDB Data Manager to create policies to manage the life cycle of CIs. For example

you can create a policy to automatically retire

archive

or delete stale CIs of a specific class."

2. ServiceNow Product Documentation. (2024). Create a CMDB Data Manager policy. Retrieved from ServiceNow Docs. This page provides step-by-step instructions for creating policies

including archive policies

based on conditions like the last update time.

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.

CMDB 360 (formerly Multisource CMDB) uses specific system properties for its configuration. The property glide.identification_engine.multisource_enabled is the primary switch that activates the core CMDB 360 feature. The glide.identification_engine.multisource_cmdb_ci_enabled property dictates whether the system captures multisource data specifically for Configuration Items within CMDB classes. For troubleshooting and diagnostics, glide.cmdb.logger.source.cmdb_multisource enables detailed logging for multisource operations. Finally, glide.identification_engine.multisource.recompute.max.ci.limit controls performance by restricting the maximum number of CIs processed during a single recompute task. The remaining option regarding non-CMDB classes applies to a different, unlisted property (multisource_non_cmdb_ci_enabled).

ServiceNow Product Documentation: Enable CMDB 360. This section outlines the required steps to activate the feature, detailing the glide.identification_engine.multisource_enabled and glide.identification_engine.multisource_cmdb_ci_enabled properties.

ServiceNow Product Documentation: CMDB properties. This reference document provides the comprehensive list of Identification and Reconciliation Engine (IRE) properties, defining the exact functions of glide.cmdb.logger.source.cmdb_multisource and the CI limits defined by glide.identification_engine.multisource.recompute.max.ci.limit.

De-Duplication Tasks are automatically generated incident-like records when duplicate Configuration Items (CIs) are identified; these are assigned to specific groups for review. The CMDB Health Dashboard Correctness Scorecard calculates and displays metrics on data integrity, specifically offering insights into the volume of duplicate, orphan, and stale CIs. De-Duplication Templates allow administrators to define rule-based actions, enabling the system to evaluate and resolve multiple duplicate tasks simultaneously in bulk. Finally, the Duplicate CI Remediator is an interactive, manual wizard that guides users through the process of comparing CIs, selecting a master CI, and merging or deleting the duplicate records individually. Certification Tasks are used for data certification and are not the primary tool for duplicate remediation.

ServiceNow Product Documentation: Resolve a de-duplication task. Section: Configuration Management Database (CMDB) -> CMDB Health -> Resolve duplicate CIs. (Details assignment and routing of duplication tasks).

ServiceNow Product Documentation: CMDB Health metrics. Section: Configuration Management Database (CMDB) -> CMDB Health. (Defines the Correctness KPI and its sub-metrics, including duplicates).

ServiceNow Product Documentation: Duplicate CI Remediator. Section: Configuration Management Database (CMDB) -> CMDB Health -> Resolve duplicate CIs. (Explains the wizard interface for individual CI reconciliation).

ServiceNow Product Documentation: Duplicate resolution templates. Section: Configuration Management Database (CMDB) -> CMDB Health -> Resolve duplicate CIs. (Explains applying templates for bulk resolution of de-duplication tasks).