Explanation:

When transitioning to CSDM-aligned lifecycle management, ServiceNow introduces a structured lifecycle framework that separates high-level intent from detailed operational state.
Life Cycle Stage represents the macro phase of a CI's existence (for example: Plan, Build, Deploy, Operate, Retire ).
Life Cycle Stage Status refines that phase with granular, sub-level states that vary by CI type.
Life Cycle Object determines which lifecycle stages and statuses apply, based on what kind of CI is being managed (hardware, application, document, etc.).
Life Cycle Mapping ensures a safe transition from legacy status fields by translating existing values into standardized CSDM lifecycle values-avoiding data loss or process disruption.
Together, these objects enable consistent lifecycle governance, improve reporting accuracy, and support automation across ITSM, ITOM, and IRM use cases-while remaining backward compatible with legacy CMDB data.

Life cycle mappings are used to review how legacy CMDB status values correspond to the newer CSDM life cycle stage and life cycle stage status model. This is a key governance activity during transition from older status fields to CSDM-aligned lifecycle management. The mapping layer allows administrators to understand and control how legacy operational values translate into standardized lifecycle stages and stage statuses. This prevents inconsistent reporting, incorrect CI retirement behavior, and confusion between old and new status models. A choice list only stores selectable values and does not provide the mapping relationship between legacy status and CSDM lifecycle fields. Life cycle properties may control behavior but do not serve as the review location for legacy-to-CSDM value alignment.
Therefore, when reviewing equivalent legacy status and CSDM lifecycle values, the correct location is Life cycle mappings.

In ServiceNow Data Foundations, specifically within CMDB Data Manager, policies are used to enforce data quality, completeness, and governance across configuration items (CIs). When defining a Data Manager policy, administrators can configure task creation for non-compliant records and specify how those tasks are assigned. One key configuration is the Assignment type, where "User Group Field" allows assignment to a group dynamically based on a group reference field on the CI record.
Out of the box, ServiceNow provides two default and universally available group reference fields for this purpose:
* Assignment Group
* Managed By Group
These two fields are considered core CMDB governance fields and are consistently available across most CI classes. They align directly with ITIL 4 Service Configuration Management and CSDM accountability models, ensuring that remediation tasks are routed to teams responsible for operational ownership or technical management of the CI.
* Assignment Group (Correct - D)This is the most commonly used operational field in ServiceNow. It represents the team responsible for working on tasks related to the CI and is fully supported by CMDB Data Manager for automated task assignment.
* Managed By Group (Correct - C)This field represents the group accountable for managing the CI throughout its lifecycle. It is a standard CMDB field and is explicitly supported by Data Manager policies for governance-driven task routing.
The other options are not default Data Manager assignment fields:
* Owned by Group is often added through extensions or governance customization and is not guaranteed to exist across all CI classes.
* Support Group is a CSDM and ITSM operational concept, commonly derived or mapped, but it is not a default group reference field exposed for CMDB Data Manager task assignment.
From a Data Foundations and CSDM governance perspective, using Assignment Group and Managed By Group ensures consistent accountability, scalable automation, and alignment with CMDB best practices.

InServiceNow, validating whether Configuration Items (CIs) still exist is a coreCMDB governanceactivity.
Over time, environments change rapidly-servers are decommissioned, cloud resources are torn down, and applications are replaced. If existence validation is not enforced, the CMDB quickly fills with obsolete or
"ghost" CIs.
Attestation policiesare specifically designed to address this need. An attestation policy automatically generates and assigns tasks to responsible users or groups, asking them toconfirm that a CI still exists and is still relevant. This process focuses on acknowledgment rather than deep data validation, making it lightweight and scalable across large CMDBs.
Certification policies (Option A) are used whenspecific attributes must be validated, such as lifecycle status, support group, or environment. While important for data correctness, certification is not intended solely to confirm CI existence. Delete (Option B) and Retire (Option C) policies are lifecycle actions that remove or transition records, but they do not validate existence before taking action.
Attestation integrates cleanly with CMDB Workspace, assigns tasks automatically, and supports auditability- ensuring accountability for CI ownership. This makes it the correct and Data Foundations-aligned policy type for validating CI existence.
Therefore,Option D - Attestationis the correct answer.

Information Objects in CSDM are used to represent logical data associated with Business Applications.
They are especially important for governance, compliance, privacy, and audit use cases because they describe the type of data a Business Application processes, stores, or transmits. For example, if an application handles personal data, payment card data, or regulated healthcare information, that logical data context should be modeled as an Information Object and related to the Business Application.
Option A is too broad and incorrectly frames the object as general data for a group of CIs. CIs represent technical components, while Information Objects describe logical business data. Option B is too narrow because API exchange data is only one possible technical integration scenario and does not define the purpose of the CSDM artifact. Therefore, the correct purpose is to describe logical data related to Business Applications.