CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
After implementing the approved change — Model appropriate development or SDLC components in Build and Integration — the data steward needs proof that it fixed: Developers need traceability for application components under active development and release. What should the steward observe?
Build and Integration represents build-phase components before delivery operations This observation validates the required outcome, not just the presence of a configured feature.
Incremental CSDM implementation reduces risk and enables feedback between milestones. It does not establish that component links point to owned development work without claiming a running production service.
Accurate CSDM mapping needs collaboration between service providers and consumers. It does not establish that component links point to owned development work without claiming a running production service.
A foundation-first adoption path prevents inconsistent references spreading across later domains. It does not establish that component links point to owned development work without claiming a running production service.
Two change requests must be delivered together. Requirement A: Enterprise architects maintain a business capability map and plans for applications they may buy. Requirement B: A program measures CSDM success by number of created rows alone despite low service ownership coverage. Select the plan that resolves both.
First: Design and Planning represents intended enterprise architecture, separate from runtime CIs Second: CSDM's value is service context and usability, not raw CI volume Both verification criteria must be met: Capability reports show planned business application relationships without fictitious deployed instances 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 other proposed action (Adopt a phased approach starting with priority services and measurable outcomes) does not implement the first control. Design and Planning represents intended enterprise architecture, separate from runtime CIs.
Design and Planning represents intended enterprise architecture, separate from runtime CIs. The other proposed action (represent the ideas in the CSDM Ideation and Strategy domain) addresses a different operation. CSDM's value is service context and usability, not raw CI volume.
Design and Planning represents intended enterprise architecture, separate from runtime CIs. CSDM's value is service context and usability, not raw CI volume. The proposed steps (Adopt a phased approach starting with priority services and measurable outcomes; represent the ideas in the CSDM Ideation and Strategy domain) address other capabilities instead of this required pair.
A CMDB program needs two changes. Requirement A: An application service has no defined entry points and automatic service mapping misses its runtime. Requirement B: A security team wants to prioritize vulnerable servers by their business criticality. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. Security and vulnerability workflows gain useful prioritization from trusted service dependencies Confirm it by testing: A critical service server is scored higher than a noncritical isolated lab server under the tested criteria
This resolves requirement A. Service mapping needs a starting entry point or suitable relationships to identify service infrastructure Confirm it by testing: The service visualization contains the expected application hosts after entry-point correction
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.
Playbooks translate measured data-quality issues into actionable remediation context.
Multihop relationship modeling is needed to evaluate complete service dependencies.
A CMDB engineer applied the control: Assign class and data-steward ownership with escalation and recurring quality reviews. This was meant to resolve: No team is accountable for correcting CI ownership gaps across cloud and on-premises inventories. Which result most directly confirms the implementation works?
Governance requires clear decision rights and accountable remediation owners This observation validates the required outcome, not just the presence of a configured feature.
Lifecycle cascades should not silently remove dependent records without approved controls. It does not establish that every affected CI class has an owner and a tracked correction backlog.
Relationship integrity is separate from a CI having complete attributes. It does not establish that every affected CI class has an owner and a tracked correction backlog.
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not establish that every affected CI class has an owner and a tracked correction backlog.
A configuration management team must address: An incident assignment group is missing on many production database CIs. What change should it implement to demonstrate this result: A test incident is directed to the intended database support group?
Reliable CI ownership fields enable routing and operational accountability The proposed control addresses the stated problem, and its acceptance check is: A test incident is directed to the intended database support group
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: Assign an authoritative support group or enrich it from governed relationships
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: Assign an authoritative support group or enrich it from governed relationships
Similar display names alone do not establish identical physical or logical identity. It does not implement the specific required change for this case; the suitable control is: Assign an authoritative support group or enrich it from governed relationships
A CMDB engineer applied the control: Separate discoverable and non-discoverable populations with suitable policies and review gates. This was meant to resolve: A governance team proposes deleting every CI not seen by a discovery scan even when some are manually maintained contracts. Which result most directly confirms the implementation works?
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI This observation validates the required outcome, not just the presence of a configured feature.
A de-duplication task groups competing CIs for controlled consolidation. It does not establish that manual business records remain while truly stale discoverable infrastructure enters review.
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately. It does not establish that manual business records remain while truly stale discoverable infrastructure enters review.
Attestation asks an accountable person to verify CI data at a defined interval. It does not establish that manual business records remain while truly stale discoverable infrastructure enters review.
A CMDB program needs two changes. Requirement A: A child CI class requires a new application build field but sibling classes must remain unaffected. Requirement B: A trusted import is allowed to update existing storage CIs but must not create new storage CIs. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. IRE data-source rules can control CI insertion separately from updating existing identified records Confirm it by testing: The import updates the matched storage CI but does not insert an unmatched device
This resolves requirement A. Child-level attributes scope specialized fields to the correct extension class Confirm it by testing: 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.
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI.
Reconciliation rule changes can require reevaluation of existing attribute choices.
A CMDB change request reports: A customer-impact report needs the set of services that depend on a failed database CI. Select the best implementation. It must pass this acceptance test: The report lists the affected services while excluding unrelated workloads.
Impact analysis uses directed dependencies to identify affected services The proposed control addresses the stated problem, and its acceptance check is: The report lists the affected services while excluding unrelated workloads
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: Traverse CI relationships from the database to related application services using a supported dependency query or map
Multisource records queries enable source-specific inventory reporting. It does not implement the specific required change for this case; the suitable control is: Traverse CI relationships from the database to related application services using a supported dependency query or map
Missing recent source activity can signal integration failure even when other feeds maintain the CI. It does not implement the specific required change for this case; the suitable control is: Traverse CI relationships from the database to related application services using a supported dependency query or map
During a CMDB review, engineers discover: A CMDB policy draft was created but the scheduled processor never executes it. Which proposed action is appropriate if success is measured by: The published eligible policy appears in the execution history at the next schedule?
Published policies, not simply saved drafts, are processed by the applicable scheduled framework The proposed control addresses the stated problem, and its acceptance check is: The published eligible policy appears in the execution history at the next schedule
Reliable CI ownership fields enable routing and operational accountability. It does not implement the specific required change for this case; the suitable control is: Validate eligibility and publish the Data Manager policy instead of assuming drafts run
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not implement the specific required change for this case; the suitable control is: Validate eligibility and publish the Data Manager policy instead of assuming drafts run
Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record. It does not implement the specific required change for this case; the suitable control is: Validate eligibility and publish the Data Manager policy instead of assuming drafts run
After implementing the approved change — Define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy — the data steward needs proof that it fixed: Cloud instances are regularly terminated but their old CMDB records are still active after three months. What should the steward observe?
Automated lifecycle governance reconciles discovered existence with administrative approval This observation validates the required outcome, not just the presence of a configured feature.
Compliance results depend on audit conditions and executed evidence rather than field population alone. It does not establish that confirmed terminated instances no longer appear as active configuration items.
Data-source coverage failures can cause stale CI results that should not be hidden by score adjustments. It does not establish that confirmed terminated instances no longer appear as active configuration items.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not establish that confirmed terminated instances no longer appear as active configuration items.
A CMDB engineer applied the control: Use a supported connector or governed API-based ingestion to populate that CI type. This was meant to resolve: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. Which result most directly confirms the implementation works?
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs This observation validates the required outcome, not just the presence of a configured feature.
Supported connectors reduce custom upgrade debt and integrate source identification. It does not establish that the non-scannable application CI is updated from the authoritative API inventory.
Additional ingestion sources should not overwrite unrelated authoritative CI attributes. It does not establish that the non-scannable application CI is updated from the authoritative API inventory.
Relationship types distinguish hosting, containment, and dependencies for impact and service maps. It does not establish that the non-scannable application CI is updated from the authoritative API inventory.
Please check your mailbox for a message from support@examlabs.com and follow the directions.