CSDM Fundamentals
About 11% of the CIS-DF exam — see all 5 domains.
CSDM (Common Service Data Model) is ServiceNow's prescriptive, standard framework for structuring service and CI data so it's consistent and product-ready.
Why CSDM: it provides a common language/structure across products (ITSM, ITOM, CSM, SecOps, APM, SPM), enabling service-aware reporting, impact analysis, and a trustworthy CMDB. Following CSDM is what makes data reusable across the platform.
CSDM domains (CSDM 5, 2025) — seven total, but they are not all the same kind of thing:
- Foundation — a supporting layer (not a lifecycle stage): referential base data (companies, business units, departments, locations, groups, users, product models, contracts). Most Foundation "common data" (Company, Department, User, etc.) are not CIs.
- The five sequential lifecycle / data-flow domains: Ideation & Strategy (new in CSDM 5) → Design & Planning (the tables formerly used by APM, now Enterprise Architecture) → Build & Integration → Service Delivery (formerly "Manage Technical Services") → Service Consumption (formerly "Sell/Consume").
- Manage Portfolios — a cross-cutting domain that spans portions of all five lifecycle domains, not a sequential stage.
Exam-timing flag: older CSDM 4 used four domains (Foundation, Design, Manage Technical Services, Sell/Consume). If the live exam still references the older names, recognize both — but teach the current CSDM 5 labels.
Key CSDM 5 specifics worth knowing: Service Delivery relabels
cmdb_ci_service_autoto "Service Instance" and adds new Service Instance sibling classes (Connection, Data, Facility, Network, Operational Process) — these are real classes that extendcmdb_ci_service_auto(introduced in the CMDB CI Class Models update), populated/maintained manually rather than auto-discovered (it is a relabel + new sibling extension classes, not a brand-new base class). CSDM 5 also adds SBOM (Software Bill of Materials,sn_sbom_core, spanning Design & Planning and Build & Integration), Ideation & Strategy (SPM), AI/OT classes, and renames Technical Service → Technology Management Service. (Note: ITBM is now SPM; APM is now EA.)Approach to abiding by CSDM: start with Foundation data, then progress through the official adoption stages Crawl → Walk → Run → Fly, building service models incrementally rather than boiling the ocean. (Foundation is treated as its own first implementation stage.)
Mapping across stakeholders/industries (scenario): correctly place CIs and services into the right CSDM domain by working with the stakeholders who own those services, regardless of industry-specific terminology.
Sample questions from this domain
Three of the 33 in this domain, with the reasoning. The full set is in the question bank.
Which statement best captures the recommended approach to adopting CSDM?
- A. Only populate the Service Consumption domain
- B. Skip Foundation data and model business services first
- C. Start with Foundation data, then build service models incrementally through the Crawl, Walk, Run, and Fly stages ✓
- D. Implement every CSDM domain fully before going live
Why: CSDM adoption is staged: establish Foundation data first, then progress through the official Crawl, Walk, Run, and Fly stages, building out service models incrementally. Trying to do everything at once, or skipping Foundation, undermines data quality.
What is the main benefit of structuring CMDB and service data according to CSDM?
- A. It guarantees the exam cut score is 70%
- B. It provides a common, prescriptive data structure that multiple ServiceNow products can reuse ✓
- C. It removes the need for the IRE
- D. It disables data source reconciliation
Why: CSDM gives a standardized, prescriptive structure so service and CI data is consistent and reusable across products (ITSM, ITOM, CSM, SecOps, SPM), enabling service-aware reporting and impact analysis. It does not replace the IRE.
A stakeholder is unsure which CSDM domain their newly modeled customer-facing business service belongs to. What is the best approach to map it correctly?
- A. Always put new services in Foundation
- B. Work with the service's stakeholders to map it to the correct CSDM domain based on how the service is designed and consumed ✓
- C. Leave it unmapped to avoid errors
- D. Place it in whichever domain has the fewest records
Why: Correct CSDM mapping comes from understanding how the service is designed, managed, and consumed, in collaboration with the stakeholders who own it — not by record counts or defaulting everything to Foundation. Leaving it unmapped harms data quality.