In CSDM,Technology Services(and their Service Offerings) representhow technical capabilities are delivered and consumedby internal teams. When a server team requests a catalog item for infrastructure services (e.g., VM provisioning, storage, OS builds), the role responsible forinitiating the request and defining requirementsis theTechnology Service Owner.
Technology Service Owners understand the operational capabilities, constraints, SLAs, and fulfillment workflows required to deliver infrastructure services. They define catalog requirements such as options, approvals, fulfillment tasks, and guardrails-ensuring the request aligns with standardization, security, and operational readiness.
Application Service Ownersfocus on how applications are delivered and supported, not on defining infrastructure catalog items.Enterprise Architectsprovide standards and guidance but do not initiate or define catalog request requirements.
Thus, the correct role isB - Technology Service Owners.

To specifically improvedata quality related to CSDM, the most effective and prescribed action is to use theCSDM Data Foundations Dashboard. InServiceNow, this dashboard is purpose-built to assess and improveCSDM alignment, not just general CMDB hygiene.
The CSDM Data Foundations Dashboard focuses onservice modeling readiness, highlighting gaps such as missing service ownership, incomplete relationships between Business Applications and Application Services, unmanaged services, and misaligned lifecycle states. It providesGet Well Playbooksthat guide administrators through structured remediation using Analyze Data, Fix Data, and Govern Data plays-directly tied to CSDM outcomes.
Option C (default CMDB Health Dashboard) is valuable, but it measuresgeneric CMDB data quality dimensions(completeness, correctness, compliance) and does not specifically evaluateCSDM constructs or service modeling maturity. Option B (ServiceNow Health Scan) provides platform-wide configuration and performance recommendations, but it is not focused on CMDB or CSDM data quality.
Therefore, to improveCSDM-specific data quality, the administrator should use theCSDM Data Foundations Dashboard, makingOption Athe correct answer.

InServiceNow, theCMDB Health Dashboarddoes not calculate health scores in real time by default. Instead, health scores are generated and refreshed byscheduled calculation jobsthat evaluate CI data against defined health rules across the dimensions ofcompleteness, correctness, and compliance.
To generate and maintain CMDB health scores, thescheduled jobs for CMDB Health must be active. These jobs periodically scan the CMDB, apply health rules (for example, required attributes populated, lifecycle status compliance, certification results), and calculate scores that are displayed on the dashboard and scorecards. Without these scheduled jobs running, the dashboard cannot produce current or meaningful health metrics.
Option B is incorrect because CMDB health scoring isnot automatic or real-time; it depends on scheduled processing. Option C is also incorrect because CMDB Health is part of the core CMDB/Data Foundations capability in ServiceNow and does not require a separate "CMDB health calculation" plugin to be installed in modern implementations.
Activating and maintaining these scheduled jobs ensures that health scores remain accurate, trendable over time, and useful for governance decisions. This is a foundational requirement for using the CMDB Health Dashboard as a data quality improvement tool.
Therefore, the correct answer isA - The scheduled jobs for the CMDB Health Dashboard must be activated.

In a mature CMDB implementation withinServiceNow, CI operational attributes are leveraged toautomate ITSM workflows. One of the most important outcomes of accurate Configuration Management isautomatic incident routing.
When a CI is selected on an Incident record, ServiceNow evaluates the CI'sSupport Groupattribute. If populated correctly, the platform automatically copies this value into theAssignment Groupfield on the Incident. This ensures incidents are routed to the correct resolver group without manual triage, reducing mean time to resolution (MTTR).
TheSupport Groupis a CI attribute, not an incident field that drives workflow directly. TheAssignment Groupis the operational field used by Incident Management to assign ownership. Managed by Group, Approval Group, and Change Group are used in other governance and lifecycle contexts and are not auto- populated during incident creation.
This behavior is a direct result of Data Foundations best practices: maintaining accurate CI-to-support-group relationships to enableautomation and consistencyacross ITSM processes.
Therefore, the correct answer isC - Assignment Group.

In CMDB governance, differentCMDB Data Manager policy typesserve different validation and enforcement purposes. When the objective is to allow an assigned individual toreview and update specific fields on a CI record, the correct policy type isCertification.
ACertification policycreates actionable tasks that require the assignee tovalidate and, if necessary, correct specific CI attributes, such as lifecycle status, support group, environment, or ownership. During certification, the user can directly update CI fields to bring the record into compliance with defined standards.
Attestation(Option C) only asks the user to confirm that a CIstill existsor is still valid; it does not require or enable attribute-level updates.Audit(Option A) is used for reporting and evidence collection, not remediation.
Compliance(Option D) measures adherence to rules but does not itself generate editable remediation tasks.
Certification is therefore the primary mechanism used whenhuman validation and correctionof CI data is required-making it a cornerstone of CMDB data quality management.
Hence, the correct answer isB - Certification.