CIS-DF · Domain 5 of 5

CIS-DF Domain 5: CSDM Fundamentals

CSDM Fundamentals covers the Common Service Data Model: mapping CIs to the correct CSDM domain with stakeholders, following the recommended approach to adopt it, and explaining the benefits of implementing it.

Exam weight estimate
11%
Official objectives estimate
3
Estimated questions estimate
~8
Suggested study time estimate
7–9 hrs

About 10 min read Reviewed October 2026

Overview

Domain 5 has three blueprint objectives about the Common Service Data Model (CSDM), ServiceNow's prescriptive model for where service, application and product information lives in the CMDB. You need to know how to work with stakeholders in different industries to map their items to the correct CSDM domain and class, how to follow the CSDM approach in an implementation, and what benefits CSDM brings.

Key objects include business capability, business application, service instance or application service, technical service and technical service offering, business service and business service offering, and dynamic CI groups. CSDM 5 organises the model into domains such as Foundation, Ideation and Strategy, Design and Planning, Build and Integration, Service Delivery, Service Consumption and Manage Portfolio. Earlier versions used fewer, broader domains, and both naming styles appear in study material.

How it's tested

CSDM questions usually describe an item in business language, such as a payroll system, the cloud instance it runs on or the IT support offered to staff, and ask which CSDM class or domain fits. Other questions ask for the next step in a phased CSDM adoption or the main benefit of following the model.

  • Where does it go

    An item is described in stakeholder language and you choose the CSDM class, such as business application, application service or technical service offering.

  • Which phase next

    An organisation has completed some CSDM work, and you choose the next recommended step in the phased approach.

  • Why CSDM

    A sponsor asks what CSDM provides, and you pick a benefit such as consistent reporting or out-of-box product support.

Reasoning it through

A stem says a bank's architects track 'Online Banking' as a product, with production and test deployments that operations support separately. Options map 'Online Banking' to a technical service, a business service offering, a business application or a server. The business application represents the software product, while each deployment is a separate application service or service instance related to it.

Objectives 3

Official objectives from the ServiceNow outline, in outline order.

5.1 Identify how to work with different stakeholders across industries to correctly map CIs with the correct CSDM domainTranslating stakeholder language into CSDM classes.
What it means
Different stakeholders describe the same landscape differently: architects talk about applications and capabilities, operations about deployed services, and service owners about offerings to consumers. CSDM gives each view a defined class and domain.
What to understand
Map enterprise architecture items to business capabilities and business applications, deployed stacks to application services or service instances, shared IT capabilities to technical services and offerings, and consumer-facing services to business services and offerings. In industries like healthcare, banking or manufacturing the names change but the mapping logic stays the same. Use workshops and examples to agree definitions.
How it shows up
A stakeholder describes an item in industry language and you choose the CSDM class.
Common confusion
Mapping a business application directly to servers without the application service layer in between.
5.2 Identify the approach to abide by CSDMA phased, prescriptive adoption path.
What it means
ServiceNow recommends adopting CSDM in phases, often described as crawl, walk, run and fly, starting with foundation data and the most valuable service and application objects.
What to understand
Begin with foundation data such as users, groups, locations and companies, then business applications and application services, then technical services and offerings, then business services and portfolio objects. Use out-of-box classes and relationships, avoid custom parallel structures, and align each phase with a process that will consume the data.
How it shows up
A scenario lists completed phases and asks for the next recommended step.
Common confusion
Trying to populate every CSDM domain at once before the foundation is reliable.
5.3 Identify the benefits of implementing CSDMWhy following the model pays off.
What it means
CSDM provides a common language and structure for services and applications, so ServiceNow products and reports work as designed and data stays consistent across teams.
What to understand
Benefits include easier adoption of products such as Event Management, Vulnerability Response and Strategic Portfolio Management that expect CSDM objects, faster upgrades because data follows the out-of-box model, clearer accountability through service ownership, and consistent reporting from capability to infrastructure.
How it shows up
A question asks for the main benefit of aligning to CSDM rather than a custom service model.
Common confusion
Seeing CSDM as optional documentation rather than the structure products depend on.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Common Service Data Model

    ServiceNow's prescriptive model for services, applications and their relationships in the CMDB.

    Remember
    It is built on out-of-box classes and relationships.
    Tested as
    Every Domain 5 question starts here.
    Trap
    Treating it as a separate product to install.
  • Business application

    Represents a software product or system as the organisation knows it, such as a payroll application.

    Remember
    It is not a running deployment.
    Tested as
    Mapping questions often test this.
    Trap
    Relating it directly to servers.
  • Application service / service instance

    A deployed, running stack of a business application, such as production payroll.

    Remember
    One business application can have several deployments.
    Tested as
    Middle layer in most mapping items.
    Trap
    Merging production and test into one instance.
  • Technical service and offering

    IT capabilities, such as database hosting, offered to other IT teams with defined commitments.

    Remember
    Offerings carry support groups and service levels.
    Tested as
    Appears in operations-focused mapping.
    Trap
    Confusing them with business services.
  • Business service and offering

    Services consumed by the business or customers, such as email for employees.

    Remember
    Offerings define how consumers receive the service.
    Tested as
    Used for consumer-facing items.
    Trap
    Mapping internal IT capabilities here.
  • Business capability

    What the business does, independent of technology, such as claims processing.

    Remember
    Linked to business applications that support it.
    Tested as
    Appears in architecture-stakeholder questions.
    Trap
    Mapping it to a running service.
  • Dynamic CI group

    A query-based group of CIs that can be related to services.

    Remember
    It keeps service membership current without manual relationships.
    Tested as
    Appears in technical service questions.
    Trap
    Maintaining large static relationship lists instead.
  • Foundation data

    Reference data such as users, groups, locations, companies and cost centers.

    Remember
    The first phase of CSDM adoption.
    Tested as
    Often the answer to what comes first.
    Trap
    Skipping it to start with services.
  • Phased approach

    Crawl, walk, run and fly stages that build the model gradually.

    Remember
    Each phase should support a consuming process.
    Tested as
    Next-step questions test the order.
    Trap
    Building all domains at once.
  • CSDM life cycle fields

    Standard life cycle stage and status fields across CSDM objects.

    Remember
    They give consistent lifecycle reporting.
    Tested as
    Links CSDM to Govern lifecycle objectives.
    Trap
    Using different status fields for each class.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Application-related CSDM objects

ConceptMeaningKey differenceCommon trap
Business capability What the business does Technology-independent Mapping it to deployments
Business application The software product Logical, not running Relating it straight to servers
Application service / service instance A running deployment Has infrastructure relationships Using one instance for all environments

Service-related CSDM objects

ConceptMeaningKey differenceCommon trap
Technical service IT capability for IT consumers Owned by IT, often shared Calling it a business service
Technical service offering Defined way a technical service is provided Carries support and commitments Skipping offerings entirely
Business service Service consumed by the business Consumer-facing Mapping infrastructure capabilities here
Business service offering A variant or level of a business service What consumers subscribe to Treating it as a CI class for hardware

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Application equals deployment

    What candidates pick
    Record production and test payroll as one business application with servers attached.
    Why it looks right
    It looks simpler with fewer records.
    Why it's wrong
    CSDM separates the logical business application from each running application service or service instance.

    Clue to watch for Multiple environments are mentioned.

  2. Internal capability as business service

    What candidates pick
    Model database hosting as a business service.
    Why it looks right
    Everything called a service seems to belong there.
    Why it's wrong
    Database hosting is consumed by IT teams, so it is a technical service with offerings.

    Clue to watch for The consumers are other IT teams.

  3. Big-bang adoption

    What candidates pick
    Populate all CSDM domains in one project phase.
    Why it looks right
    It promises completeness quickly.
    Why it's wrong
    The recommended approach is phased, starting with foundation data and the objects that a process will use first.

    Clue to watch for The stem asks for the first or next step.

  4. Custom model

    What candidates pick
    Build custom tables to fit the organisation's service vocabulary.
    Why it looks right
    It matches existing terminology.
    Why it's wrong
    Custom models break out-of-box product behaviour and upgrades; map local terms to CSDM classes instead.

    Clue to watch for The organisation uses unusual internal names.

  5. Capability as service

    What candidates pick
    Map 'claims processing' to an application service.
    Why it looks right
    It is something the insurer delivers.
    Why it's wrong
    Claims processing is a business capability; applications support it and deployments run them.

    Clue to watch for The item describes what the business does, not software.

Answer framework

Use these steps to place items in CSDM and answer approach questions.

  1. Identify the stakeholder viewpoint: enterprise architecture, application ownership, IT operations, service ownership or portfolio management.
  2. Ask whether the item is a business ability, a logical software product, a running deployment, an IT capability for IT teams or a service consumed by the business.
  3. Map to business capability, business application, application service or service instance, technical service or business service, adding offerings where commitments differ.
  4. For adoption questions, follow the phased order: foundation data, applications and deployments, technical services, then business services and portfolio objects.
  5. For benefit questions, choose answers about consistent data, product compatibility and upgradeability over answers about documentation or volume.

Practice question

A hospital's IT team provides a shared database hosting capability, with a gold offering for clinical systems and a standard offering for administrative systems, to its own application teams. How should this be modelled in CSDM?

Choose one answer

Want more like this? The CIS-DF practice test has questions for every domain.

Checklist

0 of 11

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start with the current CSDM white paper or documentation and draw the model on one page: business capability and business application on the design side, application services or service instances in the middle, technical and business services and their offerings on the delivery and consumption sides, with infrastructure CIs at the bottom.

Then practise mapping. Take three industries, such as banking, healthcare and manufacturing, and write five items for each in business language. Map each one to a class and justify it in one line. This builds the reflex the exam tests.

Next, read the phased adoption guidance and write the order of phases with one example object for each. In a Personal Developer Instance, open a business application and an application service, view their relationships, and create a dynamic CI group.

The area candidates underestimate is version naming: study material mixes CSDM 4 and CSDM 5 terms, so learn both names for application services and the main domains. Finish by revisiting Ingest and Insight questions that rely on CSDM objects.

FAQ

How many questions does CSDM Fundamentals contribute?

CSDM Fundamentals is weighted at 11% of the 75-question exam, roughly eight questions as a planning estimate. CSDM ideas also appear in other domains.

Which CSDM version does the exam use?

Recent material reflects CSDM 5 terminology, but older study sources use CSDM 4 names. Learn both, especially application service and service instance.

What is the most common mapping mistake?

Treating a business application as a running deployment. The business application is the logical product, and each environment is a separate application service or service instance.

Do I need to know every CSDM table name?

Knowing the main classes and how they relate matters more than table names, although cmdb_ci_business_app and cmdb_ci_service_technical are worth recognising.

What does crawl, walk, run and fly mean?

It describes phased CSDM adoption, from foundation data and core applications toward full service and portfolio modelling.

Why is CSDM tested in a CMDB exam?

CSDM defines where service and application data lives in the CMDB, so health, ingestion and insight work all assume it.

Other CRM & Business Applications certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 5 knowledge

You have mapped stakeholder items to CSDM classes and reviewed the adoption approach. Check that you can place items quickly and accurately under timed conditions.

Keep going