CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB engineer applied the control: Configure required or recommended class fields and a scheduled quality backlog. This was meant to resolve: A new principal CI class is selected for governance but its key ownership fields are unpopulated. Which result most directly confirms the implementation works?
Principal class focus enables targeted data foundation completeness work This observation validates the required outcome, not just the presence of a configured feature.
Published policies, not simply saved drafts, are processed by the applicable scheduled framework. It does not establish that principal class scorecards reflect the corrected ownership information.
A scoped initial data foundation is easier to govern than an unactionable inventory. It does not establish that principal class scorecards reflect the corrected ownership information.
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not establish that principal class scorecards reflect the corrected ownership information.
A CMDB administrator must resolve both independent failures: (1) A virtualization team created Linux servers under the generic Computer class and cannot report Linux-only attributes. (2) The operations dashboard should list devices present in Discovery but missing from a second inventory feed. Which coordinated plan satisfies both requirements?
First: A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type Second: Multisource gap queries identify CIs not reported by one or more participating data sources Both verification criteria must be met: Linux-specific reports include migrated server CIs without mixing desktop computers The missing-source inventory lists the seeded device and excludes a device reported by both feeds
Multisource gap queries identify CIs not reported by one or more participating data sources. The other proposed action (Set an attribute-level static reconciliation rule with authorized sources and source priority) does not implement the first control. A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. The other proposed action (inspect the class hierarchy and inherited attributes in CI Class Manager) addresses a different operation. Multisource gap queries identify CIs not reported by one or more participating data sources.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. Multisource gap queries identify CIs not reported by one or more participating data sources. The proposed steps (Set an attribute-level static reconciliation rule with authorized sources and source priority; inspect the class hierarchy and inherited attributes in CI Class Manager) address other capabilities instead of this required pair.
After implementing the approved change — Configure and run the applicable CMDB compliance audit or certification template — the data steward needs proof that it fixed: A compliance tile shows no results despite multiple mandatory fields being filled. What should the steward observe?
Compliance results depend on audit conditions and executed evidence rather than field population alone This observation validates the required outcome, not just the presence of a configured feature.
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not establish that the compliance score reflects the seeded pass and fail conditions after the audit runs.
Continuous KPI governance detects regressions after point-in-time remediation. It does not establish that the compliance score reflects the seeded pass and fail conditions after the audit runs.
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. It does not establish that the compliance score reflects the seeded pass and fail conditions after the audit runs.
A data steward is asked to resolve: Customer relationship managers need a business service offering visible to internal consumers. Which solution meets the requirement and verifies: The service catalog presents the offering linked to the supporting delivery service?
Service Consumption expresses what consumers request, rather than how technical systems are hosted The proposed control addresses the stated problem, and its acceptance check is: The service catalog presents the offering linked to the supporting delivery service
A foundation-first adoption path prevents inconsistent references spreading across later domains. It does not implement the specific required change for this case; the suitable control is: Model the consumable business service and its service offering in Service Consumption
Incremental CSDM implementation reduces risk and enables feedback between milestones. It does not implement the specific required change for this case; the suitable control is: Model the consumable business service and its service offering in Service Consumption
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: Model the consumable business service and its service offering in Service Consumption
An audit evaluates the completed action: Investigate and repair orphan relationships in the relationship health results. It addressed the problem: A relationship health report contains edges with missing parent CI references. What evidence best demonstrates success?
Relationship integrity is separate from a CI having complete attributes This observation validates the required outcome, not just the presence of a configured feature.
Governance decisions should translate into technical rules preventing unapproved overwrites. It does not establish that the corrected edge links two valid CIs and no longer appears as orphan.
Governance requires clear decision rights and accountable remediation owners. It does not establish that the corrected edge links two valid CIs and no longer appears as orphan.
Lifecycle cascades should not silently remove dependent records without approved controls. It does not establish that the corrected edge links two valid CIs and no longer appears as orphan.
An organization finds this data-foundation problem: CMDB health completeness is low because most Windows servers are missing a mandatory owned-by field. Which approach best achieves the required outcome: Required completeness improves after the sampled Windows servers receive approved owners?
Completeness Required measures required-field population for eligible CIs The proposed control addresses the stated problem, and its acceptance check is: Required completeness improves after the sampled Windows servers receive approved owners
Stewardship prevents uncoordinated changes to shared business context. It does not implement the specific required change for this case; the suitable control is: Review Required completeness failures and correct the missing mandatory ownership data
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. It does not implement the specific required change for this case; the suitable control is: Review Required completeness failures and correct the missing mandatory ownership data
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: Review Required completeness failures and correct the missing mandatory ownership data
A configuration management team must address: Cloud instances are regularly terminated but their old CMDB records are still active after three months. What change should it implement to demonstrate this result: Confirmed terminated instances no longer appear as active configuration items?
Automated lifecycle governance reconciles discovered existence with administrative approval The proposed control addresses the stated problem, and its acceptance check is: Confirmed terminated instances no longer appear as active configuration items
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: Define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy
Relationship integrity is separate from a CI having complete attributes. It does not implement the specific required change for this case; the suitable control is: Define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy
Direct record deletion can leave broken or incomplete related records. It does not implement the specific required change for this case; the suitable control is: Define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy
A CMDB engineer applied the control: Place operational application services in the Service Delivery part of CSDM. This was meant to resolve: A service operations team must map production application service instances and their infrastructure dependencies. Which result most directly confirms the implementation works?
Service Delivery describes technology and running services used to fulfill customer-facing outcomes This observation validates the required outcome, not just the presence of a configured feature.
Shared CSDM objects reduce semantic drift across workflows and reporting. It does not establish that the service instance maps to actual deployed infrastructure and support ownership.
CSDM's value is service context and usability, not raw CI volume. It does not establish that the service instance maps to actual deployed infrastructure and support ownership.
Accurate CSDM mapping needs collaboration between service providers and consumers. It does not establish that the service instance maps to actual deployed infrastructure and support ownership.
A data governance release must meet both conditions: A: An external connector imports duplicate rows for a host across multiple scheduled runs. B: A company built direct update scripts to cmdb_ci and upgrades repeatedly break its mapping rules. Select the TWO necessary actions.
This resolves requirement B. Supported extension points lower technical debt from direct internal table manipulation Confirm it by testing: An upgrade test still identifies and updates sample CIs without bypassing IRE
This resolves requirement A. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle Confirm it by testing: Two imports of an identical host leave one CI with updated source data
Relationship types distinguish hosting, containment, and dependencies for impact and service maps.
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable.
Relationship direction matters for accurate dependency traversals and service modeling.
After implementing the approved change — Define a service owner approval and change-control process for governed naming updates — the data steward needs proof that it fixed: A central team overrides business service names without approval from the service owners. What should the steward observe?
Stewardship prevents uncoordinated changes to shared business context This observation validates the required outcome, not just the presence of a configured feature.
Automated lifecycle governance reconciles discovered existence with administrative approval. It does not establish that an approved renaming request includes owner signoff and traceable changes.
Direct record deletion can leave broken or incomplete related records. It does not establish that an approved renaming request includes owner signoff and traceable changes.
Lifecycle cascades should not silently remove dependent records without approved controls. It does not establish that an approved renaming request includes owner signoff and traceable changes.
Two change requests must be delivered together. Requirement A: An orphan correctness indicator flags decommissioned CIs still in scope. Requirement B: An executive requests one CMDB health score but support teams need practical remediation actions. Select the plan that resolves both.
First: Orphan metrics reveal CIs no longer connected or useful under configured criteria Second: An aggregate score becomes useful when failures are traceable to actionable work items Both verification criteria must be met: Confirmed orphan CIs are assigned to remediation without deleting needed active objects Each critical failed metric has a named owner, affected CI sample and due date
Orphan metrics reveal CIs no longer connected or useful under configured criteria. An aggregate score becomes useful when failures are traceable to actionable work items. The proposed steps (Use guided de-duplication or an approved remediation workflow to reconcile references before deletion; configure a reviewed de-duplication template and apply it through the supported dashboard) address other capabilities instead of this required pair.
Orphan metrics reveal CIs no longer connected or useful under configured criteria. The other proposed action (configure a reviewed de-duplication template and apply it through the supported dashboard) addresses a different operation. An aggregate score becomes useful when failures are traceable to actionable work items.
An aggregate score becomes useful when failures are traceable to actionable work items. The other proposed action (Use guided de-duplication or an approved remediation workflow to reconcile references before deletion) does not implement the first control. Orphan metrics reveal CIs no longer connected or useful under configured criteria.
Please check your mailbox for a message from support@examlabs.com and follow the directions.