CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A configuration management team must address: A support engineer needs a visual path from an application service to its infrastructure dependencies. What change should it implement to demonstrate this result: The view shows the application and the expected upstream infrastructure CIs?
Dependency visualization traverses relationship edges so potential impact is easier to understand The proposed control addresses the stated problem, and its acceptance check is: The view shows the application and the expected upstream infrastructure CIs
Filters narrow graph results using attributes of different CI nodes. It does not implement the specific required change for this case; the suitable control is: Open the CI or service Dependency View or supported Unified Map
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously. It does not implement the specific required change for this case; the suitable control is: Open the CI or service Dependency View or supported Unified Map
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: Open the CI or service Dependency View or supported Unified Map
A ServiceNow implementation team encounters this issue: Two inventory tools disagree about a server's owner and the steward needs the raw source evidence. Which control most directly resolves the issue and produces this outcome: Both conflicting values are visible with the chosen CMDB value distinguished?
Multisource preview exposes reported values alongside the current CMDB selection The proposed control addresses the stated problem, and its acceptance check is: Both conflicting values are visible with the chosen CMDB value distinguished
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: Open CMDB 360 Multisource Data Preview for the CI attribute
Query access roles distinguish executing saved queries from creating and changing them. It does not implement the specific required change for this case; the suitable control is: Open CMDB 360 Multisource Data Preview for the CI attribute
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: Open CMDB 360 Multisource Data Preview for the CI attribute
A ServiceNow configuration project has two acceptance conditions. The first issue is: Network switches are imported but their upstream connection relationships are missing. The second is: A hardware laptop has both an asset record and CI record, but the two reference fields are not paired. Which paired approach is suitable?
First: Reliable network maps depend on relationship creation and correctly identified endpoints Second: Asset synchronization requires logical linkage between a physical asset and its technical CI Both verification criteria must be met: The imported switch has the expected parent-child relationship rather than an orphan link A serial-number or location update reaches the associated record where the mapping permits
Reliable network maps depend on relationship creation and correctly identified endpoints. Asset synchronization requires logical linkage between a physical asset and its technical CI. The proposed steps (Use a properly credentialed Discovery schedule covering the intended address ranges; configure supported dependent identification or hosting relationship rules and supply the required parent reference) address other capabilities instead of this required pair.
Asset synchronization requires logical linkage between a physical asset and its technical CI. The other proposed action (Use a properly credentialed Discovery schedule covering the intended address ranges) does not implement the first control. Reliable network maps depend on relationship creation and correctly identified endpoints.
Reliable network maps depend on relationship creation and correctly identified endpoints. The other proposed action (configure supported dependent identification or hosting relationship rules and supply the required parent reference) addresses a different operation. Asset synchronization requires logical linkage between a physical asset and its technical CI.
An audit evaluates the completed action: Align lifecycle attribute source authority and the asset-CI status mapping. It addressed the problem: The same hardware CI alternates between In Use and Retired after two different feeds run. What evidence best demonstrates success?
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates This observation validates the required outcome, not just the presence of a configured feature.
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not establish that repeated import cycles preserve the reviewed hardware lifecycle state.
Similar display names alone do not establish identical physical or logical identity. It does not establish that repeated import cycles preserve the reviewed hardware lifecycle state.
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. It does not establish that repeated import cycles preserve the reviewed hardware lifecycle state.
A data governance release must meet both conditions: A: A team wishes to delete non-CMDB records orphaned after retired CI cleanup. B: Cloud instances are regularly terminated but their old CMDB records are still active after three months. Select the TWO necessary actions.
This resolves requirement B. Automated lifecycle governance reconciles discovered existence with administrative approval Confirm it by testing: Confirmed terminated instances no longer appear as active configuration items
This resolves requirement A. Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself Confirm it by testing: Only the approved dangling related entries are deleted while active references remain
Traceable data changes preserve accountability for non-discoverable or manually governed CIs.
Principal class focus enables targeted data foundation completeness work.
Governance decisions should translate into technical rules preventing unapproved overwrites.
A configuration management team must address: A service owner wants to understand why a foundational-data playbook recommends a change. What change should it implement to demonstrate this result: The owner can identify the problem, impact and recommended action from the playbook?
Playbooks translate measured data-quality issues into actionable remediation context The proposed control addresses the stated problem, and its acceptance check is: The owner can identify the problem, impact and recommended action from the playbook
Saved queries preserve graph semantics and can support repeatable consumption. It does not implement the specific required change for this case; the suitable control is: Read the indicator's problem overview, business impact and fix/improve guidance
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: Read the indicator's problem overview, business impact and fix/improve guidance
Standardized service representation supports comparable portfolio and operations reporting. It does not implement the specific required change for this case; the suitable control is: Read the indicator's problem overview, business impact and fix/improve guidance
A ServiceNow Data Foundations rollout has two blockers. First: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. Second: A Data Manager Archive policy is configured for a class with no active retirement definition. Which complete two-part implementation addresses both?
First: Improved identification prevents future collisions but does not retroactively merge every old duplicate Second: Archive, Retire and Delete policy types can require class-specific active retirement definitions Both verification criteria must be met: Existing task is closed appropriately and repeat ingestion does not produce a new duplicate The policy becomes eligible without bypassing lifecycle prerequisites
Improved identification prevents future collisions but does not retroactively merge every old duplicate. Archive, Retire and Delete policy types can require class-specific active retirement definitions. The proposed steps (Review class scope, asset linkage and deployment lifecycle before mass remediation; define a service owner approval and change-control process for governed naming updates) address other capabilities instead of this required pair.
Archive, Retire and Delete policy types can require class-specific active retirement definitions. The other proposed action (Review class scope, asset linkage and deployment lifecycle before mass remediation) does not implement the first control. Improved identification prevents future collisions but does not retroactively merge every old duplicate.
Improved identification prevents future collisions but does not retroactively merge every old duplicate. The other proposed action (define a service owner approval and change-control process for governed naming updates) addresses a different operation. Archive, Retire and Delete policy types can require class-specific active retirement definitions.
An implementation review finds these independent issues: (1) The governance team needs a recommended support group field for one class without making it universally mandatory. (2) An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. Which TWO controls should the team apply?
This resolves requirement A. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles Confirm it by testing: The class receives a recommended-field completeness score while record creation is not globally blocked
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
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data.
Multisource gap queries identify CIs not reported by one or more participating data sources.
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI.
A ServiceNow Data Foundations rollout has two blockers. First: A new service CI class needs suggested parent-child relationship types visible to its modelers. Second: An attribute priority based solely on source ordering gives a poor result when most sources agree on another value. Which complete two-part implementation addresses both?
First: Suggested relationships guide consistent relationship selection without making every pairing physically true Second: Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute Both verification criteria must be met: The relationship editor proposes the intended type for a compatible parent-child pair The recomputed CI attribute follows the tested dynamic selection logic
Suggested relationships guide consistent relationship selection without making every pairing physically true. Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. The proposed steps (Use preview or recompute where supported and verify the result against source history; inspect the class hierarchy and inherited attributes in CI Class Manager) address other capabilities instead of this required pair.
Suggested relationships guide consistent relationship selection without making every pairing physically true. The other proposed action (inspect the class hierarchy and inherited attributes in CI Class Manager) addresses a different operation. Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute.
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. The other proposed action (Use preview or recompute where supported and verify the result against source history) does not implement the first control. Suggested relationships guide consistent relationship selection without making every pairing physically true.
A ServiceNow implementation team encounters this issue: No team is accountable for correcting CI ownership gaps across cloud and on-premises inventories. Which control most directly resolves the issue and produces this outcome: Every affected CI class has an owner and a tracked correction backlog?
Governance requires clear decision rights and accountable remediation owners The proposed control addresses the stated problem, and its acceptance check is: Every affected CI class has an owner and a tracked correction backlog
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. It does not implement the specific required change for this case; the suitable control is: Assign class and data-steward ownership with escalation and recurring quality reviews
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: Assign class and data-steward ownership with escalation and recurring quality reviews
A de-duplication task groups competing CIs for controlled consolidation. It does not implement the specific required change for this case; the suitable control is: Assign class and data-steward ownership with escalation and recurring quality reviews
After implementing the approved change — Use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value — the data steward needs proof that it fixed: Cloud inventory and Discovery report different operating system versions for the same CI. What should the steward observe?
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field This observation validates the required outcome, not just the presence of a configured feature.
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not establish that the reviewer sees both source values and identifies the currently selected value.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. It does not establish that the reviewer sees both source values and identifies the currently selected value.
IRE identification matches incoming payloads to existing CIs before creating new records. It does not establish that the reviewer sees both source values and identifies the currently selected value.
Please check your mailbox for a message from support@examlabs.com and follow the directions.