The correct answers are C and D. Identification and reconciliation rules are essential because they control how incoming CI data is matched to existing records and how updates from different sources are reconciled. This prevents duplicate CIs and ensures that authoritative sources update the correct attributes. CI Class Manager is also required because it provides governance over CI class structure, attributes, and inheritance. Standardized CI classes prevent each source from classifying the same real-world object differently. Option A is the cause of the problem, not the solution. Option B introduces avoidable technical debt because custom scripts are harder to govern, maintain, and upgrade. A Data Foundations-aligned solution uses standard class governance plus IRE rules to enforce consistency across all sources.

=========

Delete and archive policies are designed for end-of-life CMDB lifecycle governance. They should apply to records that are no longer active operational CIs and have reached an appropriate retired state. End of Life - Retired is the correct lifecycle state because it indicates that the CI has completed its useful operational lifecycle and can be governed through archival or deletion according to retention rules. Applying delete or archive policies to Inventory - Available records would be dangerous because those CIs may still be valid and usable. “In any lifecycle state” is wrong because unrestricted archival or deletion can remove active, dependent, or operationally important records. “Missing - Stolen” is more aligned with asset disposition and exception handling, not the standard CMDB Data Manager delete/archive target state. Therefore, these policies should affect servers in End of Life - Retired.

=========

IntegrationHub ETL is a ServiceNow data-ingestion application used to extract data from external sources, transform it through defined mappings, and load it into the CMDB. Its Robust Transform Engine provides a guided, low-code mechanism for mapping source data to appropriate CMDB classes, attributes, and relationships.

A major Data Foundations advantage of IntegrationHub ETL is its integration with the Identification and Reconciliation Engine. Incoming records can be processed through identification and reconciliation rules so that existing CIs are updated correctly, duplicate creation is reduced, and source-authority controls are respected.

Agent Client Collector is used to gather inventory and telemetry from devices through an installed endpoint agent. Service Mapping builds Application Service topology and dependency relationships; it is not the general ETL application for importing data from multiple external sources.

The guide identifies IntegrationHub ETL as the recommended method for importing external data through the Identification and Reconciliation API when a dedicated Service Graph Connector is not the applicable solution.

CMDB Workspace provides governed experiences for both duplicate remediation and CMDB Data Manager policy administration. Duplicate CI records can be investigated and remediated through the de-duplication dashboard in CMDB Workspace. This purpose-built interface centralizes duplicate identification, comparison, prioritization, and controlled remediation rather than forcing administrators to use generic task lists.

CMDB Data Manager is also available from the Management area of CMDB Workspace. An authorized administrator can create, publish, and manage policies, including certification policies that validate designated CI attributes and generate tasks for responsible users.

Discovery execution is performed through Discovery administration capabilities, not CMDB Workspace. New class creation is performed through CI Class Manager rather than being one of the direct CMDB Workspace actions tested here. Therefore, A and D are correct.

=========

The correct answer is CMDB Workspace. Service Graph Connector Central is designed to improve visibility into Service Graph Connector activity and source contribution within the CMDB operating experience. Since the objective is to understand data sources contributing to the CMDB, the functionality is surfaced in CMDB Workspace rather than a separate Service Graph Connector Workspace or Discovery Admin Workspace. CMDB Workspace is the central workspace for managing CMDB data quality, source visibility, health, governance, and operational CMDB activities. Discovery Admin Workspace is focused on Discovery configuration and operations, not central CMDB source insight. Therefore, once the Service Graph Connector Central plugin is installed, the related tab is available in CMDB Workspace.

=========

The correct option is Allow fallback to parent’s rules . In CI identification, ServiceNow evaluates the configured identification rule for the target class first. If the Tomcat rule cannot find a match using its class-specific criterion attributes, fallback behavior allows the Identification and Reconciliation Engine to attempt matching against the parent class identification rule. Since Tomcat is a more specific application class, falling back to the parent Application identification rule helps prevent unnecessary duplicate records when a match cannot be made at the subclass level. “Applies to” defines the class or scope for the identifier entry. “Independent” controls whether a rule is evaluated independently rather than through parent inheritance. “Criterion attributes” are the fields used for matching, not the fallback setting. Therefore, the correct configuration is Allow fallback to parent’s rules .

=========

Data Foundations emphasizes that “ingest” must produce CMDB data that is standardized, supportable, and upgrade-safe. When introducing custom CIs, the best practice is to reuse the most appropriate existing CI class (or an approved industry-aligned model) and only add what is necessary—this keeps the data model aligned with platform expectations and reduces downstream rework.

Option B supports this directly: the CMDB CI Class Models application is intended to help teams select a suitable existing class rather than inventing new classes unnecessarily. Reusing existing classes improves consistency across integrations, Discovery/Service Mapping patterns, reporting, and CMDB Health rules—reducing technical debt and making future platform upgrades smoother.

Option A is also aligned with best practice when used correctly: once you have the right CI class, extending that class to add additional attributes (new fields) is a standard, upgrade-safe customization approach. It preserves the underlying platform data structures and avoids breaking out-of-box behaviors, identification/reconciliation practices, and CMDB Health evaluations.

Option C is not appropriate because Asset tables serve a different purpose (financial/lifecycle tracking) than CI tables (operational/service context). Mixing CI attributes into Asset classes creates confusion and process misalignment. Option D is strongly discouraged because repurposing and renaming base attributes creates long-term ambiguity, breaks shared semantics, and increases upgrade and maintenance risk.

In ServiceNow, the Compliance dimension of the CMDB Health Dashboard is driven by Data Certification. To surface meaningful compliance results—such as identifying servers that are not on the latest patch—the platform requires a combination of Certification Policies, Data Filters, and Scheduled Jobs.

Certification Policies define what data must be validated and which attributes are subject to compliance checks (for example, patch level, OS version, or last update date). Data Filters scope the population—such as server classes only—ensuring the compliance evaluation targets the correct CIs. Scheduled Jobs automate when certifications run, keeping compliance scores current and reflective of the latest state.

Options A and C are incorrect because audits and stale/orphan/duplicate checks relate to other health dimensions (correctness and completeness), not compliance. Option B focuses on service modeling and group alignment, which does not directly drive compliance scoring for patch currency.

Therefore, configuring Certification Policies, Data Filters, and Scheduled Jobs is required to accurately measure and display patch compliance on the CMDB Health Dashboard.

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.

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.