CIS-DF Exam Dumps - ServiceNow CIS-Data Foundations (CMDB and CSDM) Questions and Answers

The correct answer is Create CMDB Groups with type Health by region . CMDB Health scores can be scoped to meaningful CI populations by using CMDB Groups. When a Configuration Manager needs region-specific health visibility, the correct design is to define CMDB Groups that represent the regional CI population and set the group type appropriately for health evaluation. This allows the dashboard to calculate and display scores for the relevant subset of CIs instead of only showing global or class-level scores. There is no standard “Group scores by region” switch that automatically creates regional scorecards. Customizing scheduled jobs is also a poor approach because it introduces unnecessary technical debt and can interfere with platform-supported health calculations. CMDB Groups provide the governed and supported way to scope health reporting to regional CI populations.

=========

Task behaviour for CIs that fail a CMDB Health condition is configured through Health Metrics . The Orphan metric evaluates whether CIs have the required relationships or contextual connections defined for their class. Its metric configuration determines how the condition is evaluated and supports the generation of remediation work for unhealthy records.

The CMDB Health Dashboard displays calculated results and scorecards, but it is primarily a reporting and investigation interface rather than the underlying metric-configuration location. CI Class Manager is used to manage CI classes, attributes, identification rules, and related class-level settings. System Properties control broader platform behaviour and are not the specific location for configuring task handling for the Orphan metric.

Because task creation is tied to the applicable health condition and its remediation behaviour, the administrator configures it through Health Metrics .

=========

Top of Form

Within the Common Service Data Model (CSDM), information objects are used to represent non-CI data entities that provide important business or governance context but are not configuration items themselves. These objects are especially important when extending service visibility beyond pure infrastructure and application relationships.

The use case described in Option A—understanding asset lifecycle compliance in a Business Application context—explicitly requires information objects. Asset lifecycle data (such as financial state, depreciation, warranty, and compliance milestones) is typically managed in IT Asset Management (ITAM) and must be associated to Business Applications without converting every asset-related data point into a CI. Information objects enable this linkage while maintaining clean CMDB boundaries.

Option B focuses on event-to-incident automation, which relies on CIs, technical services, and operational relationships, not information objects. Option C (proactive case management) is primarily a CSM and service offering use case. Option D (SecOps risk context) relies on application services and business application relationships, not information objects. Option E (business service impact) is addressed through service modeling and service mapping, again without requiring information objects.

Information objects are introduced as organizations mature and need to integrate governance, financial, or compliance data with service and application models—making asset lifecycle compliance the correct match.

Therefore, the correct answer is A.

In CMDB governance, different CMDB Data Manager policy types serve different validation and enforcement purposes. When the objective is to allow an assigned individual to review and update specific fields on a CI record, the correct policy type is Certification.

A Certification policy creates actionable tasks that require the assignee to validate 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 CI still exists or 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 when human validation and correction of CI data is required—making it a cornerstone of CMDB data quality management.

Hence, the correct answer is B – Certification.

A healthy and trusted CMDB that aligns with Data Foundations principles—covering accurate data ingestion, strong governance, and service-aware relationships—directly strengthens the insight available to Change Management. When discovered infrastructure data is integrated with well-maintained non-discoverable attributes (such as assignment groups, support groups, and ownership), the CMDB becomes a reliable source of truth for evaluating change risk and impact.

Option B is correct because Service Mapping establishes relationships between configuration items (CIs) and business services. This enables change practitioners to perform impact analysis, identifying which services, applications, and downstream components may be affected by a proposed change. Rather than relying on assumptions or tribal knowledge, change records can reference real dependency data, improving risk assessment, scheduling decisions, and stakeholder communication. This aligns directly with CSDM and CMDB best practices, where service context is essential for informed decision-making.

Option D is also correct because accurate, governed non-discoverable data—such as support and assignment groups—allows Change Management processes to dynamically route work. When a change is associated with a CI or service, the system can automatically populate the appropriate assignment group based on CMDB relationships. This improves efficiency, reduces manual errors, and ensures accountability across federated support models.

Options A and C are incorrect because a CMDB, regardless of maturity, cannot guarantee zero downtime, nor does it eliminate the need for human governance, approvals, and risk-based decision-making. Data Foundations enhance insight and control—not unchecked automation or absolute outcomes.

The CMDB Data Foundations Dashboard is designed to help administrators identify priority data issues and take structured remediation actions. When several metrics have low scores, the correct approach is not to randomly clean records or manipulate scoring rules. Instead, the administrator should prioritize the most important issues and use the recommended remediation guidance.

Option A is correct because Data Foundations emphasizes prioritizing metrics with Critical and High priority first. These metrics usually represent the most important issues affecting CMDB trust, operational readiness, service visibility, and downstream ITSM processes such as Incident, Change, and Problem Management. Focusing on the highest-priority metrics ensures remediation effort is aligned with business and operational risk.

Option C is also correct because the dashboard provides Remediation Playbooks linked to specific metrics. These playbooks give structured guidance for analyzing the issue, identifying impacted records, correcting the data, and improving governance so the problem does not return. This is the preferred Data Foundations approach because it supports repeatable, auditable, and best-practice remediation.

Option B is not recommended because changing exclusions simply to improve the score can hide poor data quality rather than fix it. Exclusion rules should only be used when records are legitimately out of scope. Option D may be valid in some lifecycle cleanup scenarios, but blindly removing non-operational or retired CIs is not the primary recommended action for improving dashboard health.

The correct answer is Data Quality Scheduled Job because CMDB data quality checks are not simply visual or manual activities. Scheduled jobs are used to execute recurring evaluations that calculate and refresh quality indicators for CI records. These jobs support CMDB health and data quality by periodically checking records against configured rules, such as stale records, missing required attributes, compliance conditions, or correctness-related metrics. CMDB Workspace is the interface where users can review and act on CMDB information, but it is not itself the mechanism that performs scheduled quality evaluation. Business rules can enforce logic during insert or update actions, but they are not the normal mechanism for recurring CMDB data quality calculation. Therefore, the Data Quality Scheduled Job is the best answer.

=========

CI Class Manager is used to configure class-level health requirements, including attributes designated as required or recommended for a selected CI class. The administrator can identify Support Group and Managed By Group as recommended attributes for the Linux Server class. Recommended fields provide operational and diagnostic value even when they are not technically mandatory for inserting a CI.

Health Preferences control how CMDB Health findings are processed, including task-generation behaviour for CIs that fail applicable health conditions. Once the health calculations identify operational Linux servers with missing recommended values, remediation tasks can be generated and assigned for corrective action. The guide confirms that task behaviour for unhealthy CIs is governed through the relevant health metric configuration rather than through the dashboard itself.

Technical Service Offerings and Dynamic CI Groups can populate and synchronize group values, but they are not the modules used to define recommended-field health checks and generate health tasks. Therefore, B is correct.

=========

To specifically improve data quality related to CSDM, the most effective and prescribed action is to use the CSDM Data Foundations Dashboard. In ServiceNow, this dashboard is purpose-built to assess and improve CSDM alignment, not just general CMDB hygiene.

The CSDM Data Foundations Dashboard focuses on service modeling readiness, highlighting gaps such as missing service ownership, incomplete relationships between Business Applications and Application Services, unmanaged services, and misaligned lifecycle states. It provides Get Well Playbooks that guide administrators through structured remediation using Analyze Data, Fix Data, and Govern Data plays—directly tied to CSDM outcomes.

Option C (default CMDB Health Dashboard) is valuable, but it measures generic CMDB data quality dimensions (completeness, correctness, compliance) and does not specifically evaluate CSDM constructs or service modeling maturity. Option B (ServiceNow Health Scan) provides platform-wide configuration and performance recommendations, but it is not focused on CMDB or CSDM data quality.

Therefore, to improve CSDM-specific data quality, the administrator should use the CSDM Data Foundations Dashboard, making Option A the correct answer.

Foundation → Use the base system tables when implementing CSDM to get the highest value from ServiceNow products and the Now Platform.

Design and Planning → Understand CIs related to Business Applications and related capabilities; identify redundancies, monitor costs, and make better investment decisions around the roadmap.

Service Consumption → Understand Business Services, ownership, cost, scope of work offered to business consumers, and request access to business services.

Service Delivery → Understand Technical Services, Technical Service Offerings, service support, and all relationships to underlying technology CIs.

CSDM separates data into domains so organizations can model business planning, consumption, and technical delivery without mixing concerns. The Foundation domain provides base reference data such as users, groups, companies, locations, and foundational tables used across the platform. Design and Planning supports architecture and portfolio planning through Business Applications, Business Capabilities, and Information Objects. Service Consumption focuses on how services are exposed to and consumed by business users through Business Services and Business Service Offerings. Service Delivery focuses on how services are technically operated using Technical Services, Technical Service Offerings, Application Services, and supporting infrastructure CIs. This separation is what makes CSDM valuable: each domain answers a different management question while still connecting to a unified service model.

=========