The CMDB Data Foundations Dashboard is paired with Get Well Playbooks that guide administrators through structured remediation. The "Services Have Owners Identified" playbook focuses on closing ownership gaps for services, which is a governance and data correction activity.
Fix Data (Option A) is used to correct missing or incorrect values, such as populating owner fields, assigning responsible groups, or updating relationships. In this playbook, Fix Data actions are required to actually remediate the issue by assigning owners to services.
Govern Data (Option D) is also required because ownership is not a one-time correction-it must be enforced and sustained. Govern Data establishes policies, ownership accountability, and controls (such as certifications or attestations) to ensure services continue to have owners over time and do not regress.
Analyze Data (Option B) is used to understand patterns and root causes, but it does not remediate the issue.
Report Data (Option C) provides visibility and communication, not corrective action.
Therefore, the remediation plays that apply to the Services Have Owners Identified playbook are Fix Data and Govern Data, making Options A and D correct.

Application Service Mapping is a critical capability in ServiceNow for enabling business-aware Change Management. Its primary value is not in identifying physical shutdown sequences or CI locations, but in translating technical changes into business impact.
When an organization plans a data center move, multiple infrastructure components-servers, databases, network devices-may be affected. On their own, these technical CIs provide little insight into business risk.
Application Service Mapping connects these CIs to Application Services and Business Services as defined by the Common Service Data Model (CSDM). This relationship allows Change Managers to see which business services, customers, and processes are impacted by the planned change.
By leveraging service maps, Change Management can answer critical questions such as:
Which customer-facing services may experience downtime?
What revenue-generating or mission-critical services are at risk?
Which stakeholders must be notified or involved in approvals?
Option A is incorrect because service mapping does not determine shutdown order; that is handled by infrastructure planning. Option C focuses on physical location data, which is typically managed through Location CIs and Discovery, not service mapping.
Therefore, the correct answer is B - To understand the business impact of CIs, which aligns directly with ITIL
4, CSDM, and Change Management best practices.

Archive and Retire are the correct CMDB Data Manager end-of-life policy types from the listed options. End-of-life governance in CMDB focuses on handling CI records that are no longer operationally active or no longer required in the active CMDB. A Retire policy is used when CIs should be moved out of active operational status while preserving lifecycle accuracy. An Archive policy is used when records should be removed from active operational use but retained for recovery, audit, or compliance purposes. Disposed and Lost are typically lifecycle status values used in asset or CI lifecycle tracking, not CMDB Data Manager policy types in this context. Decommission describes an operational lifecycle action or state transition, but it is not the Data Manager policy type being tested here.
Therefore, the valid end-of-life policy types are Archive and Retire.

The CMDB Data Manager is the ServiceNow capability responsible for generating actionable governance tasks and assigning them to CI class owners and data stewards. These tasks appear directly in the "My Work" tab within the CMDB Workspace, enabling proactive and role-based CMDB governance.
CMDB Data Manager focuses on data lifecycle management, including archival, retirement, and cleanup of CIs based on defined policies. When lifecycle rules or retention thresholds are met-or when human validation is required-the Data Manager creates tasks to prompt responsible owners to take action. This ensures that CMDB data remains accurate, compliant, and lean over time.
The CMDB Health Dashboard (Option C) provides visibility into health metrics such as completeness, correctness, and compliance, but it does not generate tasks. Similarly, De-duplication templates (Option A) support duplicate identification and remediation workflows, but they do not create ongoing governance tasks in the CMDB Workspace.
By surfacing tasks in "My Work," CMDB Data Manager operationalizes governance and embeds accountability into daily workflows, which is a key principle of CMDB Data Foundations.
Therefore, the correct answer is Option B - CMDB Data Manager.