CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
During a CMDB review, engineers discover: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Which proposed action is appropriate if success is measured by: The vendor inventory loads with mapped CI classes and no duplicate source identities?
Supported connectors reduce custom upgrade debt and integrate source identification The proposed control addresses the stated problem, and its acceptance check is: The vendor inventory loads with mapped CI classes and no duplicate source identities
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not implement the specific required change for this case; the suitable control is: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not implement the specific required change for this case; the suitable control is: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
Reliable network maps depend on relationship creation and correctly identified endpoints. It does not implement the specific required change for this case; the suitable control is: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
A CMDB change request reports: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. Select the best implementation. It must pass this acceptance test: Existing task is closed appropriately and repeat ingestion does not produce a new duplicate.
Improved identification prevents future collisions but does not retroactively merge every old duplicate The proposed control addresses the stated problem, and its acceptance check is: Existing task is closed appropriately and repeat ingestion does not produce a new duplicate
Data-source coverage failures can cause stale CI results that should not be hidden by score adjustments. It does not implement the specific required change for this case; the suitable control is: Remediate existing duplicate records separately and test the revised IRE rule for future ingests
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not implement the specific required change for this case; the suitable control is: Remediate existing duplicate records separately and test the revised IRE rule for future ingests
A stocked asset can exist financially without a currently operating CI for production impact. It does not implement the specific required change for this case; the suitable control is: Remediate existing duplicate records separately and test the revised IRE rule for future ingests
An implementation review finds these independent issues: (1) A central team overrides business service names without approval from the service owners. (2) The same hardware CI alternates between In Use and Retired after two different feeds run. Which TWO controls should the team apply?
This resolves requirement B. Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates Confirm it by testing: Repeated import cycles preserve the reviewed hardware lifecycle state
This resolves requirement A. Stewardship prevents uncoordinated changes to shared business context Confirm it by testing: An approved renaming request includes owner signoff and traceable changes
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately.
Relationship integrity is separate from a CI having complete attributes.
Similar display names alone do not establish identical physical or logical identity.
A ServiceNow Data Foundations rollout has two blockers. First: A CMDB manager wants to distinguish correctness, completeness and compliance in a monthly report. Second: An administrator deletes a duplicate CI record directly and loses change relationships attached to it. Which complete two-part implementation addresses both?
First: The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately Second: Direct record deletion can leave broken or incomplete related records Both verification criteria must be met: The report identifies the specific failed metric rather than presenting only a total percentage Related change and incident records reference the retained main CI
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately. The other proposed action (examine the Staleness correctness metric and the class's staleness definition) addresses a different operation. Direct record deletion can leave broken or incomplete related records.
Direct record deletion can leave broken or incomplete related records. The other proposed action (Define a service owner approval and change-control process for governed naming updates) does not implement the first control. The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately.
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately. Direct record deletion can leave broken or incomplete related records. The proposed steps (Define a service owner approval and change-control process for governed naming updates; examine the Staleness correctness metric and the class's staleness definition) address other capabilities instead of this required pair.
An organization finds this data-foundation problem: A service portfolio manager cannot compare service reliability because applications are inconsistently represented in CMDB. Which approach best achieves the required outcome: Two departments' equivalent services appear under consistent classes and governance definitions?
Standardized service representation supports comparable portfolio and operations reporting The proposed control addresses the stated problem, and its acceptance check is: Two departments' equivalent services appear under consistent classes and governance definitions
Dependency views operate on supported CMDB class and relationship information. It does not implement the specific required change for this case; the suitable control is: Align application and service entities with the CSDM model and use suitable foundation indicators
Playbooks translate measured data-quality issues into actionable remediation context. It does not implement the specific required change for this case; the suitable control is: Align application and service entities with the CSDM model and use suitable foundation indicators
Missing recent source activity can signal integration failure even when other feeds maintain the CI. It does not implement the specific required change for this case; the suitable control is: Align application and service entities with the CSDM model and use suitable foundation indicators
A CMDB change request reports: A compliance reviewer cannot distinguish who approved a CI's manual changes from who loaded it. Select the best implementation. It must pass this acceptance test: The updated CI has a source, approver and linked change history.
Traceable data changes preserve accountability for non-discoverable or manually governed CIs The proposed control addresses the stated problem, and its acceptance check is: The updated CI has a source, approver and linked change history
Evaluated policy scope helps prevent accidental mass retirement or deletion. It does not implement the specific required change for this case; the suitable control is: Require change records, source metadata and reviewer ownership for manual CI updates
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. It does not implement the specific required change for this case; the suitable control is: Require change records, source metadata and reviewer ownership for manual CI updates
Fresh timestamps do not prove that a human has validated business ownership. It does not implement the specific required change for this case; the suitable control is: Require change records, source metadata and reviewer ownership for manual CI updates
A data steward is asked to resolve: A service owner needs all database servers used by one application and their hosting Linux machines. Which solution meets the requirement and verifies: The saved query returns all matching application, database and Linux server paths?
A relationship-aware query traverses edges rather than filtering only a flat CI list The proposed control addresses the stated problem, and its acceptance check is: The saved query returns all matching application, database and Linux server paths
Compliance data requires completed audit evidence to make a trustworthy score. It does not implement the specific required change for this case; the suitable control is: Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships
Dashboard measures should connect data quality to measurable operational outcomes. It does not implement the specific required change for this case; the suitable control is: Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships
Standardized service representation supports comparable portfolio and operations reporting. It does not implement the specific required change for this case; the suitable control is: Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships
The change record states that the team will: Review Orphan correctness rules and the affected class ownership and relationships. The original defect was: An orphan correctness indicator flags decommissioned CIs still in scope. Which validation finding should be accepted?
Orphan metrics reveal CIs no longer connected or useful under configured criteria This observation validates the required outcome, not just the presence of a configured feature.
Principal class focus enables targeted data foundation completeness work. It does not establish that confirmed orphan CIs are assigned to remediation without deleting needed active objects.
An aggregate score becomes useful when failures are traceable to actionable work items. It does not establish that confirmed orphan CIs are assigned to remediation without deleting needed active objects.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not establish that confirmed orphan CIs are assigned to remediation without deleting needed active objects.
A configuration management team must address: A monitoring feed overwrites the serial number populated by a more authoritative Discovery source. What change should it implement to demonstrate this result: Discovery keeps the trusted serial number after the lower-priority feed runs?
Reconciliation determines which incoming source may update each attribute on an existing CI The proposed control addresses the stated problem, and its acceptance check is: Discovery keeps the trusted serial number after the lower-priority feed runs
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. It does not implement the specific required change for this case; the suitable control is: Set an attribute-level static reconciliation rule with authorized sources and source priority
Suggested relationships guide consistent relationship selection without making every pairing physically true. It does not implement the specific required change for this case; the suitable control is: Set an attribute-level static reconciliation rule with authorized sources and source priority
Child-level attributes scope specialized fields to the correct extension class. It does not implement the specific required change for this case; the suitable control is: Set an attribute-level static reconciliation rule with authorized sources and source priority
A CMDB engineer applied the control: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager. This was meant to resolve: A team configures a new custom table unrelated to cmdb_ci and expects CI Class Manager to administer it. Which result most directly confirms the implementation works?
CI Class Manager is designed for classes in the CMDB hierarchy This observation validates the required outcome, not just the presence of a configured feature.
Reconciliation rule changes can require reevaluation of existing attribute choices. It does not establish that the non-CMDB table is managed correctly and no phantom CI class appears.
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. It does not establish that the non-CMDB table is managed correctly and no phantom CI class appears.
Reconciliation determines which incoming source may update each attribute on an existing CI. It does not establish that the non-CMDB table is managed correctly and no phantom CI class appears.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A team configures a new custom table unrelated to cmdb_ci and expects CI Class Manager to administer it. The second is: Two sources insert separate server CIs because hostname alone is not a stable unique key. Which paired approach is suitable?
First: CI Class Manager is designed for classes in the CMDB hierarchy Second: IRE identification matches incoming payloads to existing CIs before creating new records Both verification criteria must be met: The non-CMDB table is managed correctly and no phantom CI class appears Two payloads for the same server resolve to one existing CI during the test
IRE identification matches incoming payloads to existing CIs before creating new records. The other proposed action (Route incoming CI payloads through a supported IRE-aware ingestion path) does not implement the first control. CI Class Manager is designed for classes in the CMDB hierarchy.
CI Class Manager is designed for classes in the CMDB hierarchy. IRE identification matches incoming payloads to existing CIs before creating new records. The proposed steps (Route incoming CI payloads through a supported IRE-aware ingestion path; use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value) address other capabilities instead of this required pair.
CI Class Manager is designed for classes in the CMDB hierarchy. The other proposed action (use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value) addresses a different operation. IRE identification matches incoming payloads to existing CIs before creating new records.
Please check your mailbox for a message from support@examlabs.com and follow the directions.