Removing obsolete or inactive CIs from the CMDB must be handled carefully to avoid data loss, audit issues, and unintended operational impact. InServiceNow, the recommended and governed approach is to use anarchive policy.
Archive policiesare designed to manageCI lifecycle cleanupbased on defined conditions such as class, last updated date, lifecycle status, or operational state. In this scenario, the condition would targetLinux Server CIsthat have not been updated in six months. Archive policies can either archive or permanently delete records in a controlled, auditable manner, ensuring compliance with data retention and governance standards.
Creating abusiness rule(Option A) is strongly discouraged for bulk CMDB cleanup because it introduces technical debt, upgrade risk, and unpredictable side effects. Ascheduled job(Option C) may automate execution but lacks governance logic and lifecycle awareness on its own.
Archive policies integrate withCMDB Data Manager, provide visibility into actions taken, and support approval and rollback where appropriate. This aligns fully with Data Foundations best practices for maintaining alean, accurate, and trusted CMDB.
Therefore, the correct and recommended action isB - Create an archive policy.

In Data Foundations, "Insight" includes measuring CMDB health in ways that are actionable-so teams can identify where data is degrading and prioritize remediation. Stale CIs (records that are no longer current, not updated, or no longer exist in the environment) are a common source of CMDB risk: they distort reporting, mislead impact analysis, and create noise for operational processes. Reducing staleness supports higher trust in the CMDB and better decision-making.
On the CMDB Health Dashboard, stale CI concerns align most closely with Compliance because staleness is fundamentally about whether CIs continue to meet defined governance expectations over time-such as update frequency, lifecycle status controls, and adherence to rules that indicate whether records are still valid.
Compliance scorecards typically highlight rule-based adherence to standards (for example, policies or health rules indicating that certain CI types must be recently updated or must not exceed staleness thresholds). This makes Compliance the right place to monitor and improve staleness.
By contrast, Completeness focuses on whether required attributes are populated (for example, owner, environment, support group). Correctness focuses on whether values are accurate and relationships make sense. While stale records can indirectly affect correctness, the dashboard tracking of "stale" is primarily treated as a governance adherence issue-whether the CMDB is being maintained according to lifecycle and freshness expectations-therefore it is surfaced through the Compliance scorecard.

The correct answer is Certification because the team is validating a specific CI attribute or relationship:
whether each server is correctly associated with its location. Data Certification is used when assigned users must review and validate specific field values on CI records, such as location, support group, lifecycle status, environment, or ownership. If incorrect, the certifier can update or correct the data. Attestation would be correct only if the question asked users to confirm that the CI still exists or is still valid in general. This question is more precise: the location association must be confirmed, which is an attribute-level validation requirement. Delete, Archive, and Retire are lifecycle policy types used to remove, archive, or transition records, not validate field accuracy. Therefore, Certification is the correct CMDB Data Manager policy type.
=========

CMDB 360 / Multisource CMDBextends the standard IRE by enablingDynamic Reconciliation Rules, which determine attribute values dynamically based on incoming data patterns rather than fixed source priority.
Within theCreate Reconciliation Rulewizard, two supporteddynamic rule typesare:
Most Reported(Option B): selects the attribute value that is reported most frequently across all sources. This is useful when multiple sources contribute data and consensus is a strong indicator of correctness.
Last Updated(Option C): selects the most recently updated value, which is useful for rapidly changing attributes such as IP address or operational state.
Option A (Smallest Value) and Option D (Last Created) are not supported dynamic reconciliation rule types in ServiceNow.
Dynamic reconciliation rules are particularly valuable in complex, multisource environments where rigid source precedence is insufficient anddata confidence must be inferred.
Therefore, the correct answers areB - Most ReportedandC - Last Updated.

Identification rules are configured through CMDB CI Class Manager . These rules define how the Identification and Reconciliation Engine determines whether an incoming CI already exists or whether a new CI record should be created. For server records, identification rules usually rely on attributes such as serial number, name, hostname, hardware identifiers, or other class-specific criteria. If these rules are weak or missing, duplicate server records can be created during Discovery, Service Graph Connector imports, or other integrations. The CMDB Health Dashboard detects health issues such as duplicates, but it is not where identification rules are configured. CMDB Workspace provides operational access to CMDB capabilities, but CI Class Manager is the correct configuration location. CMDB Data Manager governs lifecycle policies, not IRE identification logic. Therefore, the correct answer is B.
=========