ServiceNow CIS-ITSM study plan

Map the ServiceNow ITSM data model by drawing the relationships among Incident, Problem, Change, Request, and CI records

Configure an Incident record end-to-end in a personal developer instance, including category, subcategory, assignment group, and assignment rules

Explain the difference between incident states, impact/urgency, and priority calculation, and state the priority matrix values from memory

Build one assignment rule and one business rule and describe in writing when each should be used instead of the other

Configure and test a major incident candidate workflow, including promotion and demotion logic

Set up at least two SLA definitions that attach to Incident and verify which one wins when both apply

Demonstrate the Incident to Problem and Incident to Change escalation paths and record which fields carry over

Write out the difference between the incident state model on Incident, Incident Task, and the Service Desk call record

Diagram the change lifecycle from New through Review, Authorize, Scheduled, Implement, Review, and Closed, noting which transitions are gated by approvals

Configure a standard, normal, and emergency change model and document which fields each model requires or locks

Build one change approval workflow using an approval policy and verify it against a conflicting approval rule

Explain how the change schedule, CAB workbench, and conflict detection interact, and identify what triggers a conflict

Identify the CI classes in the CMDB class hierarchy and explain which class a server, database, application service, and business service each belong to

Create a CI and populate it through the Identification and Reconciliation Engine (IRE) using a test data source and import set

Demonstrate one reconciliation rule (for example, a precedence or merge rule) and record the outcome on a duplicate CI

Explain the purpose of CMDB health dashboards, CI relations, and the difference between a depend on and a used by relationship

Run a Problem record from Create through Root Cause Analysis, Fix, and Close, capturing the required fields at each state

Create one known error and link it to an incident, then verify the known error surfaces during incident resolution

Configure a problem task and describe when a problem task is preferable to a work note on the problem record

Compare the reactive, proactive, and problem-based change paths and state which one closes a problem as Fixed by Change

Create a knowledge base, an article, and a workflow that moves the article from Draft through Review to Published

Configure user criteria and a can-read/can-contribute rule and verify visibility with two different test users

Link a published article to a catalog item and to an incident, and confirm the article appears in the relevant search context

Explain article versioning, feedback, and the retirement/expiration process and set an expiration date on a sample article

Build a catalog item with variables, a variable set, and a UI policy, then submit it and trace the resulting request, requested item, and catalog tasks

Configure a record producer that creates an incident and one that creates a request, and state when each is appropriate

Create an SLA definition with a schedule, a pause condition, and a workflow, and verify the SLA attaches and pauses as designed

Differentiate SLAs, OLAs, and underpinning contracts and describe how an SLA breach escalation is triggered

Take two full-length timed practice exams and review every missed item back to its source domain

Rework your weakest three domains by rebuilding the associated records from scratch without notes

Recite the priority matrix, change state model, and CMDB class hierarchy from memory

Build a one-page cheat sheet of the field names and state transitions you missed most often