CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
After implementing the approved change — Review the de-duplication task and choose the valid main CI with its associated evidence — the data steward needs proof that it fixed: An IRE job detects two CIs representing the same router and creates a duplicate remediation task. What should the steward observe?
A de-duplication task groups competing CIs for controlled consolidation This observation validates the required outcome, not just the presence of a configured feature.
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. It does not establish that one authoritative router CI remains with agreed values and related records.
Stewardship prevents uncoordinated changes to shared business context. It does not establish that one authoritative router CI remains with agreed values and related records.
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not establish that one authoritative router CI remains with agreed values and related records.
An organization finds this data-foundation problem: A central team overrides business service names without approval from the service owners. Which approach best achieves the required outcome: An approved renaming request includes owner signoff and traceable changes?
Stewardship prevents uncoordinated changes to shared business context The proposed control addresses the stated problem, and its acceptance check is: 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. It does not implement the specific required change for this case; the suitable control is: Define a service owner approval and change-control process for governed naming updates
Relationship integrity is separate from a CI having complete attributes. It does not implement the specific required change for this case; the suitable control is: Define a service owner approval and change-control process for governed naming updates
Similar display names alone do not establish identical physical or logical identity. It does not implement the specific required change for this case; the suitable control is: Define a service owner approval and change-control process for governed naming updates
During a CMDB review, engineers discover: A retired application server is still linked as actively hosting an important service. Which proposed action is appropriate if success is measured by: Only the truly decommissioned server is retired and the service map points to its replacement?
CI lifecycle changes affect service dependency reporting and should be validated with owners The proposed control addresses the stated problem, and its acceptance check is: Only the truly decommissioned server is retired and the service map points to its replacement
Attestation asks an accountable person to verify CI data at a defined interval. It does not implement the specific required change for this case; the suitable control is: Review the service impact and relationship dependencies before retiring or archiving its CI
Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations. It does not implement the specific required change for this case; the suitable control is: Review the service impact and relationship dependencies before retiring or archiving its CI
Compliance results depend on audit conditions and executed evidence rather than field population alone. It does not implement the specific required change for this case; the suitable control is: Review the service impact and relationship dependencies before retiring or archiving its CI
A ServiceNow configuration project has two acceptance conditions. The first issue is: An executive wants a quick breakdown of where CMDB stewardship should focus first. The second is: A security team wants to prioritize vulnerable servers by their business criticality. Which paired approach is suitable?
First: Foundation indicators make recurring quality gaps visible and link them to improvement actions Second: Security and vulnerability workflows gain useful prioritization from trusted service dependencies Both verification criteria must be met: The report identifies the poorest-quality principal classes and a prioritized action A critical service server is scored higher than a noncritical isolated lab server under the tested criteria
Foundation indicators make recurring quality gaps visible and link them to improvement actions. The other proposed action (grant the documented query-builder read role rather than the authoring role) addresses a different operation. Security and vulnerability workflows gain useful prioritization from trusted service dependencies.
Foundation indicators make recurring quality gaps visible and link them to improvement actions. Security and vulnerability workflows gain useful prioritization from trusted service dependencies. The proposed steps (Open CMDB 360 Multisource Data Preview for the CI attribute; grant the documented query-builder read role rather than the authoring role) address other capabilities instead of this required pair.
Security and vulnerability workflows gain useful prioritization from trusted service dependencies. The other proposed action (Open CMDB 360 Multisource Data Preview for the CI attribute) does not implement the first control. Foundation indicators make recurring quality gaps visible and link them to improvement actions.
A CMDB program needs two changes. Requirement A: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. Requirement B: A hardware asset moves to pending disposal but its technical CI still reports the old hardware status. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable Confirm it by testing: The associated hardware CI reflects the approved disposition after the asset state changes
This resolves requirement A. Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs Confirm it by testing: The non-scannable application CI is updated from the authoritative API inventory
Relationship records encode application dependencies beyond the CI attributes themselves.
A correct source mapping is needed before identifier rules can classify incoming device records.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
Two ServiceNow configuration issues require separate remedies. First: A trusted import is allowed to update existing storage CIs but must not create new storage CIs. Second: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. Select exactly TWO appropriate steps.
This resolves requirement A. IRE data-source rules can control CI insertion separately from updating existing identified records Confirm it by testing: The import updates the matched storage CI but does not insert an unmatched device
This resolves requirement B. Reconciliation rule changes can require reevaluation of existing attribute choices Confirm it by testing: The selected CI value changes only as justified by configured source data and the tested recomputation
Multisource gap queries identify CIs not reported by one or more participating data sources.
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type.
A data steward is asked to resolve: A dashboard must compare two cloud inventory sources to reveal CIs absent from one feed. Which solution meets the requirement and verifies: The seeded one-source-only CI is returned and fully covered CIs are excluded?
A gap query reports mismatched source coverage rather than merely comparing displayed names The proposed control addresses the stated problem, and its acceptance check is: The seeded one-source-only CI is returned and fully covered CIs are excluded
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: Create a CMDB 360 Find Gap saved query across the selected sources
Impact analysis uses directed dependencies to identify affected services. It does not implement the specific required change for this case; the suitable control is: Create a CMDB 360 Find Gap saved query across the selected sources
Multihop relationship modeling is needed to evaluate complete service dependencies. It does not implement the specific required change for this case; the suitable control is: Create a CMDB 360 Find Gap saved query across the selected sources
Two ServiceNow configuration issues require separate remedies. First: A Data Manager Delete policy unexpectedly targets active production databases. Second: An executive requests one CMDB health score but support teams need practical remediation actions. Select exactly TWO appropriate steps.
This resolves requirement B. An aggregate score becomes useful when failures are traceable to actionable work items Confirm it by testing: Each critical failed metric has a named owner, affected CI sample and due date
This resolves requirement A. Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal Confirm it by testing: No active database is selected and only approved retired test records are eligible
Orphan metrics reveal CIs no longer connected or useful under configured criteria.
A de-duplication task groups competing CIs for controlled consolidation.
CI lifecycle changes affect service dependency reporting and should be validated with owners.
A ServiceNow configuration project has two acceptance conditions. The first issue is: The operations team cannot see where Database Server inherits its mandatory CI fields. The second is: Two sources insert separate server CIs because hostname alone is not a stable unique key. Which paired approach is suitable?
First: Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported Second: IRE identification matches incoming payloads to existing CIs before creating new records Both verification criteria must be met: The administrator identifies which parent supplies each required field before making a change Two payloads for the same server resolve to one existing CI during the test
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. IRE identification matches incoming payloads to existing CIs before creating new records. The proposed steps (Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources; use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value) address other capabilities instead of this required pair.
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. 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.
IRE identification matches incoming payloads to existing CIs before creating new records. The other proposed action (Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources) does not implement the first control. Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported.
A CMDB program needs two changes. Requirement A: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Requirement B: A hardware asset moves to pending disposal but its technical CI still reports the old hardware status. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Supported connectors reduce custom upgrade debt and integrate source identification Confirm it by testing: The vendor inventory loads with mapped CI classes and no duplicate source identities
This resolves requirement B. Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable Confirm it by testing: The associated hardware CI reflects the approved disposition after the asset state changes
Reliable network maps depend on relationship creation and correctly identified endpoints.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
Processing order and endpoint matching prevent dangling or mismatched relationship references.
A data steward is asked to resolve: The same hardware CI alternates between In Use and Retired after two different feeds run. Which solution meets the requirement and verifies: Repeated import cycles preserve the reviewed hardware lifecycle state?
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates The proposed control addresses the stated problem, and its acceptance check is: Repeated import cycles preserve the reviewed hardware lifecycle state
Similar display names alone do not establish identical physical or logical identity. It does not implement the specific required change for this case; the suitable control is: Align lifecycle attribute source authority and the asset-CI status mapping
Direct record deletion can leave broken or incomplete related records. It does not implement the specific required change for this case; the suitable control is: Align lifecycle attribute source authority and the asset-CI status mapping
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: Align lifecycle attribute source authority and the asset-CI status mapping
Please check your mailbox for a message from support@examlabs.com and follow the directions.