CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB change request reports: A reporting team needs all servers last reported by a particular source with a particular OS family. Select the best implementation. It must pass this acceptance test: The report lists matching discovered servers while excluding other sources.
Multisource records queries enable source-specific inventory reporting The proposed control addresses the stated problem, and its acceptance check is: The report lists matching discovered servers while excluding other sources
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: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters
Impact analysis uses directed dependencies to identify affected services. It does not implement the specific required change for this case; the suitable control is: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters
ITSM workflows can use trustworthy configuration context for incident routing. It does not implement the specific required change for this case; the suitable control is: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters
An organization finds this data-foundation problem: The operations team cannot see where Database Server inherits its mandatory CI fields. Which approach best achieves the required outcome: The administrator identifies which parent supplies each required field before making a change?
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported The proposed control addresses the stated problem, and its acceptance check is: The administrator identifies which parent supplies each required field before making a change
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: Inspect the class hierarchy and inherited attributes in CI Class Manager
Multisource gap queries identify CIs not reported by one or more participating data sources. It does not implement the specific required change for this case; the suitable control is: Inspect the class hierarchy and inherited attributes in CI Class Manager
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates. It does not implement the specific required change for this case; the suitable control is: Inspect the class hierarchy and inherited attributes in CI Class Manager
A data governance release must meet both conditions: A: Product managers track strategic product ideas before any technology build is approved. B: A service offering catalog describes customer support hours but engineers put it on a server CI. Select the TWO necessary actions.
This resolves requirement A. Strategy records concern proposed opportunities before detailed architecture or delivery Confirm it by testing: An unapproved idea is visible in strategic planning but not misrepresented as a deployed service
This resolves requirement B. Service offerings describe consumable business commitments, not server hardware attributes Confirm it by testing: The customer-visible offering holds the schedule and its underlying instances remain separate
CSDM's value is service context and usability, not raw CI volume.
Foundation provides common organizational and reference data reused by other CSDM domains.
A foundation-first adoption path prevents inconsistent references spreading across later domains.
A ServiceNow implementation team encounters this issue: The governance team needs a recommended support group field for one class without making it universally mandatory. Which control most directly resolves the issue and produces this outcome: The class receives a recommended-field completeness score while record creation is not globally blocked?
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles The proposed control addresses the stated problem, and its acceptance check is: The class receives a recommended-field completeness score while record creation is not globally blocked
Multisource gap queries identify CIs not reported by one or more participating data sources. It does not implement the specific required change for this case; the suitable control is: Configure a class-specific recommended field through CI Class Manager health settings
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 a class-specific recommended field through CI Class Manager health settings
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: Configure a class-specific recommended field through CI Class Manager health settings
A data governance release must meet both conditions: A: A large batch of duplicate devices needs repeatable treatment across the same CI class. B: An executive requests one CMDB health score but support teams need practical remediation actions. Select the TWO necessary actions.
This resolves requirement A. Reusable templates provide consistent merge decisions across many de-duplication tasks Confirm it by testing: Sampled tasks keep their approved main CI and relationship settings after the batch
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
Attestation asks an accountable person to verify CI data at a defined interval.
Governance requires clear decision rights and accountable remediation owners.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A team wishes to delete non-CMDB records orphaned after retired CI cleanup. The second is: A new CMDB program imports every discovered object before deciding which services it supports. Which paired approach is suitable?
First: Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself Second: A scoped initial data foundation is easier to govern than an unactionable inventory Both verification criteria must be met: Only the approved dangling related entries are deleted while active references remain The selected classes serve the defined use cases and have health acceptance criteria
A scoped initial data foundation is easier to govern than an unactionable inventory. The other proposed action (Establish an attribute-level source-of-truth decision and enforce it through reconciliation) does not implement the first control. Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself.
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. A scoped initial data foundation is easier to govern than an unactionable inventory. The proposed steps (Establish an attribute-level source-of-truth decision and enforce it through reconciliation; configure a Data Manager Archive policy and the required retirement definition for eligible classes) address other capabilities instead of this required pair.
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. The other proposed action (configure a Data Manager Archive policy and the required retirement definition for eligible classes) addresses a different operation. A scoped initial data foundation is easier to govern than an unactionable inventory.
An audit evaluates the completed action: Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal. It addressed the problem: A company built direct update scripts to cmdb_ci and upgrades repeatedly break its mapping rules. What evidence best demonstrates success?
Supported extension points lower technical debt from direct internal table manipulation This observation validates the required outcome, not just the presence of a configured feature.
Relationship types distinguish hosting, containment, and dependencies for impact and service maps. It does not establish that an upgrade test still identifies and updates sample CIs without bypassing IRE.
Reliable network maps depend on relationship creation and correctly identified endpoints. It does not establish that an upgrade test still identifies and updates sample CIs without bypassing IRE.
Additional ingestion sources should not overwrite unrelated authoritative CI attributes. It does not establish that an upgrade test still identifies and updates sample CIs without bypassing IRE.
An audit evaluates the completed action: Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction. It addressed the problem: A hardware asset moves to pending disposal but its technical CI still reports the old hardware status. What evidence best demonstrates success?
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable 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 the associated hardware CI reflects the approved disposition after the asset state changes.
Supported extension points lower technical debt from direct internal table manipulation. It does not establish that the associated hardware CI reflects the approved disposition after the asset state changes.
Staging and mapping preserve input validation and can hand CI writes to supported IRE processing. It does not establish that the associated hardware CI reflects the approved disposition after the asset state changes.
A configuration management team must address: An attribute priority based solely on source ordering gives a poor result when most sources agree on another value. What change should it implement to demonstrate this result: The recomputed CI attribute follows the tested dynamic selection logic?
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute The proposed control addresses the stated problem, and its acceptance check is: The recomputed CI attribute follows the tested dynamic selection logic
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: Evaluate a supported dynamic reconciliation rule backed by CMDB 360 for that attribute
Child-level attributes scope specialized fields to the correct extension class. It does not implement the specific required change for this case; the suitable control is: Evaluate a supported dynamic reconciliation rule backed by CMDB 360 for that attribute
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. It does not implement the specific required change for this case; the suitable control is: Evaluate a supported dynamic reconciliation rule backed by CMDB 360 for that attribute
A data governance release must meet both conditions: A: A CMDB user can view saved graph queries but is not allowed to author new queries. B: A dashboard shows empty compliance results after no audit has run. Select the TWO necessary actions.
This resolves requirement A. Query access roles distinguish executing saved queries from creating and changing them Confirm it by testing: The analyst runs approved queries but cannot modify their definitions
This resolves requirement B. Compliance data requires completed audit evidence to make a trustworthy score Confirm it by testing: A configured test audit supplies actual pass/fail results to the dashboard
Dependency visualization traverses relationship edges so potential impact is easier to understand.
Security and vulnerability workflows gain useful prioritization from trusted service dependencies.
A single aggregate hides which technical quality condition is worsening.
During a CMDB review, engineers discover: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Which proposed action is appropriate if success is measured by: The vendor inventory loads with mapped CI classes and no duplicate source identities?
Supported connectors reduce custom upgrade debt and integrate source identification The proposed control addresses the stated problem, and its acceptance check is: The vendor inventory loads with mapped CI classes and no duplicate source identities
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: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not implement the specific required change for this case; the suitable control is: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
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: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
Please check your mailbox for a message from support@examlabs.com and follow the directions.