ServiceNow CIS-DF Certified Implementation Specialist - Data Foundations (CMDB and CSDM) Exam Practice Test

IntegrationHub ETL provides a guided, low-code Extract, Transform, and Load experience. Administrators can define a source, map source fields and relationships to ServiceNow target structures, transform the data through the Robust Transform Engine, and execute recurring imports.

It also integrates with the Identification and Reconciliation Engine for CMDB targets. Incoming CI data is processed against identification rules to determine whether a record should be inserted or updated. Reconciliation rules and source precedence then control whether the source is permitted to update specific attributes.

IntegrationHub ETL does not inherently require SQL or extensive scripting for normal transformations. It also does not replace Discovery or Service Mapping. Discovery actively identifies infrastructure and technical relationships, while Service Mapping builds application-service topology. IntegrationHub ETL primarily imports and transforms data supplied by an external source.

=========

When building advanced CMDB queries using CMDB Query Builder in ServiceNow, the correct approach is to model CI scope, relationships, and task context explicitly on the canvas.

To limit results to databases in a specific location, the administrator must filter the Database CI node by the Location attribute. Therefore, Option C is required to scope the query to Database CIs where Location = Seattle.

To include Incidents related to those databases, the Incident table must be added from the Non-CMDB Tables list and linked through the task_ci relationship. This is exactly what Option A provides. CMDB Query Builder separates CMDB tables (CIs) from task and transactional tables, so incidents must be explicitly added from the Non-CMDB section.

Option B is incorrect because property columns on Application Services do not scope databases or incidents. Option D is unnecessary because relationship depth alone does not include non-CMDB task data and does not filter by location.

Thus, the correct actions are A (add Incident table) and C (filter Database by location).

Service Graph Connectors are a key Data Foundations ingestion capability in ServiceNow. They provide out-of-the-box, upgrade-safe integrations that ingest data into the CMDB using the Identification and Reconciliation Engine (IRE), ensuring data quality and source governance.

Two primary categories of Service Graph Connectors are:

Cloud (Option A): These connectors integrate with major cloud providers and platforms (such as AWS, Azure, and GCP) to ingest infrastructure, platform, and service data into the CMDB. They are essential for managing hybrid and multi-cloud environments and maintaining accurate cloud CI relationships.

Observability (Option B): These connectors integrate with monitoring and observability tools (such as APM, infrastructure monitoring, and telemetry platforms). They provide near-real-time operational data that enriches CI records and supports incident correlation, impact analysis, and service health insights.

Option C (DevOps) is incorrect because DevOps integrations are typically handled through CI/CD tools and workflow integrations rather than Service Graph Connectors. Option D (Workflow Automation) is unrelated; Service Graph Connectors focus on data ingestion, not process orchestration.

Therefore, the correct connector categories are Cloud and Observability, making Options A and B the correct answers.

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.

=========

Discovery and Service Mapping are the correct answers because both capabilities can automatically create CMDB relationships that support Application Services. ServiceNow Discovery identifies infrastructure, applications, running processes, and dependencies in the environment. During discovery, it can create technical relationships between discovered CIs, such as servers, applications, databases, and other supporting components. Service Mapping extends this further by building application service topology, identifying how application components interact, and creating the relationship model that connects CIs into an Application Service. These relationships are essential for impact analysis, change risk assessment, incident correlation, and service-aware operations. Event Management does not create application-service CI relationships; it correlates operational events and alerts. Data Manager governs lifecycle, attestation, certification, archival, retirement, and deletion policies, but it does not discover application topology. IntegrationHub ETL can ingest and transform external CMDB data, but it does not automatically discover service relationships in the same way Discovery and Service Mapping do. Therefore, Discovery and Service Mapping are the ServiceNow solutions that automatically create these relationships.

A CMDB Data Foundations Dashboard playbook provides a Problem Overview and information about likely Root Causes . The Problem Overview explains the deficient metric, why the condition matters, and the operational or governance risks created by poor performance. The Root Cause material helps administrators identify why the condition exists, such as incomplete source data, incorrect transformations, missing ownership, inappropriate class usage, or weak governance controls.

The guide describes these playbooks as structured, prescriptive guidance for identifying root causes, assessing ingestion and governance gaps, and applying appropriate corrective actions.

Playbooks may recommend analysis, correction, reporting, and governance activities, but they do not normally provide fully automated remediation scripts that should be executed without review. “Problem Analysis” is not the named documentation component tested here; analysis is instead performed through the recommended remediation plays.

=========

Retire and Archive are supported CMDB Data Manager policy types. A Retire policy manages the lifecycle transition of CIs that should no longer be considered active or operational. An Archive policy removes eligible records from active CMDB use while retaining them according to configured retention and restoration requirements.

CMDB Data Manager also supports other policy types, including Attestation, Certification, and Delete. Together, these policies automate CI lifecycle management, validation, retention, and governed cleanup.

De-duplication is handled through duplicate-identification and remediation capabilities, such as de-duplication templates, tasks, and the Duplicate CI Remediator. It is not a CMDB Data Manager policy type. Reconciliation is configured through the Identification and Reconciliation Engine and determines source authority and attribute update precedence; it is also not a Data Manager lifecycle policy.

Therefore, from the options provided, Retire and Archive are correct.

=========

The Unified Map is designed to provide enhanced visual insight and analysis across the CMDB by consolidating configuration item (CI) relationships from multiple sources—such as Discovery, Service Mapping, and manual relationships—into a single, interactive view. While traditional Service Mapping maps are optimized for modeling and understanding application-to-infrastructure dependencies, the Unified Map extends this capability with more flexible visualization and exploration features.

Option B is correct because the Unified Map allows users to zoom in and out, enabling both high-level overviews and detailed inspections of complex CI relationships. This capability is particularly valuable in large enterprise environments where services may span hundreds or thousands of infrastructure components. Zoom functionality supports impact analysis, troubleshooting, and architectural reviews without overwhelming the user with unnecessary detail.

Option C is also correct because the Unified Map supports filtering of map nodes based on user preferences. Administrators and analysts can filter by CI class, relationship type, lifecycle state, or other attributes, allowing them to focus on what is most relevant to their task—such as identifying only production CIs, security-relevant components, or a specific technology stack. This aligns strongly with Data Foundations principles by improving usability and decision-making without altering underlying data.

Option A is incorrect because modifying the number of levels displayed is a characteristic more closely associated with Service Mapping configuration rather than an added Unified Map capability. Option D is incorrect because visibility into an application and its host is a core Service Mapping function, not an enhancement unique to the Unified Map.

In summary, the Unified Map adds value by improving interactivity, flexibility, and user-driven insight across the CMDB.

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.

=========

A web server is a software-based CI hosted on underlying server hardware or a virtual machine. The standard ServiceNow relationship is therefore Runs on::Runs . From the Web Server CI’s perspective, it runs on the Server CI. When the same relationship is viewed in the reverse direction, the Server runs the Web Server.

The reverse wording in Option B incorrectly changes the parent-to-child direction. “Uses::Used by” represents a dependency or consumption relationship, not the direct hosting relationship between installed software and its host. Option D reverses that unrelated relationship type.

ServiceNow documentation defines Runs on::Runs as the standard relationship between a software application CI and its hosting hardware or virtual machine, giving Tomcat running on a Linux server as an example. Discovery can automatically identify and load these CI relationships into the CMDB.

=========

The CMDB Data Foundations Dashboard is specifically designed to assess whether foundational CMDB configurations and data practices align with ServiceNow recommendations. It exposes gaps involving required attributes, ownership, relationships, identification practices, ingestion controls, and other foundational conditions.

The dashboard provides actionable metrics and connects deficient results to structured Get Well or remediation playbooks. These playbooks guide administrators through understanding the problem, identifying affected records and sources, correcting the data, and implementing controls that prevent recurrence.

CMDB Workspace is the broader operational interface. CMDB Data Manager governs CI lifecycle policies such as certification, attestation, retirement, archival, and deletion. The CMDB Health Dashboard calculates health dimensions such as completeness, correctness, and compliance, but it does not provide the same curated assessment of alignment with recommended Data Foundations practices.

=========

The query must contain the Application Service and Configuration Item nodes, the appropriate relationship between those nodes, and filters that restrict the results to the named Application Service and operational CIs.

Option A only adds Operational Status and Name as result columns. Displaying a field as a column does not filter records according to that field, so non-operational CIs could still appear.

Option C unnecessarily adds the Business Application class. The requirement is to find CIs belonging to a specific Application Service; no Business Application condition or relationship is required. Adding unnecessary classes can complicate the query and potentially alter its results.

CMDB Query Builder is designed to traverse relationships between CMDB classes. The guide similarly explains that Application Services and their related infrastructure should be represented through a CMDB query and connected through CMDB relationships.

Therefore, the correct sequence is Option B.

=========

In CSDM 5, production line monitoring systems (such as SCADA, MES, IoT telemetry platforms, and operational monitoring tools) are technical systems responsible for operating, monitoring, and supporting services, not for designing them or consuming them. These systems directly align with the Service Delivery (Manage Technical) domain.

The Service Delivery domain is used to model how services are technically delivered and operated, including the infrastructure, platforms, and operational technologies that ensure availability, performance, and reliability. In a manufacturing context, production line monitoring systems continuously observe equipment health, throughput, alerts, and operational metrics—making them part of the technical service delivery layer.

Option A (Build and Integration) applies to CI/CD pipelines and system construction activities. Option B (Foundation) focuses on base CIs such as locations, people, and organizations. Option C (Service Consumption) models how customers or consumers use services, which is not applicable here. Option D (Design and Planning) is used for service architecture and planning artifacts, not live operational systems.

Therefore, production line monitoring systems correctly belong in Service Delivery (Manage Technical), making Option E the correct answer.

The Dynamic CI Group must be populated in the Configuration Item field on the Change Request form. A Dynamic CI Group represents a rule-based group of CIs, such as all Windows servers or all CIs matching a specific operational condition. When a Change needs to apply across multiple CIs, referencing the Dynamic CI Group in the Configuration Item field allows the platform to associate the Change with the relevant CI population. Service Offering and Business Service describe service context, but they do not represent the target CI group for the technical change. The Configuration Item field is the correct field because Change Management operates against affected configuration items and their dependencies. Therefore, C is correct.

=========

The Asset-CI Field Mapping capability is specifically designed to control synchronization between related Asset and CI records. The Configuration Analyst can create or configure a field-mapping rule so that the Computer CI’s Owned by value is propagated to the corresponding Asset field through the platform’s supported synchronization framework.

CI Class Manager controls CMDB class definitions and does not create parent-child inheritance between Asset and CI tables for field synchronization. A scheduled integration could copy the information, but it introduces unnecessary processing and delay when an out-of-box synchronization mechanism exists. A scripted business rule could also work technically, but it introduces custom code, maintenance effort, and upgrade risk.

Using Asset-CI Field Mapping provides a governed, supportable, and reusable configuration that keeps the operational CI and financial Asset perspectives aligned.

=========

In Data Foundations, “insight” focuses on turning trusted configuration data into clear visual understanding—so teams can assess relationships, troubleshoot impact, and validate service context. Unified Map supports this by providing a graphical view of CIs and their relationships, combining strengths of traditional dependency views and service-mapping-style visualization into a single, consistent map experience.

Unified Map is accessed from CMDB Workspace, typically via a Quick Links entry (and in some experiences, also from relevant CI/service contexts). This location makes sense in the Data Foundations model because CMDB Workspace is the central place where configuration and service data is explored, validated, and used for operational decision-making—exactly what mapping relationships is meant to enable.

The other options do not fit the purpose or access pattern. CI Class Manager is focused on defining and maintaining CI class structures and related class settings; it is not the user entry point for relationship visualization. CMDB Data Manager is focused on governance through lifecycle policies (attestation, archival, deletion) and bulk lifecycle operations—again, not the primary interface for interactive mapping and dependency exploration.

Therefore, for a Configuration Manager seeking to use Unified Map for relationship and dependency insight, the correct access point is CMDB Workspace.

CMDB 360 / Multisource CMDB extends the standard IRE by enabling Dynamic Reconciliation Rules, which determine attribute values dynamically based on incoming data patterns rather than fixed source priority.

Within the Create Reconciliation Rule wizard, two supported dynamic rule types are:

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 and data confidence must be inferred.

Therefore, the correct answers are B – Most Reported and C – Last Updated.

Information Objects in CSDM are used to represent logical data associated with Business Applications. They are especially important for governance, compliance, privacy, and audit use cases because they describe the type of data a Business Application processes, stores, or transmits. For example, if an application handles personal data, payment card data, or regulated healthcare information, that logical data context should be modeled as an Information Object and related to the Business Application. Option A is too broad and incorrectly frames the object as general data for a group of CIs. CIs represent technical components, while Information Objects describe logical business data. Option B is too narrow because API exchange data is only one possible technical integration scenario and does not define the purpose of the CSDM artifact. Therefore, the correct purpose is to describe logical data related to Business Applications.

When transitioning to CSDM-aligned lifecycle management, ServiceNow introduces a structured lifecycle framework that separates high-level intent from detailed operational state.

Life Cycle Stage represents the macro phase of a CI’s existence (for example: Plan, Build, Deploy, Operate, Retire ).

Life Cycle Stage Status refines that phase with granular, sub-level states that vary by CI type.

Life Cycle Object determines which lifecycle stages and statuses apply, based on what kind of CI is being managed (hardware, application, document, etc.).

Life Cycle Mapping ensures a safe transition from legacy status fields by translating existing values into standardized CSDM lifecycle values—avoiding data loss or process disruption.

Together, these objects enable consistent lifecycle governance, improve reporting accuracy, and support automation across ITSM, ITOM, and IRM use cases—while remaining backward compatible with legacy CMDB data.

Business Criticality in the Service Offering is the correct CSDM attribute because the requirement is prioritization based on business impact. Customer-facing services that affect revenue should be modeled and prioritized according to their business importance, not only by technical ownership or affected infrastructure. In CSDM, Service Offerings represent consumable versions of services and can carry important business context such as audience, availability expectations, and criticality. Business Criticality helps Incident, Change, and operational teams understand which services require faster response because disruption would create greater business or customer impact. Assignment Group is used for routing work, not determining service priority. Service classification in a Technical Service describes the nature of a technical service, not customer-facing business impact. Affected CIs identify technical scope, but they do not directly express revenue or business criticality. Therefore, Business Criticality in the Service Offering is the correct prioritization attribute.

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.

Business Application records represent logical applications from a portfolio, ownership, investment, risk, and lifecycle perspective. They are principally used by Application Portfolio Management and Enterprise Architecture to support application rationalization .

Rationalization enables an organization to evaluate applications based on factors such as business value, technical fitness, cost, risk, lifecycle status, capability alignment, and functional redundancy. Decision-makers can then determine whether an application should be invested in, tolerated, migrated, consolidated, replaced, or retired.

Application availability is normally monitored through operational Application Services and their supporting infrastructure rather than through the logical Business Application record. Change impact analysis also relies mainly on Application Services, service maps, and relationships to affected infrastructure CIs.

Because Business Applications belong to the Design and Planning context and provide strategic portfolio information, application rationalization is the appropriate business-decision use case

Bottom of Form

The correct answer is CSDM Data Foundation Dashboard because the requirement is specifically about end-to-end service modeling and guided improvement through status and playbooks. CSDM guidance focuses on modeling services, application services, business applications, offerings, technical services, and their relationships. The CSDM Data Foundation Dashboard provides visibility into CSDM maturity and uses playbooks to guide remediation of weak or missing service-model data. Service Mapping is only one technical capability used to discover and map service relationships; it is not the overall governance dashboard for CSDM adoption. CMDB Workspace is the broader operational workspace for CMDB management, but the question asks for status and playbook-based guidance for CSDM service modeling quality. Therefore, the best reference point is the CSDM Data Foundation Dashboard.

=========

CMDB Data Manager is the governance capability designed to control the lifecycle of CI records through policy-driven actions. Its policy types include Retire, Archive, Delete, Attestation, and Certification. These policies enable obsolete or no-longer-relevant records to be identified and processed consistently rather than removed through uncontrolled scripts or manual cleanup.

Archive policies remove eligible records from active operational use while retaining them for a defined recovery or compliance period. Delete policies permanently remove records after applicable lifecycle and retention requirements are satisfied. Retire policies transition CIs out of active operational status. The guide identifies automated archival and deletion according to retention policies as a primary purpose of CMDB Data Manager.

The CMDB Health and Data Foundations dashboards identify problems but do not perform lifecycle removal themselves. CI Class Manager governs classes, while de-duplication templates address duplicates specifically. Therefore, B is correct.

=========

The CMDB aligns to business processes by giving the organization a trusted operational data foundation. First, it enhances decision-making and operational efficiency because Incident, Problem, Change, Risk, Security, and Service Management teams can assess impact, ownership, dependency, and priority using reliable CI and relationship data. Second, it provides a centralized view of configuration items and relationships , which is the core function of the CMDB. That centralized relationship model is what makes service impact analysis, change risk assessment, outage analysis, and operational routing possible. Tracking software licenses is primarily an IT Asset Management and Software Asset Management concern, not the main CMDB business-process alignment value. Extending service delivery management to all enterprise departments is too broad and belongs more to enterprise service management strategy than core CMDB alignment. Therefore, A and C are correct.

=========

Service Graph Connectors are predefined, vendor-specific integrations that import and synchronize external data with the ServiceNow CMDB. They are generally delivered through the ServiceNow Store and use standardized mappings, supported class models, source tracking, and Identification and Reconciliation Engine processing. This reduces the amount of custom scripting and transformation logic required to integrate third-party platforms.

Agent Client Collector is an agent-based inventory and telemetry collection mechanism. IRE identifies incoming CIs and controls how authorized sources update CMDB attributes, but it is an underlying data-processing engine rather than a packaged external-system integration. Service Mapping discovers and models Application Service dependencies; it is not a library of predefined third-party connectors.

The Data Foundations material describes Service Graph Connectors as prebuilt Store integration solutions requiring minimal customization. It also identifies them as the preferred method for third-party CI ingestion when minimizing technical debt and maintaining upgrade compatibility are priorities.

=========

In ServiceNow, the CMDB Health Dashboard does not calculate health scores in real time by default. Instead, health scores are generated and refreshed by scheduled calculation jobs that evaluate CI data against defined health rules across the dimensions of completeness, correctness, and compliance.

To generate and maintain CMDB health scores, the scheduled jobs for CMDB Health must be active. These jobs periodically scan the CMDB, apply health rules (for example, required attributes populated, lifecycle status compliance, certification results), and calculate scores that are displayed on the dashboard and scorecards. Without these scheduled jobs running, the dashboard cannot produce current or meaningful health metrics.

Option B is incorrect because CMDB health scoring is not automatic or real-time; it depends on scheduled processing. Option C is also incorrect because CMDB Health is part of the core CMDB/Data Foundations capability in ServiceNow and does not require a separate “CMDB health calculation” plugin to be installed in modern implementations.

Activating and maintaining these scheduled jobs ensures that health scores remain accurate, trendable over time, and useful for governance decisions. This is a foundational requirement for using the CMDB Health Dashboard as a data quality improvement tool.

Therefore, the correct answer is A – The scheduled jobs for the CMDB Health Dashboard must be activated.

The correct answer is Use the CMDBTransformUtil API in the transform script . Import Sets and Transform Maps can create duplicate CIs if they write directly into CMDB tables without routing the data through the Identification and Reconciliation Engine. The CMDBTransformUtil API is used in transform scripting to process incoming CI data through the CMDB identification and reconciliation logic. This allows ServiceNow to evaluate existing CIs using configured identification rules and then update the correct CI rather than creating a duplicate record. Coalesce rules are not sufficient for CMDB ingestion because they rely on simple field matching and do not apply the full IRE logic. “Comparison rules” is not the correct mechanism. A system property alone is also not the recommended implementation pattern for vendor shipment import data. Therefore, CMDBTransformUtil is the correct method to prevent duplicate CI creation through import sets.

In ServiceNow, ingesting custom CIs must be done with a strong focus on upgrade safety, governance, and long-term maintainability. Data Foundations guidance explicitly discourages repurposing or overloading base classes, as this creates technical debt and upgrade risk.

Option B is a best practice because the CMDB CI Class Models Store delivers ServiceNow-supported CI classes that align with platform evolution. Before creating or extending classes, administrators should verify whether a suitable class already exists or has been introduced in newer releases. This avoids duplication and ensures future compatibility.

Option D is also correct. When no suitable class exists, extending an existing CI class (under the appropriate parent) to add required attributes preserves inheritance, discovery behavior, reporting, and upgrade compatibility. This approach is preferred over creating entirely new, disconnected schemas.

Option A is incorrect because repurposing base classes and renaming attributes breaks standard semantics, causes confusion, and complicates upgrades. Option C is incorrect because extending Asset tables to represent CIs conflates ITAM and CMDB concerns; assets and CIs serve different purposes and lifecycles.

Therefore, the solutions that minimize technical debt and ensure upgrade compliance are B and D.

The CMDB Integrations Dashboard provides visibility into integrations that populate the CMDB, including Service Graph Connector activity and mapping information. It enables administrators to inspect how source data is mapped to ServiceNow target classes and fields, review connector execution information, and investigate ingestion or mapping problems.

Service Graph Connectors are prebuilt, governed integrations that import third-party data into the CMDB through standardized class mappings and IRE processing. They are intended to minimize custom transformations and preserve source and reconciliation information. The guide describes Service Graph Connectors as upgrade-safe integrations that ingest external data while applying Identification and Reconciliation Engine controls.

Integration Hub is the broader integration and automation framework, not the specific dashboard for reviewing Service Graph Connector field mappings. IntegrationHub ETL is a separate tool for building and managing ETL transformations. It does not serve as the inspection dashboard for mappings belonging to an installed Service Graph Connector.

Therefore, B is correct.

Principal Classes are a key CMDB configuration concept used to control which CI classes are selectable in reference fields across ITSM processes. This helps reduce noise, prevent incorrect CI selection, and improve data quality.

In ServiceNow, Principal Classes are designated within the CI Class Manager. This tool allows CMDB administrators to manage the CI class hierarchy, define ownership, and explicitly mark classes as principal. Once a class is marked as principal, its CIs become available in CI reference fields such as those on Incident, Change, and Problem forms.

Option A (CMDB Workspace) provides operational and analytical views but does not control schema-level class behavior. Option C (System Properties) does not manage class designation. Option D (CMDB Data Manager) governs lifecycle and data quality policies, not reference field behavior.

By configuring Principal Classes in the CI Class Manager, organizations ensure that only relevant, high-value CI classes are exposed to end users, aligning with Data Foundations best practices.

Therefore, the correct answer is B – CI Class Manager.

The two applicable roles are cmdb_dm_admin and cmdb_dm_user . The administrative role provides permission to configure, publish, and manage CMDB Data Manager policies. These policies govern activities such as attestation, certification, retirement, archival, and deletion of CI records.

The user role provides access to the operational work generated by those policies. Assigned users can review and complete applicable Data Manager tasks through the My Work tab in CMDB Workspace.

The alternative role names data_manager_user and data_manager_admin do not represent the CMDB Data Manager roles tested in this question. The distinction is important: policy administrators configure governance controls in the Management area, while task users act on the resulting assignments. CMDB Data Manager therefore separates policy administration from task execution through these two roles.

=========

The correct answer is Data Quality Scheduled Job because CMDB data quality checks are not simply visual or manual activities. Scheduled jobs are used to execute recurring evaluations that calculate and refresh quality indicators for CI records. These jobs support CMDB health and data quality by periodically checking records against configured rules, such as stale records, missing required attributes, compliance conditions, or correctness-related metrics. CMDB Workspace is the interface where users can review and act on CMDB information, but it is not itself the mechanism that performs scheduled quality evaluation. Business rules can enforce logic during insert or update actions, but they are not the normal mechanism for recurring CMDB data quality calculation. Therefore, the Data Quality Scheduled Job is the best answer.

=========

The Unified Map in ServiceNow provides a consolidated view of services and their underlying components, integrating Discovery and Service Mapping data. To make this view actionable, Service Owners can apply filters to focus on relevant elements and reduce visual noise.

Filtering by CI type (Option A) is a core capability. It allows the Service Owner to show or hide categories such as servers, databases, load balancers, or applications—making it easier to analyze specific layers of the service.

Filtering by Business Criticality (Option D) is also available and highly valuable. This enables Service Owners to prioritize views around high-impact components, ensuring attention is focused on CIs that pose the greatest risk to service delivery.

Option B (Discovery source) is not typically exposed as a Unified Map filter because the map focuses on operational and service context, not ingestion provenance. Option C (Managed by group) is a governance attribute and is not a standard visual filter within the Unified Map.

Thus, the correct filter options are A – CI type and D – Business criticality.

In a mature Configuration Management implementation within ServiceNow, CI operational attributes are leveraged to automate Change Management workflows and reduce manual effort.

When a CI is selected on a Change record, ServiceNow evaluates the CI’s Change Group attribute. If this field is populated on the CI, the platform automatically copies its value into the Change Group field on the Change form. This ensures that change ownership and governance are immediately aligned with the responsible technical team.

The Change Group is distinct from the Assignment Group, which is used primarily in Incident and Task routing. Managed by Group represents lifecycle ownership and is used by CMDB governance tools, while Approval Group controls approval workflows but is not auto-populated from CI selection.

This behavior demonstrates the value of accurate CI attributes: once populated consistently, they enable automatic field population, reduced manual errors, and faster processing across ITSM workflows.

Therefore, the correct answer is A – Change Group.

The correct answer is Service Delivery . In CSDM, the Service Delivery domain focuses on how services are technically delivered and operated. It includes the modeling of technical services, technical service offerings, application services, infrastructure CIs, and the relationships that connect them. The scenario specifically asks about Infrastructure CIs, Technology Management Offerings, Technical Service Offerings, and Application Services, which are all part of the technical operating model for delivering services. Foundation is used for base reference data such as locations, groups, companies, and users. Design and Planning focuses on business applications, capabilities, and planning artifacts. Service Consumption focuses on how consumers access and consume services. Build and Integration is associated with development and deployment activities. Because the question is about technical service relationships and operational service delivery, Service Delivery is the correct CSDM domain.

=========

When using Import Sets and Transform Maps to ingest data into the CMDB, it is critical that records are processed through the Identification and Reconciliation Engine (IRE) to prevent duplicates and enforce source precedence. In ServiceNow, this is achieved by invoking the IRE after the transform logic has completed.

The onAfter transform script is the correct place to call the IRE API. At this stage, the transformed data has already been mapped and prepared, allowing the IRE to correctly identify whether a CI already exists and reconcile updates according to defined rules.

The onBefore and onStart scripts execute too early—before data mapping is complete—making them unsuitable for IRE processing. The onComplete script runs after the entire import job finishes and is not intended for per-record CI identification and reconciliation.

Because Import Sets can bypass IRE if not configured correctly, using an onAfter script is a critical Data Foundations safeguard when this ingestion method is chosen.

Therefore, the correct answer is C – onAfter.

The CMDB Data Foundations Dashboard gives Configuration Management teams visibility into the condition, readiness, and quality of CMDB data. It presents curated metrics that expose gaps involving important attributes, configuration practices, relationships, ownership, and data-governance readiness. These results help administrators determine where corrective action is necessary and prioritize remediation according to operational risk.

The dashboard does not eliminate audits. Auditing, certification, attestation, and health calculations remain separate controls required to validate data. It also does not automatically correct every issue. Instead, the dashboard provides actionable findings and links to structured remediation playbooks that guide administrators through analysing, correcting, and governing the affected data.

The study guide specifically describes dashboard benefits as providing actionable insights for improving data quality and completeness and enabling CMDB health to be monitored over time. Therefore, improved visibility into CMDB health and data quality is the only accurate answer.

=========

The CMDB plays a critical role in security operations by providing trusted, structured insight into the organization’s IT landscape. When built according to Data Foundations principles—accurate discovery, governed relationships, and alignment to CSDM—the CMDB becomes an essential enabler for security incident response and vulnerability management.

Option D is correct because the CMDB allows security teams to identify exactly which IT infrastructure components are affected by a vulnerability. By correlating vulnerability scan results with configuration items (CIs), security teams can determine whether an issue exists on a server, application, cloud resource, or network device—and understand where that CI sits within the broader service context. This eliminates blind spots and reduces time spent investigating unknown or unmanaged assets.

Option A is also correct because the CMDB supports assessment and remediation activities during security incidents. Once affected CIs are identified, the CMDB provides ownership, support group, environment, and service relationships. This enables security teams to quickly route remediation tasks to the correct resolver groups, assess business impact, and prioritize response based on service criticality. While the CMDB does not perform remediation itself, it enables informed and coordinated action.

Option B is incorrect because vulnerabilities are not auto-resolved by the CMDB; remediation requires human decision-making and execution through security, patching, or change processes. Option C, while related to governance and compliance use cases, is more aligned with GRC and audit functions rather than day-to-day security operations, making it less appropriate for this question.

In summary, the CMDB’s primary value in security operations is visibility and actionable insight, enabling faster identification, assessment, and response to security threats.

Application Service Mapping is a critical capability in ServiceNow for enabling business-aware Change Management. Its primary value is not in identifying physical shutdown sequences or CI locations, but in translating technical changes into business impact.

When an organization plans a data center move, multiple infrastructure components—servers, databases, network devices—may be affected. On their own, these technical CIs provide little insight into business risk. Application Service Mapping connects these CIs to Application Services and Business Services as defined by the Common Service Data Model (CSDM). This relationship allows Change Managers to see which business services, customers, and processes are impacted by the planned change.

By leveraging service maps, Change Management can answer critical questions such as:

Which customer-facing services may experience downtime?

What revenue-generating or mission-critical services are at risk?

Which stakeholders must be notified or involved in approvals?

Option A is incorrect because service mapping does not determine shutdown order; that is handled by infrastructure planning. Option C focuses on physical location data, which is typically managed through Location CIs and Discovery, not service mapping.

Therefore, the correct answer is B – To understand the business impact of CIs, which aligns directly with ITIL 4, CSDM, and Change Management best practices.

Asset Management → Tracks the lifecycle of a CI

Asset Management uses CMDB and asset data to track an item throughout its lifecycle, including procurement, deployment, operation, maintenance, retirement, and disposal. This helps the organization understand both the operational status of the CI and its financial or contractual information.

Event Management → Automates incident creation based on threshold configuration

Event Management collects events from monitoring tools and evaluates them against configured rules and thresholds. When a threshold is exceeded or a significant alert is generated, ServiceNow can automatically create an incident and associate it with the affected CI in the CMDB.

Incident Management → Uses the CMDB to identify and resolve issues faster

Incident Management uses CI records and relationships to determine which component is affected, who supports it, and which services depend on it. This provides technicians with accurate context, enabling faster assignment, troubleshooting, impact assessment, and resolution.

Change Management → Identifies the impact on downstream CIs when planning for an upgrade

Change Management uses CMDB relationships to evaluate the potential impact of a planned change. Before upgrading a server, application, or other CI, the change team can identify dependent and downstream CIs or services that could be affected, reducing the risk of outages or unexpected disruption.

The correct answer is Establishing clear governance and continuously monitoring CMDB health . A functional CMDB is not achieved simply by loading large quantities of data or deploying discovery tools. Operationalizing the CMDB requires ownership, standards, data policies, lifecycle controls, class governance, relationship governance, health monitoring, and remediation processes. Discovery is valuable, but without governance it can still create stale, incomplete, duplicated, or poorly related CI data. Allowing teams to freely modify CMDB records creates inconsistency and weakens trust. Populating the CMDB with as much data as possible is also a common failure pattern because excessive, unmanaged data reduces usability and increases maintenance effort. Data Foundations emphasizes trusted, governed, and actionable data. Therefore, the most critical success factor is clear governance combined with continuous CMDB Health monitoring.

=========

IRE applies identification logic to determine whether incoming data represents an existing record or requires the creation of a new record. This makes Option A correct: properly configured identifiers reduce duplicate creation by matching incoming data to existing records before insertion.

IRE also applies reconciliation controls after identification. Reconciliation rules establish which data sources are authorized to update particular classes or attributes and define source precedence when multiple sources provide competing values. Therefore, Option D is correct because an unauthorized or lower-priority source can be prevented from overwriting controlled data.

IRE does not generally prevent an authorized ingestion source from inserting a genuinely new record when no match exists, so Option B is too broad. Option C is incorrect because identification is based on identifier attributes and identification rules, not simply on whether relationships exist.

The guide describes IRE as the mechanism that uniquely identifies records, reduces duplicate creation, applies source precedence, and protects records from unauthorized overwrites.

=========

The correct answer is C. Service Graph Connectors are ServiceNow-supported integrations when used as delivered or configured within supported boundaries. When an administrator customizes the mappings, the implementation moves away from the supported out-of-box connector behavior. This creates upgrade and support implications because ServiceNow cannot guarantee that customized mappings will remain compatible with future connector updates. The customer becomes responsible for validating, maintaining, and troubleshooting those customizations. Option A is not the primary consequence because customized fields are not simply protected by a special CMDB tag. Option B is incorrect because custom mapping does not automatically block connector execution pending approval. The key risk is supportability and technical debt, making C the correct answer.

=========

The Common Service Data Model (CSDM) organizes CMDB data into domains that reflect how services are planned, 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 describe how the business operates and 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 represent what applications exist and who owns them . They anchor ownership, lifecycle, and governance but are not directly operational.

Service Delivery domain → Application Service

Application Services represent running, 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 represent what 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 with CSDM v5 guidance and ensures clear separation between planning constructs, foundational records, operational services, and consumer-facing services—a key principle for a scalable and governed CMDB.

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.

A Web Server is an application or software CI hosted on an underlying physical or virtual Server CI. The standard ServiceNow relationship is therefore Runs on::Runs .

From the Web Server’s direction, the relationship reads Web Server runs on Server . From the reverse direction, the Server runs Web Server . This bidirectional relationship allows users and platform processes to traverse the relationship correctly during incident investigation, service impact analysis, change planning, and service mapping.

“Uses::Used by” represents a broader dependency or consumption relationship and does not accurately express direct software hosting. “Runs::Runs on” reverses the standard relationship direction presented in the question.

Discovery can identify the running software and its host and create the relationship automatically as part of the ingestion process. Therefore, the correct relationship is Web Server > Runs on::Runs > Server.

=========

CSDM significantly enhances Change Management by providing service-aware context, enabling better planning, risk assessment, and stakeholder communication.

One key benefit is the ability to identify blackout windows (Option A). Through CSDM-aligned Business Services, Service Offerings, and service calendars, Change Managers can clearly see when services are unavailable for change due to business constraints, regulatory requirements, or peak usage periods. This helps prevent changes from being scheduled during high-risk windows.

Another critical benefit is the ability to understand the impact of the change on services (Option D). CSDM establishes clear relationships between infrastructure CIs, Application Services, and Business Services. When a change is proposed, these relationships enable accurate impact analysis, allowing Change Managers to assess risk based on business criticality rather than just technical scope.

Option B (root cause determination) is primarily a Problem Management function. Option C (dynamic routing of changes) is driven by workflow and approval logic, not directly by CSDM.

Therefore, the correct answers are A – Identify blackout windows and D – Understand the impact of the change on services.

In Data Foundations, “Insight” focuses on turning configuration data into actionable visibility. CMDB 360 (often associated with Multisource CMDB capabilities) provides a guided experience in CMDB Workspace for exploring CI data and running queries across sources. Within this experience, Saved Queries are managed directly under the CMDB 360 area of CMDB Workspace because they are part of the CMDB 360 query-and-analysis workflow.

A CMDB 360 Saved Query is not the same as a generic CMDB Query Builder query created from classic navigation modules. The CMDB 360 experience typically uses a tile/window approach where users can view existing saved queries, create new queries, modify them, and run them to retrieve CMDB 360 data aligned to multisource reporting and analysis. Keeping saved queries on the CMDB 360 tab makes them easy to discover and reuse for repeatable insights (for example, coverage and source comparisons, CI data quality checks by source, and targeted investigation of records).

The Insights tab in CMDB Workspace is generally used to understand adoption and health-related insights about CMDB features, not as the primary location for creating CMDB 360 multisource saved queries. “Coverage” is a specific lens/view and does not represent the saved-query creation workspace. “CMDB Query Builder” is a related capability, but the question explicitly asks where CMDB 360/Multisource Saved Queries are viewed and created in CMDB Workspace , which is the Saved queries window on the CMDB 360 tab.

CMDB groups can represent either a deliberately selected set of CIs or a dynamically maintained population. For a static grouping, administrators can manually select the required Windows Server CIs and associate them with the named group.

For a dynamic grouping, an encoded query or equivalent CMDB query condition can identify records based on class and attribute criteria. For example, the query can select active Windows Server CIs in a particular location, environment, or support group. As CI records begin or cease to meet the conditions, group membership can be updated accordingly.

Tag-based mapping is principally associated with cloud-native Application Service mapping rather than the standard mechanism described for CMDB group membership. Reconciliation rules determine which source can update CI attributes; they do not assign CIs to operational groups based on source priority. Dynamic CI groups are designed to maintain membership through defined filtering criteria.

=========

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.

Foundation → Use the base system tables when implementing CSDM to get the highest value from ServiceNow products and the Now Platform.

Design and Planning → Understand CIs related to Business Applications and related capabilities; identify redundancies, monitor costs, and make better investment decisions around the roadmap.

Service Consumption → Understand Business Services, ownership, cost, scope of work offered to business consumers, and request access to business services.

Service Delivery → Understand Technical Services, Technical Service Offerings, service support, and all relationships to underlying technology CIs.

CSDM separates data into domains so organizations can model business planning, consumption, and technical delivery without mixing concerns. The Foundation domain provides base reference data such as users, groups, companies, locations, and foundational tables used across the platform. Design and Planning supports architecture and portfolio planning through Business Applications, Business Capabilities, and Information Objects. Service Consumption focuses on how services are exposed to and consumed by business users through Business Services and Business Service Offerings. Service Delivery focuses on how services are technically operated using Technical Services, Technical Service Offerings, Application Services, and supporting infrastructure CIs. This separation is what makes CSDM valuable: each domain answers a different management question while still connecting to a unified service model.

=========

The CMDB Health Dashboard organizes data quality into practical, action-oriented metrics:

Audits validate correctness by comparing CI values against defined expectations (rules, policies, certifications).

Duplicate CIs represent redundant records and should be reduced to improve trust and reporting accuracy.

Orphan CIs lack required relationships or key context, limiting impact analysis and service visibility.

Recommended fields are not mandatory but add diagnostic value during incidents and problem investigations.

Required fields are enforced by the platform and closely tied to Identification & Reconciliation remediation.

Stale CIs signal aging data that no longer reflects the current environment.

This mapping aligns with CMDB Data Foundations best practices and how the Health Dashboard is designed to guide prioritization and remediation.

In Data Foundations (CMDB and CSDM), relationship modeling must reflect real operational dependency so that incident triage, change impact analysis, and service visibility remain accurate. When an Application is hosted on a Server, the standard hosting-style relationship used in CMDB relationship governance is expressed as “Runs on::Runs”. This pairing represents the two directional descriptors of the same relationship type: from the application perspective it runs on the server, and from the server perspective it runs the application.

This matters because CMDB relationships are used by downstream capabilities (for example, dependency views, impact calculations, and governance rules). Using the correct out-of-box relationship descriptor pair ensures consistent reporting and prevents confusion when teams traverse relationships “upstream” and “downstream.” In addition, relationship governance rules and inheritance are commonly built around standard relationship types; using the correct “Runs on::Runs” semantics supports validation across subclasses (for example, specific application and server subclasses) without requiring custom relationship definitions.

The other options are either reversed (“Runs::Runs On”), represent different semantics (“Uses::Used by”), or do not align with the typical hosting relationship naming used for application-to-server hosting dependencies. Therefore, the correct relationship expression between an Application and a Server is Application > Runs on::Runs > Server.

In ServiceNow, the Duplicate CI Remediator is designed to resolve duplicate records while preserving the most authoritative data from each source. Data Foundations guidance clearly states that automated discovery is the system of record for technical attributes, such as IP address, hostname, and operational status, while manually maintained records often contain valuable business context, such as relationships to business applications or services.

In this scenario, the discovered CI contains the most accurate and up-to-date technical data, making it the correct CI to retain as the primary record. However, the manually imported CI has a critical relationship to a business application, which is essential for impact analysis, incident prioritization, and CSDM alignment. Deleting this CI without preserving the relationship would result in loss of business context and reduced CMDB value.

The Duplicate CI Remediator supports selective merging, allowing administrators to retain one CI while merging specific attributes or relationships from the duplicate. Option C reflects this best practice by retaining the discovered CI and merging the relationship from the manually imported CI, ensuring both technical accuracy and business relevance are preserved.

Options A and D would result in the loss of important relationship data, while Option B would discard the discovered CI, violating the principle that discovery should be the authoritative source for technical attributes.

Therefore, Option C is the correct and Data Foundations–aligned answer.

Dynamic reconciliation rules are tied to CMDB 360 / Multisource CMDB because they depend on visibility into multiple contributing data sources for the same CI. Standard reconciliation rules control which data source is allowed to update specific CI attributes based on source precedence, but dynamic reconciliation adds more advanced logic, such as choosing a value based on source reporting behavior or data comparison rules. CMDB Workspace and CMDB Data Manager do not enable dynamic reconciliation; they are management and governance interfaces. Reconciliation Rules alone are not the enabling feature because basic IRE reconciliation can exist without the CMDB 360 dynamic reconciliation capability. Therefore, to use dynamic reconciliation rules, CMDB 360 / Multisource CMDB must be enabled.

=========

Identification Inclusion Rules restrict the population of existing CIs that the Identification and Reconciliation Engine considers when attempting to identify an incoming CI. They add qualifying conditions to the identification process so that IRE searches only the relevant subset of records instead of evaluating every CI in the class.

For example, an inclusion rule could constrain matching to CIs belonging to a particular company, environment, domain, or other defined population. After narrowing the candidate records, IRE applies the class’s identifier entries and identification criteria to decide whether an existing CI matches the incoming data. Identification rules determine whether an incoming record matches an existing CI or requires creation of a new record.

Option A describes reconciliation rules, which control source authority over attributes. Option B is incorrect because inclusion rules do not stop the source from submitting data.

The video displays “Health Inclusion Rules,” but that is a terminology error. Health Inclusion Rules control CMDB Health scope; Identification Inclusion Rules are used by IRE.

=========

In Data Foundations, “Ingest” is not limited to Discovery. It includes establishing reliable sources and mechanisms to populate and maintain CMDB attributes—especially those that Discovery cannot provide. Warranty expiration dates are a classic example of non-discoverable data: they typically come from procurement systems, asset repositories, vendors, or contract tools rather than from device interrogation.

The correct approach is to maintain these attributes via a scheduled data import from an authoritative external source. This ensures ongoing accuracy and consistency at scale. A scheduled import allows you to define a repeatable integration pattern, apply data quality checks, and keep warranty data current as vendors and procurement records change—without relying on manual updates that inevitably drift over time.

Option A is incorrect because the CMDB Reconciliation Engine resolves conflicts between multiple data sources and applies precedence rules; it does not create the warranty values out of thin air. Reconciliation helps decide which source wins when updates occur, but you still need a source feed providing the warranty attribute values. Option B is also not recommended because creating a new CI class just to hold non-discoverable attributes fragments the model and complicates reporting and processes. Best practice is to keep the attributes on the appropriate hardware CI classes (or related normalized structures, when applicable) and manage them through governed ingestion from authoritative systems. Therefore, C is the best method.

The CMDB Data Foundations Dashboard identifies foundational CMDB data-quality deficiencies, including hardware CIs that lack important identification attributes such as serial numbers. A missing serial number is particularly serious because serial number is commonly included in Hardware identification rules. Without it, Discovery and external integrations may fail to match an incoming device to its existing record, resulting in duplicate CIs.

The dashboard exposes the affected population and provides remediation playbooks that help administrators analyse the responsible data sources, correct existing records, and establish controls to ensure that serial numbers continue to be populated.

CI Class Manager is used to configure class structures and identification rules, but it is not the dashboard used to locate the full population of affected CIs. CMDB Data Manager governs lifecycle policies, while the CSDM dashboard focuses on service-model alignment.

=========

In Data Foundations, the “Insight” topic is about making CMDB and service data easy to discover, understand, and use for operational decisions. Natural Language Queries (NLQ) support this by enabling admins and practitioners to ask questions in plain language (for example, finding specific CIs, services, or relationships) and quickly retrieve relevant results without navigating multiple tables and filters.

NLQ is performed in CMDB Workspace because CMDB Workspace is the primary user experience for exploring configuration data, visualizing relationships, and consuming insights from the CMDB in a guided way. It is designed as the central hub where CMDB users validate CI information, examine dependencies, and use workspace capabilities to troubleshoot and analyze. NLQ fits naturally here: it accelerates discovery and analysis by reducing the need for advanced query building and manual report construction.

The other options are not the correct home for NLQ in the Data Foundations context. The CMDB Health Dashboard is focused on KPIs, completeness, correctness, and compliance scoring—showing what is wrong, not serving as the main interface for free-form natural language exploration. CI Class Manager is used for class modeling and class configuration tasks. CMDB Data Manager is used for governance automation such as lifecycle policies (attestation, archival, deletion) and controlled data operations. Therefore, the correct place for administrators to perform NLQ for CMDB exploration and analysis is CMDB Workspace.