Configuration Management Database
About 15% of the CIS-SM exam — see all 6 domains.
Service Mapping is both a producer and a consumer of the CMDB, so the exam expects fluency in the data model.
Application services in the CMDB and CSDM
The Common Service Data Model (CSDM) is ServiceNow's standard for organizing service data in the CMDB. Service Mapping populates the application service record (cmdb_ci_service_auto / service tables) and the relationships beneath it. Under CSDM, the application service is the central technical-service construct; it can be associated upward with business-facing services and downward with the CIs that compose it. Knowing how CSDM concepts map to CMDB tables — and that Service Mapping output is meant to populate the technical/application service layer — is a frequent exam target.
CI relationships
Service Mapping's value is the relationships (dependency edges) it creates between CIs. These relationships drive impact analysis, dependency views, and Event Management impact calculations. The relationship direction (depends on / used by) matters for how impact propagates.
Grouping and dynamic membership
- CMDB groups collect CIs for management and operations.
- Dynamic CI groups define membership by query so the group self-updates as the CMDB changes — the same mechanism that can populate an application service.
- Tags (notably from cloud providers) can drive both discovery scope and service membership.
Data quality
Accurate maps require a healthy CMDB: correct CI identification (so CIs are not duplicated), good reconciliation (so the authoritative source wins on each attribute), and clean class assignment. Poor identification produces duplicate or mismatched CIs and broken maps — which is why CMDB health is treated as a prerequisite to a successful Service Mapping deployment.
Fast-recall — Domain 5
- Service Mapping populates the application service layer of the CMDB, aligned to CSDM.
- Know how CSDM concepts map to CMDB tables; application service is the central technical construct.
- The relationships it creates drive impact analysis and dependency views; direction matters.
- CMDB groups, dynamic CI groups (query-based, self-updating), and tags organize membership.
- CMDB health (identification + reconciliation) is a prerequisite for good maps.
Sample questions from this domain
Three of the 45 in this domain, with the reasoning. The full set is in the question bank.
What does the CMDB Identification and Reconciliation Engine (IRE) primarily prevent?
- A. Duplicate CIs by applying identification rules before insert/update ✓
- B. Event alerts
- C. MID Server failures
- D. Slow discovery
Why: IRE applies identification rules to match incoming data to existing CIs, preventing duplicates. It is not primarily about discovery speed, alerts, or MID Server failures.
In IRE, what is an identification rule?
- A. A defined set of identifier criteria (attributes) used to uniquely match a CI of a given class ✓
- B. A discovery schedule
- C. An event rule
- D. A credential mapping
Why: An identification rule defines the identifier attributes used to uniquely match a CI of a class. It is not a credential mapping, schedule, or event rule.
What is the CI Class Manager used for?
- A. Running Discovery
- B. Managing CMDB classes, their attributes, identification rules, and relationships in one interface ✓
- C. Storing credentials
- D. Sending events
Why: CI Class Manager centralizes management of CMDB classes, attributes, identification/reconciliation rules, and relationships. It does not send events, run Discovery, or store credentials.