Free Practice Questions for ServiceNow CIS-DF Exam

In ServiceNow CMDB governance, theCI Class Managerallows administrators to assignownership and accountabilityat the class level. This ownership is used by governance tools—especiallyCMDB Data Manager—to automatically determinewho receives tasks and actionsrelated to data lifecycle management.

The group reference field that aligns with class ownership and is consumed byCMDB Data Manager policiesis theManaged By Group. This field represents the team responsible for thetechnical stewardship and lifecycle managementof CIs within that class.

When CMDB Data Manager executes policies such as retention, archival, or cleanup, it uses theManaged By Groupto assign tasks to the appropriate data owners. This ensures governance actions are routed to the correct accountable team without manual intervention.

Approval Group, Support Group, and Change Group serve different purposes. Approval Group is used for workflow approvals, Support Group is used for operational ticket routing, and Change Group supports Change Management governance. None of these reflectdata ownership at the class level.

Therefore, to leverage CI class ownership defined in the CI Class Manager within CMDB Data Manager policies, the correct field isManaged By Group, makingOption Bthe verified answer.

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.