CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
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.
A ServiceNow implementation team encounters this issue: Two visually similar server names do not mean two CIs are identical physical hosts. Which control most directly resolves the issue and produces this outcome: Distinct hosts remain separate and a truly matching test pair is consolidated?
Similar display names alone do not establish identical physical or logical identity The proposed control addresses the stated problem, and its acceptance check is: Distinct hosts remain separate and a truly matching test pair is consolidated
Published policies, not simply saved drafts, are processed by the applicable scheduled framework. It does not implement the specific required change for this case; the suitable control is: Verify stable identification evidence before merging a suspected duplicate pair
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. It does not implement the specific required change for this case; the suitable control is: Verify stable identification evidence before merging a suspected duplicate pair
Reliable CI ownership fields enable routing and operational accountability. It does not implement the specific required change for this case; the suitable control is: Verify stable identification evidence before merging a suspected duplicate pair
A ServiceNow configuration project has two acceptance conditions. The first issue is: An analyst needs to compare the CI population connected to either Linux or Windows hosts in one graph. The second is: A security team wants to prioritize vulnerable servers by their business criticality. Which paired approach is suitable?
First: Graph query logic must represent OR alternatives rather than forcing both branches simultaneously Second: Security and vulnerability workflows gain useful prioritization from trusted service dependencies Both verification criteria must be met: Both valid host types appear and unrelated CI pairs do not A critical service server is scored higher than a noncritical isolated lab server under the tested criteria
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously. Security and vulnerability workflows gain useful prioritization from trusted service dependencies. The proposed steps (Validate supported service entry points and mapping context before inspecting the resulting map; 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 (Validate supported service entry points and mapping context before inspecting the resulting map) does not implement the first control. Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously. 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.
A ServiceNow implementation team encounters this issue: A query should include only Windows servers in a specific data center connected to a selected application service. Which control most directly resolves the issue and produces this outcome: The target data-center servers are returned and unrelated servers are excluded?
Filters narrow graph results using attributes of different CI nodes The proposed control addresses the stated problem, and its acceptance check is: The target data-center servers are returned and unrelated servers are excluded
Multisource preview exposes reported values alongside the current CMDB selection. It does not implement the specific required change for this case; the suitable control is: Apply class-node attribute filters and relationship conditions in CMDB Query Builder
A gap query reports mismatched source coverage rather than merely comparing displayed names. It does not implement the specific required change for this case; the suitable control is: Apply class-node attribute filters and relationship conditions in CMDB Query Builder
Dependency visualization traverses relationship edges so potential impact is easier to understand. It does not implement the specific required change for this case; the suitable control is: Apply class-node attribute filters and relationship conditions in CMDB Query Builder
Two ServiceNow configuration issues require separate remedies. First: A Data Manager Delete policy unexpectedly targets active production databases. Second: A retired application server is still linked as actively hosting an important service. Select exactly TWO appropriate steps.
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
This resolves requirement B. CI lifecycle changes affect service dependency reporting and should be validated with owners Confirm it by testing: Only the truly decommissioned server is retired and the service map points to its replacement
A stocked asset can exist financially without a currently operating CI for production impact.
Orphan metrics reveal CIs no longer connected or useful under configured criteria.
A de-duplication task groups competing CIs for controlled consolidation.
A team configured: Create the required retirement definition before activating the eligible archive policy. Its original requirement was: A Data Manager Archive policy is configured for a class with no active retirement definition. Which observation proves that the desired operational outcome was achieved?
Archive, Retire and Delete policy types can require class-specific active retirement definitions This observation validates the required outcome, not just the presence of a configured feature.
Reusable templates provide consistent merge decisions across many de-duplication tasks. It does not establish that the policy becomes eligible without bypassing lifecycle prerequisites.
Direct record deletion can leave broken or incomplete related records. It does not establish that the policy becomes eligible without bypassing lifecycle prerequisites.
Completeness Required measures required-field population for eligible CIs. It does not establish that the policy becomes eligible without bypassing lifecycle prerequisites.
A team configured: Save and schedule a supported CMDB Query Builder query and use its result set for reporting. Its original requirement was: A saved query must be reused for monthly reporting with consistent class and relationship criteria. Which observation proves that the desired operational outcome was achieved?
Saved queries preserve graph semantics and can support repeatable consumption This observation validates the required outcome, not just the presence of a configured feature.
Standardized service representation supports comparable portfolio and operations reporting. It does not establish that the next scheduled execution returns a comparable scoped result set.
Linked CI dependencies reveal potential blast radius before infrastructure changes. It does not establish that the next scheduled execution returns a comparable scoped result set.
Map accuracy depends on relationship data rather than cosmetic icon changes. It does not establish that the next scheduled execution returns a comparable scoped result set.
The change record states that the team will: Create the correctly directed CI relationship with the appropriate relationship type. The original defect was: A web application CI has no dependency link to its database and impact analysis misses downstream failures. Which validation finding should be accepted?
Relationship records encode application dependencies beyond the CI attributes themselves This observation validates the required outcome, not just the presence of a configured feature.
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. It does not establish that a dependency view now traverses from the application to the correct database CI.
Additional ingestion sources should not overwrite unrelated authoritative CI attributes. It does not establish that a dependency view now traverses from the application to the correct database CI.
Supported connectors reduce custom upgrade debt and integrate source identification. It does not establish that a dependency view now traverses from the application to the correct database CI.
A ServiceNow implementation team encounters this issue: A dashboard shows empty compliance results after no audit has run. Which control most directly resolves the issue and produces this outcome: A configured test audit supplies actual pass/fail results to the dashboard?
Compliance data requires completed audit evidence to make a trustworthy score The proposed control addresses the stated problem, and its acceptance check is: A configured test audit supplies actual pass/fail results to the dashboard
A gap query reports mismatched source coverage rather than merely comparing displayed names. It does not implement the specific required change for this case; the suitable control is: Validate the compliance audit configuration and execution before interpreting the empty tile as clean
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: Validate the compliance audit configuration and execution before interpreting the empty tile as clean
A relationship-aware query traverses edges rather than filtering only a flat CI list. It does not implement the specific required change for this case; the suitable control is: Validate the compliance audit configuration and execution before interpreting the empty tile as clean
After implementing the approved change — Monitor CMDB 360 'not reported by source' potential issues and reporting intervals — the data steward needs proof that it fixed: A weekly review shows one inventory feed stopped sending data without deleting the existing CIs. What should the steward observe?
Missing recent source activity can signal integration failure even when other feeds maintain the CI This observation validates the required outcome, not just the presence of a configured feature.
Dependency views operate on supported CMDB class and relationship information. It does not establish that the stopped feed appears in the issue list while current feeds remain healthy.
Map accuracy depends on relationship data rather than cosmetic icon changes. It does not establish that the stopped feed appears in the issue list while current feeds remain healthy.
Saved queries preserve graph semantics and can support repeatable consumption. It does not establish that the stopped feed appears in the issue list while current feeds remain healthy.
A CMDB engineer applied the control: Check the Duplicate CI Remediator scale limit and use a supported safe alternate remediation strategy. This was meant to resolve: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. Which result most directly confirms the implementation works?
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets This observation validates the required outcome, not just the presence of a configured feature.
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. It does not establish that the large set is processed within supported limits with auditable relationship handling.
Lifecycle cascades should not silently remove dependent records without approved controls. It does not establish that the large set is processed within supported limits with auditable relationship handling.
Staleness evaluates the recency of reported CI updates or discovery according to its rules. It does not establish that the large set is processed within supported limits with auditable relationship handling.
Please check your mailbox for a message from support@examlabs.com and follow the directions.