When organizations transition from legacy CMDB status fields (such as custom install status or operational status values) toCSDM-aligned lifecycle status fields, the goal is tomap old values to standardized lifecycle stageswithout disrupting existing processes. InServiceNow, this is achieved through theLife Cycle Mappingtable.
TheLife Cycle Mappingtable is specifically designed to translatelegacy or custom status valuesintoCSDM lifecycle stages and statuses. This allows organizations to preserve historical data and integrations while progressively adopting CSDM standards. By modifying this table, administrators can define how existing status values correspond to CSDM lifecycle stages such asPlan, Build, Deploy, Operate, and Retire.
TheLife Cycle Stagestable (Option A) defines the standard stages themselves and should not be modified, as these are core to CSDM governance.Life Cycle Stage Status(Option C) defines valid statuses within a stage and is also part of the standardized model.Life Cycle Controls(Option D) enforce governance rules but do not perform value translation.
Therefore, to safely transition from legacy status fields to CSDM lifecycle statuses, the correct and supported approach is to modify theLife Cycle Mappingtable, makingOption Bthe correct answer.

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.
=========

In ServiceNow, de-duplication tasks generated by the Identification and Reconciliation Engine (IRE) are operational governance tasks that require action by CMDB administrators or data owners. These tasks are surfaced in a role-based and actionable manner to ensure they are addressed promptly.
Within the CMDB Workspace, such tasks are accessed via the My Work tab, specifically under the Total status section. This area consolidates all actionable CMDB-related work items assigned to the user or their groups, including duplicate CI remediation tasks, data certification tasks, attestation requests, and lifecycle governance actions generated by CMDB Data Manager and IRE processes.
Option A is incorrect because the Home tab focuses on high-level navigation and featured actions, not task execution. Option B is also incorrect because the Insights tab and feature adoption tiles provide visibility and analytics, not task management.
By centralizing de-duplication tasks in My Work, ServiceNow ensures CMDB governance is embedded into daily operations, improving responsiveness and data quality while maintaining accountability.
Therefore, the correct answer is C - Total status under the My Work tab.

In ServiceNow, protecting CMDB data quality during ingestion is a core Data Foundations principle. The Identification and Reconciliation Engine (IRE) is designed to ensure that CI records are uniquely identified, merged correctly, and protected from unauthorized overwrites. Any ingestion method that bypasses IRE introduces a high risk of duplicates and data corruption.
IntegrationHub ETL is the recommended method because it is natively designed to work with the Identification and Reconciliation API. When properly configured, IntegrationHub ETL ensures that incoming data is processed through IRE, applying identification rules, reconciliation rules, and source precedence. This allows multiple data sources to coexist safely while maintaining CMDB integrity.
Option B (Table API) is explicitly discouraged for CMDB ingestion because it writes directly to CMDB tables and bypasses IRE entirely, making it one of the most common causes of duplicate and conflicting CI records. While REST and SOAP APIs are powerful, they are not safe for CMDB ingestion unless they explicitly invoke the IRE API, which most generic table integrations do not.
Option C (Import Sets and Transform Maps) can be configured to call IRE, but this requires additional scripting and strict governance. Because of this complexity and higher risk of misconfiguration, it is not the recommended approach when safer, purpose-built options exist.
Therefore, IntegrationHub ETL is the verified and best-practice answer, making Option A correct.

The fastest and most supportable time-to-value option is the SCCM Service Graph Connector . Service Graph Connectors are purpose-built integrations for bringing third-party source data into the CMDB using ServiceNow-supported mappings, Identification and Reconciliation Engine processing, source tracking, and standardized class alignment. For SCCM specifically, the SCCM Service Graph Connector avoids the technical debt of building custom JDBC imports, transform maps, and scripts. Import sets and transform maps can work, but they require more implementation effort and create higher risk if IRE is not correctly invoked.
IntegrationHub ETL with RTE is a stronger pattern than raw imports, but for SCCM the dedicated Service Graph Connector is still the fastest and most governed solution. SCCM Usage Metering Spoke is not the CMDB ingestion tool for Windows computer CI data. Therefore, D is correct.