CIS-DF Practice Questions

The CMDB Data Foundations Dashboard is designed to help administrators identify priority data issues and take structured remediation actions. When several metrics have low scores, the correct approach is not to randomly clean records or manipulate scoring rules. Instead, the administrator should prioritize the most important issues and use the recommended remediation guidance.

Option A is correct because Data Foundations emphasizes prioritizing metrics with Critical and High priority first. These metrics usually represent the most important issues affecting CMDB trust, operational readiness, service visibility, and downstream ITSM processes such as Incident, Change, and Problem Management. Focusing on the highest-priority metrics ensures remediation effort is aligned with business and operational risk.

Option C is also correct because the dashboard provides Remediation Playbooks linked to specific metrics. These playbooks give structured guidance for analyzing the issue, identifying impacted records, correcting the data, and improving governance so the problem does not return. This is the preferred Data Foundations approach because it supports repeatable, auditable, and best-practice remediation.

Option B is not recommended because changing exclusions simply to improve the score can hide poor data quality rather than fix it. Exclusion rules should only be used when records are legitimately out of scope. Option D may be valid in some lifecycle cleanup scenarios, but blindly removing non-operational or retired CIs is not the primary recommended action for improving dashboard health.

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 CMD

B.  

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 approach is controlled consolidation rather than preserving unnecessary custom classes or deleting records indiscriminately. CI Class Manager should be used to review the class hierarchy, identify suitable out-of-box ServiceNow classes, and govern the target data model. The existing CIs should then be moved or reclassified into those standard classes, with custom attributes mapped carefully to corresponding standard or approved extended attributes.

Retaining fragmented classes preserves the exact reporting and integration problems described in the scenario. Deleting the custom classes and manually recreating every CI is unnecessarily destructive and risks losing relationships, historical references, source information, and task associations.

Data Foundations recommends using existing supported classes wherever possible and extending an appropriate class only when the required model does not exist. Standardized classes improve inheritance, reporting, identification, reconciliation, Discovery integration, and upgrade compatibility.

=========

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.

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.

=========