CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB program needs two changes. Requirement A: A team wants server support group to affect completeness but does not want it required by the dictionary. Requirement B: A policy owner changes filter conditions but does not test the effect on thousands of CIs. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Recommended completeness assesses configured helpful fields separately from mandatory creation rules Confirm it by testing: Empty support groups appear under Recommended without blocking unrelated CI creation
This resolves requirement B. Evaluated policy scope helps prevent accidental mass retirement or deletion Confirm it by testing: A dry-run sample matches only the intended classes, lifecycle states and locations
A stocked asset can exist financially without a currently operating CI for production impact.
An aggregate score becomes useful when failures are traceable to actionable work items.
Governance requires clear decision rights and accountable remediation owners.
A team configured: Define baseline health metrics and scheduled KPIs with owners and achievable thresholds. Its original requirement was: An auditor asks how CMDB quality improvement will be measured rather than relying on a one-time cleanup. Which observation proves that the desired operational outcome was achieved?
Continuous KPI governance detects regressions after point-in-time remediation This observation validates the required outcome, not just the presence of a configured feature.
Direct record deletion can leave broken or incomplete related records. It does not establish that monthly measurements show trend, responsible owner and completed corrective actions.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not establish that monthly measurements show trend, responsible owner and completed corrective actions.
A stocked asset can exist financially without a currently operating CI for production impact. It does not establish that monthly measurements show trend, responsible owner and completed corrective actions.
A team configured: Configure a Data Manager Archive policy and the required retirement definition for eligible classes. Its original requirement was: A company wants retired laptop CIs automatically archived after the approved retention interval. Which observation proves that the desired operational outcome was achieved?
Archive policies operate on retired CIs under controlled lifecycle prerequisites This observation validates the required outcome, not just the presence of a configured feature.
An aggregate score becomes useful when failures are traceable to actionable work items. It does not establish that a retired test laptop is archived only after meeting the retention criteria.
Traceable data changes preserve accountability for non-discoverable or manually governed CIs. It does not establish that a retired test laptop is archived only after meeting the retention criteria.
A stocked asset can exist financially without a currently operating CI for production impact. It does not establish that a retired test laptop is archived only after meeting the retention criteria.
A CMDB administrator must resolve both independent failures: (1) An auditor asks how CMDB quality improvement will be measured rather than relying on a one-time cleanup. (2) A CMDB steward wants to certify a critical CI's business owner field rather than merely mark it updated recently. Which coordinated plan satisfies both requirements?
First: Continuous KPI governance detects regressions after point-in-time remediation Second: Fresh timestamps do not prove that a human has validated business ownership Both verification criteria must be met: Monthly measurements show trend, responsible owner and completed corrective actions The responsible person signs off on the current owner value with dated evidence
Fresh timestamps do not prove that a human has validated business ownership. The other proposed action (Verify stable identification evidence before merging a suspected duplicate pair) does not implement the first control. Continuous KPI governance detects regressions after point-in-time remediation.
Continuous KPI governance detects regressions after point-in-time remediation. The other proposed action (examine the Staleness correctness metric and the class's staleness definition) addresses a different operation. Fresh timestamps do not prove that a human has validated business ownership.
Continuous KPI governance detects regressions after point-in-time remediation. Fresh timestamps do not prove that a human has validated business ownership. The proposed steps (Verify stable identification evidence before merging a suspected duplicate pair; examine the Staleness correctness metric and the class's staleness definition) address other capabilities instead of this required pair.
A CMDB administrator must resolve both independent failures: (1) A weekly review shows one inventory feed stopped sending data without deleting the existing CIs. (2) An incident management team wants CIs to determine the right assignment group without manually guessing owners. Which coordinated plan satisfies both requirements?
First: Missing recent source activity can signal integration failure even when other feeds maintain the CI Second: ITSM workflows can use trustworthy configuration context for incident routing Both verification criteria must be met: The stopped feed appears in the issue list while current feeds remain healthy A seeded incident routes to the accountable support team using CI context
Missing recent source activity can signal integration failure even when other feeds maintain the CI. The other proposed action (validate the compliance audit configuration and execution before interpreting the empty tile as clean) addresses a different operation. ITSM workflows can use trustworthy configuration context for incident routing.
Missing recent source activity can signal integration failure even when other feeds maintain the CI. ITSM workflows can use trustworthy configuration context for incident routing. The proposed steps (Align application and service entities with the CSDM model and use suitable foundation indicators; validate the compliance audit configuration and execution before interpreting the empty tile as clean) address other capabilities instead of this required pair.
ITSM workflows can use trustworthy configuration context for incident routing. The other proposed action (Align application and service entities with the CSDM model and use suitable foundation indicators) does not implement the first control. Missing recent source activity can signal integration failure even when other feeds maintain the CI.
Two ServiceNow configuration issues require separate remedies. First: A CMDB user can view saved graph queries but is not allowed to author new queries. Second: A weekly review shows one inventory feed stopped sending data without deleting the existing CIs. Select exactly TWO appropriate steps.
This resolves requirement B. Missing recent source activity can signal integration failure even when other feeds maintain the CI Confirm it by testing: The stopped feed appears in the issue list while current feeds remain healthy
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
Security and vulnerability workflows gain useful prioritization from trusted service dependencies.
Dependency visualization traverses relationship edges so potential impact is easier to understand.
A single aggregate hides which technical quality condition is worsening.
An implementation review finds these independent issues: (1) A new service CI class needs suggested parent-child relationship types visible to its modelers. (2) A source stopped reporting network devices three weeks ago even though their CIs still exist. Which TWO controls should the team apply?
This resolves requirement A. Suggested relationships guide consistent relationship selection without making every pairing physically true Confirm it by testing: The relationship editor proposes the intended type for a compatible parent-child pair
This resolves requirement B. Per-source reporting timestamps help detect coverage gaps even when a CI has historical data Confirm it by testing: The stopped source is flagged for affected CIs while healthy sources remain current
Reconciliation rule changes can require reevaluation of existing attribute choices.
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates.
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field.
A ServiceNow implementation team encounters this issue: A team sees a server icon in Dependency View but expects it to expose non-CMDB records unrelated to cmdb_ci. Which control most directly resolves the issue and produces this outcome: Non-CMDB records remain outside the CI graph and modeled CIs render correctly?
Dependency views operate on supported CMDB class and relationship information The proposed control addresses the stated problem, and its acceptance check is: Non-CMDB records remain outside the CI graph and modeled CIs render correctly
Playbooks translate measured data-quality issues into actionable remediation context. It does not implement the specific required change for this case; the suitable control is: Model supported CMDB CIs and relationships rather than assuming arbitrary tables appear in CI maps
Multisource records queries enable source-specific inventory reporting. It does not implement the specific required change for this case; the suitable control is: Model supported CMDB CIs and relationships rather than assuming arbitrary tables appear in CI maps
Multihop relationship modeling is needed to evaluate complete service dependencies. It does not implement the specific required change for this case; the suitable control is: Model supported CMDB CIs and relationships rather than assuming arbitrary tables appear in CI maps
Two ServiceNow configuration issues require separate remedies. First: A service map displays duplicate relationship edges and misleading service impact chains. Second: A change advisory board needs to identify downstream services affected by a database replacement. Select exactly TWO appropriate steps.
This resolves requirement A. Map accuracy depends on relationship data rather than cosmetic icon changes Confirm it by testing: Duplicate edges disappear and valid dependencies still appear
This resolves requirement B. Linked CI dependencies reveal potential blast radius before infrastructure changes Confirm it by testing: The test database change lists its genuinely dependent services for review
A single aggregate hides which technical quality condition is worsening.
A relationship-aware query traverses edges rather than filtering only a flat CI list.
Missing recent source activity can signal integration failure even when other feeds maintain the CI.
An implementation review finds these independent issues: (1) Two visually similar server names do not mean two CIs are identical physical hosts. (2) A new CMDB program imports every discovered object before deciding which services it supports. Which TWO controls should the team apply?
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. A scoped initial data foundation is easier to govern than an unactionable inventory Confirm it by testing: The selected classes serve the defined use cases and have health acceptance criteria
Reliable CI ownership fields enable routing and operational accountability.
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates.
Published policies, not simply saved drafts, are processed by the applicable scheduled framework.
Two ServiceNow configuration issues require separate remedies. First: Developers need traceability for application components under active development and release. Second: Two stakeholder teams disagree whether a technical service should be classified under consumer or delivery concepts. Select exactly TWO appropriate steps.
This resolves requirement B. Accurate CSDM mapping needs collaboration between service providers and consumers Confirm it by testing: The revised model separates technical delivery capability from the consumer-visible business service
This resolves requirement A. Build and Integration represents build-phase components before delivery operations Confirm it by testing: 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.
CSDM distinguishes the planned business capability/application from running service instances.
Shared CSDM objects reduce semantic drift across workflows and reporting.
Please check your mailbox for a message from support@examlabs.com and follow the directions.