To specifically improvedata quality related to CSDM, the most effective and prescribed action is to use theCSDM Data Foundations Dashboard. InServiceNow, this dashboard is purpose-built to assess and improveCSDM alignment, not just general CMDB hygiene.
The CSDM Data Foundations Dashboard focuses onservice modeling readiness, highlighting gaps such as missing service ownership, incomplete relationships between Business Applications and Application Services, unmanaged services, and misaligned lifecycle states. It providesGet Well Playbooksthat guide administrators through structured remediation using Analyze Data, Fix Data, and Govern Data plays-directly tied to CSDM outcomes.
Option C (default CMDB Health Dashboard) is valuable, but it measuresgeneric CMDB data quality dimensions(completeness, correctness, compliance) and does not specifically evaluateCSDM constructs or service modeling maturity. Option B (ServiceNow Health Scan) provides platform-wide configuration and performance recommendations, but it is not focused on CMDB or CSDM data quality.
Therefore, to improveCSDM-specific data quality, the administrator should use theCSDM Data Foundations Dashboard, makingOption Athe correct answer.

The correct answer is C . In CSDM and Application Portfolio Management, a platform should be modeled as a Business Application with the architecture type Platform Host . Applications that run on or are provided by that platform should be modeled as Platform Applications and should reference the platform host. In this scenario, the ServiceNow Platform is the platform host, while Incident and Change are platform applications because they are capabilities delivered on the ServiceNow Platform. The relationship is not best represented by making all three applications generic web-based applications. That would lose the platform/application distinction. The preferred model is also not simply a Depends On relationship, because CSDM provides a more specific platform host reference model for this use case. Therefore, ServiceNow Platform should be Platform Host, and Incident and Change should be Platform Applications referencing ServiceNow Platform.
=========

The correct answer is Relationship Map. In CMDB Workspace, the Relationship Map is used to visualize how Configuration Items are connected through CMDB relationships. This is useful when a Configuration Manager needs to understand dependency paths, parent-child relationships, hosted-on relationships, application-to-infrastructure relationships, or other CI-to-CI connections. Unified Map is more service- oriented and is typically used to understand the composition of a service and related operational context.
Business Service Map is focused on service-level visualization rather than general CI relationship inspection.
Since the question asks specifically how CIs are connected to each other, the most precise tool is the Relationship Map.

This question tests understanding of how the Identification and Reconciliation Engine (IRE) evaluates incoming CI data against Identification Rules and their priority order in ServiceNow.
From the identification rule shown:
Serial number (+ type) # Priority 100
Serial number # Priority 200
Name (Hardware) # Priority 300
MAC address + name (Network Adapter) # Priority 400
For a CI to be identified and matched, the incoming record must satisfy one complete identifier entry exactly as defined for that class.
CI1 (Name match only)
Although the name matches an existing Hardware CI, name alone is a low-priority identifier (300) and is not sufficient to uniquely identify a Hardware CI unless no higher-priority identifiers exist and the identifier entry criteria are fully satisfied. In practice, Hardware identification relies on serial number-based identifiers, not name-only matching, to avoid false positives. Therefore, CI1 cannot be confidently matched and is inserted as a new record.
CI2 (IP address match)
IP address is not part of any Hardware identification rule shown. IP address is typically used for discovery correlation or network relationships, not as a primary Hardware identifier. Since no identifier entry includes IP address, CI2 does not match any valid identification rule and is also inserted as a new record.
Because neither CI satisfies a valid identifier entry, both records are inserted as new CIs.

Within ServiceNow CMDB governance,AttestationandData Certificationserve distinct but complementary purposes. The key difference lies inwhat is being validated.
Attestationis focused onexistence and ownership confirmation. When a CI is attested, the assigned user or group is asked to confirm that the CIstill exists, is still relevant, and is still owned or managed by the appropriate team. No detailed attribute-level validation is required. This lightweight process is commonly used to prevent "ghost CIs" from lingering in the CMDB.
Data Certification, on the other hand, is more rigorous. It requires the certifier tovalidate specific attributesof the CI, such as lifecycle status, support group, environment, or service relationships. Certification ensuresdata correctness and completeness, which directly impacts CMDB Health scores and downstream processes like Change and Incident Management.
Options A, B, and C incorrectly describe these mechanisms or their assignment and scheduling capabilities.
Both attestation and certification can be scheduled and assigned flexibly, but theirvalidation depthis what truly differentiates them.
Therefore,Option Dcorrectly describes the distinction: attestation confirms existence, while data certification validates CI attributes.