Explanation:

TheCommon Service Data Model (CSDM)organizes CMDB data into domains that reflect how services areplanned, delivered, and consumed. Correct placement of objects is essential for reporting, ownership, and downstream ITSM, ITOM, and IRM use cases.
Design and Planning domain # Business Process
Business Processes describehow the business operatesand what capabilities are required. These are planning constructs used to design services and applications before they are built or delivered.
Foundation domain # Business Application
Business Applications are foundational reference objects that representwhat applications existandwho owns them. They anchor ownership, lifecycle, and governance but are not directly operational.
Service Delivery domain # Application Service
Application Services representrunning, operational technical services(often created via Service Mapping).
They are central to Incident, Change, and Event Management, making them part of Service Delivery.
Sell / Consume domain # Business Service
Business Services representwhat is offered to customers or consumers. They define value delivery, SLAs, and consumption context, which is why they belong in the Sell/Consume domain.
This mapping aligns withCSDM v5 guidanceand ensures clear separation betweenplanning constructs, foundational records, operational services, and consumer-facing services-a key principle for a scalable and governed CMDB.

TheCMDB Data Managerperforms governance activities such ascreating, publishing, and managing lifecycle policies(archival, certification, attestation, cleanup) to ensure long-term CMDB health. These activities are executed within theCMDB Workspace, specifically under theManagement tab.
InServiceNow, theCMDB Workspace - Management tabis the centralized location for CMDB governance operations. From here, Data Managers can define policy logic, assign ownership, schedule execution, monitor outcomes, and manage remediation tasks generated by those policies.
Option A (CMDB 360 tab) focuses onvisibility and analysisof CI data and relationships, not policy authoring.
Option B (Service Operations Workspace) is used for operational response and service monitoring, not CMDB governance. Option C (CI Class Manager) is used to define class hierarchy and ownership, but it does not manage lifecycle policies.
Therefore, the correct location for CMDB Data Manager policy management isCMDB Workspace - Management tab, makingOption Dcorrect.

Explanation:

Enhancing Incident Management inServiceNowoften involves integrating complementary products that enrichcontext, prioritization, and decision-making.
Discoverystrengthens incident resolution by automatically populating accurate CI data and relationships, allowing responders to quickly understand affected infrastructure and applications.
Hardware Asset Management (HAM)adds visibility into asset lifecycle, ownership, and maintenance actions, which is especially valuable when incidents involve physical devices or failures.
Risk Management(part of IRM) provides insight intobusiness and financial risk exposure, helping teams prioritize incidents based on potential regulatory, safety, or financial impact.
Service Portfolio Management (SPM)connects incidents to theservice lifecycle, enabling better understanding of whether an incident affects a live, retiring, or planned service-and improving communication with stakeholders.
Together, these integrations transform Incident Management from a reactive process into acontext-rich, business-aligned capability.

This question tests understanding ofreconciliation source priorityin theIdentification and Reconciliation Engine (IRE)inServiceNow.
In reconciliation rules,lower numeric values represent higher priority. Therefore, the priority order is:
ServiceNow (100)- highest authority
Altiris (200)
SCCM (300)- lowest authority
Why A is correct
BecauseAltiris (200)hashigher priority than SCCM (300), data from Altiriscan update records originally inserted by SCCM. This is exactly how reconciliation precedence works-higher-priority sources can overwrite lower-priority ones.
Why C is correct
SCCM, even though it has thelowest priority, is still anauthorized discovery source. Itcan insert new recordsinto the Windows Server table when no existing CI is identified. Priority only affectsupdates, not the ability to create records.
Why B is incorrect
ServiceNow (priority 100)can update records from Altiris and SCCMbecause it has the highest priority. The statement incorrectly claims it cannot.
Why D is incorrect
SCCM doesnothave the highest authority. Ahigher numeric value means lower priority, so SCCM cannot update records created by higher-priority sources.

Explanation:

InServiceNow, duplicate CI management spansdetection, insight, and remediation:
TheCMDB Health Dashboard - Correctnesssurfaceswhere duplicates existand their impact, providing visibility and prioritization.
Certification Taskssupportgoverned resolution, allowing assignment to individuals or groups to validate and correct data.
De-duplication Templatesenablebulk remediation, ideal when standardized merge rules can be applied across many duplicates.
TheDuplicate CI Remediatoroffers aguided, record-by-record wizard, preserving relationships and history for safer individual resolutions.
De-duplication Tasksare the work items generated by these processes, but they do not themselves represent an outcome-hencenot applicable.
This mapping aligns withCMDB Data Foundations best practices, ensuring duplicates are identified, prioritized, and remediated efficiently and safely.