CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A ServiceNow implementation team encounters this issue: The correctness score reports numerous duplicate Linux servers created by two tools. Which control most directly resolves the issue and produces this outcome: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures?
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions The proposed control addresses the stated problem, and its acceptance check is: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not implement the specific required change for this case; the suitable control is: Review the Duplicate correctness metric and the applicable CI identification rules
A scoped initial data foundation is easier to govern than an unactionable inventory. It does not implement the specific required change for this case; the suitable control is: Review the Duplicate correctness metric and the applicable CI identification rules
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: Review the Duplicate correctness metric and the applicable CI identification rules
A ServiceNow implementation team encounters this issue: A custom CMDB integration uses a direct table insert and bypasses existing IRE identification logic. Which control most directly resolves the issue and produces this outcome: The ingest uses identification rules and does not insert another copy of a known CI?
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates The proposed control addresses the stated problem, and its acceptance check is: The ingest uses identification rules and does not insert another copy of a known CI
CI Class Manager is designed for classes in the CMDB hierarchy. It does not implement the specific required change for this case; the suitable control is: Route incoming CI payloads through a supported IRE-aware ingestion path
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. It does not implement the specific required change for this case; the suitable control is: Route incoming CI payloads through a supported IRE-aware ingestion path
Attribute-level history identifies the source of accepted updates after applicable rules are enabled. It does not implement the specific required change for this case; the suitable control is: Route incoming CI payloads through a supported IRE-aware ingestion path
The change record states that the team will: Test insertion versus matching-update behavior separately and configure reconciliation for updates. The original defect was: An update payload identifies an existing CI but an administrator expects reconciliation rules to apply to first-time inserts identically. Which validation finding should be accepted?
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI This observation validates the required outcome, not just the presence of a configured feature.
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 first valid insert succeeds and later conflicting source updates obey reconciliation precedence.
Suggested relationships guide consistent relationship selection without making every pairing physically true. It does not establish that the first valid insert succeeds and later conflicting source updates obey reconciliation precedence.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. It does not establish that the first valid insert succeeds and later conflicting source updates obey reconciliation precedence.
An implementation review finds these independent issues: (1) A compliance reviewer cannot distinguish who approved a CI's manual changes from who loaded it. (2) A Data Manager Archive policy is configured for a class with no active retirement definition. Which TWO controls should the team apply?
This resolves requirement A. Traceable data changes preserve accountability for non-discoverable or manually governed CIs Confirm it by testing: The updated CI has a source, approver and linked change history
This resolves requirement B. Archive, Retire and Delete policy types can require class-specific active retirement definitions Confirm it by testing: The policy becomes eligible without bypassing lifecycle prerequisites
Evaluated policy scope helps prevent accidental mass retirement or deletion.
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself.
Fresh timestamps do not prove that a human has validated business ownership.
A CMDB change request reports: A program measures CSDM success by number of created rows alone despite low service ownership coverage. Select the best implementation. It must pass this acceptance test: The adoption report shows verified owners and valid links for the priority services.
CSDM's value is service context and usability, not raw CI volume The proposed control addresses the stated problem, and its acceptance check is: The adoption report shows verified owners and valid links for the priority services
Foundation provides common organizational and reference data reused by other CSDM domains. It does not implement the specific required change for this case; the suitable control is: Define adoption KPIs for correctly mapped services, owners and relationships
Portfolio governance spans CSDM domains rather than duplicating their objects. It does not implement the specific required change for this case; the suitable control is: Define adoption KPIs for correctly mapped services, owners and relationships
Strategy records concern proposed opportunities before detailed architecture or delivery. It does not implement the specific required change for this case; the suitable control is: Define adoption KPIs for correctly mapped services, owners and relationships
An organization finds this data-foundation problem: A service operations team must map production application service instances and their infrastructure dependencies. Which approach best achieves the required outcome: The service instance maps to actual deployed infrastructure and support ownership?
Service Delivery describes technology and running services used to fulfill customer-facing outcomes The proposed control addresses the stated problem, and its acceptance check is: The service instance maps to actual deployed infrastructure and support ownership
Service offerings describe consumable business commitments, not server hardware attributes. It does not implement the specific required change for this case; the suitable control is: Place operational application services in the Service Delivery part of CSDM
CSDM's value is service context and usability, not raw CI volume. It does not implement the specific required change for this case; the suitable control is: Place operational application services in the Service Delivery part of CSDM
Shared CSDM objects reduce semantic drift across workflows and reporting. It does not implement the specific required change for this case; the suitable control is: Place operational application services in the Service Delivery part of CSDM
A ServiceNow Data Foundations rollout has two blockers. First: Stale active servers should first be marked retired rather than immediately removed from CMDB. Second: A compliance reviewer cannot distinguish who approved a CI's manual changes from who loaded it. Which complete two-part implementation addresses both?
First: Retire policies transition eligible active CIs before downstream archive or deletion Second: Traceable data changes preserve accountability for non-discoverable or manually governed CIs Both verification criteria must be met: The stale test server reaches the retired state and is still recoverable for review The updated CI has a source, approver and linked change history
Retire policies transition eligible active CIs before downstream archive or deletion. Traceable data changes preserve accountability for non-discoverable or manually governed CIs. The proposed steps (Verify stable identification evidence before merging a suspected duplicate pair; preview or evaluate policy targets and approval requirements before publishing the change) address other capabilities instead of this required pair.
Traceable data changes preserve accountability for non-discoverable or manually governed CIs. The other proposed action (Verify stable identification evidence before merging a suspected duplicate pair) does not implement the first control. Retire policies transition eligible active CIs before downstream archive or deletion.
Retire policies transition eligible active CIs before downstream archive or deletion. The other proposed action (preview or evaluate policy targets and approval requirements before publishing the change) addresses a different operation. Traceable data changes preserve accountability for non-discoverable or manually governed CIs.
An organization finds this data-foundation problem: A large batch of duplicate devices needs repeatable treatment across the same CI class. Which approach best achieves the required outcome: Sampled tasks keep their approved main CI and relationship settings after the batch?
Reusable templates provide consistent merge decisions across many de-duplication tasks The proposed control addresses the stated problem, and its acceptance check is: Sampled tasks keep their approved main CI and relationship settings after the batch
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: Configure a reviewed de-duplication template and apply it through the supported dashboard
Governance requires clear decision rights and accountable remediation owners. It does not implement the specific required change for this case; the suitable control is: Configure a reviewed de-duplication template and apply it through the supported dashboard
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: Configure a reviewed de-duplication template and apply it through the supported dashboard
A configuration management team must address: A child CI class requires a new application build field but sibling classes must remain unaffected. What change should it implement to demonstrate this result: The new field appears for the intended child class while sibling forms remain unaffected?
Child-level attributes scope specialized fields to the correct extension class The proposed control addresses the stated problem, and its acceptance check is: The new field appears for the intended child class while sibling forms remain unaffected
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. It does not implement the specific required change for this case; the suitable control is: Add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition
Reconciliation rule changes can require reevaluation of existing attribute choices. It does not implement the specific required change for this case; the suitable control is: Add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI. It does not implement the specific required change for this case; the suitable control is: Add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition
A CMDB change request reports: A data owner needs quarterly human confirmation that a set of CIs is still correct. Select the best implementation. It must pass this acceptance test: Reviewers receive and complete the required attestation tasks for sampled CIs.
Attestation asks an accountable person to verify CI data at a defined interval The proposed control addresses the stated problem, and its acceptance check is: Reviewers receive and complete the required attestation tasks for sampled CIs
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: Use a Data Manager Attestation policy assigned to the accountable reviewers
CI lifecycle changes affect service dependency reporting and should be validated with owners. It does not implement the specific required change for this case; the suitable control is: Use a Data Manager Attestation policy assigned to the accountable reviewers
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: Use a Data Manager Attestation policy assigned to the accountable reviewers
Two change requests must be delivered together. Requirement A: An external connector imports duplicate rows for a host across multiple scheduled runs. Requirement B: A hardware laptop has both an asset record and CI record, but the two reference fields are not paired. Select the plan that resolves both.
First: Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle Second: Asset synchronization requires logical linkage between a physical asset and its technical CI Both verification criteria must be met: Two imports of an identical host leave one CI with updated source data A serial-number or location update reaches the associated record where the mapping permits
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. Asset synchronization requires logical linkage between a physical asset and its technical CI. The proposed steps (Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal; use a properly credentialed Discovery schedule covering the intended address ranges) 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 (Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal) does not implement the first control. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. The other proposed action (use a properly credentialed Discovery schedule covering the intended address ranges) addresses a different operation. Asset synchronization requires logical linkage between a physical asset and its technical CI.
Please check your mailbox for a message from support@examlabs.com and follow the directions.