Insight practice questions

Which metric category on the CMDB Health Dashboard measures whether CIs have been updated recently and are not abandoned or stale?

Trap 1: Reconciliation

Reconciliation is an engine mechanism, not a CMDB health scoring pillar.

Trap 2: Completeness

Completeness measures whether mandatory fields are populated.

Trap 3: Correctness

Correctness measures duplicate CIs, orphan CIs, and orphan rules.

A
Reconciliation
Why it fails: Reconciliation is an engine mechanism, not a CMDB health scoring pillar.
B
Completeness
Why it fails: Completeness measures whether mandatory fields are populated.
C
Compliance
Compliance measures staleness and audit results to ensure CIs are actively updated.
D
Correctness
Why it fails: Correctness measures duplicate CIs, orphan CIs, and orphan rules.

Question 2mediummultiple choice

An enterprise wants to customize the node grouping and visual presentation within Dependency Views to highlight high-risk hardware. Where are the configuration settings for Dependency Views map formatters and indicators managed?

Trap 1: CI Class Manager

CI Class Manager governs class hierarchy, identification and reconciliation rules, and CI attributes, not Dependency Views map formatters or indicators. It is tempting because it is the CMDB configuration hub, but map presentation settings live in the Dependency Views map configuration, reached via the map's own formatter and indicator options.

Trap 2: CMDB Workspace Dashboard settings

CMDB Workspace Dashboard settings control dashboard widgets and layout, not the Dependency Views map formatters or indicators that determine node grouping and visual styling. It is tempting because both surface CMDB data visually, but the map's formatters and indicators are configured through the Dependency Views map configuration itself.

Trap 3: Service Mapping Configuration Workspace

Service Mapping Configuration Workspace manages service instance mapping, entry points, and traffic-based discovery, not Dependency Views map formatters or indicators. It is tempting because both concern service topology, but node grouping and visual presentation settings belong to the Dependency Views map configuration, not the mapping engine's workspace.

A
Dependency Views Properties and Formatters configuration tables
Dependency Views map formatters and indicators are configured through the Dependency Views Properties and Formatters configuration tables, which govern node grouping, iconography and visual presentation. This satisfies the requirement to customise node grouping and highlight high-risk hardware directly within Dependency Views.
B
CI Class Manager
Why it fails: CI Class Manager governs class hierarchy, identification and reconciliation rules, and CI attributes, not Dependency Views map formatters or indicators. It is tempting because it is the CMDB configuration hub, but map presentation settings live in the Dependency Views map configuration, reached via the map's own formatter and indicator options.
C
CMDB Workspace Dashboard settings
Why it fails: CMDB Workspace Dashboard settings control dashboard widgets and layout, not the Dependency Views map formatters or indicators that determine node grouping and visual styling. It is tempting because both surface CMDB data visually, but the map's formatters and indicators are configured through the Dependency Views map configuration itself.
D
Service Mapping Configuration Workspace
Why it fails: Service Mapping Configuration Workspace manages service instance mapping, entry points, and traffic-based discovery, not Dependency Views map formatters or indicators. It is tempting because both concern service topology, but node grouping and visual presentation settings belong to the Dependency Views map configuration, not the mapping engine's workspace.

Question 3mediummultiple choice

A stakeholder needs to track the count of orphaned CIs (CIs with no relationships) across the entire CMDB on a weekly dashboard. Which built-in tool or dashboard is best suited for providing this data?

Trap 1: CI Class Manager

CI Class Manager defines class hierarchy, identification and reconciliation rules, not CMDB-wide reporting. It cannot count orphaned CIs across all classes. It is the right place to configure class-specific health or identification settings, not to build weekly dashboards.

Trap 2: CSDM Data Foundations Dashboard

CSDM Data Foundations focuses on alignment to CSDM stages (Foundations, Design, Manage Technical Services, Sell/Consume), not individual orphaned hardware/software CI relationship health metrics.

Trap 3: Discovery Dashboard

The Discovery Dashboard displays status and errors specifically related to Discovery schedules and patterns.

A
CI Class Manager
Why it fails: CI Class Manager defines class hierarchy, identification and reconciliation rules, not CMDB-wide reporting. It cannot count orphaned CIs across all classes. It is the right place to configure class-specific health or identification settings, not to build weekly dashboards.
B
CSDM Data Foundations Dashboard
Why it fails: CSDM Data Foundations focuses on alignment to CSDM stages (Foundations, Design, Manage Technical Services, Sell/Consume), not individual orphaned hardware/software CI relationship health metrics.
C
CMDB Health Dashboard
The CMDB Health Dashboard tracks metrics like orphaned CIs under the Correctness KPI category.
D
Discovery Dashboard
Why it fails: The Discovery Dashboard displays status and errors specifically related to Discovery schedules and patterns.

Question 4mediummultiple choice

A CMDB administrator notices that multiple duplicate server records were created because different discovery tools used slightly different naming conventions. Which dashboard helps isolate and report on these duplicate CIs before remediation?

Trap 1: CMDB Query Builder execution log

The CMDB Query Builder execution log records query runs and their results, not duplicate CI detection, so it cannot isolate duplicates. It is tempting because Query Builder can filter CIs, and it would be correct for auditing who ran which CMDB queries and when.

Trap 2: CSDM Data Foundations Dashboard - Foundations stage

The CSDM Data Foundations Dashboard reports CSDM maturity and data conformance across domains, not duplicate CI pairs, so it cannot isolate duplicates for remediation. It is tempting because it surfaces data quality gaps, and it would be correct for assessing CSDM adoption progress.

Trap 3: Service Mapping Dashboard

The Service Mapping Dashboard reports service instance and mapping health, not duplicate CI records, so it cannot isolate duplicates. It is tempting because mapping exposes topology errors, and it would be correct for diagnosing missing or broken application service mappings.

A
CMDB Query Builder execution log
Why it fails: The CMDB Query Builder execution log records query runs and their results, not duplicate CI detection, so it cannot isolate duplicates. It is tempting because Query Builder can filter CIs, and it would be correct for auditing who ran which CMDB queries and when.
B
CSDM Data Foundations Dashboard - Foundations stage
Why it fails: The CSDM Data Foundations Dashboard reports CSDM maturity and data conformance across domains, not duplicate CI pairs, so it cannot isolate duplicates for remediation. It is tempting because it surfaces data quality gaps, and it would be correct for assessing CSDM adoption progress.
C
Service Mapping Dashboard
Why it fails: The Service Mapping Dashboard reports service instance and mapping health, not duplicate CI records, so it cannot isolate duplicates. It is tempting because mapping exposes topology errors, and it would be correct for diagnosing missing or broken application service mappings.
D
CMDB Health Dashboard - Correctness metric
The Correctness metric within the CMDB Health Dashboard isolates duplicate CIs by evaluating them against data-integrity rules, directly surfacing the naming-convention collisions the discovery tools produced. It reports these duplicates before remediation, satisfying the stem's requirement to identify and report on duplicate configuration items.

Question 5easymultiple choice

Which ServiceNow workspace or dashboard provides a unified view for monitoring overall ITOM health, including Discovery status, Service Mapping coverage, and event alerts?

Trap 1: Service Portfolio Management Workspace

Service Portfolio Management Workspace manages service offerings and portfolios, not ITOM operational health. It is tempting because it aggregates service data, but Discovery status, Service Mapping coverage and event alerts belong to the ITOM Health dashboard.

Trap 2: CMDB Data Manager Workspace

CMDB Data Manager Workspace governs CI lifecycle, certification and attestation policies, not live ITOM monitoring. It is tempting as a CMDB-focused console, yet unified Discovery, Service Mapping and event health views reside in the ITOM Health dashboard.

Trap 3: Instance Security Center

Instance Security Center reports on security compliance, hardening and access risks, not ITOM operational health. It is tempting as a central monitoring console, but Discovery status, Service Mapping coverage and event alerts are surfaced by the ITOM Health dashboard.

A
ITOM Visibility / Health Dashboard
The ITOM Visibility Health Dashboard aggregates Discovery status, Service Mapping coverage and event alerts into a single pane, directly satisfying the stem's requirement for unified ITOM health monitoring. It draws on Configuration Management Database (CMDB) data and MID Server telemetry, giving administrators one consolidated operational view rather than separate module reports.
B
Service Portfolio Management Workspace
Why it fails: Service Portfolio Management Workspace manages service offerings and portfolios, not ITOM operational health. It is tempting because it aggregates service data, but Discovery status, Service Mapping coverage and event alerts belong to the ITOM Health dashboard.
C
CMDB Data Manager Workspace
Why it fails: CMDB Data Manager Workspace governs CI lifecycle, certification and attestation policies, not live ITOM monitoring. It is tempting as a CMDB-focused console, yet unified Discovery, Service Mapping and event health views reside in the ITOM Health dashboard.
D
Instance Security Center
Why it fails: Instance Security Center reports on security compliance, hardening and access risks, not ITOM operational health. It is tempting as a central monitoring console, but Discovery status, Service Mapping coverage and event alerts are surfaced by the ITOM Health dashboard.

Question 6mediummulti select

Which TWO of the following capabilities are provided out-of-the-box by the CMDB Health Dashboard? (Choose two.)

Trap 1: Executing automated network IP discovery scans

Automated network IP discovery scans are performed by Discovery and Service Mapping, not the CMDB Health Dashboard, which reports on CI data quality. Discovery would be correct when populating the CMDB with network devices rather than assessing existing CI health.

Trap 2: Designing multi-class CMDB Query Builder reports

CMDB Query Builder report design is a separate reporting capability, not a CMDB Health Dashboard KPI; the dashboard provides completeness, correctness and compliance metrics. It is tempting because Query Builder reports can surface health data, but designing them is not an out-of-the-box dashboard capability.

Trap 3: Configuring CI identification and reconciliation rules

Identification and reconciliation rules are configured in the CMDB Health configuration, not delivered as a dashboard capability. It tempts because reconciliation directly affects health scores, but the dashboard reports results; defining those rules is an administrative setup task performed separately.

A
Tracking duplicate CI counts under Correctness metrics
Duplicate CI counts appear under the Correctness metrics on the CMDB Health Dashboard without custom configuration, satisfying the out-of-the-box requirement. The dashboard's Correctness scorecard natively includes duplicate, orphan and stale CI checks, so no additional scripting or custom health metrics are needed to surface duplication.
B
Executing automated network IP discovery scans
Why it fails: Automated network IP discovery scans are performed by Discovery and Service Mapping, not the CMDB Health Dashboard, which reports on CI data quality. Discovery would be correct when populating the CMDB with network devices rather than assessing existing CI health.
C
Designing multi-class CMDB Query Builder reports
Why it fails: CMDB Query Builder report design is a separate reporting capability, not a CMDB Health Dashboard KPI; the dashboard provides completeness, correctness and compliance metrics. It is tempting because Query Builder reports can surface health data, but designing them is not an out-of-the-box dashboard capability.
D
Configuring CI identification and reconciliation rules
Why it fails: Identification and reconciliation rules are configured in the CMDB Health configuration, not delivered as a dashboard capability. It tempts because reconciliation directly affects health scores, but the dashboard reports results; defining those rules is an administrative setup task performed separately.
E
Monitoring CI staleness and compliance audit results
The CMDB Health Dashboard ships with health metrics covering CI staleness and audit compliance results, flagging records that are outdated or failing audits. These two are default indicators, requiring no custom metric configuration to surface.

Question 7hardmulti select

Which THREE of the following actions can an administrator take to remediate duplicate CIs identified by the CMDB Health Dashboard? (Choose three.)

Trap 1: Manually delete all records in the cmdb_ci table older than 90 days

Deleting all cmdb_ci records older than 90 days destroys valid CIs regardless of duplication, breaking relationships and history. It is tempting as bulk cleanup, but remediation targets identified duplicate pairs via deduplication tasks or the CMDB Data Manager, not age-based deletion.

Trap 2: Rebuild all Service Mapping entry points from scratch

Rebuilding every Service Mapping entry point from scratch does not resolve duplicate CIs and disrupts mapping. It is tempting as a reset, but duplicate remediation uses deduplication tasks, merge or delete of the duplicate record, and reconciliation, not wholesale entry-point reconstruction.

A
Manually delete all records in the cmdb_ci table older than 90 days
Why it fails: Deleting all cmdb_ci records older than 90 days destroys valid CIs regardless of duplication, breaking relationships and history. It is tempting as bulk cleanup, but remediation targets identified duplicate pairs via deduplication tasks or the CMDB Data Manager, not age-based deletion.
B
Run automated deduplication tasks configured in CMDB Health
Automated deduplication tasks configured in CMDB Health directly satisfy the remediation requirement by merging or retiring duplicate CIs according to administrator-defined rules, such as matching on name, serial number or IP address. This removes the duplicates the dashboard flagged without manual intervention, keeping the CMDB accurate.
C
Use the CMDB Duplicate Remediation wizard to merge duplicate CI records
The CMDB Duplicate Remediation wizard directly merges duplicate CI records, consolidating attributes and relationships into a single authoritative CI. This satisfies the stem's requirement to remediate duplicates flagged by the CMDB Health Dashboard, resolving them at source rather than merely reporting or suppressing them.
D
Refine IRE (Identification and Reconciliation Engine) rules to prevent future duplicates
Refining IRE rules addresses the root cause by tightening the reconciliation criteria that create duplicate CIs during discovery. Where the dashboard flags duplicates arising from matching failures, adjusting these rules prevents recurrence, satisfying the requirement for a remediation action rather than merely cleaning existing records.
E
Rebuild all Service Mapping entry points from scratch
Why it fails: Rebuilding every Service Mapping entry point from scratch does not resolve duplicate CIs and disrupts mapping. It is tempting as a reset, but duplicate remediation uses deduplication tasks, merge or delete of the duplicate record, and reconciliation, not wholesale entry-point reconstruction.

Question 8mediummulti select

Which TWO of the following metrics are categorized under the Correctness pillar of the CMDB Health Dashboard? (Choose two.)

Trap 1: CI Staleness (time since last update)

Staleness measures how long since a CI was last updated, which the CMDB Health framework scores under the Completeness pillar, not Correctness. It is tempting because both pillars concern data quality, but Correctness covers duplicates, orphans and audit failures; staleness is a freshness metric.

Trap 2: Service Mapping pattern error count

Pattern error counts belong to Service Mapping diagnostics and Discovery monitoring, not the CMDB Health Correctness pillar. It is tempting because pattern failures create incorrect CIs, but the Correctness pillar scores duplicate, orphan and audit results; pattern errors are tracked as discovery health, not CMDB correctness.

Trap 3: Missing mandatory field population

Missing mandatory field population is scored under the Completeness pillar, which measures whether required attributes are filled. It is tempting because empty fields look like data-quality defects, but Correctness evaluates duplicate CIs, orphan CIs and audit compliance; completeness covers absent values.

A
CI Staleness (time since last update)
Why it fails: Staleness measures how long since a CI was last updated, which the CMDB Health framework scores under the Completeness pillar, not Correctness. It is tempting because both pillars concern data quality, but Correctness covers duplicates, orphans and audit failures; staleness is a freshness metric.
B
Duplicate CIs
Duplicate CIs fall under Correctness because they represent multiple records describing the same real-world item, which identification and reconciliation should have merged. This is a data accuracy defect, not a completeness or compliance gap, so it belongs to the Correctness pillar.
C
Service Mapping pattern error count
Why it fails: Pattern error counts belong to Service Mapping diagnostics and Discovery monitoring, not the CMDB Health Correctness pillar. It is tempting because pattern failures create incorrect CIs, but the Correctness pillar scores duplicate, orphan and audit results; pattern errors are tracked as discovery health, not CMDB correctness.
D
Missing mandatory field population
Why it fails: Missing mandatory field population is scored under the Completeness pillar, which measures whether required attributes are filled. It is tempting because empty fields look like data-quality defects, but Correctness evaluates duplicate CIs, orphan CIs and audit compliance; completeness covers absent values.
E
Orphan CIs (CIs with no relationships)
Orphan CIs are measured under the Correctness pillar.

Question 9mediummulti select

Which TWO of the following dashboards help an organization monitor CSDM adoption and data alignment? (Choose two.)

Trap 1: Discovery Administration Dashboard

The Discovery Administration Dashboard reports discovery schedules, status and errors, not CSDM domain coverage or data alignment. It is tempting because discovery feeds the CMDB, but CSDM adoption is measured by the CSDM Data Foundation and CMDB Health dashboards instead.

Trap 2: CMDB Health Dashboard

CMDB Health measures data quality attributes (completeness, correctness, compliance), not CSDM stages.

Trap 3: Instance Security Center

The Instance Security Center reports user access, roles and security hardening, not CSDM domain coverage or CI data alignment. It is tempting because it monitors instance-wide configuration, but CSDM adoption is tracked through the CSDM Data Foundation and CMDB Health dashboards.

A
Discovery Administration Dashboard
Why it fails: The Discovery Administration Dashboard reports discovery schedules, status and errors, not CSDM domain coverage or data alignment. It is tempting because discovery feeds the CMDB, but CSDM adoption is measured by the CSDM Data Foundation and CMDB Health dashboards instead.
B
CMDB Health Dashboard
Why it fails: CMDB Health measures data quality attributes (completeness, correctness, compliance), not CSDM stages.
C
CSDM Data Foundations Dashboard
The CSDM Data Foundations Dashboard reports on CSDM-compliant data coverage, surfacing gaps in lifecycle and foundation data. It directly satisfies the stem's requirement to monitor CSDM adoption and alignment, letting administrators track progress against the Common Service Data Model.
D
Service Portfolio Workspace
The Service Portfolio Workspace provides governance views over service offerings and their supporting CIs, exposing misalignment between services and CSDM-modelled data. It satisfies the stem's monitoring requirement by letting owners review service-level adoption and correct drift.
E
Instance Security Center
Why it fails: The Instance Security Center reports user access, roles and security hardening, not CSDM domain coverage or CI data alignment. It is tempting because it monitors instance-wide configuration, but CSDM adoption is tracked through the CSDM Data Foundation and CMDB Health dashboards.

Question 10easymultiple choice

A platform administrator is configuring CMDB Health dashboards to track completeness, compliance, and correctness of CI records. Which metric is evaluated specifically under the Correctness KPI score?

Trap 1: Empty mandatory fields

Empty mandatory fields are evaluated under the Completeness KPI, not Correctness.

Trap 2: Unassigned owner fields

Unassigned owner fields contribute to the Completeness score of the CI records.

Trap 3: Unauthorized software installations

Unauthorized software tracking falls under Software Asset Management compliance, not CMDB Health correctness.

A
Empty mandatory fields
Why it fails: Empty mandatory fields are evaluated under the Completeness KPI, not Correctness.
B
Unassigned owner fields
Why it fails: Unassigned owner fields contribute to the Completeness score of the CI records.
C
Unauthorized software installations
Why it fails: Unauthorized software tracking falls under Software Asset Management compliance, not CMDB Health correctness.
D
Orphan CIs
Orphan CIs lack relationships to other CIs and represent a failure of correctness based on defined CSDM and relationship rules.

Question 11hardmultiple choice

A user is utilizing Dependency Views to analyze a critical business application outage. The map displays multiple downstream relationships, but one expected server CI is missing from the view. What is the most likely cause for this behavior in Service Mapping and Dependency Views?

Trap 1: The CI class of the server does not belong to the cmdb_ci table…

Dependency Views renders CIs whose classes extend cmdb_ci, so a class outside that hierarchy cannot appear on the map. It is tempting because custom classes must still be properly modelled, but the real cause is usually a missing or stale relationship record, not class inheritance.

Trap 2: The server CI has a 'Retired' lifecycle stage, which completely…

Retirement sets a lifecycle stage value; it does not purge the record, so the CI remains queryable and would still surface through relationships. It is tempting because retired CIs are excluded from many operational reports, but Dependency Views omits the server because no relationship connects it.

Trap 3: Dependency Views only render relationships up to two hops by…

Dependency Views can be expanded manually or configured to show additional levels of relationships.

A
The CI class of the server does not belong to the cmdb_ci table hierarchy.
Why it fails: Dependency Views renders CIs whose classes extend cmdb_ci, so a class outside that hierarchy cannot appear on the map. It is tempting because custom classes must still be properly modelled, but the real cause is usually a missing or stale relationship record, not class inheritance.
B
The server CI has a 'Retired' lifecycle stage, which completely purges it from the CMDB database.
Why it fails: Retirement sets a lifecycle stage value; it does not purge the record, so the CI remains queryable and would still surface through relationships. It is tempting because retired CIs are excluded from many operational reports, but Dependency Views omits the server because no relationship connects it.
C
The relationship record between the application and the server does not exist in the cmdb_rel_ci table.
Dependency Views traverse the cmdb_rel_ci table; if the relationship record is absent, the child node cannot be displayed.
D
Dependency Views only render relationships up to two hops by default and cannot be expanded.
Why it fails: Dependency Views can be expanded manually or configured to show additional levels of relationships.

Question 12mediummultiple choice

An enterprise architect wants to visualize the hierarchical relationship between Business Applications, Technical Services, and underlying Application Services using native CSDM visualization tools. Which tool provides the most appropriate structured view for this CSDM domain alignment?

Trap 1: Network Topology Map

Network Topology maps low-level hardware and IP connections, not high-level CSDM abstract domains.

Trap 2: Data Certification schedule view

Data Certification is used for validating attribute accuracy with owners, not structural architecture visualization.

Trap 3: Service Portfolio Management workbench hierarchy view

While SPM shows services, the CSDM Dashboard specifically evaluates the alignment and status across foundation, design, manage technical services, and sell/consume domains.

A
CSDM Dashboard and CSDM 3.0 widgets
The CSDM Dashboard provides structured visibility into the implementation status and relationships across the CSDM domains.
B
Network Topology Map
Why it fails: Network Topology maps low-level hardware and IP connections, not high-level CSDM abstract domains.
C
Data Certification schedule view
Why it fails: Data Certification is used for validating attribute accuracy with owners, not structural architecture visualization.
D
Service Portfolio Management workbench hierarchy view
Why it fails: While SPM shows services, the CSDM Dashboard specifically evaluates the alignment and status across foundation, design, manage technical services, and sell/consume domains.

Question 13hardmulti select

Which THREE capabilities are available when analyzing insights from Service Mapping visualization and map data? (Choose three.)

Trap 1: Automatically generating software purchase orders for…

Purchase order generation is a procurement/SAM function, not a Service Mapping capability.

A
Isolating upstream and downstream impact paths during incident investigation
Maps allow technicians to trace impact paths to determine what business services are affected by a failing CI.
B
Tracing traffic connections and dependencies originating from defined entry points
Service Mapping uses entry points to discover and map inbound and outbound dependencies.
C
Automatically generating software purchase orders for under-licensed CIs
Why it fails: Purchase order generation is a procurement/SAM function, not a Service Mapping capability.
D
Identifying single points of failure (SPOFs) within a mapped application service
Service Mapping highlights redundant paths and potential single points of failure.
E
Viewing real-time alert aggregation and health status directly on map nodes
Maps integrate with Event Management to display active alerts on affected CIs.

Question 14mediummultiple choice

A CMDB administrator is reviewing the CMDB Health Dashboard and needs to understand why the Completeness KPI for the Server class is lower than expected. The administrator wants to generate a report that lists all Server CIs missing required attributes such as serial number or operating system. Which feature should the administrator use to accomplish this?

Trap 1: Service Mapping to visualize server dependencies

Service Mapping discovers and maps application services and their underlying infrastructure, but it does not report on missing required attributes for Server CIs. It focuses on relationships and traffic flows, not data completeness, so it cannot identify which servers lack serial number or operating system.

Trap 2: CMDB Data Manager to create a cleanup policy

CMDB Data Manager is used to automate lifecycle operations such as archiving, deleting, or attesting CIs based on policies, not to identify missing attributes. It does not provide a drill-down list of incomplete CIs and is not the right tool for diagnosing Completeness KPI failures.

Trap 3: CMDB Query Builder with a filter on missing attributes

CMDB Query Builder is designed to create complex relationship queries across multiple CI classes, not simply to list CIs missing specific attributes. While it can be used for some reporting, it is not the primary tool for drill-down on health KPI failures, and it does not natively surface missing required attributes as the Health Dashboard does.

A
CMDB Health Dashboard drill-down on the Completeness KPI
The CMDB Health Dashboard Completeness KPI provides a drill-down that lists CIs missing required attributes, allowing the administrator to see exactly which Server records lack serial number or operating system. This directly addresses the need to identify incomplete CIs without building custom reports.
B
Service Mapping to visualize server dependencies
Why it fails: Service Mapping discovers and maps application services and their underlying infrastructure, but it does not report on missing required attributes for Server CIs. It focuses on relationships and traffic flows, not data completeness, so it cannot identify which servers lack serial number or operating system.
C
CMDB Data Manager to create a cleanup policy
Why it fails: CMDB Data Manager is used to automate lifecycle operations such as archiving, deleting, or attesting CIs based on policies, not to identify missing attributes. It does not provide a drill-down list of incomplete CIs and is not the right tool for diagnosing Completeness KPI failures.
D
CMDB Query Builder with a filter on missing attributes
Why it fails: CMDB Query Builder is designed to create complex relationship queries across multiple CI classes, not simply to list CIs missing specific attributes. While it can be used for some reporting, it is not the primary tool for drill-down on health KPI failures, and it does not natively surface missing required attributes as the Health Dashboard does.

Question 15easymultiple choice

A service owner wants to understand the overall health of a critical business service by viewing a single dashboard that shows the status of all underlying CIs, including servers, applications, and network devices. Which ServiceNow feature provides this consolidated view?

Trap 1: Service Mapping

Service Mapping discovers and maps application services and their dependencies, but it does not provide a consolidated health dashboard for all underlying CIs. It focuses on creating the service model, not on displaying real-time health status across multiple CI types.

Trap 2: CMDB Query Builder

CMDB Query Builder allows users to create complex queries to find CIs and relationships, but it does not provide a real-time health dashboard. It is a reporting and analysis tool, not a monitoring interface for service health.

Trap 3: CMDB Health Dashboard

The CMDB Health Dashboard monitors data quality metrics like completeness and correctness, not the operational health of CIs. It does not show the live status of servers, applications, or network devices, so it cannot provide the requested consolidated health view.

A
Service Mapping
Why it fails: Service Mapping discovers and maps application services and their dependencies, but it does not provide a consolidated health dashboard for all underlying CIs. It focuses on creating the service model, not on displaying real-time health status across multiple CI types.
B
CMDB Query Builder
Why it fails: CMDB Query Builder allows users to create complex queries to find CIs and relationships, but it does not provide a real-time health dashboard. It is a reporting and analysis tool, not a monitoring interface for service health.
C
CMDB Health Dashboard
Why it fails: The CMDB Health Dashboard monitors data quality metrics like completeness and correctness, not the operational health of CIs. It does not show the live status of servers, applications, or network devices, so it cannot provide the requested consolidated health view.
D
Service Operations Workspace
Service Operations Workspace provides a unified view of service health, aggregating alerts, incidents, and CI status from multiple sources. It is designed for service owners to monitor the operational health of business services and their underlying infrastructure in one place.

Question 16hardmultiple choice

An organization requires a custom report that extracts CIs that match a complex multi-class criteria: Linux servers running a specific Oracle version that connect to a Business Service via a downstream 'Depends on::Used by' relationship. What is the most efficient native way to generate this dataset?

Trap 1: Write a Database View joining cmdb_ci, cmdb_rel_ci, and…

A database view is a custom schema artefact requiring development and maintenance, not the native reporting route, and it does not itself deliver the report output the administrator needs. It is tempting because views can join arbitrary tables, and it would be correct where no native reporting construct can express the required joins.

Trap 2: Build a custom Service Mapping Traffic Connection report.

Traffic Connection reports are generated from Service Mapping traffic-based discovery data, which records observed network connections rather than CMDB relationship types, so the 'Depends on::Used by' chain and Oracle version filter cannot be expressed. It is tempting because it queries service topology, and it would be correct where the requirement is to show discovered traffic links between CIs.

Trap 3: Create a standard ServiceNow List Report on the CI [cmdb_ci] table…

A list report on cmdb_ci cannot traverse the cmdb_rel_ci relationship table to reach the Business Service, nor join cmdb_software_product for the Oracle version, so the multi-class criteria cannot be combined. It is tempting because list reports are the quickest native output, and it would be correct for filtering a single table on its own fields.

A
Write a Database View joining cmdb_ci, cmdb_rel_ci, and cmdb_software_product.
Why it fails: A database view is a custom schema artefact requiring development and maintenance, not the native reporting route, and it does not itself deliver the report output the administrator needs. It is tempting because views can join arbitrary tables, and it would be correct where no native reporting construct can express the required joins.
B
Build a custom Service Mapping Traffic Connection report.
Why it fails: Traffic Connection reports are generated from Service Mapping traffic-based discovery data, which records observed network connections rather than CMDB relationship types, so the 'Depends on::Used by' chain and Oracle version filter cannot be expressed. It is tempting because it queries service topology, and it would be correct where the requirement is to show discovered traffic links between CIs.
C
Use CMDB Query Builder to construct a multi-node relationship query and save it as a reporting source.
CMDB Query Builder supports multi-node relationship traversal, so you can join Linux server CIs, their Oracle software CIs, and the downstream 'Depends on::Used by' path to a Business Service in one query, then save it as a reporting source. This avoids scripting and satisfies the complex multi-class criteria natively.
D
Create a standard ServiceNow List Report on the CI [cmdb_ci] table with multiple join conditions.
Why it fails: A list report on cmdb_ci cannot traverse the cmdb_rel_ci relationship table to reach the Business Service, nor join cmdb_software_product for the Oracle version, so the multi-class criteria cannot be combined. It is tempting because list reports are the quickest native output, and it would be correct for filtering a single table on its own fields.

Question 17easymultiple choice

An incident manager wants to see all upstream business services impacted by a failed network switch directly from the infrastructure alert. Where can they view this immediate impact path?

Trap 1: CMDB Baseline Diff Viewer

The Baseline Diff Viewer compares two snapshots of a CI's attributes over time; it does not traverse relationship graphs, so it cannot surface upstream business services from an alert. It would be the right tool when auditing configuration drift between baselines, not for impact analysis.

Trap 2: Event Management Alert Correlation Form

The Alert Correlation Form groups related alerts into a single incident, operating on alert-to-alert matching rules rather than CI relationship traversal, so it cannot display upstream business services. It is correct when reducing alert noise by correlating multiple monitoring events into one actionable incident.

Trap 3: CSDM Conceptual Diagram

The CSDM Conceptual Diagram is static documentation of the Common Service Data Model's domain structure; it holds no live CI relationship data, so it cannot trace an actual failed switch to impacted services. It is the right reference when designing or validating your CSDM taxonomy.

A
CMDB Baseline Diff Viewer
Why it fails: The Baseline Diff Viewer compares two snapshots of a CI's attributes over time; it does not traverse relationship graphs, so it cannot surface upstream business services from an alert. It would be the right tool when auditing configuration drift between baselines, not for impact analysis.
B
Event Management Alert Correlation Form
Why it fails: The Alert Correlation Form groups related alerts into a single incident, operating on alert-to-alert matching rules rather than CI relationship traversal, so it cannot display upstream business services. It is correct when reducing alert noise by correlating multiple monitoring events into one actionable incident.
C
Dependency Views map on the switch CI record
The Dependency Views map on the switch CI record renders the CMDB relationship graph, showing upstream business services that depend on the failed switch. This gives the incident manager the immediate impact path directly from the infrastructure alert without manual correlation.
D
CSDM Conceptual Diagram
Why it fails: The CSDM Conceptual Diagram is static documentation of the Common Service Data Model's domain structure; it holds no live CI relationship data, so it cannot trace an actual failed switch to impacted services. It is the right reference when designing or validating your CSDM taxonomy.

Question 18mediummultiple choice

A team needs to evaluate the overall health of their CSDM implementation by verifying if technical services are correctly linked to applications and infrastructure. Which built-in assessment tool provides this specific visibility?

Trap 1: Service Portfolio Workspace

Service Portfolio Workspace is a management interface for browsing and editing portfolio offerings, not an assessment tool that scores CSDM linkage health. It is tempting because it surfaces services and their relationships visually, but it would be correct for portfolio governance and lifecycle management.

Trap 2: CMDB Health Dashboard

The CMDB Health Dashboard scores completeness, correctness and compliance of CI attributes and relationships, but does not specifically verify technical service linkage to applications and infrastructure. It is tempting because it is the obvious CMDB assessment tool, yet it would be correct for general CI data quality.

Trap 3: Instance Security Center

Instance Security Center reports configuration and vulnerability compliance for instances, not CSDM linkage between technical services, applications and infrastructure. It is tempting because it is a built-in assessment surface, but it would be the right tool for hardening and security posture, not data-model health.

A
Service Portfolio Workspace
Why it fails: Service Portfolio Workspace is a management interface for browsing and editing portfolio offerings, not an assessment tool that scores CSDM linkage health. It is tempting because it surfaces services and their relationships visually, but it would be correct for portfolio governance and lifecycle management.
B
CMDB Health Dashboard
Why it fails: The CMDB Health Dashboard scores completeness, correctness and compliance of CI attributes and relationships, but does not specifically verify technical service linkage to applications and infrastructure. It is tempting because it is the obvious CMDB assessment tool, yet it would be correct for general CI data quality.
C
Instance Security Center
Why it fails: Instance Security Center reports configuration and vulnerability compliance for instances, not CSDM linkage between technical services, applications and infrastructure. It is tempting because it is a built-in assessment surface, but it would be the right tool for hardening and security posture, not data-model health.
D
CSDM Data Foundations Dashboard
The CSDM Data Foundations Dashboard assesses whether technical services are correctly linked to applications and infrastructure, exposing gaps in the Common Service Data Model. It provides the specific health visibility the team needs, unlike CMDB health dashboards that focus on data completeness rather than CSDM relationship integrity.

Question 19easymultiple choice

An administrator wants to view the hierarchical relationship and physical connections between a Business Application and its underlying database infrastructure in the CMDB. Which feature should they open from the Configuration Item form?

Trap 1: Service Portfolio Management

Service Portfolio Management governs the service catalogue and its offerings, holding no CI relationship or connection data. It is opened when defining published services, whereas the hierarchical and physical connection view between a Business Application and its database infrastructure comes from Service Mapping's map.

Trap 2: Map Builder

Map Builder renders dependency views for a single CI's relationships, not the hierarchical service-to-infrastructure path the administrator needs; it is intended for building custom CI relationship maps. The correct feature is Service Mapping or the CSDM-aligned dependency view, which traces Business Application down to database CIs.

Trap 3: CMDB Query Builder

CMDB Query Builder produces tabular, class-based query results across CIs, not a hierarchical visualisation of physical connections from a Business Application to its database. It is intended for reporting and data audits, whereas the requirement is a relationship map showing the service-to-infrastructure hierarchy.

A
Service Portfolio Management
Why it fails: Service Portfolio Management governs the service catalogue and its offerings, holding no CI relationship or connection data. It is opened when defining published services, whereas the hierarchical and physical connection view between a Business Application and its database infrastructure comes from Service Mapping's map.
B
Dependency Views
Dependency Views renders a hierarchical, connection-aware map of CIs and their relationships, letting administrators trace a Business Application down to its underlying database infrastructure. This satisfies the requirement to view hierarchical and physical connections from the CI form.
C
Map Builder
Why it fails: Map Builder renders dependency views for a single CI's relationships, not the hierarchical service-to-infrastructure path the administrator needs; it is intended for building custom CI relationship maps. The correct feature is Service Mapping or the CSDM-aligned dependency view, which traces Business Application down to database CIs.
D
CMDB Query Builder
Why it fails: CMDB Query Builder produces tabular, class-based query results across CIs, not a hierarchical visualisation of physical connections from a Business Application to its database. It is intended for reporting and data audits, whereas the requirement is a relationship map showing the service-to-infrastructure hierarchy.

Question 20hardmultiple choice

During a Dependency Views troubleshooting session, an engineer notices that a specific application server is missing its connected database nodes. What is the most likely cause when relationships are missing despite successful Discovery runs?

Trap 1: Data archiving automatically deletes relationship records older…

ServiceNow does not automatically purge CMDB relationship records after 30 days; archiving targets task and audit data, not cmdb_rel_ci entries. It is tempting because archiving does remove aged records, and would be the cause if the missing data were historical task records rather than active dependency relationships.

Trap 2: The CMDB Query Builder cache needs to be manually cleared.

CMDB Query Builder results are computed at query time and cached per session; a stale cache would not remove database nodes from Dependency Views, which reads relationships directly. It is tempting because cache clearing is a common troubleshooting step, and would be correct if the query results themselves appeared outdated.

Trap 3: The cmdb_ci table has reached its maximum row count limit for…

The cmdb_ci table has no maximum row count that silently drops relationships; missing nodes stem from absent or incorrect cmdb_rel_ci records, often due to discovery patterns or credentials. It is tempting because large CMDBs do hit performance limits, and would be relevant if the instance were genuinely throttled by table size.

A
The relationship type filter in the Dependency Views UI is hiding specific relationship types.
Dependency Views applies relationship-type filters when rendering the map. If a filter excludes the database-to-application-server relationship type, discovered CIs appear without their connecting edges, so the nodes look missing even though Discovery populated them correctly.
B
Data archiving automatically deletes relationship records older than 30 days.
Why it fails: ServiceNow does not automatically purge CMDB relationship records after 30 days; archiving targets task and audit data, not cmdb_rel_ci entries. It is tempting because archiving does remove aged records, and would be the cause if the missing data were historical task records rather than active dependency relationships.
C
The CMDB Query Builder cache needs to be manually cleared.
Why it fails: CMDB Query Builder results are computed at query time and cached per session; a stale cache would not remove database nodes from Dependency Views, which reads relationships directly. It is tempting because cache clearing is a common troubleshooting step, and would be correct if the query results themselves appeared outdated.
D
The cmdb_ci table has reached its maximum row count limit for relationships.
Why it fails: The cmdb_ci table has no maximum row count that silently drops relationships; missing nodes stem from absent or incorrect cmdb_rel_ci records, often due to discovery patterns or credentials. It is tempting because large CMDBs do hit performance limits, and would be relevant if the instance were genuinely throttled by table size.