A Business Relationship Manager in an organization wants to implement Service Portfolio Management (SPM) and present offerings to business consumers.
Which CSDM domain does this align with?
Answer : D
The correct answer is Service Consumption. Service Portfolio Management focuses on defining, organizing, and presenting services and offerings to business consumers. In CSDM, this aligns with the Service Consumption, or Sell/Consume, domain. This domain explains how business-facing services and offerings are made available to users, departments, locations, or customer groups. Design and Planning is concerned with strategic planning objects such as Business Applications, Business Capabilities, and Information Objects. Build and Integration focuses on development and delivery pipelines. Service Delivery focuses on the technical operation and management of services. Since the scenario is about presenting offerings to business consumers through Service Portfolio Management, it clearly belongs to Service Consumption.
=========
A CMDB Administrator wants to configure Identification and Reconciliation Engine rules for the CMDB. The Administrator opens CI Class Manager and sees the Identification Inclusion Rules tab available under a CI class.
How are these rules used by the IRE?
Answer : C
Identification Inclusion Rules restrict the population of existing CIs that the Identification and Reconciliation Engine considers when attempting to identify an incoming CI. They add qualifying conditions to the identification process so that IRE searches only the relevant subset of records instead of evaluating every CI in the class.
For example, an inclusion rule could constrain matching to CIs belonging to a particular company, environment, domain, or other defined population. After narrowing the candidate records, IRE applies the class's identifier entries and identification criteria to decide whether an existing CI matches the incoming data. Identification rules determine whether an incoming record matches an existing CI or requires creation of a new record.
Option A describes reconciliation rules, which control source authority over attributes. Option B is incorrect because inclusion rules do not stop the source from submitting data.
The video displays ''Health Inclusion Rules,'' but that is a terminology error. Health Inclusion Rules control CMDB Health scope; Identification Inclusion Rules are used by IRE.
=========
A Configuration Manager wants to explore ServiceNow CMDB 360 saved queries to see if the reports can assist with managing CMDB data.
What insights are gained from CMDB 360 queries?
(Choose 2 options)
Answer : C, D
CMDB 360, also known as Multisource CMDB, is designed to provide visibility into how multiple discovery or integration sources contribute data to the same CI. Its value is not simply identifying duplicate or orphan CIs; those are handled through CMDB Health and de-duplication capabilities. CMDB 360 helps administrators compare source contributions and understand conflicts or gaps across those sources. A key insight is gaps in attribute data, where one source supplies certain CI attributes while another source does not. Another key insight is different attribute values from different data sources, which helps identify reconciliation problems, source precedence issues, and inconsistent discovery results. This is central to improving data trust because the CMDB often receives data from Discovery, SCCM, cloud connectors, manual imports, and third-party systems. Therefore, the correct insights are gaps in attribute data and different attribute values across sources.
A CMDB Administrator has imported data into the ServiceNow CMDB from a third-party source by using a Service Graph Connector. The Administrator wants to review specific field-to-field mappings for the import.
Which feature shows this information?
Answer : B
The CMDB Integrations Dashboard provides visibility into integrations that populate the CMDB, including Service Graph Connector activity and mapping information. It enables administrators to inspect how source data is mapped to ServiceNow target classes and fields, review connector execution information, and investigate ingestion or mapping problems.
Service Graph Connectors are prebuilt, governed integrations that import third-party data into the CMDB through standardized class mappings and IRE processing. They are intended to minimize custom transformations and preserve source and reconciliation information. The guide describes Service Graph Connectors as upgrade-safe integrations that ingest external data while applying Identification and Reconciliation Engine controls.
Integration Hub is the broader integration and automation framework, not the specific dashboard for reviewing Service Graph Connector field mappings. IntegrationHub ETL is a separate tool for building and managing ETL transformations. It does not serve as the inspection dashboard for mappings belonging to an installed Service Graph Connector.
Therefore, B is correct.
(Choose two options.)
A CMDB Administrator wants to educate the team about the actions that can be performed within CMDB Workspace.
Which actions can be initiated from CMDB Workspace?
Answer : A, D
CMDB Workspace provides governed experiences for both duplicate remediation and CMDB Data Manager policy administration. Duplicate CI records can be investigated and remediated through the de-duplication dashboard in CMDB Workspace. This purpose-built interface centralizes duplicate identification, comparison, prioritization, and controlled remediation rather than forcing administrators to use generic task lists.
CMDB Data Manager is also available from the Management area of CMDB Workspace. An authorized administrator can create, publish, and manage policies, including certification policies that validate designated CI attributes and generate tasks for responsible users.
Discovery execution is performed through Discovery administration capabilities, not CMDB Workspace. New class creation is performed through CI Class Manager rather than being one of the direct CMDB Workspace actions tested here. Therefore, A and D are correct.
=========
A ServiceNow Administrator wants to implement Sen/ice Graph Connectors to provide integrations to many third-party solutions that the company wants integrated into the CMDB
Which categories of connectors are available to the Administrator"?
Answer : A, B
Service Graph Connectors are a key Data Foundations ingestion capability in ServiceNow. They provide out-of-the-box, upgrade-safe integrations that ingest data into the CMDB using the Identification and Reconciliation Engine (IRE), ensuring data quality and source governance.
Two primary categories of Service Graph Connectors are:
Cloud (Option A): These connectors integrate with major cloud providers and platforms (such as AWS, Azure, and GCP) to ingest infrastructure, platform, and service data into the CMDB. They are essential for managing hybrid and multi-cloud environments and maintaining accurate cloud CI relationships.
Observability (Option B): These connectors integrate with monitoring and observability tools (such as APM, infrastructure monitoring, and telemetry platforms). They provide near-real-time operational data that enriches CI records and supports incident correlation, impact analysis, and service health insights.
Option C (DevOps) is incorrect because DevOps integrations are typically handled through CI/CD tools and workflow integrations rather than Service Graph Connectors. Option D (Workflow Automation) is unrelated; Service Graph Connectors focus on data ingestion, not process orchestration.
Therefore, the correct connector categories are Cloud and Observability, making Options A and B the correct answers.
A CMDB Administrator is reviewing the health of the CMDB and notices a large percentage of the Hardware CIs are missing serial numbers. The Administrator is concerned this may cause duplicate CIs and would like to resolve the issue in a timely manner.
What structured guidelines provided by ServiceNow are available to troubleshoot and resolve the issue?
Answer : C
In Data Foundations, ''Insight'' includes using dashboards and guided remediation to identify and fix issues that degrade CMDB trust. Missing serial numbers on Hardware CIs is a high-risk data quality issue because serial number is commonly used as a key identifier for uniqueness. When it is missing, identification and reconciliation become less reliable, increasing the likelihood of duplicate CI creation from Discovery, integrations, or manual entry.
ServiceNow provides structured, prescriptive guidance through the CMDB Data Foundations Dashboard Playbooks. These playbooks are designed specifically to help administrators move from a dashboard finding (for example, low uniqueness or incomplete key identifiers) to a repeatable remediation approach. They typically guide you to: confirm the scope of impacted CI classes, validate which sources should populate serial number (Discovery, integrations, import sets, vendor feeds), verify mapping and transformation logic, and then remediate existing records while putting controls in place to prevent recurrence.
Option B focuses on CMDB Health Dashboard guidance, which is helpful for health scoring and rules, but the question explicitly references a data foundations-type remediation need tied to data completeness of key identifiers and timely resolution using structured guidelines. Options A and D are CSDM-focused and do not directly address CI identifier population and duplication risk in the CMDB ingestion context. Therefore, the structured guidelines to troubleshoot and resolve missing serial numbers in a Data Foundations context are the CMDB Data Foundations Dashboard Playbooks.