CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
An audit evaluates the completed action: Read the indicator's problem overview, business impact and fix/improve guidance. It addressed the problem: A service owner wants to understand why a foundational-data playbook recommends a change. What evidence best demonstrates success?
Playbooks translate measured data-quality issues into actionable remediation context This observation validates the required outcome, not just the presence of a configured feature.
Multihop relationship modeling is needed to evaluate complete service dependencies. It does not establish that the owner can identify the problem, impact and recommended action from the playbook.
Linked CI dependencies reveal potential blast radius before infrastructure changes. It does not establish that the owner can identify the problem, impact and recommended action from the playbook.
Multisource records queries enable source-specific inventory reporting. It does not establish that the owner can identify the problem, impact and recommended action from the playbook.
A CMDB administrator must resolve both independent failures: (1) A query should include only Windows servers in a specific data center connected to a selected application service. (2) A dashboard must compare two cloud inventory sources to reveal CIs absent from one feed. Which coordinated plan satisfies both requirements?
First: Filters narrow graph results using attributes of different CI nodes Second: A gap query reports mismatched source coverage rather than merely comparing displayed names Both verification criteria must be met: The target data-center servers are returned and unrelated servers are excluded 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 other proposed action (Open the CI or service Dependency View or supported Unified Map) does not implement the first control. Filters narrow graph results using attributes of different CI nodes.
Filters narrow graph results using attributes of different CI nodes. A gap query reports mismatched source coverage rather than merely comparing displayed names. The proposed steps (Open the CI or service Dependency View or supported Unified Map; traverse CI relationships from the database to related application services using a supported dependency query or map) address other capabilities instead of this required pair.
Filters narrow graph results using attributes of different CI nodes. The other proposed action (traverse CI relationships from the database to related application services using a supported dependency query or map) addresses a different operation. A gap query reports mismatched source coverage rather than merely comparing displayed names.
A team configured: Use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages. Its original requirement was: A portfolio manager wants an overall view spanning strategy, delivery and consumer-facing services. Which observation proves that the desired operational outcome was achieved?
Portfolio governance spans CSDM domains rather than duplicating their objects This observation validates the required outcome, not just the presence of a configured feature.
A foundation-first adoption path prevents inconsistent references spreading across later domains. It does not establish that portfolio review traces a service from planning through delivery to consumption.
Service offerings describe consumable business commitments, not server hardware attributes. It does not establish that portfolio review traces a service from planning through delivery to consumption.
CSDM's value is service context and usability, not raw CI volume. It does not establish that portfolio review traces a service from planning through delivery to consumption.
A CMDB administrator must resolve both independent failures: (1) A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. (2) A company built direct update scripts to cmdb_ci and upgrades repeatedly break its mapping rules. Which coordinated plan satisfies both requirements?
First: Dependent identification may rely on relationships to identify CIs within a parent context Second: Supported extension points lower technical debt from direct internal table manipulation Both verification criteria must be met: The dependent CI matches its existing record when the required parent relationship is supplied An upgrade test still identifies and updates sample CIs without bypassing IRE
Dependent identification may rely on relationships to identify CIs within a parent context. Supported extension points lower technical debt from direct internal table manipulation. The proposed steps (Model procurement assets and operational CIs separately and link them where the model category supports it; apply reconciliation source priority and valid identification as the new data source is onboarded) address other capabilities instead of this required pair.
Dependent identification may rely on relationships to identify CIs within a parent context. The other proposed action (apply reconciliation source priority and valid identification as the new data source is onboarded) addresses a different operation. Supported extension points lower technical debt from direct internal table manipulation.
Supported extension points lower technical debt from direct internal table manipulation. The other proposed action (Model procurement assets and operational CIs separately and link them where the model category supports it) does not implement the first control. Dependent identification may rely on relationships to identify CIs within a parent context.
A CMDB program needs two changes. Requirement A: Two visually similar server names do not mean two CIs are identical physical hosts. Requirement B: A team wishes to delete non-CMDB records orphaned after retired CI cleanup. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Similar display names alone do not establish identical physical or logical identity Confirm it by testing: Distinct hosts remain separate and a truly matching test pair is consolidated
This resolves requirement B. 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
Published policies, not simply saved drafts, are processed by the applicable scheduled framework.
Reliable CI ownership fields enable routing and operational accountability.
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates.
After implementing the approved change — Model procurement assets and operational CIs separately and link them where the model category supports it — the data steward needs proof that it fixed: A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. What should the steward observe?
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies This observation validates the required outcome, not just the presence of a configured feature.
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. It does not establish that financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not establish that financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets.
Non-discoverable configuration data still needs controlled creation and periodic validation. It does not establish that financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets.
A configuration management team must address: An external inventory provides CSV files weekly and no ready connector exists. What change should it implement to demonstrate this result: A representative file creates or updates only the intended CI records?
Staging and mapping preserve input validation and can hand CI writes to supported IRE processing The proposed control addresses the stated problem, and its acceptance check is: A representative file creates or updates only the intended CI records
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: Use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls
Non-discoverable configuration data still needs controlled creation and periodic validation. It does not implement the specific required change for this case; the suitable control is: Use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls
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: Use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls
A CMDB change request reports: A new service CI class needs suggested parent-child relationship types visible to its modelers. Select the best implementation. It must pass this acceptance test: The relationship editor proposes the intended type for a compatible parent-child pair.
Suggested relationships guide consistent relationship selection without making every pairing physically true The proposed control addresses the stated problem, and its acceptance check is: The relationship editor proposes the intended type for a compatible parent-child pair
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: Configure the appropriate suggested relationships for the class in CI Class Manager
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: Configure the appropriate suggested relationships for the class in CI Class Manager
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data. It does not implement the specific required change for this case; the suitable control is: Configure the appropriate suggested relationships for the class in CI Class Manager
A CMDB engineer applied the control: Establish an attribute-level source-of-truth decision and enforce it through reconciliation. This was meant to resolve: Two integration owners disagree about the authoritative source for application environment status. Which result most directly confirms the implementation works?
Governance decisions should translate into technical rules preventing unapproved overwrites This observation validates the required outcome, not just the presence of a configured feature.
Archive, Retire and Delete policy types can require class-specific active retirement definitions. It does not establish that a lower-priority feed cannot overwrite the reviewed authoritative attribute.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not establish that a lower-priority feed cannot overwrite the reviewed authoritative attribute.
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. It does not establish that a lower-priority feed cannot overwrite the reviewed authoritative attribute.
A ServiceNow implementation team encounters this issue: A Data Manager Archive policy is configured for a class with no active retirement definition. Which control most directly resolves the issue and produces this outcome: The policy becomes eligible without bypassing lifecycle prerequisites?
Archive, Retire and Delete policy types can require class-specific active retirement definitions The proposed control addresses the stated problem, and its acceptance check is: The policy becomes eligible without bypassing lifecycle prerequisites
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: Create the required retirement definition before activating the eligible archive policy
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: Create the required retirement definition before activating the eligible archive policy
Stewardship prevents uncoordinated changes to shared business context. It does not implement the specific required change for this case; the suitable control is: Create the required retirement definition before activating the eligible archive policy
The change record states that the team will: Respect the supported asset-to-CI cost synchronization direction and keep asset financial data authoritative. The original defect was: Finance changes asset acquisition cost and expects manual reversal from the CI to rewrite the purchase ledger. Which validation finding should be accepted?
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings This observation validates the required outcome, not just the presence of a configured feature.
Dependent identification may rely on relationships to identify CIs within a parent context. It does not establish that asset cost updates the CI view but CI-only changes do not overwrite authoritative asset cost.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not establish that asset cost updates the CI view but CI-only changes do not overwrite authoritative asset cost.
Supported connectors reduce custom upgrade debt and integrate source identification. It does not establish that asset cost updates the CI view but CI-only changes do not overwrite authoritative asset cost.
Please check your mailbox for a message from support@examlabs.com and follow the directions.