CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
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.
During a CMDB review, engineers discover: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. Which proposed action is appropriate if success is measured by: The large set is processed within supported limits with auditable relationship handling?
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets The proposed control addresses the stated problem, and its acceptance check is: The large set is processed within supported limits with auditable relationship handling
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: Check the Duplicate CI Remediator scale limit and use a supported safe alternate remediation strategy
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: Check the Duplicate CI Remediator scale limit and use a supported safe alternate remediation strategy
Recommended completeness assesses configured helpful fields separately from mandatory creation rules. It does not implement the specific required change for this case; the suitable control is: Check the Duplicate CI Remediator scale limit and use a supported safe alternate remediation strategy
Two ServiceNow configuration issues require separate remedies. First: A portfolio manager wants an overall view spanning strategy, delivery and consumer-facing services. Second: A company starts CSDM by creating detailed service maps before standardizing departments and locations. Select exactly TWO appropriate steps.
This resolves requirement A. Portfolio governance spans CSDM domains rather than duplicating their objects Confirm it by testing: Portfolio review traces a service from planning through delivery to consumption
This resolves requirement B. A foundation-first adoption path prevents inconsistent references spreading across later domains Confirm it by testing: Two service teams resolve to the same authoritative company, location and support groups
CSDM distinguishes the planned business capability/application from running service instances.
Service offerings describe consumable business commitments, not server hardware attributes.
Shared CSDM objects reduce semantic drift across workflows and reporting.
During a CMDB review, engineers discover: A hardware laptop has both an asset record and CI record, but the two reference fields are not paired. Which proposed action is appropriate if success is measured by: A serial-number or location update reaches the associated record where the mapping permits?
Asset synchronization requires logical linkage between a physical asset and its technical CI The proposed control addresses the stated problem, and its acceptance check is: A serial-number or location update reaches the associated record where the mapping permits
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. It does not implement the specific required change for this case; the suitable control is: Establish the correct asset-to-CI association and model category mapping
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. It does not implement the specific required change for this case; the suitable control is: Establish the correct asset-to-CI association and model category mapping
Dependent identification may rely on relationships to identify CIs within a parent context. It does not implement the specific required change for this case; the suitable control is: Establish the correct asset-to-CI association and model category mapping
A data governance release must meet both conditions: A: A dashboard shows empty compliance results after no audit has run. B: A service portfolio manager cannot compare service reliability because applications are inconsistently represented in CMDB. Select the TWO necessary actions.
This resolves requirement A. 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
This resolves requirement B. Standardized service representation supports comparable portfolio and operations reporting Confirm it by testing: Two departments' equivalent services appear under consistent classes and governance definitions
A relationship-aware query traverses edges rather than filtering only a flat CI list.
Saved queries preserve graph semantics and can support repeatable consumption.
A gap query reports mismatched source coverage rather than merely comparing displayed names.
An organization finds this data-foundation problem: A team claims CMDB health is improving based only on an overall score despite rising duplicate servers. Which approach best achieves the required outcome: The review identifies the duplicate metric trend and lists its affected class?
A single aggregate hides which technical quality condition is worsening The proposed control addresses the stated problem, and its acceptance check is: The review identifies the duplicate metric trend and lists its affected class
Saved queries preserve graph semantics and can support repeatable consumption. It does not implement the specific required change for this case; the suitable control is: Drill into the correctness metric and class-specific duplicate scorecards
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: Drill into the correctness metric and class-specific duplicate scorecards
Service mapping needs a starting entry point or suitable relationships to identify service infrastructure. It does not implement the specific required change for this case; the suitable control is: Drill into the correctness metric and class-specific duplicate scorecards
A ServiceNow implementation team encounters this issue: The organizational chart lists departments, companies and locations that several service teams share. Which control most directly resolves the issue and produces this outcome: Application and service records reference the same governed department and location records?
Foundation provides common organizational and reference data reused by other CSDM domains The proposed control addresses the stated problem, and its acceptance check is: Application and service records reference the same governed department and location records
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 shared reference entities in the CSDM Foundation domain
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 shared reference entities in the CSDM Foundation domain
CSDM distinguishes the planned business capability/application from running service instances. It does not implement the specific required change for this case; the suitable control is: Model shared reference entities in the CSDM Foundation domain
During a CMDB review, engineers discover: A virtualization team created Linux servers under the generic Computer class and cannot report Linux-only attributes. Which proposed action is appropriate if success is measured by: Linux-specific reports include migrated server CIs without mixing desktop computers?
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type The proposed control addresses the stated problem, and its acceptance check is: Linux-specific reports include migrated server CIs without mixing desktop computers
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: Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes
More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not implement the specific required change for this case; the suitable control is: Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes
Reconciliation determines which incoming source may update each attribute on an existing CI. It does not implement the specific required change for this case; the suitable control is: Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes
The change record states that the team will: Establish foundational reference and ownership data before expanding to advanced service maps. The original defect was: A company starts CSDM by creating detailed service maps before standardizing departments and locations. Which validation finding should be accepted?
A foundation-first adoption path prevents inconsistent references spreading across later domains This observation validates the required outcome, not just the presence of a configured feature.
Foundation provides common organizational and reference data reused by other CSDM domains. It does not establish that two service teams resolve to the same authoritative company, location and support groups.
Build and Integration represents build-phase components before delivery operations. It does not establish that two service teams resolve to the same authoritative company, location and support groups.
Strategy records concern proposed opportunities before detailed architecture or delivery. It does not establish that two service teams resolve to the same authoritative company, location and support groups.
The change record states that the team will: Add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition. The original defect was: A child CI class requires a new application build field but sibling classes must remain unaffected. Which validation finding should be accepted?
Child-level attributes scope specialized fields to the correct extension class This observation validates the required outcome, not just the presence of a configured feature.
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates. It does not establish that the new field appears for the intended child class while sibling forms remain unaffected.
More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not establish that the new field appears for the intended child class while sibling forms remain unaffected.
Reconciliation rule changes can require reevaluation of existing attribute choices. It does not establish that the new field appears for the intended child class while sibling forms remain unaffected.
Two ServiceNow configuration issues require separate remedies. First: Developers need traceability for application components under active development and release. Second: A service offering catalog describes customer support hours but engineers put it on a server CI. Select exactly TWO appropriate steps.
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
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
Shared CSDM objects reduce semantic drift across workflows and reporting.
A foundation-first adoption path prevents inconsistent references spreading across later domains.
Accurate CSDM mapping needs collaboration between service providers and consumers.
Please check your mailbox for a message from support@examlabs.com and follow the directions.