ServiceNow Updated CIS-DF Exam Questions and Answers by franciszek

CMDB Data Foundations Dashboard playbooks explain why a deficient metric matters and provide recommended actions for improving it. This includes insight into downstream consequences such as duplicate creation, inaccurate assignment, unreliable impact analysis, weak service context, incorrect reporting, or ineffective Incident, Change, and Security Operations processes.

The playbooks also provide remediation options. These guide administrators through analysing affected records, identifying responsible data sources, correcting existing data, and introducing governance controls to prevent the condition from returning. The guide describes remediation playbooks as structured guidance for analysing issues and implementing targeted corrective actions.

They are not automatically executed scripts. Human analysis, source correction, ownership decisions, and governance changes are generally required. They are also more than generic remediation templates because their value includes contextual impact information and metric-specific recommendations.

Therefore, the two stated benefits are downstream-impact insight and remediation options, making B and D correct.

=========

In ServiceNow, Dynamic CI Groups are a core Data Foundations capability used to automatically manage CI membership based on rules rather than manual maintenance. When Technology Management Service Offerings (Technical Service Offerings) are related to Dynamic CI Groups, ServiceNow uses those relationships to synchronize operational support attributes to the member CIs.

The two CI attributes that are intentionally designed to sync in this model are the Managed by Group and the Support Group. These groups directly influence operational ownership and support routing, which is why they are automatically aligned when Dynamic CI Groups are used. This ensures that incidents, changes, problems, and operational tasks are routed consistently as CI membership changes over time.

The Support Group defines who provides day-to-day operational support and is critical for Incident and Request Management workflows. The Managed by Group represents the team responsible for the technical lifecycle and operational health of the CI. Synchronizing these attributes eliminates manual updates and reduces misrouted tickets, which is a key goal of Configuration Management maturity.

The Approval Group (Option A) is not synced because approvals are process-driven and often context-specific rather than CI-driven. Similarly, the Owned by Group (Option C) represents accountability or financial ownership, which is intentionally decoupled from dynamic operational grouping to avoid unintended governance changes.

Therefore, the correct answers are B (Managed by Group) and D (Support Group).

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.

In ServiceNow, the Duplicate CI Remediator is designed to resolve duplicate records while preserving the most authoritative data from each source. Data Foundations guidance clearly states that automated discovery is the system of record for technical attributes, such as IP address, hostname, and operational status, while manually maintained records often contain valuable business context, such as relationships to business applications or services.

In this scenario, the discovered CI contains the most accurate and up-to-date technical data, making it the correct CI to retain as the primary record. However, the manually imported CI has a critical relationship to a business application, which is essential for impact analysis, incident prioritization, and CSDM alignment. Deleting this CI without preserving the relationship would result in loss of business context and reduced CMDB value.

The Duplicate CI Remediator supports selective merging, allowing administrators to retain one CI while merging specific attributes or relationships from the duplicate. Option C reflects this best practice by retaining the discovered CI and merging the relationship from the manually imported CI, ensuring both technical accuracy and business relevance are preserved.

Options A and D would result in the loss of important relationship data, while Option B would discard the discovered CI, violating the principle that discovery should be the authoritative source for technical attributes.

Therefore, Option C is the correct and Data Foundations–aligned answer.