CCNA CMDB Integration And Maintenance Questions

A Discovery Source records the tool or process that created or updated a configuration item, giving each CI record provenance. This lets administrators trace data origin, reconcile conflicting updates and trust records produced by authorised discovery methods, satisfying the need to know what populated the CMDB.

Staleness measures how long since a CI's last update by Discovery. When Discovery has not refreshed the Windows server records within the configured staleness threshold, the CMDB Health Dashboard flags them, producing the high staleness score described in the stem.

The CMDB Health Dashboard provides metrics and tools to identify duplicate CIs and other data quality issues. Regularly reviewing and reconciling duplicates helps maintain CMDB integrity. Even with good identification rules, duplicates can occur due to data inconsistencies. Using the dashboard to detect and merge duplicates is a proactive measure to minimize their impact. This action complements the identification rules.

A Discovery Exclusion List prevents specified devices or IP ranges from being probed and created as configuration items, directly satisfying the requirement to keep them out of the CMDB. It is applied before discovery runs, so excluded devices never generate CIs.

Reconciliation rules block unauthorized sources from updating records.

Service Mapping builds its service model by resolving CIs through identification attributes, so unstable or duplicate identifiers break topology generation. Ensuring existing CIs carry stable, unique identification attributes lets Service Mapping reliably match and extend the relationships already held in the CMDB during migration.

Discovery probes infrastructure and returns CIs and relationships as raw data; the Identification and Reconciliation Engine then applies identification rules to create or update authoritative CMDB records. This pipeline satisfies the stem by defining Discovery's role as a source feeding the CMDB rather than writing to it directly.

Duplicate CIs are those sharing identical identification criteria — the same combination of identifying attributes defined for their class. This matches the dashboard's duplicate metric, which flags records whose identification fingerprints collide, regardless of name or other non-identifying fields, satisfying the stem's requirement for how duplicates are defined.

The Discovery Dashboard aggregates discovery status metrics, showing totals of CIs discovered against those updated, which directly surfaces efficiency gaps in your Discovery infrastructure. It satisfies the stem's requirement for a summary view identifying potential issues, unlike raw logs or individual CI records that lack consolidated comparison.

A configuration item becomes stale when discovery has not refreshed its attributes within the expected reconciliation window, so the record no longer reflects reality. This differs from a missing CI, which discovery has never found at all.

Temporary Variables capture a step's returned data so later steps can reference it without re-querying the target. This satisfies the scenario's need to carry query output forward through the pattern's execution sequence, enabling dependent steps to consume values such as discovered attributes or identifiers.

Staleness arises when CIs are never revisited by Discovery. Ensuring every target device falls within a discovery schedule guarantees each CI is periodically re-verified, preventing devices from being silently omitted and their records ageing beyond acceptable staleness thresholds.

Without a matching pattern, Discovery cannot execute the probes and classification steps needed to identify and populate the device record, so the horizontal discovery run for that CI ends incomplete rather than producing a fully mapped configuration item. The missing-pattern constraint therefore halts completion for that device specifically.

Each discovery run creates a Discovery Status record, and its related Discovery Log tab lists per-device scan activity, including the specific device's probe results, errors and timings, making it the location to inspect that device's log.

In the CMDB, the 'ip_address' field on a server CI is typically a single-value field that stores the primary IP address. Additional IP addresses are represented as separate Network Adapter CIs (cmdb_ci_network_adapter) related to the server. Discovery patterns often populate the primary IP and create or update network adapter CIs for each interface. This design allows multiple IPs to be tracked without overloading a single field.

IRE applies identification and reconciliation rules to incoming Discovery payloads, matching CIs against existing records and resolving conflicting attribute values. This prevents duplicate CIs and enforces data integrity before anything is written to the CMDB.

Dependency View renders a CI's relationships as an interactive graphical map, showing upstream and downstream connections visually. This satisfies the graphical-format requirement, unlike list-based CI records, which present relationships as text and are harder to interpret at a glance.

Debug mode replays the discovery and mapping process step by step, exposing where CI attributes or relationships diverge from the actual infrastructure. This pinpoints why the business service is flagged inaccurate, which is the standard diagnostic path before rebuilding the service.

Reconciliation rules define which data source wins when multiple sources report conflicting values for a CI attribute, letting you set source precedence per attribute. This directly satisfies the stem's requirement to change a data source's priority, since precedence is configured there rather than in identification or CI class settings.

An orphan CI is a configuration item that has no relationships defined to any other CI in the CMDB. This typically results from incomplete discovery or missing dependency mapping, and it prevents accurate impact analysis until relationships are established.

Presence of required fields directly feeds the Completeness score, which measures whether mandatory attributes are populated on each CI. The dashboard flags CIs missing those fields, so this factor satisfies the stem's requirement for a completeness contributor rather than correctness, duplicate or orphan metrics.

Identification rules define the attributes IRE uses to match incoming Discovery data to existing records. If those criteria are wrong, the same physical hardware fails to match its existing CI, so Discovery inserts a new record instead, producing duplicates.

Identification Rules specify which CI attributes, such as serial number, MAC address or name, are compared against incoming discovery data to determine whether a record matches an existing CI. This satisfies the stem's requirement for the rule's primary function within the CMDB.

Identification Rules define the attributes and conditions Discovery uses to recognise and reconcile CIs into the correct class. Without one, discovered devices fall into default or unrelated classes, so the custom class is never populated, defeating the purpose of creating it.

CI Class Manager includes reconciliation rules that define source precedence for CI attributes. By ranking the Discovery source higher than the import source for the serial number attribute, the platform applies Discovery's value when both sources update the CI. This is the supported way to resolve conflicting attribute values between discovery sources and imports in the CMDB.

CMDB Data Manager automates lifecycle management of configuration items, satisfying the stem's focus on governing CI records across their lifespan. It applies policies for creation, certification, retirement and deletion, enforcing data hygiene without manual intervention. This directly addresses the requirement to manage CIs from onboarding through decommissioning, rather than merely discovering or reconciling them.

The Identification and Reconciliation Engine applies identification rules and reconciliation precedence to normalise incoming discovery data before it reaches the CMDB. This satisfies the requirement to orchestrate CI data flow while enforcing data quality and deduplication.

Dependency View renders CIs and their relationships as an interactive map, exposing upstream and downstream connections that flat lists hide. It satisfies the requirement to visualise dependencies, unlike related lists or CI class managers, which present records without topology context.

IRE requires identification rules to resolve to a single CI. When a payload matches multiple CIs, uniqueness cannot be established, so the engine rejects the payload and returns a non-uniqueness error rather than merging or arbitrarily selecting a record.

Staleness measures how long since a configuration item was last updated by a discovery source. When that interval exceeds the defined threshold, the CMDB Health Dashboard flags the CI as stale, indicating the record may no longer reflect reality.

The `cmdb_identifier_entry` table stores the identification rules that Discovery applies per CI class, so inspecting it reveals exactly which attribute combinations are being matched. Duplicates arise when those entries are misconfigured or missing, causing the same server to fail matching and create a new CI record instead.

Compliance is one of the three CMDB Health Dashboard metric families, evaluating CIs against defined certification, audit and policy requirements. It satisfies the stem's requirement by being an explicitly tracked health metric, alongside completeness and correctness, rather than a discovery or reconciliation setting.

The CMDB Health Dashboard aggregates discovery data into daily metrics on completeness, compliance and correctness, directly satisfying the requirement for daily monitoring. Unlike raw discovery logs or ad hoc queries, it surfaces stale or missing CIs continuously, letting administrators spot failing discovery schedules and credential issues before they degrade CMDB accuracy.

Using 'serial_number' as the sole identifier ensures that Discovery matches on this unique attribute. If a CI with the same serial number exists, it will be updated rather than duplicated. This is the correct approach because serial number is unique and reliable for routers.

Discovery Patterns are the probe definitions that instruct Discovery on which protocols, commands and credentials to use when querying devices. They sit at the collection stage of the Discovery-to-CMDB pipeline, translating raw device responses into structured attribute data before it reaches the CMDB.

The discovery pattern must include a step that maps the SNMP OID value to the correct CI attribute. If the pattern lacks this mapping or the mapping is incorrect, the attribute will remain empty even if the OID is queried. This is the most likely reason because the OID is correctly queried but the data is not stored, indicating a mapping issue in the pattern.

Each Discovery run is assigned a discovery_id that labels every log entry it produces, letting administrators trace messages back to one specific scan execution. This distinguishes concurrent or historical scans when correlating errors and statuses across the MID Server logs.

The Configuration > CIs module provides a list of all CIs in the CMDB. From there, you can open a specific CI record and edit its attributes manually. This is the standard way to correct a CI's data. It allows you to update fields like operating system version directly on the CI form.

The CMDB Identification and Reconciliation Engine (IRE) is designed to manage data from multiple sources. It uses identification rules to match incoming data to existing CIs and reconciliation rules to determine which source is authoritative for each attribute. This ensures that duplicates are minimized and the most trusted data is used. IRE is the correct feature to use in this scenario.

IRE Data Source Rules govern how discovered data is mapped onto CMDB attributes during identification and reconciliation. If 'Last discovered' updates but 'Operational status' does not, the data source rule controlling that field's mapping is where the discrepancy originates.

Because the CI Identification rule for the class uses Hostname as the sole identifier, a match on hostname is sufficient to identify the existing CI. Discovery will then update the CI's attributes, including the serial number, with the newly discovered value. This ensures the CMDB reflects the current state without creating duplicates.

Identification rules define the criteria and identifier attributes the Identification Engine uses to match incoming discovery data against existing CIs. Verifying them ensures records are correlated to the same physical device rather than spawning duplicate CIs for each discovery run.

In ServiceNow Discovery, each MID Server is configured with IP ranges and behaviors that define which network segments it is allowed to discover. When two MID Servers overlap on the same subnet, both can discover the same host, causing attribute values to alternate. Reviewing and correcting the MID Server IP range assignments so only one MID Server is authoritative for the subnet resolves the flipping.

Precedence ensures a single source wins for each attribute when both report values. This stabilizes the stored values so subsequent discovery runs match the existing CI instead of triggering re-identification and creating duplicates due to fluctuating attribute values.

Discovery patterns are written for specific classes and populate only the attributes they are designed to map. Business application CIs are typically created by Service Mapping or manually, so if no pattern or integration writes Environment, the attribute stays blank until populated by another source.

A reverting value almost always points to a precedence conflict where another source is listed above Discovery for that attribute. Inspecting the precedence list for CPU count on the Linux Server class reveals whether a second integration is overwriting Discovery's correct value during reconciliation.

The Identification and Reconciliation Engine logs record how discovered data is matched, merged and written to the CMDB, including why attributes such as memory are rejected or skipped. Inspecting them reveals the reconciliation failure preventing the record update.

The Identification payload is sent to the Identification and Reconciliation Engine, which applies identification rules, reconciliation rules and CI class precedence to decide whether the discovered data creates a new CI, updates an existing one, or is discarded as duplicate.

Reconciliation Rules resolve conflicts by comparing attribute values against a priority hierarchy, so assigning Discovery a higher precedence ensures its collected values prevail over imported external data. This directly satisfies the requirement that external asset imports must not overwrite Discovery-sourced attributes during reconciliation.

The CI Class Manager defines and maintains the class hierarchy and the CI identification and reconciliation rules that govern how discovered items are classified. This satisfies the requirement to manage both class structure and the rules applied to configuration items.

A pattern step timeout means the operation exceeded its configured limit, so raising that step's timeout value lets the longer-running command complete. This directly addresses the timeout constraint without altering the underlying discovery logic or credentials.

Reconciliation rules decide which source's attributes win when the same CI is discovered by multiple sources. Misconfigured precedence causes the engine to discard incoming values it should accept, so legitimate updates from valid sources are rejected and the CMDB goes stale.

Without the correct permissions in the reconciliation rule, the Discovery data source cannot update the attribute.

Orphaned CIs are those lacking any relationship to other configuration items, which is precisely the CMDB Health Dashboard's orphan metric. The dashboard flags records with zero inbound or outbound relations, indicating broken dependency mapping. This satisfies the stem's constraint: the CI exists but sits isolated, so no relationship records reference it.

Copying the default pattern preserves the original as a read-only baseline, letting you edit the duplicate without affecting out-of-box behaviour or breaking future upgrades. This satisfies the stem's requirement to prepare safely before modification, since ServiceNow overwrites customised defaults during patching, whereas a copied pattern remains untouched.

CMDB Data Manager allows you to create policies that automatically retire or delete CIs based on conditions such as last discovered date or operational status. It can be scheduled to run periodically, ensuring that stale CIs are marked as retired without manual intervention. This directly addresses the requirement to automatically retire decommissioned CIs.

The Data Source is the payload's declared origin, and it drives precedence during IRE processing: it determines which source's values win when multiple discovery sources contribute attributes to the same CI, affecting whether the CI is updated or created.

IRE logs record each identification and reconciliation decision, showing which identifier rule matched and which attribute value was written to the CMDB. This directly satisfies the requirement to debug why a specific CI attribute received its value.

Identification Rules define which CI attributes (such as serial number, name, or BIOS UUID) are matched to detect an existing CI before insertion. Misconfigured or missing rules cause Discovery to create new records instead of updating existing ones, producing duplicates.

The CI Class Manager governs the CMDB class model: it defines the class hierarchy and configures identification and reconciliation rules that determine how discovered data maps to CIs and how duplicates merge. This directly satisfies the requirement to manage hierarchy, identification, and reconciliation.

To establish a relationship between a printer and a switch, Discovery often relies on the switch's MAC address table (CAM table) to see which MAC addresses are learned on which ports. The printer's MAC address must be present in that table. If the switch's pattern fails to collect or process the MAC address table, the relationship cannot be created. This is a common reason for missing network relationships in Discovery.

Reconciliation rules resolve conflicting CI attribute values by applying the configured priority order, so the source with the higher priority overwrites the lower-priority value. This satisfies the stem's conflict scenario directly: precedence determines which discovered value persists in the CMDB, without manual intervention or record duplication.

Using the CMDB CI Lifecycle Management to transition the CI to a retired state is a structured approach to decommissioning. It ensures that the CI goes through the proper lifecycle stages, updating its status and potentially triggering workflows. This maintains data integrity by keeping a record of the CI's lifecycle and ensuring that it is no longer considered active. It is a recommended practice.

Identification rules determine how incoming CIs are matched and reconciled against existing records. Reviewing them first confirms the new tool's data will be identified correctly, preventing duplicate CIs before any discovery schedules or probes are configured.

The CMDB Audit History related list on a CI record logs each attribute change with the old and new value, the user or integration that performed the change, and a timestamp. This directly answers which source modified which attribute and when, making it the right tool for this review.

A Parse step applies a regular expression to the raw command output, extracting the required value from multi-line text by matching a defined pattern rather than relying on fixed line positions. This handles the multi-line output constraint reliably within the Discovery Pattern.

The CMDB Health Dashboard continuously scores configuration items against completeness, correctness and compliance metrics, surfacing stale, duplicate or orphaned records. This directly satisfies the stem's requirement to identify and report data quality issues, giving administrators actionable insight into CMDB integrity rather than merely storing data.

Orphaned CIs are those lacking any relationship record to other configuration items, leaving them disconnected from the service model. This status flags them for remediation so the CMDB accurately reflects dependencies rather than isolated, unlinked entries.

The CI Timeline displays a history of updates and the data sources that performed them.

Reconciliation Rules govern which data source may update a given CMDB attribute. If a rule excludes ServiceNow as an allowed source for the Operating System field, the pattern's correctly extracted value is discarded, leaving the attribute unchanged despite successful discovery.