CIS-DF Exam Questions & Answers

Within Data Foundations, ''Configuration'' includes designing the CMDB data model in a way that supports operational usability---especially for ITSM processes like Incident and Change. One common usability challenge is that CI reference fields (such as the Incident ''Configuration item'' field) can become cluttered and confusing if they allow selection from every CI class, including highly technical or rarely used classes. To address this, ServiceNow uses the concept of Principal Classes: a curated subset of CI classes that are considered primary for operational selection and reporting.

Principal Classes are designated in the CI Class Manager, because this is where administrators configure and manage CI class behaviors and class-level settings. Defining Principal Classes at the class-management layer ensures that the platform can consistently apply this constraint across CI reference fields and related experiences. This aligns with Data Foundations goals: improving data quality and process outcomes by making it easier for users to select the correct CI, which in turn increases accuracy for assignment, routing, impact analysis, and analytics.

The other options do not fit the responsibility. CMDB Workspace is primarily used for exploring and analyzing CMDB data, not configuring class-level constraints. CMDB Data Manager focuses on governance automation (like lifecycle policies and bulk remediation operations), not CI class designation rules. System Properties may influence global behaviors, but Principal Class designation is a modeling configuration handled through CI class configuration, which is why CI Class Manager is the correct location.

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

Archive policies are designed to manage CI lifecycle cleanup based on defined conditions such as class, last updated date, lifecycle status, or operational state. In this scenario, the condition would target Linux Server CIs that 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 a business rule (Option A) is strongly discouraged for bulk CMDB cleanup because it introduces technical debt, upgrade risk, and unpredictable side effects. A scheduled job (Option C) may automate execution but lacks governance logic and lifecycle awareness on its own.

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

Therefore, the correct and recommended action is B -- Create an archive policy.

Retire and Archive are supported CMDB Data Manager policy types. A Retire policy manages the lifecycle transition of CIs that should no longer be considered active or operational. An Archive policy removes eligible records from active CMDB use while retaining them according to configured retention and restoration requirements.

CMDB Data Manager also supports other policy types, including Attestation, Certification, and Delete. Together, these policies automate CI lifecycle management, validation, retention, and governed cleanup.

De-duplication is handled through duplicate-identification and remediation capabilities, such as de-duplication templates, tasks, and the Duplicate CI Remediator. It is not a CMDB Data Manager policy type. Reconciliation is configured through the Identification and Reconciliation Engine and determines source authority and attribute update precedence; it is also not a Data Manager lifecycle policy.

Therefore, from the options provided, Retire and Archive are correct.

The correct answer is CMDB Workspace. Service Graph Connector Central is designed to improve visibility into Service Graph Connector activity and source contribution within the CMDB operating experience. Since the objective is to understand data sources contributing to the CMDB, the functionality is surfaced in CMDB Workspace rather than a separate Service Graph Connector Workspace or Discovery Admin Workspace. CMDB Workspace is the central workspace for managing CMDB data quality, source visibility, health, governance, and operational CMDB activities. Discovery Admin Workspace is focused on Discovery configuration and operations, not central CMDB source insight. Therefore, once the Service Graph Connector Central plugin is installed, the related tab is available in CMDB Workspace.

CSDM is designed to connect technology delivery to business consumption so organizations can answer questions like ''who is impacted?'' quickly and consistently. In a critical incident, the healthcare provider needs to identify impacted users in business terms---clinicians, admin teams, specific sites, or departments---rather than only listing technical components.

Option D (''Service Offerings by Department or Location'') is the most CSDM-aligned data because it reflects who consumes the service and how that consumption is segmented. In CSDM, a Business Service / Service Offering represents what customers consume, and the offering can be associated with organizational constructs such as department, business unit, or location. For healthcare, this is especially valuable because impact is often location-based (hospital site, clinic) and role-based (patient intake, scheduling, ward operations). Using service offerings and their consumer mapping helps quickly identify likely impacted user groups and prioritize communications and workarounds.

Option A (environment attribute) helps differentiate production vs non-production and can support prioritization, but it does not identify impacted users. Option B is historical context, not a reliable mechanism to determine current impacted users. Option C is useful operationally for listing impacted configuration items, but it is ITSM task data, not specifically CSDM consumer modeling. CSDM's value here is linking the technical disruption to the business consumer view via service offerings and consumption segmentation.