CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB change request reports: A CMDB manager wants to distinguish correctness, completeness and compliance in a monthly report. Select the best implementation. It must pass this acceptance test: The report identifies the specific failed metric rather than presenting only a total percentage.
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately The proposed control addresses the stated problem, and its acceptance check is: The report identifies the specific failed metric rather than presenting only a total percentage
Stewardship prevents uncoordinated changes to shared business context. It does not implement the specific required change for this case; the suitable control is: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance
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: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. It does not implement the specific required change for this case; the suitable control is: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance
A ServiceNow Data Foundations rollout has two blockers. First: A data owner needs quarterly human confirmation that a set of CIs is still correct. Second: No team is accountable for correcting CI ownership gaps across cloud and on-premises inventories. Which complete two-part implementation addresses both?
First: Attestation asks an accountable person to verify CI data at a defined interval Second: Governance requires clear decision rights and accountable remediation owners Both verification criteria must be met: Reviewers receive and complete the required attestation tasks for sampled CIs Every affected CI class has an owner and a tracked correction backlog
Attestation asks an accountable person to verify CI data at a defined interval. The other proposed action (review the de-duplication task and choose the valid main CI with its associated evidence) addresses a different operation. Governance requires clear decision rights and accountable remediation owners.
Attestation asks an accountable person to verify CI data at a defined interval. Governance requires clear decision rights and accountable remediation owners. The proposed steps (Review class scope, asset linkage and deployment lifecycle before mass remediation; review the de-duplication task and choose the valid main CI with its associated evidence) address other capabilities instead of this required pair.
Governance requires clear decision rights and accountable remediation owners. The other proposed action (Review class scope, asset linkage and deployment lifecycle before mass remediation) does not implement the first control. Attestation asks an accountable person to verify CI data at a defined interval.
A CMDB administrator must resolve both independent failures: (1) A compliance tile shows no results despite multiple mandatory fields being filled. (2) A large batch of duplicate devices needs repeatable treatment across the same CI class. Which coordinated plan satisfies both requirements?
First: Compliance results depend on audit conditions and executed evidence rather than field population alone Second: Reusable templates provide consistent merge decisions across many de-duplication tasks Both verification criteria must be met: The compliance score reflects the seeded pass and fail conditions after the audit runs Sampled tasks keep their approved main CI and relationship settings after the batch
Compliance results depend on audit conditions and executed evidence rather than field population alone. The other proposed action (assign class and data-steward ownership with escalation and recurring quality reviews) addresses a different operation. Reusable templates provide consistent merge decisions across many de-duplication tasks.
Compliance results depend on audit conditions and executed evidence rather than field population alone. Reusable templates provide consistent merge decisions across many de-duplication tasks. The proposed steps (Remediate existing duplicate records separately and test the revised IRE rule for future ingests; assign class and data-steward ownership with escalation and recurring quality reviews) address other capabilities instead of this required pair.
Reusable templates provide consistent merge decisions across many de-duplication tasks. The other proposed action (Remediate existing duplicate records separately and test the revised IRE rule for future ingests) does not implement the first control. Compliance results depend on audit conditions and executed evidence rather than field population alone.
A CMDB change request reports: A CMDB steward wants to certify a critical CI's business owner field rather than merely mark it updated recently. Select the best implementation. It must pass this acceptance test: 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 proposed control addresses the stated problem, and its acceptance check is: The responsible person signs off on the current owner value with dated evidence
Staleness evaluates the recency of reported CI updates or discovery according to its rules. It does not implement the specific required change for this case; the suitable control is: Use an appropriate certification or attestation control requiring explicit confirmation of that value
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: Use an appropriate certification or attestation control requiring explicit confirmation of that value
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: Use an appropriate certification or attestation control requiring explicit confirmation of that value
The change record states that the team will: Establish stable service records and correct CSDM links instead of copying separate spreadsheet services. The original defect was: An implementation team wants the same service identifiers used in ITSM incidents and portfolio dashboards. Which validation finding should be accepted?
Shared CSDM objects reduce semantic drift across workflows and reporting This observation validates the required outcome, not just the presence of a configured feature.
Service Consumption expresses what consumers request, rather than how technical systems are hosted. It does not establish that an incident and a portfolio view reference the same authoritative service identifier.
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. It does not establish that an incident and a portfolio view reference the same authoritative service identifier.
Design and Planning represents intended enterprise architecture, separate from runtime CIs. It does not establish that an incident and a portfolio view reference the same authoritative service identifier.
The change record states that the team will: Verify stable identification evidence before merging a suspected duplicate pair. The original defect was: Two visually similar server names do not mean two CIs are identical physical hosts. Which validation finding should be accepted?
Similar display names alone do not establish identical physical or logical identity 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 distinct hosts remain separate and a truly matching test pair is consolidated.
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. It does not establish that distinct hosts remain separate and a truly matching test pair is consolidated.
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. It does not establish that distinct hosts remain separate and a truly matching test pair is consolidated.
A configuration management team must address: Business analysts confuse a Business Application with a deployed Application Service instance. What change should it implement to demonstrate this result: One business application is linked to relevant production service instances without duplicate application records?
CSDM distinguishes the planned business capability/application from running service instances The proposed control addresses the stated problem, and its acceptance check is: One business application is linked to relevant production service instances without duplicate application records
Build and Integration represents build-phase components before delivery operations. It does not implement the specific required change for this case; the suitable control is: Separate the design-level business application from its operational application service
Portfolio governance spans CSDM domains rather than duplicating their objects. It does not implement the specific required change for this case; the suitable control is: Separate the design-level business application from its operational application service
Foundation provides common organizational and reference data reused by other CSDM domains. It does not implement the specific required change for this case; the suitable control is: Separate the design-level business application from its operational application service
A ServiceNow Data Foundations rollout has two blockers. First: An import succeeds but all devices appear as generic cmdb_ci records rather than servers. Second: A team assumes changing CI Install Status automatically updates Hardware Status for the same computer. Which complete two-part implementation addresses both?
First: A correct source mapping is needed before identifier rules can classify incoming device records Second: Install Status and Hardware Status are independent fields rather than automatic mirrors of each other Both verification criteria must be met: Subsequent imports identify the expected server subclasses instead of generic CI entries A status change affects only the mapped field and not an unrelated status field
A correct source mapping is needed before identifier rules can classify incoming device records. The other proposed action (use a controlled manual CI maintenance process with steward ownership, required fields, and review dates) addresses a different operation. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other.
Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. The other proposed action (Use a supported connector or governed API-based ingestion to populate that CI type) does not implement the first control. A correct source mapping is needed before identifier rules can classify incoming device records.
A correct source mapping is needed before identifier rules can classify incoming device records. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. The proposed steps (Use a supported connector or governed API-based ingestion to populate that CI type; use a controlled manual CI maintenance process with steward ownership, required fields, and review dates) address other capabilities instead of this required pair.
An audit evaluates the completed action: Review the Duplicate correctness metric and the applicable CI identification rules. It addressed the problem: The correctness score reports numerous duplicate Linux servers created by two tools. What evidence best demonstrates success?
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions 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 consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures.
Improved identification prevents future collisions but does not retroactively merge every old duplicate. It does not establish that consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures.
Similar display names alone do not establish identical physical or logical identity. It does not establish that consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures.
Two change requests must be delivered together. Requirement A: Servers remain active in CMDB although their last discovery time is older than the agreed threshold. Requirement B: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. Select the plan that resolves both.
First: Staleness evaluates the recency of reported CI updates or discovery according to its rules Second: Improved identification prevents future collisions but does not retroactively merge every old duplicate Both verification criteria must be met: Expired server records are flagged and newly refreshed servers clear the staleness rule Existing task is closed appropriately and repeat ingestion does not produce a new duplicate
Staleness evaluates the recency of reported CI updates or discovery according to its rules. Improved identification prevents future collisions but does not retroactively merge every old duplicate. The proposed steps (Define a service owner approval and change-control process for governed naming updates; review class scope, asset linkage and deployment lifecycle before mass remediation) address other capabilities instead of this required pair.
Staleness evaluates the recency of reported CI updates or discovery according to its rules. The other proposed action (review class scope, asset linkage and deployment lifecycle before mass remediation) addresses a different operation. Improved identification prevents future collisions but does not retroactively merge every old duplicate.
Improved identification prevents future collisions but does not retroactively merge every old duplicate. The other proposed action (Define a service owner approval and change-control process for governed naming updates) does not implement the first control. Staleness evaluates the recency of reported CI updates or discovery according to its rules.
A ServiceNow implementation team encounters this issue: The correctness score reports numerous duplicate Linux servers created by two tools. Which control most directly resolves the issue and produces this outcome: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures?
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions The proposed control addresses the stated problem, and its acceptance check is: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures
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: Review the Duplicate correctness metric and the applicable CI identification rules
A scoped initial data foundation is easier to govern than an unactionable inventory. It does not implement the specific required change for this case; the suitable control is: Review the Duplicate correctness metric and the applicable CI identification rules
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not implement the specific required change for this case; the suitable control is: Review the Duplicate correctness metric and the applicable CI identification rules
Please check your mailbox for a message from support@examlabs.com and follow the directions.