ServiceNow Updated CIS-DF Exam Questions and Answers by zuri

Creating new CI classes is ahigh-impact configuration activityand must follow strictData Foundations and CSDM-aligned best practicesto avoid long-term technical debt and upgrade risk.

Option Bis a recommended first step. Before creating any new CI class, administrators shouldinstall or update the CMDB CI Class Models Store applicationand verify whether an appropriate class already exists. ServiceNow frequently delivers new CI classes through updates and class model packages, and duplicating an existing or planned class can lead to fragmentation and governance issues.

Option Cis also correct. When a new class is truly required, it should beadded under an appropriate parent classto inherit attributes, behaviors, and discovery patterns. For an IoT Sensor, this might be under a hardware or device-related parent class, ensuring consistency and minimizing customization.

Option A is incorrect and dangerous—deleting unused classes can break dependencies and historical data. Option D is also discouraged; modifying existing classes to repurpose them violates upgrade-safe design principles and can negatively impact discovery, integrations, and reporting.

By verifying existing models first and extending the class hierarchy correctly, organizations maintain aclean, scalable, and upgrade-safe CMDB.

Therefore, the correct answers areB and C.

In CMDB governance, differentCMDB Data Manager policy typesserve different validation and enforcement purposes. When the objective is to allow an assigned individual toreview and update specific fields on a CI record, the correct policy type isCertification.

ACertification policycreates actionable tasks that require the assignee tovalidate and, if necessary, correct specific CI attributes, such as lifecycle status, support group, environment, or ownership. During certification, the user can directly update CI fields to bring the record into compliance with defined standards.

Attestation(Option C) only asks the user to confirm that a CIstill existsor is still valid; it does not require or enable attribute-level updates.Audit(Option A) is used for reporting and evidence collection, not remediation.Compliance(Option D) measures adherence to rules but does not itself generate editable remediation tasks.

Certification is therefore the primary mechanism used whenhuman validation and correctionof CI data is required—making it a cornerstone of CMDB data quality management.

Hence, the correct answer isB – Certification.

Removing obsolete or inactive CIs from the CMDB must be handled carefully to avoid data loss, audit issues, and unintended operational impact. InServiceNow, the recommended and governed approach is to use anarchive policy.

Archive policiesare designed to manageCI lifecycle cleanupbased on defined conditions such as class, last updated date, lifecycle status, or operational state. In this scenario, the condition would targetLinux Server CIsthat have not been updated in six months. Archive policies can either archive or permanently delete records in a controlled, auditable manner, ensuring compliance with data retention and governance standards.

Creating abusiness rule(Option A) is strongly discouraged for bulk CMDB cleanup because it introduces technical debt, upgrade risk, and unpredictable side effects. Ascheduled job(Option C) may automate execution but lacks governance logic and lifecycle awareness on its own.

Archive policies integrate withCMDB Data Manager, provide visibility into actions taken, and support approval and rollback where appropriate. This aligns fully with Data Foundations best practices for maintaining alean, accurate, and trusted CMDB.

Therefore, the correct and recommended action isB – Create an archive policy.

TheCMDBis a foundational capability that enables organizations to operate IT services withconfidence, resilience, and efficiency. Its value lies not in automation for its own sake or financial data management, but in how it supportsservice-aware operations and decision-making.

Strengthening operational resiliency(Option A) is a core value of the CMDB. By maintaining accurate configuration data and relationships, organizations can better understand dependencies, assess risk, and recover more quickly from incidents or outages. A trusted CMDB enables proactive problem management and informed change planning, directly contributing to resiliency.

Streamlining Incident and Change Management(Option B) is another primary value. Accurate CI data allows incidents to be routed automatically to the correct support groups, enables faster root-cause analysis, and supports risk-based change assessments. This reduces manual effort, improves response times, and lowers operational risk.

Option C is incorrect becauseautomating CI relationship maintenanceis a capability enabled by tools like Discovery and Service Mapping—not a value in itself. Option D is also incorrect becausefinancial data managementis the domain of IT Asset Management (ITAM) and Financial Management, not the CMDB’s core value proposition.

In summary, the CMDB delivers value byimproving operational resilienceandoptimizing ITSM processes, makingOptions A and Bthe correct answers.