The correct answer is Service Delivery . In CSDM, the Service Delivery domain focuses on how services are technically delivered and operated. It includes the modeling of technical services, technical service offerings, application services, infrastructure CIs, and the relationships that connect them. The scenario specifically asks about Infrastructure CIs, Technology Management Offerings, Technical Service Offerings, and Application Services, which are all part of the technical operating model for delivering services. Foundation is used for base reference data such as locations, groups, companies, and users. Design and Planning focuses on business applications, capabilities, and planning artifacts. Service Consumption focuses on how consumers access and consume services. Build and Integration is associated with development and deployment activities. Because the question is about technical service relationships and operational service delivery, Service Delivery is the correct CSDM domain.
=========

In ServiceNow, the Compliance dimension of the CMDB Health Dashboard is driven by Data Certification.
To surface meaningful compliance results-such as identifying servers that are not on the latest patch-the platform requires a combination of Certification Policies, Data Filters, and Scheduled Jobs.
Certification Policies define what data must be validated and which attributes are subject to compliance checks (for example, patch level, OS version, or last update date). Data Filters scope the population-such as server classes only-ensuring the compliance evaluation targets the correct CIs. Scheduled Jobs automate when certifications run, keeping compliance scores current and reflective of the latest state.
Options A and C are incorrect because audits and stale/orphan/duplicate checks relate to other health dimensions (correctness and completeness), not compliance. Option B focuses on service modeling and group alignment, which does not directly drive compliance scoring for patch currency.
Therefore, configuring Certification Policies, Data Filters, and Scheduled Jobs is required to accurately measure and display patch compliance on the CMDB Health Dashboard.

Creating new CI classes is a high-impact configuration activity and must follow strict Data Foundations and CSDM-aligned best practices to avoid long-term technical debt and upgrade risk.
Option B is a recommended first step. Before creating any new CI class, administrators should install or update the CMDB CI Class Models Store application and verify whether an appropriate class already exists.
ServiceNow frequently delivers new CI classes through updates and class model packages, and duplicating an existing or planned class can lead to fragmentation and governance issues.
Option C is also correct. When a new class is truly required, it should be added under an appropriate parent class to inherit attributes, behaviors, and discovery patterns. For an IoT Sensor, this might be under a hardware or device-related parent class, ensuring consistency and minimizing customization.
Option A is incorrect and dangerous-deleting unused classes can break dependencies and historical data.
Option D is also discouraged; modifying existing classes to repurpose them violates upgrade-safe design principles and can negatively impact discovery, integrations, and reporting.
By verifying existing models first and extending the class hierarchy correctly, organizations maintain a clean, scalable, and upgrade-safe CMDB.
Therefore, the correct answers are B and C.

Archive is the correct policy type because the requirement is not permanent removal; it is controlled removal with the ability to restore records within a defined retention period. In CMDB Data Manager, archive policies support CMDB data lifecycle governance by moving eligible CI records out of active operational use while preserving them for recovery, audit, or historical review. This is different from Delete, which is used when records should be removed permanently and restoration is not the intended governance outcome. Certification is used to validate specific CI attributes, not remove records. Retire changes or manages lifecycle state but does not satisfy the specific requirement to remove records while preserving restore capability. Therefore, when the objective is to reduce active CMDB volume while retaining recoverability, the correct Data Manager policy type is Archive.

The Design and Planning domain of CSDM focuses on planning-level constructs such as Business Applications, Business Capabilities, Information Objects, and architecture context. The two roles most directly involved are the Application Owner and the Enterprise Architect . Application Owners provide authoritative ownership, lifecycle, criticality, and portfolio information for Business Applications. Enterprise Architects define and govern enterprise capabilities, application rationalization, architecture alignment, and strategic planning relationships. Application Service Owners are more closely aligned with operational service delivery and application service health, especially in the technical/manage domain. Business Relationship Managers are more closely tied to consumption, offerings, and business-facing service value.
Because Design and Planning is about application portfolio and enterprise architecture structure, the correct roles are Application Owner and Enterprise Architect.
=========