SERVICENOW UNIVERSITY • FIVE-COURSE BOOK

See the system.
Then answer the question.

This book follows the five courses in the Data Foundations credential path. Start with the visual model, open the details when a term is unclear, and finish each course with scenario practice.

1CMDB Fundamentals 2CSDM Fundamentals 3Health Deep Dive 4Configure Lab 5Health Lab
SOURCE CONTROL

Nothing important should disappear in a summary

Each source is tracked separately. “Captured” means the material is represented below; “pending lab” is a visible gap, not an implied completion.

COURSE 1

CMDB Fundamentals

Captured

Introduction, Configure, Ingest, Govern, Insight, knowledge checks and simulator task list.

Lesson concepts are mapped to the visual chapters below.
COURSE 2

CSDM Fundamentals

Labs + quiz completed

82 official slides, 6 labs / 87 pages, and the 15-question knowledge check.

The University UI marks CSDM Labs and CSDM Quiz completed; the overall course remains 63% because its video lessons are not marked complete.
COURSE 3

CMDB Health Deep Dive

Assessment captured

All 32 assessment objectives and answer choices; dashboard documentation cross-check.

The video narrative is represented by its tested concepts, not copied as a transcript.
COURSE 4

Configure CMDB Simulator

Executed · 100% passed

All 15 tasks were completed and independently accepted by the official simulator validator.

Exact configuration, IRE output, source precedence and dynamic-reconciliation evidence are captured below.
COURSE 5

CMDB Health Simulator

Executed · 100% passed

All 12 published tasks were completed and independently accepted by the official simulator validator.

Persisted values, counts, scheduled jobs and query results are captured below.
Coverage ruleA compact explanation may hide detail under a disclosure, but it may not delete a tested concept. Any inaccessible lab remains visibly marked until captured.
Open the course-by-course extraction ledger
Course sourceCaptured contentWhere it appearsOpen gap
CMDB Fundamentals — IntroductionCMDB/CSDM, CI, class, attribute, relationship, Asset vs CI, principal/logical CI, foundation data, discoverable data, three pillarsCourse 1 mental model and object/class visualsNone identified
CMDB Fundamentals — ConfigureCI Class Manager, relationships, required/recommended, IRE, identifiers, data source rules, reconciliation, multisource, dynamic reconciliation, reclassificationCourse 1 IRE pipeline + exact-name referenceHands-on simulator screens tracked separately
CMDB Fundamentals — IngestDiscovery phases, Service Mapping, ACC, Service Graph Connectors, IH-ETL, Import Sets, group synchronization, source valuesCourse 1 tool map + CSDM group precedenceNone identified
CMDB Fundamentals — GovernCompleteness/Correctness/Compliance, health scope, duplicates, orphans, stale, remediation, lifecycle, Asset-CI sync, Data ManagerCourse 1 health visual + Course 3 + referenceHealth simulator screens tracked separately
CMDB Fundamentals — InsightQuery Builder, Unified Map, Intelligent Search/NLQ, Data Foundations, product consumptionCourse 1 insight surfacesNone identified
CSDM Fundamentals — 82 slidesCSDM purpose/pillars, six domains, service/product terminology, lifecycle, portfolios, deprecated patterns, implementation approachesCourse 2 domain and object mapsNone identified
CSDM Fundamentals — 6 labs / 87 pagesEnd-to-end model, outcomes, dynamic groups, DPM, CSM/SPM, EA/SPM; official Labs and Quiz items completedCourse 2 six-lab implementation storyNo lab gap; video-only narrative remains a separate course-coverage check
CSDM knowledge check — 15 questionsAll objectives and correct selectionsCourse 2 + CSDM simulator bankNone identified
CMDB Health Deep Dive — 32-question assessmentAll stems/options, tested dashboards, playbooks, jobs, thresholds, group sync, remediation safetyCourse 3 + Govern simulator bankVideo is summarized by tested concepts, not stored as transcript
Configure CMDB SimulatorAll 15 tasks executed; exact class, identifier, dependency, multisource, static reconciliation, Data Refresh and dynamic reconciliation state verifiedCourse 4 + Configuration simulator bankNone identified; official result 100% Passed
CMDB Health SimulatorBlueprint plus all 12 tasks executed; exact rules, counts, jobs, remediation and Query Builder results verifiedCourse 5 + Govern/Insight simulator bankNone identified; official result 100% Passed
START HERE

One mental model for the whole certification

Read this from left to right whenever a scenario feels overloaded.

CONFIGUREDefine the language

Classes, attributes, relationships, identification and source authority.

INGESTBring facts in

Discovery, Service Mapping, ACC, connectors and ETL feed IRE.

GOVERNKeep facts trustworthy

Health, ownership, lifecycle, remediation and Data Manager.

INSIGHTUse the model

Queries, maps, dashboards, impact and operational decisions.

CSDMconnects business intent, services, deployed instances and technical CIs across the entire loop.
1What object?CI, class, source, service, offering or dashboard metric?
2What moment?Before ingest, during IRE, after storage, during health evaluation?
3What decision?Match, authorize update, scope, calculate, remediate or visualize?
4What level?Class default, offering override, individual CI or portfolio?
COURSE 1

CMDB Fundamentals

The complete operating story: model → ingest → govern → insight.

Practice

A CMDB stores managed objects and meaningful relationships

ASSET VIEWserver-017

cost · contract · depreciation · stockroom

same physical thingdifferent lifecycle questions
CI VIEWweb-prod-01

status · owner · relationships · incidents

web-prod-01RunsApacheDepends onorders-db-prodSupportsOnline Shop PROD
Do not merge the ideas: an asset answers financial-lifecycle questions; a CI answers operational/configuration questions. A record can be linked across both views.

Class hierarchy is a family tree

cmdb_ciName · status · owner
HardwareApplicationService
ComputerDatabaseApplication Service
ServerWindows ServerLinux Server
CLASSType of CI

A table in the hierarchy. Child classes inherit parent fields and behavior.

ATTRIBUTEFact about a CI

Name, serial number, OS, owner, lifecycle stage.

RELATIONSHIPMeaningful connection

Depends on::Used by, Runs on::Runs, Contains::Contained by.

PRINCIPAL CLASSOperationally selectable class

Constrains CI selection in consuming processes so users do not browse every technical class.

LOGICAL CIManaged but not physical

Software, a service, or another logical construct can still be a CI when its configuration matters.

FOUNDATION DATAReferenced, not a CMDB relationship

Users, groups, companies, and locations give CIs context but are not stored as CI relationships.

DISCOVERABILITYObserved vs governed

OS/RAM/MAC may be discovered; ownership, warranty, and financial values need authoritative non-discovery sources.

IRE is a controlled border crossing

PAYLOADIncoming objectsource + class + attributes
1IdentifyWhich CI is this?
2Insert gateMay this source create it?
3ReconcileMay this source update each field?
RESULTOne governed CIwith source history
0 matches

Insert only if the data source rule allows it.

1 match

Update only the attributes the source is authorized to change.

2+ matches

Duplicate condition; IRE cannot choose one unique CI.

Identification, reconciliation and multisource — full detail
  • Identification uses stable identifiers. Name or IP alone is often weak; installed applications may need host and installation/configuration path context.
  • Static reconciliation uses source priorities. Lower order means higher priority. Data refresh can let a lower-priority source update a value after the winning source becomes stale.
  • Dynamic reconciliation calculates a winner: First Reported, Most Reported, Last Reported, Largest or Smallest. It overrides static reconciliation for the same attribute.
  • Multisource CMDB / CMDB 360 retains source-specific values in cmdb_multisource_data; rejected values are not simply lost.
  • glide.identification_engine.multisource_enabled is the master capability switch; separate properties cover cmdb_ci and non-CMDB classes.

Choose the ingestion path by the shape of the problem

BOTTOM-UPDiscovery

Broad technical inventory. Scan → Classify → Identify → Explore.

OS, RAM, MAC, processes, devices
TOP-DOWNService Mapping

Start with one service and map the stack that delivers it.

impact and root-cause context
AGENTACC

Lightweight agent-based discovery and near-real-time monitoring.

endpoints and workloads
PACKAGEDService Graph Connector

Supported vendor integration from the Store; CMDB- and IRE-aware.

ready vendor feed
CUSTOMIntegrationHub ETL

Build mappings when no packaged connector fits.

extract · transform · load
LEGACYImport Set

Use CMDBTransformUtil from onBefore to invoke IRE.

never treat direct CMDB write as harmless

Govern asks three different quality questions

TRUSTED CImust pass all three
COMPLETENESSDo we have the fields?

Required + recommended

CORRECTNESSIs the record structurally credible?

Duplicates + orphans + stale

COMPLIANCEDoes it match desired state?

Desired State + scripted audits

Health failureMetric statusRemediation taskRuleWorkflowVerified CI
Govern — tested details that must not be skipped

Correctness

  • Duplicate = multiple records for one real object.
  • Orphan = missing required relationship; there are no baseline orphan rules.
  • Stale uses sys_updated_on; the course example is 60 days.

Reclassification

  • Upgrade: parent → child.
  • Downgrade: child → parent.
  • Switch: another hierarchy branch.
  • Downgrade/switch can lose class-specific data.

Data Manager

  • Retirement, Archiving, Deletion, Attestation, Certification.
  • Archive/delete require a retired or end-of-life CI.
  • De-duplication and reclassification are not Data Manager policy types.

Lifecycle

  • Use Life Cycle Stage + Stage Status for modern CSDM alignment.
  • CI/Asset synchronization uses life_cycle_mapping.
  • Asset and CI keep different lifecycle purposes.

Insight chooses the surface that answers the question

RELATIONSHIP QUERYCMDB Query Builder

Find CIs that match class, attribute and relationship conditions.

TOPOLOGY + WORKUnified Map

Blend service maps and dependency views; inspect incidents and changes.

NATURAL LANGUAGEIntelligent Search / NLQ

Translate a question into CMDB search context.

MODEL ADOPTIONData Foundations

Indicators, priorities, risks and remediation playbooks.

COURSE 2

CSDM Fundamentals

A shared language from business intention to a running service.

Practice
CSDM is guidance and a data model.It is not a SKU, a separate product, a process, a report, or an automatic repair tool.

Six domains: follow the idea until it is consumed

FOUNDATIONWho and where?

Users · groups · companies · locations

IDEATION & STRATEGYWhy invest?

Mission · goals · product ideas · planning

DESIGN & PLANNINGWhat should exist?

Capabilities · business apps · information objects

BUILD & INTEGRATIONWhat do we build?

SDLC components · deployables · digital assets

SERVICE DELIVERYWhat is running?

Service instances · technical services · CIs

SERVICE CONSUMPTIONWhat is received?

Business services · offerings · subscriptions

One Online Shop, seen from every layer

PLANBusiness CapabilitySell Products OnlineBusiness ApplicationOnline ShopInformation ObjectCustomer Order
CONSUMERBusiness ServiceOnline OrderingBusiness OfferingGold · 24×7↓ usesService InstanceOnline Shop PROD
PROVIDERTechnology Mgmt ServiceUnix PlatformTechnology Mgmt OfferingProduction 24×7→ containsDynamic CI GroupProduction Unix servers
RUNNING CIsApplicationApacheServerweb-prod-01Databaseorders-db-prod
Business Applicationlogical portfolio record

All environments, ownership, cost, risk and roadmap. Not a running stack.

Applicationcmdb_ci_appl

Discoverable installed or running software component.

Service Instanceformerly Application Service

One deployed stack/environment with operational dependencies.

Business Serviceconsumer-facing

Operational value delivered to a business consumer.

Technology Mgmt Serviceprovider-facing

Internal technical capability used to support services and instances.

Offeringspecific option

Commitments, region, environment, price, support hours and responsible groups.

Group precedence: specific beats general

CLASS DEFAULTCI Class Manager

Server → Managed by: Server Team

overridden by
SPECIFIC OFFERINGTechnology Mgmt Offering

Production Unix → Unix Support

syncs through
CI POPULATIONDynamic CI Group

query selects exact CIs

to
RESULTUnderlying CIs

Managed by · Support · Change

Why Discovery cannot solve this: a scan can observe OS and RAM; it cannot reliably infer organizational responsibility. CSDM - Sync Group Attributes transfers the governed group values.

The six official labs form one implementation story

LAB 1Build the model

Foundation data → Business Application/Capability/Information Object → Business Service/Offering → Technology Service/Offering → Service Instance.

LAB 2Realize outcomes

Auto-route Incident and Change, inspect Dependency View and Unified Map, trace Event Management root cause, review EA context.

LAB 3Dynamic CI Groups

CMDB Group query → Dynamic CI Group → Technology Offering → groups synchronized by scheduled jobs.

LAB 4Digital Portfolio

Portfolio → Taxonomy Node → Service → Offering → infrastructure. KPIs map, inherit and roll up.

LAB 5CSM + SPM

Sold Product, Product Model, Offering, Account and Case connect customer consumption to service delivery.

LAB 6EA + SPM

Product Idea and Demand extend Planning Item and connect the strategy pipeline to Business Applications.

Lab implementation details and operational outcomes

Lab 1 — creation path

Build groups/locations, Business Application, Capability and Information Object; create Business and Technology Management Services/Offerings; use Application Service Wizard to create and relate the Service Instance.

Lab 2 — routing and impact

Incident uses the CI Support group, with offering context as fallback; Change uses Change group. Dependency View, Unified Map and Event Management consume the service relationships.

Lab 3 — dynamic populations

CMDB Group encoded query → Dynamic CI Group cmdb_ci_query_based_service → Technology Offering. Update Query Based Services refreshes membership; CSDM Data Sync applies groups.

Lab 3 — Change behavior

Selecting a Dynamic CI Group can unpack matching records into Affected CIs; Refresh Impacted Services then recalculates impacted service context.

Lab 4 — DPM

Portfolio → Taxonomy Node → Service → Offering → infrastructure. KPI Group and KPI Mapping support daily collection, inheritance and roll-up.

Labs 5–6 — cross-product model

Sold Product/Product Model link customer consumption to offerings. Product Idea and Demand extend Planning Item and expose the strategy pipeline in Enterprise Architecture.

CSDM lifecycle, portfolios and release-sensitive terminology

Lifecycle

Use Life Cycle Stage and Life Cycle Stage Status. Logical and physical objects use appropriate value sets.

Deprecated patterns

Use_for gives way to Environment; prefer modern lifecycle fields; avoid the base Service class when a Business or Technology Management Service class fits.

TEAMs

Modern responsibility patterns replace older generic cmdb_rel_group approaches. Recognize both old and current labels in questions.

Implementation

Outcome-centric, domain-centric and step-wise approaches are all incremental. CSDM is not an all-at-once migration.

Official lab statusCSDM Labs, Read Me: Before Taking Quiz and CSDM Quiz are marked completed in ServiceNow University. The six-lab, 87-page package is represented above. This does not claim that the entire 5 h 51 min video course is complete.
COURSE 3

CMDB Health Deep Dive

Turn a red indicator into an evidence-based remediation decision.

Practice

Do not start with the fix; read the whole metric

RESULTHow far from target?

Percentage of records meeting the condition.

+
PRIORITYHow important by default?

Foundation-prescribed order of attention.

+
BUSINESS DRIVERWhat matters here?

Internal risk can override the default priority order.

ACTIONChoose the next metric

Open evidence and its Get Well playbook.

0–<50%Red
50–90%Yellow
>90%Green

Exam nuance: with equal business drivers, dashboard priority wins even if another metric has a lower result. A stronger internal business driver is a valid reason to reverse that order.

Every Get Well playbook tells the same causal story

UPSTREAM CAUSEWhy did the issue appear?

No naming standard, duplicate source, direct writes, missing ownership, no class review.

METRICWhat can be measured?

Unique Locations, stale CIs, custom CMDB tables, dynamic groups without CMDB Group.

CONSEQUENCEWhat breaks downstream?

Wrong routing, poor binding, slower MTTR, unsafe changes, low trust.

REMEDIATIONWhat changes safely?

Inspect records, use guidance, test scripts, record rollback, verify the metric again.

High-yield playbooks from the official assessment

UNIQUE LOCATIONSOpen duplicate records from the metric

Use hierarchical, clear and unique names; populate Full name; maintain one authoritative source.

INCIDENTS REFERENCING A CIImprove selection and auto-population

Reference qualifier and an appropriate business rule reduce empty or invalid CI values.

CUSTOM u_cmdb_ci* TABLESGovern class creation

Upstream causes: no class review and no CMDB customization governance.

DUPLICATE CIsRestore one operational truth

Improves CI selection/binding and removes confusing duplicate rows.

STALE CIsRefresh or retire evidence

Fresh data supports accurate analysis and better decisions.

DYNAMIC CI GROUP + CMDB GROUPMake population reusable

Supports affected-CI population and safer patch/change execution.

OFFERING GROUPSPopulate Managed by, Support, Change

Ownership becomes discoverable; routing and operational accountability improve.

HEALTH DASHBOARD ENABLEDMeasure continuously

Less manual validation and greater trust in CMDB data.

CMDB Data Foundations and CSDM Data Foundations are not the same dashboard

CMDB DATA FOUNDATIONSQuality and operating practices

Best Practices · Customizations · Data Management Practices · ITSM Processes

Immediate refresh: CMDB Get Well Metric Collection + CMDB Data Foundations PA Metric Collection
CSDM DATA FOUNDATIONSModel adoption and maturity

Foundation · Crawl · Walk · Run · Fly

Indicators connect CSDM relationships and product outcomes to remediation guidance.
REMEDIATION SCRIPTDevelopment/test firstRecord for rollbackRun on a scoped setVerify metric + records
EXAM-PRECISION LAYER

Exact names worth recognizing

These names, scopes and release-sensitive distinctions are the layer that generic platform experience may not supply.

Properties

glide.required.attribute.enabledIRE enforcement of required attributes; disabling it relaxes enforcement.
glide.identification_engine.multisource_enabledMaster switch for Multisource CMDB / CMDB 360.
glide.identification_engine.multisource_cmdb_ci_enabledSource values for classes extending cmdb_ci.
glide.identification_engine.multisource_non_cmdb_ci_enabledSource values for non-CMDB classes. Do not lose the word non.
glide.identification_engine.skip_duplicatesCourse default: true; controls processing when IRE encounters multiple matches.
glide.identification_engine.skip_duplicates.thresholdCourse default: 5; limits duplicate matches processed in this mode.
glide.class.upgrade.enabledGlobal automatic parent → child reclassification.
glide.class.downgrade.enabledGlobal automatic child → parent reclassification.
glide.class.switch.enabledGlobal automatic move to another hierarchy branch.
glide.identification_engine.update_without_upgrade_enabledAllow attribute update while blocking upgrade.
glide.identification_engine.update_without_downgrade_enabledAllow attribute update while blocking downgrade.
glide.identification_engine.update_without_switch_enabledAllow attribute update while blocking switch.
glide.cmdb.query.nlq.activatedActivates natural-language CMDB query capability.

Jobs, rules, tables and roles

CMDB Health Dashboard - Completeness Score CalculationRecalculates Completeness.
CMDB Get Well Metric CollectionRefreshes Get Well metric data.
CMDB Data Foundations PA Metric CollectionRefreshes CMDB Data Foundations reporting.
Update Query Based ServicesRefreshes query-based / Dynamic CI Group populations.
CSDM Data SyncScheduled group-value synchronization for the CSDM pattern.
CSDM - Sync Group AttributesBusiness rule associated with Managed by, Support and Change groups.
cmdb_health_metric_statusHealth metric status records.
cmdb_multisource_dataSource-specific values used by Multisource CMDB.
life_cycle_mappingMappings used for CI/Asset lifecycle synchronization.
data_manager_admin / data_manager_userCMDB Data Manager roles in the course.

CSDM class names

cmdb_ci_business_appBusiness Application: logical portfolio/planning record; not a deployed stack.
cmdb_ci_applApplication: discoverable installed/running code or application component.
cmdb_ci_service_autoService Instance / former Application Service: one deployed operational stack.
cmdb_ci_serviceBusiness Service: operational consumer-facing service.
cmdb_ci_service_technicalTechnology Management Service: provider-focused technical capability.
service_offeringSpecific consumable option beneath a service, including commitments and group fields.
cmdb_ci_query_based_serviceDynamic CI Group: query-defined operational CI population.
sn_cmdb_ws_nlq_sample_searchSample NLQ searches; companion table configuration uses sn_cmdb_ws_nlq_sample_search_table.

Old label → current label

Application ServiceService Instance
Technical ServiceTechnology Management Service
Technical Service OfferingTechnology Management Offering
Assignment group on offeringChange group
CMDB WorkspaceService Graph Workspace
Use_forEnvironment
Lower reconciliation ordermeans higher source priority.
Reconciliationdoes not decide insertion.
Data Refreshaffects static, not dynamic reconciliation.
Offering-level groupoverrides a broader class default.
Overall healthcan be lower because a CI must pass all selected checks.
Health inclusion rule “is a”includes the selected class hierarchy.
COURSE 4

Configure CMDB Simulator

One practical chain, not fifteen unrelated clicks.

Practice
SETUPValidate MID Server
MODELCreate a class
IDENTIFYTest CI identity
OBSERVEEnable multisource
CONTROLReconcile sources
ADAPTRefresh + dynamic winner
  1. 1Validate the MID ServerProve that the integration execution point is ready before testing data behavior.
  2. 2Create the new classPut the object in the correct hierarchy and inherit the right attributes.
  3. 3–6Test identification under variationBaseline identity, version upgrade, a second Mongoose app on the same host, then a second discovery source.
  4. 7–8Enable and verify Multisource CMDBRetain source-specific values and confirm which source value becomes the CI value.
  5. 9–11Configure and test static reconciliationDefine source authority, then test ServiceNow and LANDesk behavior separately.
  6. 12–13Create and test Data RefreshAllow a lower-priority source only when the preferred value is stale.
  7. 14–15Create and test Dynamic ReconciliationChoose the winner from reported values rather than a fixed source order.
Exact class and IRE design verified in the lab

Mongoose Web Server configuration

u_cmdb_ci_mongoose_web_serverChild of cmdb_ci_web_server; display name and icon are Mongoose Web Server / Web Server.
Mongoose Web Server ruleDependent identification rule, active, priority 100.
sys_class_name + running_process_commandIdentifier criteria. Version is deliberately excluded, so an upgrade updates the existing installation.
Runs on::Runs → HardwareInherited dependent relationship that supplies the host context.
Same command, new versionUPDATE the existing application CI.
Different command pathINSERT a second application CI on the same host.
Same server, second sourceHardware identifier matches by Name; no duplicate server is created.
Second identical payloadApplication, host and relationship all return NO_CHANGE.
Source control chain verified in the lab
  1. 1Enable source historyglide.identification_engine.multisource_enabled = true. CMDB 360 stores source-specific values in cmdb_multisource_data.
  2. 2Apply static precedenceWindows Server rule applies to all attributes: ServiceNow[1] outranks LANDesk[2]. Lower numeric order means higher authority.
  3. 3Observe a rejected attributeAfter ServiceNow set RAM to 2048, a LANDesk payload reporting 4096 returned maskedAttributes: ["ram"]. The payload was identified, but RAM remained protected.
  4. 4Permit a stale-value exceptionData Refresh rule: ServiceNow, effective duration 7 days. LANDesk then updated the pre-seeded stale SPLI-WIN-SERVER RAM to 4096 without becoming permanently higher priority.
  5. 5Override static order for one attributeDynamic rule Largest Value on RAM. A later ServiceNow payload reporting 2048 triggered DYNAMIC_RECONCILIATION; the CI displayed 4096 from the stored LANDesk value.
Discovery source is not the winning-value explanation

In the final task the CI can show Discovery source = ServiceNow because ServiceNow submitted the latest accepted payload, while RAM = 4096 because Dynamic Reconciliation selected the largest source-specific value. Use cmdb_datasource_last_update and CMDB 360 data to explain field authority and source history.

Live verificationAll fifteen official tasks reached Task Result: Success; the simulator reported 100% Passed and awarded the Configure the CMDB micro-certification.
COURSE 5

CMDB Health Simulator

Exact lab logic: configure → calculate → inspect evidence → remediate → recalculate.

Practice
ASSESSMENT60 minutes · 13 graded tasksEach task is graded independently; required score: 80%.
COURSE PRACTICE12 published tasksThe practice list and the certification assessment task count are not the same.
RETAKESUnlimitedBlueprint states that the simulator can be retaken as needed.
50%Health Dashboard ConfigurationActivation, CMDB Group, schedules, Completeness, Compliance and Correctness.
10%CI ReclassificationSystem properties controlling automatic class changes.
20%Query BuilderSimple CMDB query and query joined to a non-CMDB table.
20%CMDB RemediationDuplicate remediation and remediation configuration.
ConfigureScope, rule, audit, schedule or query
CalculateRun the correct score job
InspectValidate records, numerator and denominator
RemediatePreserve valid data and relationships
RecalculateProve both record state and score
Dashboard configuration · tasks 1–4
  1. 1Activate and execute the three Health jobsCompleteness Score Calculation, Compliance Score Calculation, Correctness Score Calculation. Verify Active, nine complete rows in cmdb_health_metric_status, and dashboard scores. Lab scope: 3.01K CIs.
  2. 2Create a Health-type CMDB GroupName: Unix and Windows Servers. Combine AIX, HPUX, Solaris and Windows Server classes with encoded queries/conditions; sample scope is 146 CIs. Re-run all three score jobs.
  3. 3Schedule all three Scorecard jobsActive, twice daily, at 07:00 and 19:00, starting today. A calculated score is only as current as the last successful job.
  4. 4Configure Server recommended fieldsLocation, Owned by, Support group. Run Completeness Scorecard; the lab verifies 110/146 CIs missing at least one recommended value.
Compliance and correctness · tasks 5–9
  1. 5Build a desired-state audit chainFilter scopes cmdb_ci_win_server; template requires Windows 2012 R2 Standard, 2016 Standard or 2019 Datacenter; audit references the template and is executed. Scope → pass criteria → run.
  2. 6Expose only relevant audit resultsDeactivate base-system audits, keep the custom Windows Audit active, run Compliance Score Calculation. Sample result: 54/123 failed, therefore 56% compliant; after duplicate remediation the denominator can be 122.
  3. 7Create an Email Server orphan ruleAn Email Server is orphaned when it lacks Runs on::Runs to cmdb_ci_server. Run Correctness Scorecard; sample evidence is 7/11 orphaned.
  4. 8Create class-specific staleness rulesWindows Server: 7 days; Unix Server: 14 days. The displayed Healthy value is the number of non-stale CIs, not the number of stale CIs.
  5. 9Remediate a duplicate without data lossKeep the oldest OWA-SD-01 as main CI; copy Cost center, Company and Assigned to from the duplicate; merge all relationships; then delete the duplicate. Re-run Correctness and verify both the remaining record and the closed-complete task.
Reclassification and Query Builder · tasks 10–12
  1. 10Force manual review of every reclassificationSet glide.class.upgrade.enabled, glide.class.downgrade.enabled and glide.class.switch.enabled to false, so upgrade, downgrade and switch produce review tasks instead of being applied automatically.
  2. 11Build and independently validate a simple querySaved query returns only Windows 2012 R2 Standard, 2016 Standard and 2019 Datacenter servers. Run it, note the count, store the count in Description, and save again.
  3. 12Connect CMDB and non-CMDB dataQuery Configuration Item where Owned by is empty, connected to Incident where Priority is 1 - Critical. Results must satisfy both sides of the relationship.
Why the validator can fail after correct configuration

The simulator validates persisted configuration and recalculated evidence. Saving a rule is not enough: run the named job, wait for completion, refresh the metric if necessary, and verify both the scoped records and the displayed score.

Live verificationAll twelve published tasks reached Task Result: Success; the simulator reported 100% Passed and awarded the CMDB Health micro-certification. Counts above are the observed lab evidence, not generic production defaults.
FAST RECALL

Thirty-second decision board

Use this before a drill, not as a replacement for the chapters.

Existing or new CI?Identification
Who may update the field?Reconciliation
Source may update but not insert?Data source rule
Broad inventory?Discovery
One service dependency map?Service Mapping
Packaged vendor feed?Service Graph Connector
Custom transformation?IntegrationHub ETL
Missing fields?Completeness
Duplicate/orphan/stale?Correctness
Desired state?Compliance
Portfolio application?Business Application
Deployed stack?Service Instance
Consumer value?Business Service
Provider capability?Technology Mgmt Service
Specific service option?Offering
Specific CI population?Dynamic CI Group