In CMDB governance, different CMDB Data Manager policy types serve different validation and enforcement purposes. When the objective is to allow an assigned individual to review and update specific fields on a CI record, the correct policy type is Certification.
A Certification policy creates actionable tasks that require the assignee to validate and, if necessary, correct specific CI attributes, such as lifecycle status, support group, environment, or ownership. During certification, the user can directly update CI fields to bring the record into compliance with defined standards.
Attestation (Option C) only asks the user to confirm that a CI still exists or is still valid; it does not require or enable attribute-level updates. Audit (Option A) is used for reporting and evidence collection, not remediation. Compliance (Option D) measures adherence to rules but does not itself generate editable remediation tasks.
Certification is therefore the primary mechanism used when human validation and correction of CI data is required-making it a cornerstone of CMDB data quality management.
Hence, the correct answer is B - Certification.

Comprehensive and Detailed Explanation (200-300 words)
Within ServiceNow Data Foundations, CMDB Data Manager provides multiple policy types to support governance, data quality, and lifecycle management of configuration items (CIs). The scenario described- confirming that servers recorded in the CMDB physically exist in the data center-is a classic example of existence validation and ownership confirmation, which is exactly the purpose of an Attestation policy.
An Attestation policy is designed to request a human validation from a responsible individual or group (such as a data center manager, platform owner, or infrastructure team). The policy generates attestation tasks that require reviewers to explicitly confirm whether a CI is valid, accurate, and still exists. This aligns directly with CMDB governance best practices and ITIL 4 Service Configuration Management, where periodic verification ensures trust in the CMDB as a system of record.
The other policy types do not meet this requirement:
* Certification is typically used to validate compliance with defined data standards (e.g., mandatory fields populated), not physical existence.
* Delete, Archive, and Retire are lifecycle actions, used after a CI has already been identified as obsolete or no longer required.
* None of these options involve human confirmation of real-world existence.
From a CSDM and Data Foundations perspective, attestation supports:
* CMDB accuracy and credibility
* Audit and regulatory compliance (especially critical in financial services)
* Clear accountability for CI ownership and validation
Therefore, when the goal is to confirm that servers actually exist, the correct and fully aligned CMDB Data Manager policy type is Attestation (E).

In the CMDB class hierarchy, Server is a generic parent class, while Linux Server and Windows Server are more specific child classes. When ServiceNow Discovery detects sufficient evidence (such as OS signatures) to move a CI from a generic class to a more specialized one, this action is called a Class Upgrade.
A Class Upgrade occurs when a CI is reclassified down the hierarchy into a more specific subclass, enriching the record with additional attributes, behaviors, and discovery patterns appropriate to that class. This is a standard and expected behavior in mature CMDB implementations and aligns with Data Foundations best practices.
A Class Switch would imply lateral movement between unrelated classes, which is not what happens here. A Class Downgrade would move a CI from a specific class back to a more generic one, typically when discovery confidence is reduced-not the case in this scenario.
By performing class upgrades automatically, Discovery improves CMDB accuracy, reporting precision, and service mapping quality without manual intervention.
Therefore, the correct answer is C - Class Upgrade.

Explanation:
Agent Client Collector
Automated agent-based solution running patterns
Import Sets
Organization-built solution using transform maps
Service Graph Connector
Pre-built store integration solutions that require minimal customization ServiceNow Discovery Automated agentless solution running patterns Agent Client Collector: This is ServiceNow ' s agent-based approach. It requires a software agent to be installed on the target host to run discovery patterns locally.
Import Sets: This is the traditional, manual way to bring in data. You define the source, and the organization builds the logic (Transform Maps) to move that data into the CMDB.
Service Graph Connector: These are found in the ServiceNow Store. They are " certified " integrations built to work with specific third-party vendors (like SCCM or Jamf) with minimal setup.
ServiceNow Discovery: The classic agentless method. It probes the network and uses patterns to identify and map CIs without needing software installed on every machine.

A CMDB delivers business value when it enables better outcomes across IT and enterprise service delivery- especially when aligned with CSDM so services, offerings, and supporting technology are connected in a consumable model. Two major business values are improved operational execution and improved business continuity.
Option C is a direct business value: a trusted CMDB improves incident and change management by providing accurate CI details, relationships, and service context. This supports faster triage and assignment, better prioritization, and higher-quality impact analysis for changes. When incidents and changes are informed by dependable configuration data, organizations reduce downtime, avoid unnecessary escalations, and make safer change decisions-benefits that the business experiences as higher service quality and fewer disruptions.
Option D is also a core business value: CMDB strengthens operational resiliency by enabling clearer dependency understanding and faster response to failures. Resiliency improves when teams can quickly identify what's impacted, understand upstream/downstream relationships, and plan mitigation steps using known service-to-technology mappings. In regulated or mission-critical environments, this translates into better continuity, reduced risk exposure, and improved compliance reporting.
Option A can be beneficial, but it is more of a technical/operational mechanism than a primary "business value" statement in Data Foundations framing. Option B is primarily the domain of IT Asset Management and financial systems; while CMDB can relate to assets, it is not the system of record for financial management.
Hence, the best two business values are streamlining incident and change management and strengthening operational resiliency.