CCNA Insight Questions

Dependency Views supports filtering by relationship type, letting users isolate specific connection categories within the displayed map. This satisfies the scenario's requirement to narrow visualised relationships, since the view renders multiple relationship types simultaneously and filtering reduces noise without altering the underlying dependency data.

Dependency Views render the CMDB relationship map around a target CI, exposing upstream and downstream dependencies. During change planning this reveals which services and CIs could be impacted, satisfying the stem's requirement for a primary visual benefit when assessing change risk.

The CMDB Health Dashboard's Completeness metric specifically scores CIs against required fields, including owner and support group, and surfaces those failing the check. This directly highlights the applications missing assigned ownership, satisfying the director's need to isolate that completeness gap rather than broader data quality issues.

The Service Delivery domain in CSDM includes Business Applications, Application Services, and Technical Services, and defines how they relate. The linkage between Business Applications and Application Services is a key relationship within this domain, so the administrator should focus here to identify and resolve unlinked Business Applications.

CMDB Query Builder supports multi-node relationship steps, letting you chain hops between CI classes in a single query. That directly satisfies the requirement to traverse up to three relationship hops from the database instance to dependent Business Services.

Query Builder inherits the platform's standard domain separation runtime logic, so an administrator's session visibility determines which child-domain CIs appear in the aggregated report. No separate Query Builder-specific domain filter exists; the report therefore respects domain separation rules automatically across all domains.

Traffic connection views satisfy the live network communication flows requirement by rendering discovered TCP connections between configuration items, mapping each service's actual runtime dependencies rather than static records. This visualisation exposes communication paths and traffic direction across the estate, which is precisely the insight Service Mapping provides.

Performance Analytics pulls time-series data from Service Mapping discovery runs, letting you aggregate mean completion duration across every critical business service. Standard reporting cannot compute this rolling average, so the widgets and dashboards satisfy the stem's requirement for average full-map discovery time analytics.

Traversal halts when the pattern cannot authenticate or lacks a step to query the load balancer's backend pool members. Since traffic is visible but the map stops, the missing extension or credentials prevent discovering the web servers, satisfying the requirement to explain why backend nodes never appear.

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.

System Properties prefixed with glide.ui.dependency_view define the default relationship filters rendered in Dependency Views, letting the administrator restrict rendering to 'Runs on::Runs' and 'Hosted on::Hosts' for all users without per-user configuration. This satisfies the stem's requirement for a global default.

The cmdb_ci table is the base CI class holding all configuration items, and its Operational Status field records lifecycle states such as In Use, Maintenance and Retired. Grouping on this field produces the required distribution of CIs across operational statuses.

CMDB Query Builder provides a graphical interface for constructing multi-class CI relationship queries, then executing and exporting the results. This satisfies the requirement to generate insights by visually assembling complex relationship queries without writing code manually.

The Relationships related list on the CI form directly satisfies the requirement to view relationship-based insights, displaying all inbound and outbound dependencies for that configuration item. It queries the cmdb_rel_ci table, rendering parent-child and peer connections inline, so no separate reporting module or dashboard configuration is needed.

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.

Visual graphical querying joins related CMDB tables with operational tables, letting you traverse the Business Application relationship to Windows Servers and correlate open critical Incidents in one definition. This satisfies the stem's requirement to combine configuration relationships with live incident data, which single-table filters cannot achieve.

CMDB Query Builder natively exports results to JSON or CSV, satisfying the requirement for built-in data extraction without external tooling. This export capability lets administrators pull query output directly into reporting or integration pipelines, confirming it as one of the three native features the question demands.

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.

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.

CMDB Data Manager provides lifecycle policies that automate archival of historical configuration items, satisfying the requirement to schedule archival without manual intervention. Policies define retention thresholds and target CI classes, then run on defined schedules to retire stale records, preserving database performance and accuracy.

IRE relationship identification rules define the matching attributes that decide whether an incoming relationship is new or already exists. Without them, Discovery creates duplicate links between the same CIs, corrupting dependency maps and any relationship-based insight the CMDB reports.

The Traffic Connections view displays live network connections and traffic flows between application nodes, satisfying the requirement for real-time connection insight in the service map. Unlike static dependency views, it captures actual observed traffic, letting the administrator analyse active communication paths directly within Service Mapping.

The Compliance KPI configuration allows administrators to define required relationships and attributes for CI classes. By setting up compliance rules, the administrator can specify that a Server must be related to an Application Service, and the KPI will flag violations. This directly addresses the need to enforce required relationships.

Correctness is one of the three primary CMDB Health Dashboard components, alongside completeness and compliance. It measures the accuracy of configuration item attributes against expected values, satisfying the stem's requirement to identify components evaluated under the health framework rather than related metrics such as duplicate or orphan CIs.

The green indicator means the measured metric satisfies or surpasses the target threshold configured for that CMDB data-quality metric, confirming acceptable health. Amber and red denote approaching or breaching thresholds respectively, so green specifically signals the target is met or exceeded.

Tuning IRE identification rules directly addresses the duplicate CIs flagged under Correctness. These rules define the attribute combinations (such as serial number or MAC address) that IRE uses to match incoming integration payloads against existing records; weak or missing criteria cause each payload to be inserted as a new CI rather than merged.

The Dependency Views icon beside the Configuration Item field opens a graphical map showing the CI's upstream and downstream relationships, including business services. This satisfies the requirement to assess affected services directly from the incident ticket without leaving the record.

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.

The Pattern Designer Debugger executes the discovery pattern step by step, exposing the raw payload and intermediate variable values at each operation. That lets the engineer pinpoint exactly which step fails to populate the custom application server's attributes, rather than inferring from final output alone.

Scheduled Data Export references a saved Query Builder result set or export definition, then runs it on a recurring schedule and delivers output to an external SFTP server. This provides the weekly automated export without manual intervention.

CI status indicators and map decorators render computed conditions directly onto the node, so a custom script evaluating warranty expiry within 30 days drives the alert symbol. This satisfies the requirement for a visual indicator tied to a dynamic condition rather than a static icon.

The Relationships related list on a Configuration Item form permits manual creation of CI-to-CI associations, satisfying the requirement to add a relationship without relying on Discovery. Discovery populates relationships automatically, whereas this related list supports direct user-defined entries, making it the appropriate location for manual linkage.

CMDB Data Manager enforces lifecycle policies that automatically retire or archive CIs once they match conditions such as operational status and last update date, directly satisfying the stem's requirement for rule-based, date-driven CI retirement without manual intervention.

The Correctness KPI includes stale CI scorecards identifying CIs that have exceeded the defined age threshold without an update.

The CSDM Data Foundations Dashboard specifically reports CSDM alignment across the four domains named in the stem: foundations, design, manage technical services, and sell/consume. It surfaces completeness and compliance gaps, directly satisfying the visibility requirement.

The Dependency Views Relationship Filter panel provides a dedicated control for toggling relationship types on the map, so selecting only "Hosted on" hides every other link. This directly satisfies the requirement to filter out non-essential relationships without altering the underlying CMDB data or rebuilding the map.

Saved queries become reusable reporting data sources, satisfying the stem's requirement for a key CMDB Query Builder attribute. Query Builder persists each definition, letting scheduled reports and dashboards consume the same result set without rebuilding logic, which distinguishes it from ad-hoc filtering elsewhere in the platform.

Standardising service data structures across the enterprise is a core CSDM benefit: it enforces a common taxonomy for business services, service offerings and CI relationships, eliminating divergent local models. This shared structure is precisely what lets the Data Foundations Dashboard aggregate comparable data and report on CSDM maturity against the stem's requirement.

Saved queries can be reused for reports and exports.

CMDB PA dashboards aggregate indicators and scores over time, exposing trends and data point movements that static list reports cannot show. This historical visibility satisfies the requirement to analyse how CMDB health and completeness change across periods.

The Discovery Log or Mapping Log attached to the specific CI node records each discovery step and explains why a process was skipped or excluded, giving the analyst the precise reason it never appeared on the map.

Audit history on the Configuration Item Relationship [cmdb_rel_ci] table records field-level changes to relationship records, capturing who manually altered each CI relationship and when. This directly satisfies the 30-day audit requirement for manual relationship modifications on production servers, since relationship edits are stored against that table rather than the CI records themselves.

Custom widget indicators and map decorators for Dependency Views are defined in the Dependency View Indicators configuration, where each indicator's condition, such as CPU utilisation above 90 per cent, and its warning badge are set.

The CMDB Health Dashboard's Completeness KPI can be configured with a list of attributes that are considered required for a class. Drilling into the KPI reveals an attribute-by-attribute breakdown, showing exactly which fields are missing and on how many CIs, which directly supports tasking data stewards with targeted remediation.

CMDB Baselines capture point-in-time snapshots of configuration items, and the Baseline Diff Viewer compares them against later states, satisfying the requirement to detect drift in critical infrastructure CIs. Both are native ServiceNow capabilities, so no custom development or external tooling is needed to establish the baseline.

A Partial status means Service Mapping could not complete the topology: discovery hit errors, lacked credentials for some devices, or saw traffic it could not map to a CI. The entry point is therefore only partially traced.

Traffic connections appear as directional lines between nodes, revealing live communication flows that satisfy the requirement to view active network relationships on the map. Service Mapping derives these from discovered TCP connections, so the map displays actual traffic paths rather than inferred dependencies, directly meeting the indicator-visibility constraint.

Correctness is one of the CMDB Health framework's primary pillars, alongside Completeness and Compliance. It measures whether CI records accurately reflect reality, covering duplicates, orphans and stale data, making it a foundational component of the health scoring model.

The map relies entirely on relationship records stored in the cmdb_rel_ci table to draw connections.

The CMDB Health Dashboard aggregates quality scores across the three prescribed axes — Completeness, Correctness, and Compliance — into one centralised view, directly satisfying the stem's requirement for a single reporting interface monitoring CMDB data quality. No other module consolidates all three metrics together.