CIS-DF Practice Questions

In Data Foundations for CMDB and CSDM, a dashboard indicator (like “Services Have Owners Identified”) highlights a data quality condition—in this case, Services missing required ownership information. The playbook-driven remediation model typically follows a practical sequence: first you identify and validate the scope of the issue, then you correct the underlying records so the metric improves and remains sustainable.

The Analyze Data play is used to break down what the dashboard is reporting into actionable detail. It helps determine which Service records are failing the ownership requirement, what ownership fields are missing (for example, service owner / business owner / technical owner depending on configuration), and where the gaps are concentrated (by business unit, environment, lifecycle stage, or service portfolio segment). This ensures the remediation effort targets the correct records and avoids inaccurate assignments.

The Fix Data play is used to perform the actual remediation—populating or correcting the owner attributes on the Service records so accountability is clear and operational processes can route approvals, escalations, and service decisions correctly. In CSDM terms, clearly assigned owners enable proper stewardship of Service Portfolio and Service Offerings and improve downstream outcomes such as incident assignment accuracy, change impact analysis, and reporting reliability.

While Govern Data supports preventing recurrence (policies, controls, ownership model, and stewardship routines) and Report Data communicates progress, the two plays directly used to remediate the dashboard issue are Analyze Data and Fix Data.

The Common Service Data Model (CSDM) organizes CMDB data into domains that reflect how services are planned, delivered, and consumed. Correct placement of objects is essential for reporting, ownership, and downstream ITSM, ITOM, and IRM use cases.

Design and Planning domain → Business Process

Business Processes describe how the business operates and what capabilities are required. These are planning constructs used to design services and applications before they are built or delivered.

Foundation domain → Business Application

Business Applications are foundational reference objects that represent what applications exist and who owns them. They anchor ownership, lifecycle, and governance but are not directly operational.

Service Delivery domain → Application Service

Application Services represent running, operational technical services (often created via Service Mapping). They are central to Incident, Change, and Event Management, making them part of Service Delivery.

Sell / Consume domain → Business Service

Business Services represent what is offered to customers or consumers. They define value delivery, SLAs, and consumption context, which is why they belong in the Sell/Consume domain.

This mapping aligns with CSDM v5 guidance and ensures clear separation between planning constructs, foundational records, operational services, and consumer-facing services—a key principle for a scalable and governed CMD

B.  

In ServiceNow, ingesting custom CIs must be done with a strong focus on upgrade safety, governance, and long-term maintainability. Data Foundations guidance explicitly discourages repurposing or overloading base classes, as this creates technical debt and upgrade risk.

Option B is a best practice because the CMDB CI Class Models Store delivers ServiceNow-supported CI classes that align with platform evolution. Before creating or extending classes, administrators should verify whether a suitable class already exists or has been introduced in newer releases. This avoids duplication and ensures future compatibility.

Option D is also correct. When no suitable class exists, extending an existing CI class (under the appropriate parent) to add required attributes preserves inheritance, discovery behavior, reporting, and upgrade compatibility. This approach is preferred over creating entirely new, disconnected schemas.

Option A is incorrect because repurposing base classes and renaming attributes breaks standard semantics, causes confusion, and complicates upgrades. Option C is incorrect because extending Asset tables to represent CIs conflates ITAM and CMDB concerns; assets and CIs serve different purposes and lifecycles.

Therefore, the solutions that minimize technical debt and ensure upgrade compliance are B and

D.  

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.