CIS-DF Certification Exam Guide + Practice Questions Updated 2026

Explanation:
In Data Foundations, “insight” focuses on turning trusted configuration data into clear visual understanding―so teams can assess relationships, troubleshoot impact, and validate service context. Unified Map supports this by providing a graphical view of CIs and their relationships, combining strengths of traditional dependency views and service-mapping-style visualization into a single, consistent map experience.
Unified Map is accessed from CMDB Workspace, typically via a Quick Links entry (and in some experiences, also from relevant CI/service contexts). This location makes sense in the Data Foundations model because CMDB Workspace is the central place where configuration and service data is explored, validated, and used for operational decision-making―exactly what mapping relationships is meant to enable.
The other options do not fit the purpose or access pattern. CI Class Manager is focused on defining and maintaining CI class structures and related class settings; it is not the user entry point for relationship visualization. CMDB Data Manager is focused on governance through lifecycle policies (attestation, archival, deletion) and bulk lifecycle operations―again, not the primary interface for interactive mapping and dependency exploration.
Therefore, for a Configuration Manager seeking to use Unified Map for relationship and dependency insight, the correct access point is CMDB Workspace.

Explanation:
CSDM significantly enhances Change Management by providing service-aware context, enabling better planning, risk assessment, and stakeholder communication.
One key benefit is the ability to identify blackout windows (Option A). Through CSDM-aligned Business Services, Service Offerings, and service calendars, Change Managers can clearly see when services are unavailable for change due to business constraints, regulatory requirements, or peak usage periods. This helps prevent changes from being scheduled during high-risk windows.
Another critical benefit is the ability to understand the impact of the change on services (Option D). CSDM establishes clear relationships between infrastructure CIs, Application Services, and Business Services. When a change is proposed, these relationships enable accurate impact analysis, allowing Change Managers to assess risk based on business criticality rather than just technical scope.
Option B (root cause determination) is primarily a Problem Management function.
Option C (dynamic routing of changes) is driven by workflow and approval logic, not directly by CSDM.
Therefore, the correct answers are A C Identify blackout windows and D C Understand the impact of the change on services.

Explanation:
In Data Foundations, a low “Unique Locations” result indicates the CMDB contains duplicate Location records (or inconsistent location usage) that reduce data reliability for operational reporting and service analytics. This sits under “Insight” because the dashboard is highlighting a measurable quality issue, and the playbook provides a structured remediation path to restore confidence.
The recommended playbook-aligned process is to review the duplicate locations, determine which one is correct per the organization’s naming and data standards, then re-point dependent records (CIs) to the correct Location before removing the duplicate. That sequence is essential: if you delete a duplicate location without first updating related CIs, you risk leaving CIs with missing/invalid location references, creating new completeness and correctness issues.
Option C matches best practice: validate which location record should remain, update all affected CIs (and any other dependent records) to use the correct location, and then delete (or retire/merge, depending on process controls) the duplicate record.
Option B is risky because it skips validation and dependency updates.
Option D defeats the purpose of “Unique Locations” by allowing ongoing inconsistency.
Option A is not the best fit because “Duplicate CI Remediator” is oriented toward CI duplicates; Location is typically a reference/organization data domain and is handled through the specific remediation steps for that data set. Therefore, C is the recommended process.

Explanation:
Comprehensive and Detailed Explanation (200C300 words)
Within ServiceNow Data Foundations, CMDB Data Manager provides multiple policy types to support governance, data quality, and lifecycle management of configuration items (CIs). The scenario described―confirming that servers recorded in the CMDB physically exist in the data center―is a classic example of existence validation and ownership confirmation, which is exactly the purpose of an Attestation policy.
An Attestation policy is designed to request a human validation from a responsible individual or group (such as a data center manager, platform owner, or infrastructure team). The policy generates attestation tasks that require reviewers to explicitly confirm whether a CI is valid, accurate, and still exists. This aligns directly with CMDB governance best practices and ITIL 4 Service Configuration Management, where periodic verification ensures trust in the CMDB as a system of record.
The other policy types do not meet this requirement:
Certification is typically used to validate compliance with defined data standards (e.g., mandatory fields populated), not physical existence.
Delete, Archive, and Retire are lifecycle actions, used after a CI has already been identified as obsolete or no longer required.
None of these options involve human confirmation of real-world existence.
From a CSDM and Data Foundations perspective, attestation supports:
CMDB accuracy and credibility
Audit and regulatory compliance (especially critical in financial services)
Clear accountability for CI ownership and validation
Therefore, when the goal is to confirm that servers actually exist, the correct and fully aligned CMDB Data Manager policy type is Attestation (E).

Explanation:
When data quality issues such as missing serial numbers threaten CMDB integrity and increase the risk of duplicates, ServiceNow provides prescriptive, step-by-step remediation guidance through the CMDB Data Foundations Dashboard Playbooks.
These playbooks are specifically designed to help administrators identify root causes, assess ingestion and governance gaps, and apply corrective actions using structured remediation plays (Analyze Data, Fix Data, Govern Data). For missing serial numbers, the playbooks guide teams to review Discovery patterns, identification rules, reconciliation sources, and governance controls to ensure authoritative data capture and prevention of future issues.
The CMDB Health Dashboard Playbooks focus on health scoring and metrics, not guided remediation. CSDM Data Foundations Dashboard Playbooks is not a distinct product naming; the correct construct is CMDB Data Foundations. Now Create Playbooks provide implementation project guidance, not operational troubleshooting for live data issues.
Therefore, the correct answer is A C CMDB Data Foundations Dashboard Playbooks, which are purpose-built to quickly troubleshoot and remediate CMDB data quality problems while aligning
with best practices in ServiceNow.