CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB administrator must resolve both independent failures: (1) An update payload identifies an existing CI but an administrator expects reconciliation rules to apply to first-time inserts identically. (2) Cloud inventory and Discovery report different operating system versions for the same CI. Which coordinated plan satisfies both requirements?
First: IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI Second: CMDB 360 retains visibility into competing reported attributes rather than showing only the final field Both verification criteria must be met: The first valid insert succeeds and later conflicting source updates obey reconciliation precedence The reviewer sees both source values and identifies the currently selected value
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI. The other proposed action (add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition) addresses a different operation. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field.
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. The other proposed action (Use preview or recompute where supported and verify the result against source history) does not implement the first control. IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI.
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. The proposed steps (Use preview or recompute where supported and verify the result against source history; add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition) address other capabilities instead of this required pair.
A CMDB program needs two changes. Requirement A: A saved query must be reused for monthly reporting with consistent class and relationship criteria. Requirement B: A CIO wants to know whether CMDB data improvements are delivering value to incident response. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Saved queries preserve graph semantics and can support repeatable consumption Confirm it by testing: The next scheduled execution returns a comparable scoped result set
This resolves requirement B. Dashboard measures should connect data quality to measurable operational outcomes Confirm it by testing: The sampled incidents route more accurately after governed CI ownership remediation
Playbooks translate measured data-quality issues into actionable remediation context.
Security and vulnerability workflows gain useful prioritization from trusted service dependencies.
A single aggregate hides which technical quality condition is worsening.
An organization finds this data-foundation problem: A health dashboard shows bad scores for lab CI classes that should not be evaluated. Which approach best achieves the required outcome: The target KPI excludes the approved lab class while retaining production CIs?
Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations The proposed control addresses the stated problem, and its acceptance check is: The target KPI excludes the approved lab class while retaining production CIs
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: Use scoped CMDB Health inclusion rules for the intended principal CI population
Retire policies transition eligible active CIs before downstream archive or deletion. It does not implement the specific required change for this case; the suitable control is: Use scoped CMDB Health inclusion rules for the intended principal CI population
Reusable templates provide consistent merge decisions across many de-duplication tasks. It does not implement the specific required change for this case; the suitable control is: Use scoped CMDB Health inclusion rules for the intended principal CI population
A CMDB engineer applied the control: Populate and maintain accurate support group and service ownership fields on the relevant CIs. This was meant to resolve: An incident management team wants CIs to determine the right assignment group without manually guessing owners. Which result most directly confirms the implementation works?
ITSM workflows can use trustworthy configuration context for incident routing This observation validates the required outcome, not just the presence of a configured feature.
Filters narrow graph results using attributes of different CI nodes. It does not establish that a seeded incident routes to the accountable support team using CI context.
Foundation indicators make recurring quality gaps visible and link them to improvement actions. It does not establish that a seeded incident routes to the accountable support team using CI context.
Multihop relationship modeling is needed to evaluate complete service dependencies. It does not establish that a seeded incident routes to the accountable support team using CI context.
After implementing the approved change — Ingest or construct relationship payloads with resolvable parent and child CIs — the data steward needs proof that it fixed: Network switches are imported but their upstream connection relationships are missing. What should the steward observe?
Reliable network maps depend on relationship creation and correctly identified endpoints This observation validates the required outcome, not just the presence of a configured feature.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not establish that the imported switch has the expected parent-child relationship rather than an orphan link.
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. It does not establish that the imported switch has the expected parent-child relationship rather than an orphan link.
Supported extension points lower technical debt from direct internal table manipulation. It does not establish that the imported switch has the expected parent-child relationship rather than an orphan link.
Two ServiceNow configuration issues require separate remedies. First: Servers remain active in CMDB although their last discovery time is older than the agreed threshold. Second: A duplicate server task contains competing IP values and two incident histories. Select exactly TWO appropriate steps.
This resolves requirement B. Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record Confirm it by testing: The incidents reference the surviving CI and the chosen authoritative IP is retained
This resolves requirement A. Staleness evaluates the recency of reported CI updates or discovery according to its rules Confirm it by testing: Expired server records are flagged and newly refreshed servers clear the staleness rule
Direct record deletion can leave broken or incomplete related records.
Reliable CI ownership fields enable routing and operational accountability.
Stewardship prevents uncoordinated changes to shared business context.
A ServiceNow implementation team encounters this issue: An executive requests one CMDB health score but support teams need practical remediation actions. Which control most directly resolves the issue and produces this outcome: Each critical failed metric has a named owner, affected CI sample and due date?
An aggregate score becomes useful when failures are traceable to actionable work items The proposed control addresses the stated problem, and its acceptance check is: Each critical failed metric has a named owner, affected CI sample and due date
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not implement the specific required change for this case; the suitable control is: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks
Reusable templates provide consistent merge decisions across many de-duplication tasks. It does not implement the specific required change for this case; the suitable control is: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks
Archive policies operate on retired CIs under controlled lifecycle prerequisites. It does not implement the specific required change for this case; the suitable control is: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks
The change record states that the team will: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters. The original defect was: A reporting team needs all servers last reported by a particular source with a particular OS family. Which validation finding should be accepted?
Multisource records queries enable source-specific inventory reporting This observation validates the required outcome, not just the presence of a configured feature.
Playbooks translate measured data-quality issues into actionable remediation context. It does not establish that the report lists matching discovered servers while excluding other sources.
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously. It does not establish that the report lists matching discovered servers while excluding other sources.
Standardized service representation supports comparable portfolio and operations reporting. It does not establish that the report lists matching discovered servers while excluding other sources.
An organization finds this data-foundation problem: A team wishes to delete non-CMDB records orphaned after retired CI cleanup. Which approach best achieves the required outcome: Only the approved dangling related entries are deleted while active references remain?
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself The proposed control addresses the stated problem, and its acceptance check is: Only the approved dangling related entries are deleted while active references remain
Traceable data changes preserve accountability for non-discoverable or manually governed CIs. It does not implement the specific required change for this case; the suitable control is: Apply the appropriate Delete CMDB Related Entry policy after checking related table references
Governance decisions should translate into technical rules preventing unapproved overwrites. It does not implement the specific required change for this case; the suitable control is: Apply the appropriate Delete CMDB Related Entry policy after checking related table references
Principal class focus enables targeted data foundation completeness work. It does not implement the specific required change for this case; the suitable control is: Apply the appropriate Delete CMDB Related Entry policy after checking related table references
The change record states that the team will: Refine the applicable CI identification rule with reliable class-appropriate identifiers and test it in the IRE simulator. The original defect was: Two sources insert separate server CIs because hostname alone is not a stable unique key. Which validation finding should be accepted?
IRE identification matches incoming payloads to existing CIs before creating new records This observation validates the required outcome, not just the presence of a configured feature.
Suggested relationships guide consistent relationship selection without making every pairing physically true. It does not establish that two payloads for the same server resolve to one existing CI during the test.
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. It does not establish that two payloads for the same server resolve to one existing CI during the test.
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not establish that two payloads for the same server resolve to one existing CI during the test.
The change record states that the team will: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path. The original defect was: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Which validation finding should be accepted?
Supported connectors reduce custom upgrade debt and integrate source identification This observation validates the required outcome, not just the presence of a configured feature.
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not establish that the vendor inventory loads with mapped CI classes and no duplicate source identities.
Dependent identification may rely on relationships to identify CIs within a parent context. It does not establish that the vendor inventory loads with mapped CI classes and no duplicate source identities.
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. It does not establish that the vendor inventory loads with mapped CI classes and no duplicate source identities.
Please check your mailbox for a message from support@examlabs.com and follow the directions.