ServiceNow CIS-DF Exam Questions
Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (Page 5 )

Updated On: 20-Mar-2026

An organization is changing data centers and needs to know the consequences of the planned changes.

How can Application Service Mapping be used as part of Change Management?

  1. To identify which devices will go offline first
  2. To understand the business impact of CIs
  3. To understand the physical location of CIs

Answer(s): B

Explanation:

Application Service Mapping is a critical capability in ServiceNow for enabling business-aware Change Management. Its primary value is not in identifying physical shutdown sequences or CI locations, but in translating technical changes into business impact.

When an organization plans a data center move, multiple infrastructure components--servers, databases, network devices--may be affected. On their own, these technical CIs provide little insight into business risk. Application Service Mapping connects these CIs to Application Services and Business Services as defined by the Common Service Data Model (CSDM). This relationship allows Change Managers to see which business services, customers, and processes are impacted by the planned change.

By leveraging service maps, Change Management can answer critical questions such as:

Which customer-facing services may experience downtime?

What revenue-generating or mission-critical services are at risk?

Which stakeholders must be notified or involved in approvals?

Option A is incorrect because service mapping does not determine shutdown order; that is handled by infrastructure planning. Option C focuses on physical location data, which is typically managed through Location CIs and Discovery, not service mapping.

Therefore, the correct answer is B ­ To understand the business impact of CIs, which aligns directly with ITIL 4, CSDM, and Change Management best practices.



What ensures data volume in the CMDB is manageable?

  1. Business Rules
  2. Scheduled Jobs
  3. Archive Policies

Answer(s): C

Explanation:

Managing CMDB data volume is a key Data Foundations governance objective. Over time, CMDBs naturally accumulate retired, obsolete, or decommissioned CIs. If these records are not properly managed, they degrade CMDB performance, reduce reporting accuracy, and negatively impact discovery reconciliation and health scores.

Archive Policies are the mechanism designed to address this challenge. They define when CI records should be archived or deleted based on lifecycle state, age, or retention requirements. By automating archival and cleanup, archive policies ensure that only relevant, active CIs remain in the operational CMDB, keeping data volume manageable and performant.

Business Rules (Option A) are used to enforce logic during record creation or updates, not for long- term data volume control. Scheduled Jobs (Option B) may execute tasks, but without archive policies they have no governance logic to determine what should be removed or retained.

Archive policies work in conjunction with CMDB Data Manager to enforce lifecycle-based retention and cleanup, making them the correct and verified answer.

Therefore, Option C ­ Archive Policies is correct.



(Choose 2 options)

The Configuration Manager is preparing justification to utilize the CMDB Data Foundations Dashboard.

Which benefits align with the usage of this dashboard?

  1. It automates approval processes for Change Management
  2. It provides actionable insights to improve data quality and completeness
  3. It helps detect and eliminate duplicate records in the CMDB
  4. It enables monitoring and tracking of CMDB health over time

Answer(s): B,D

Explanation:

The CMDB Data Foundations Dashboard is designed to provide visibility, insight, and guidance into the overall health of CMDB data. Its purpose is not to automate ITSM workflows, but to enable informed decision-making and continuous improvement of configuration data.

One of its primary benefits is providing actionable insights to improve data quality and completeness (Option B). The dashboard highlights gaps in CI attributes, missing relationships, and compliance issues, enabling CMDB administrators and data owners to take targeted corrective actions using Get Well Playbooks.

Another core benefit is enabling organizations to monitor and track CMDB health over time (Option D). The dashboard presents trends across health dimensions--completeness, correctness, and compliance--allowing teams to measure progress, justify investments, and demonstrate maturity improvements aligned to CSDM adoption stages.

Option A is incorrect because Change Management approvals are handled by workflow and policy engines, not the Data Foundations Dashboard. Option C is also incorrect because duplicate detection and remediation are handled through de-duplication tools and the Duplicate CI Remediator, not directly by the dashboard itself.

Therefore, the correct answers are B and D, which accurately reflect the strategic and operational value of the CMDB Data Foundations Dashboard.



A Configuration Manager needs to leverage a policy type to automate the creation and assignment of tasks to validate the existence of CIs.

Which policy type should be used to accomplish this goal?

  1. Certification
  2. Delete
  3. Retire
  4. Attestation

Answer(s): D

Explanation:

In ServiceNow, validating whether Configuration Items (CIs) still exist is a core CMDB governance activity. Over time, environments change rapidly--servers are decommissioned, cloud resources are torn down, and applications are replaced. If existence validation is not enforced, the CMDB quickly fills with obsolete or "ghost" CIs.

Attestation policies are specifically designed to address this need. An attestation policy automatically generates and assigns tasks to responsible users or groups, asking them to confirm that a CI still exists and is still relevant. This process focuses on acknowledgment rather than deep data validation, making it lightweight and scalable across large CMDBs.

Certification policies (Option A) are used when specific attributes must be validated, such as lifecycle status, support group, or environment.
While important for data correctness, certification is not intended solely to confirm CI existence. Delete (Option B) and Retire (Option C) policies are lifecycle actions that remove or transition records, but they do not validate existence before taking action.

Attestation integrates cleanly with CMDB Workspace, assigns tasks automatically, and supports auditability--ensuring accountability for CI ownership. This makes it the correct and Data Foundations­aligned policy type for validating CI existence.

Therefore, Option D ­ Attestation is the correct answer.



(Choose 2 options)

Configuration Management needs to ensure data quality for all CIs in the CMDB.

What areas of data quality for CIs are included in the CMDB Health Dashboard?

  1. Downgraded CIs
  2. Upgraded CIs
  3. Missing CIs
  4. Stale CIs
  5. Duplicate CIs

Answer(s): D,E

Explanation:

The CMDB Health Dashboard is a central component of CMDB Data Foundations insight and governance. It measures and tracks data quality using well-defined health indicators that focus on the accuracy, relevance, and usability of CI data.

Two key data quality areas included in the dashboard are Stale CIs and Duplicate CIs.

Stale CIs (Option D) refer to configuration items that have not been updated within a defined time window. These records are risky because they may no longer reflect the current state of the environment, leading to inaccurate impact analysis, poor change decisions, and misrouted incidents. Monitoring staleness helps organizations identify where discovery, integrations, or ownership processes are failing.

Duplicate CIs (Option E) occur when the same real-world asset or service is represented by multiple records. Duplicates undermine trust in the CMDB, distort reporting, and break service mappings. The CMDB Health Dashboard highlights duplicate trends and integrates with de-duplication and remediation workflows to address them.

Options A (Downgraded CIs), B (Upgraded CIs), and C (Missing CIs) are not standard CMDB Health Dashboard quality dimensions.
While "missing" data may be inferred through completeness checks, Missing CIs as a category is not directly tracked.

Therefore, the correct answers are D ­ Stale CIs and E ­ Duplicate CIs, which are core CMDB Health indicators used to maintain high-quality configuration data.



Viewing page 5 of 21
Viewing questions 21 - 25 out of 75 questions



Post your Comments and Discuss ServiceNow CIS-DF exam dumps with other Community members:

CIS-DF Exam Discussions & Posts

AI Tutor 👋 I’m here to help!