One story instead of a hundred facts
A company wants to operate a service. It models relevant objects as CIs, ingests data from sources, governs data quality, links the CIs to a service model, and uses the result to make decisions.
Terms Map: One Online Shop on all layers
CSDM does not describe one object with ten synonyms. It models one world from several viewpoints: what the business can do, which application it plans, what is actually running, which service a consumer receives, and which CIs deliver it.
The key distinction: plan, running instance, and technical component
Business Capability
What the business must be able to do to achieve an outcome: sell online, manage finances, or hire employees. It is not an application, server, or running system.
Business Application
A logical portfolio record with an owner, risk, cost, and roadmap. It usually covers all environments. Online Shop remains one Business Application even when PROD and TEST are deployed separately.
Service Instance
The running stack; its former name is Application Service. Online Shop PROD contains related applications, hosts, databases, and an entry point. It provides operational impact context for incidents and changes.
Application CI
A specific detectable program or module on the infrastructure: Apache, Oracle instance, Tomcat. One Service Instance may contain multiple Application CIs, and one Application CI may participate in multiple service instances.
Business Service
Operating service published for business consumer: Online Ordering, Procurement or Shipping. It describes the value it receives, not the internal platform.
Business Service Offering
Specific Business Service consumed: Gold/Silver, region, support hours, availability, price and service commitments. Offering answers the question “What version of the service does the consumer receive?”
Technology Management Service
An internal provider-focused technical service that supports business services or service instances: Unix Platform, Database Platform, Network Service.
Configuration Item
A physical or logical entity under configuration management: server, router, database, application, or entire service instance. CI is a broad category; Business Application is also a model CI, but not the same as Server CI.
Not one straight chain, but four useful relationships
The planned application receives specific deployed environments: PROD, TEST, DEV.
What the consumer has ordered depends on the actual stack that it delivers.
The operating service consists of interrelated application, server, database and network CIs.
The technical service option manages a specific set of infrastructure CIs.
How to know the correct object by wording
| If the question mentions... | Choose | Why |
|---|---|---|
| Portfolio, investment, owner, risk, roadmap, all environments | Business Application | This is the logical object of planning. |
| Deployed stack, entry point, dependencies, PROD instance | Service Instance / Application Service | This is a working operational instance. |
| Apache/Tomcat/Oracle process | Application CI | This is a detectable technical program. |
| Value or result for a business user | Business Service | It's a consumer-facing service. |
| Gold/Silver, SLA, availability, price, geography, commitments | Service Offering | This is a specific version of the service. |
| Platform that an internal IT provider provides to services | Technology Management Service | Provider-facing technical capability. |
| Specific server, database, router or application | Configuration Item | It is a managed component of the CMDB. |
Configuration: identify the object and control who may change it
Configuration defines the rules before data is ingested. If the class model or IRE is configured poorly, every later dashboard will simply present an inaccurate CMDB more attractively.
Class = family tree
cmdb_ci is the root. A child class inherits fields and behavior from its parents: Computer → Server → Windows Server. Create a custom class only when no suitable standard class exists.
CI Class Manager = tree editor
Use it for Basic Info, class fields, identification and reconciliation rules, and class health settings. Pinned Classes provides shortcuts; Added shows fields defined directly on the selected class.
Required ≠ Recommended
Required can stop the insert/update via IRE. Recommended does not normally block a record, but reduces Completeness and can create a remediation task.
A relationship has meaning and direction
Use standard types such as Depends on::Used by. Maps, queries, and other ServiceNow products understand their semantics. Relationships can be many-to-many.
IRE as Passport Control
“Which CI is this?” Rules and identifiers look for an existing CI. 0 matches → insertion may be allowed. 1 match → update that CI. Multiple matches → duplicate condition.
Can this source create new CIs? You can allow updates, but not inserts.
“May this source change this attribute?” Static reconciliation uses fixed source priorities. Dynamic reconciliation calculates the winning value from the reported data.
Stores source-specific values, shows discrepancies and what value won.
| If the question says... | Think... | Don't choose. |
|---|---|---|
| Unique, match, new or existing | Identification rule | Reconciliation |
| Which source may update RAM | Reconciliation rule | Identifier |
| Source may update but not insert | IRE data source rule | Health inclusion rule |
| Largest / most reported value wins | Dynamic reconciliation | Static priority |
CMDB 360: Three similar properties
| Properties | What does it include? |
|---|---|
glide.identification_engine.multisource_enabled | CMDB 360/multisource master switch. |
...multisource_cmdb_ci_enabled | Source-specific data for classes that inherit cmdb_ci. |
...multisource_non_cmdb_ci_enabled | Source-specific data for classes outside cmdb_ci. |
non You can't lose it. One community test didn't have it, so the answer for non-CMDB classes was wrong. Dynamic reconciliation also refers to CMDB 360: it selects winning value from stored source-specific values.Identification fallback: If a child-class rule finds no CI, Allow fallback to parent's rules lets IRE try a more general parent rule. It does not bypass IRE or automatically permit insertion.
Reclassification
- Upgrade: parent → more specific child class.
- Downgrade: child → parent class.
- Switch: move to another hierarchy branch.
- Downgrade and switch may lose class-specific values when the target class lacks the corresponding fields.
Ingest: How data enters the CMDB
Don’t choose a tool just because it “downloads data.” First ask: is data collected from the bottom up, one service built from the top down, a ready-made vendor feed comes in, or does it need your own ETL?
First, separate four objects: service → offering → CI set → individual CIs
Exam questions often place these terms in one sentence even though they answer different questions. Imagine an internal team providing a managed Unix platform.
Technology Management Service
A provider-facing technical service: what IT provides and supports. Former name: Technical Service. It may support Business Services or Service Instances and may contain multiple offerings.
Technology Management Offering
A specific option of the parent service: for whom, where, in which environment, and under which conditions. Availability, performance, geography, price, commitments, and responsible groups may differ. Former name: Technical Service Offering; table: service_offering.
Dynamic CI Group
Not a team of people, but a CI population continuously calculated from a CMDB query—for example, Class = Server, OS = Linux, Environment = Production. An offering can use the group to govern the entire matching CI set.
CI Class Manager
Defines a general class-level default. If the Server class has Managed by = Server Team, that value applies unless a narrower offering-level assignment overrides it.
Why Offering Can Change Groups to CI
Managed by group
Who manages quality and responsibility for CI or class: ensures that data is complete and correct. It's not necessarily the same team that fixes every incident.
Support group
Who usually receives and handles incidents for these CIs. In offering, you can set a separate support team for a specific level of service.
Change group
Who is responsible for changes and technical alignment of changes for related CIs. This is its own field — it is not a renamed Assignment group, which stays a separate task-routing field.
CSDM Data Sync
Copies group values from the offering to its Dynamic CI Group and then to the CIs in that group. A newly discovered CI may receive the values when the scheduled synchronization job runs, not during Discovery itself.
CI Class Manager says that all Servers are run by Server Team by default.
Offering Production Unix 24×7 includes Dynamic CI Group only with production Unix servers.
Managed by = Unix Support. This rule applies to a more specific set of CIs.
For CIs in this offering's group, Unix Support overrides the general class-level default, Server Team.
Why this is on Ingest: Discovery collects technical facts – OS, RAM, MAC, processes. But organizational data on who manages, supports, and changes cannot be reliably detected by scanning. They come from a managed CSDM model and are synchronized in CI as authoritative values.
Now choose the technical data path
Scans infrastructure: OS, RAM, MAC, processes and communications. Phase: Scanning → Classification → Identification → Exploration
It starts with a specific service and builds dependencies. It helps to assess impact change and find root cause incident faster.
Lightweight agent-based discovery and near-real-time monitoring.
Ready integration of a specific external product from Store, CMDB-aware and IRE-aware.
Visual Extract/Transform/Load when there is no ready-made connector or you need your own mapping rules.
For a CMDB, transform map must call an IRE via onBefore + CMDBTransformUtil. Live recording is dangerous.
Unavailable Discovery data: warranty expiration, contractual and financial values Discovery itself does not know. They are regularly imported from an authoritative vendor/asset source, saving the way for CI through IRE and reconciliation.
How to Read Ingest Questions
| The phrase in question | That she's checking. | Where to look |
|---|---|---|
| All reachable servers and devices | Broad bottom-up inventory | Discovery |
| Dependencies of one online service | Top-down service context | Service Mapping |
| Supported vendor feed from Store | CMDB-aware integration | Service Graph Connector |
| No connector; custom mapping | Own Extract/Transform/Load | IntegrationHub ETL |
| May update but must not insert | Source resolution within the IRE | IRE data source rule |
| Support, Change or Managed by | Organizational responsibility, not scan | CI Class Manager or Technology Management Offering |
SNAssetManagement. CI, created by Discovery itself, usually has a source. ServiceNow.Govern: Can you trust CMDB tomorrow?
Govern is the hardest section of the exam. It mixes metrics, denominators, remediation, ownership and lifecycle. Always decide first what quality question is asked.
Is the data complete?
Required + Recommended. Missing required/recommended fields. You can automatically create tasks.
Is the data credible?
Duplicates + Orphans + Staleness. Relevance, uniqueness and expected relationships.
Is the data normal?
Audits. Desired State, certification templates/filters and scripted audits.
Health inclusion rule Determine which CIs are included in the calculation. Therefore, two identical numbers can give different percentages at different scope. Always find numerator and denominator.
If you need a score only for a region or an organizational scope, create a score health-type CMDB group with the right filter. No separate CI class or rewrite of a global scheduled job is required.
Do not confuse “number of duplicate records” with “number of duplicate groups.”
Correctness without confusion
- Stale:
sys_updated_onover effective duration; the basic example of the course is 60 days. - Orphan: There is no expected relationship. The rule must be configured; out-of-box orphan rules may not be available.
- Duplicate: Several records represent one object. De-Duplication Template makes remediation repeatable.
- Main CI recommendation: Most relationships, oldest created or most recently updated. This is a recommendation, not an absolute business truth.
- If Discovery is allowed to continue with multiple matches, the course indicates the update of the oldest CI by creation date.
Data Manager = Managed Lifecycle
It's not a mandatory rigid sequence of all policies, but a way of discerning intent: retirement changes lifecycle; attestation asks owner "CI still exists?"; certification validates data; archive/delete clears eligible data. Before archive/delete CI must be retired or end-of-life.
| term | Short question. |
|---|---|
| Attestation | "Are you confirming that this CI exists?" |
| Certification | “Does the data meet the requirements?” |
| Remediation Rule | “What kind of workflow to run to fix the problem?” |
| Data Manager policy | “What is the system to do with lifecycle/check/clean up?” |
Insight: What question do we ask data?
Insight is not a single application, but choosing the right way to see or find data.
| Need to. | Tool. | Why? |
|---|---|---|
| Find CI by class, terms and relationships | CMDB Query Builder | Graphic structured request |
| Ask CMDB with the usual phrase | Intelligent Search | Natural-language query |
| Service map + dependency view | Unified Map | Single visual map |
| Duplicates, Orphans, Staleness | CMDB Health Dashboard | Quality of CI data |
| CSDM adoption, Crawl/Walk/Run/Fly, playbooks | CSDM Data Foundations Dashboard | Maturity of the overall model |
Unified Map by layer: Topology canvas shows connections. Contextual side panel Details of the selected CI. His Related Items contain related Incidents and Changes.
sn_cmdb_ws plugin. Know both names, reject any option claiming one replaced the other, and answer from the function the question describes.CSDM: from an idea to a working service
CSDM is a language that links business, architecture, development, working CI and what the consumer gets. The main reason for mistakes is choosing the right word on the wrong layer.
Business Capability · Business Application · Information Object
SDLC Component
Application Service · Technology Management Service/Offering · Dynamic CI Group · discovered CIs
Business Service · Business Service Offering · Service Portfolio
Four words that should not be confused
Logical object of enterprise architecture: investment, risk, owner, roadmap. Not necessarily one deployed instance.
A specific deployed stack and its dependencies. Operational CI for Incident/Change. Parental table cmdb_ci_service_auto.
Managed technical capability of an internal provider, such as Database Platform Service.
A specific service consumed with commitments, groups and terms.
For application-focused parts Design & Planning particularly Application Owner and Enterprise ArchitectThe first is responsible for a specific application, the second connects Business Capability, Business Application and Information Object into a holistic architecture.
Operational model
- Dynamic CI Group A query-based set of CI, not user groups. It is better not to associate CI through different groups with multiple technical offerings, otherwise synchronization of ownership can conflict.
- Service Builder It simplifies the creation of Business/Technology Management Services and Offerings.
- Application Service Wizard Links Application Service to Technology offering, Business offering and/or Business Application.
- Digital Portfolio Management Provides unified lifecycle workspace for portfolios, services, offerings and products.
- Life cycle stage + stage status The recommended modern pair of lifecycle fields; the old Install/Operational/Hardware status remains for compatibility and synchronization.
Data Foundations maturity
Practice with CSDM Lab instance
The CSDM Labs lesson doesn’t contain a separate workbook or step list: it delivers a customized sandbox. In it, you need to recognize the following work screens and understand why they are needed.
Service Instance Settings
Defines required attributes and required relationships for service instances. Available attributes include: environment, version, model ID, operational status, support/change/managed by group, owned by. Relationships include Business Application, Technology Service Offering, Business Service Offering, and Parent Application Service.
Service table configs
Form fields: Name, Service table, Application, Mapping level and Active. Mapping level selects Service or Service offering. This describes how the original service table is involved in CSDM mapping.
CSDM Service mappings
Links the entry from the selected Service table with the canonical CSDM service and CSDM Service offering. Fields: Service table, Service, CSDM service, CSDM Service offering, Active.
Data Foundations Dashboard
Tabs Foundation, Crawl, Walk, Run, Fly. The indicators lines show Name, Priority, Result, Remediation playbook URL and Updated. It's not just score: a playbook leads from a gap to a fix.
Five distinctions that close the remaining gaps
Use this page for recall; use the five-course book when one of these chains is not obvious.
Observed vs governed relationships
Discovery/Service Mapping can observe technical dependencies. Business intent, ownership and regulatory scope need an authoritative integration or controlled manual governance.
Six health metrics
Completeness: Required + Recommended. Correctness: Duplicates + Orphans + Staleness. Compliance: Audits against desired state.
Data Manager flow
Prerequisites and target → define action/scope → preview records → publish → execute/review tasks → verify outcomes and exceptions.
Two saved-query families
Query Builder asks graph/relationship questions. CMDB 360 asks Get Records, Find Gap or Compare Attribute Values; schedule it for Reporting.
How to complete 75 questions in 90 minutes
The average budget is 72 seconds per question. The purpose of the first pass is to answer everything, not to prove to yourself that every difficult question is solved perfectly.
- 0-55 min First passSimple single-choice at once. A long scenario is not understood in 75-90 seconds - best current answer + flag + next.
- 55–75 mins · multi + matchingReturn to select-two/three and drag-drop. First, eliminate a clearly foreign domain, then check each pair selected.
- 75-86 minutes · flagsChange the answer only for a specific reason: found the word limiter, remembered the rule, noticed an extra option.
- 86-90 minutes · integrityWhether unanswered; all multiple selects have an exact number; all matchings have slots filled.
Reading the long question
What was used
Official course CMDB Fundamentals and its knowledge checks; official CSDM Fundamentals quiz; CSDM 5 white paper; hands-on study dedicated CSDM Lab instance; ServiceNow Australia documentation on IRE, Data Manager, CSDM domains and Data Foundations Dashboard; local deduplicated deck. The wording of training questions is created anew and are not real exam questions.
IRE documentation · CSDM glossary · Design & Planning domain · Service Delivery domain · Service Consumption domain · Group assignment attributes · CSDM domains · CSDM Data Foundations Dashboard · Data Manager