CIS IT Service Management - ServiceNow Practice Test 2026
ITSM is core ServiceNow language. Incident, problem, change, request, SLA, knowledge, and service catalog all show up. These 198 questions are a tight bank for sharpening the fundamentals.
Price is shown at checkout on Udemy. 30-day money-back guarantee.
Start practicing nowBefore you start: CIS-DF is a prerequisite for this exam from Jan 1, 2027. See the CIS-DF practice test.
Next step: CIS Data Foundations / CSDM.
What's included
- 198 questions covering incident, problem, change, request, and SLA fundamentals
- Every answer links to the official ServiceNow documentation so you can verify it yourself.
- Wrong answers are explained too. You see why each option fails, not just which one wins.
- Current for the Zurich release and the 2026 exam blueprint.
- Lifetime access. When new questions are added, you get them at no extra charge.
- Written by an author who passed all 18 ServiceNow exams on the first attempt.
- 30-day money-back guarantee through Udemy.
15 Free Preview Questions
Answer 5 questions free. Enter your email to continue through question 15. The full course has 198 questions on Udemy.
- Asn_business_user
- Bsn_problem_read
- Csn_service_owner
- Dsn_problem_business_user
- Eproblem_write
Show full explanation
Correct Answer
B - sn_problem_read
Source
ServiceNow Zurich Documentation - Problem Management Roles
Expert Explanation
The ITSM roles plugin installs several granular roles for each ITSM process. For Problem Management, the sn_problem_read role grants read-only access to problem records, tasks, and related lists. This is the right fit when business users need visibility into problems affecting their products without the ability to modify investigation data.
Why the Others Are Wrong
sn_business_user is too generic and not problem-specific. sn_service_owner relates to service ownership, not problem viewing. sn_problem_business_user is not a valid out-of-box role. problem_write grants edit access, which exceeds the stated requirement of view-only access.
Memory Tip
Think "read" in the role name - the customer wants to "read" (view) problem records, so the role is sn_problem_read.
Real-World Example
A product manager needs to check which open problems affect the CRM application. With sn_problem_read, they can view problem records and run reports but cannot accidentally change the state or reassign the problem to a different group.
- AIf 7 days has passed, since the Problem was closed, it cannot be re-opened
- BProblem Manager clicks Re-Analyze on the Problem record
- CProblem Assignee clicks Re-Open on the Problem record
- DAdministrator clicks Re-Open on the Problem Record
Show full explanation
Correct Answer
B - Problem Manager clicks Re-Analyze on the Problem record
Source
ServiceNow Zurich Documentation - Problem Management Process
Expert Explanation
ServiceNow Problem Management includes a Re-Analyze UI action that allows the Problem Manager to reopen a closed investigation. This is distinct from a simple Re-Open because it specifically signals that a new round of root cause analysis is needed. The action transitions the problem back to an appropriate investigation state.
Why the Others Are Wrong
There is no 7-day lockout on closed problems. Re-Open is not the designated action for revisiting a closed investigation - Re-Analyze is the purpose-built action. The workflow does not require an Administrator; the Problem Manager role has the authority to trigger Re-Analyze.
Memory Tip
The scenario says "re-visit the root cause analysis" - the key word is "analysis." Match it to the Re-Analyze action. Re-Analyze = resume the analysis.
Real-World Example
A known error for intermittent VPN drops was closed because the team accepted the risk of using a workaround. Two weeks later, the issue frequency triples. The Problem Manager clicks Re-Analyze to reopen the investigation and pursue a permanent fix.
- ASLA definition record
- BDefault SLA flow
- CSLA Properties application
- DSLA trigger conditions
Show full explanation
Correct Answer
B - Default SLA flow
Source
ServiceNow Zurich Documentation - SLA Flow
Expert Explanation
In ServiceNow, SLA breach warning notifications are controlled by the SLA flow (or SLA workflow in pre-Flow Designer implementations). The flow defines percentage-based or duration-based thresholds that trigger notifications before the actual breach occurs. For example, a flow might send a warning at 50% elapsed and another at 75% elapsed.
Why the Others Are Wrong
The SLA definition record defines what the SLA measures and its target, but the notification timing logic lives in the attached flow. SLA Properties control global settings, not per-SLA warning timeframes. SLA trigger conditions is not a distinct configuration area for this purpose.
Memory Tip
Think of SLA Definition as the "what" (target, conditions) and SLA Flow as the "when" (warning timing, notification triggers). Warning notifications = Flow.
Real-World Example
An IT team wants a warning email when a P1 incident SLA reaches 75% of its 4-hour target. The admin opens the default SLA flow and configures the percentage threshold and notification action at the 75% stage.
- AThey are resolved exclusively through manual processes.
- BThey only affect a single user.
- CThey are incidents of high impact and urgency affecting a large number of users.
- DThey can only be created manually.
Show full explanation
Correct Answer
C - They are incidents of high impact and urgency affecting a large number of users.
Source
ServiceNow Zurich Documentation - Major Incident Management
Expert Explanation
Major Incidents represent the most severe category of incidents in ITSM. They are characterized by high impact (affecting many users or critical services) and high urgency (requiring immediate attention). ServiceNow provides a dedicated Major Incident Management process that includes a separate communication plan, a major incident manager role, and accelerated resolution workflows.
Why the Others Are Wrong
Major incidents leverage automated workflows and structured processes - they are not resolved exclusively through manual effort. They by definition affect many users, not just one. They can be triggered automatically through rules or promoted from existing incidents, not only created manually.
Memory Tip
Major = Many users. High impact + high urgency + many affected = Major Incident. Think of a company-wide email outage - that is "major."
Real-World Example
The corporate email system goes down during business hours, affecting 5,000 employees. This is flagged as a Major Incident, triggering an automatic bridge call, executive notifications, and a dedicated incident commander to coordinate the response.
- APopulate Assignment Group based on CI/SO
- BAuto-populate ITSM Assignment Groups
- CITSM Assignment Lookup Rule
- DAutomatic Assignment for ITSM
Show full explanation
Correct Answer
A - Populate Assignment Group based on CI/SO
Source
ServiceNow Zurich Documentation - Incident Management Business Rules
Expert Explanation
ServiceNow ships a business rule called "Populate Assignment Group based on CI/SO" that fires on Incident, Problem, and Change tables. When a user selects a Configuration Item or Service Offering, this rule looks up the associated support group and auto-populates the Assignment Group field. This reduces manual effort and ensures tickets are routed to the correct team.
Why the Others Are Wrong
The other options are plausible-sounding names but do not match the actual out-of-box business rule. ServiceNow named this rule to clearly indicate its logic: it populates the assignment group based on the Configuration Item (CI) or Service Offering (SO).
Memory Tip
Remember "CI/SO" in the name. The assignment is populated based on CI (Configuration Item) or SO (Service Offering). CI/SO = the key to finding the right group.
Real-World Example
A user logs an incident and selects the "SAP Production Server" CI. The business rule fires, looks up that CI's support group (SAP Basis Team), and automatically fills the Assignment Group field - no manual routing needed.
- AState Transition Models
- BState Flows
- CWorkflows 2.0
- DConditional Change Models
Show full explanation
Correct Answer
A - State Transition Models
Source
ServiceNow Zurich Documentation - Change Management State Model
Expert Explanation
State Transition Models let organizations define different processing paths for different types of changes. A standard change might skip the CAB approval state, while an emergency change follows an expedited path. Each model defines which states are available, the valid transitions between them, and the conditions under which each transition is allowed. This is the "fit for purpose" approach referenced in the question.
Why the Others Are Wrong
State Flows, Workflows 2.0, and Conditional Change Models are not real ServiceNow feature names. The platform uses the term "State Transition Models" for this capability in Change Management.
Memory Tip
"Fit for purpose" = different paths for different change types. State Transition Models define those paths. Think: States + Transitions + Conditions = Model.
Real-World Example
A company configures three state transition models: one for standard changes (auto-approved), one for normal changes (requires CAB review), and one for emergency changes (post-implementation review only). Each model defines the allowed state transitions based on the change type and risk level.
- AThe agent is prompted to select the Assignment group
- BThe Assignment group field is populated with agent’s user group
- CAn error is displayed indicating the Assignment group field must be populated before executing the Assign to me UI action
- DThe Assignment group field remains empty
Show full explanation
Correct Answer
B - The Assignment group field is populated with agent's user group
Source
ServiceNow Zurich Documentation - Assign to Me
Expert Explanation
The "Assign to me" UI action sets the Assigned to field to the current user. When the Assignment Group is empty and the agent belongs to exactly one user group, ServiceNow auto-fills the Assignment Group with that group. If the agent belongs to multiple groups, the behavior differs - the agent may be prompted to choose. But with a single group, the platform resolves the assignment automatically.
Why the Others Are Wrong
No prompt appears because the system can determine the group unambiguously (single group membership). No error is thrown - this is expected behavior. The field does not remain empty because ServiceNow fills it to ensure proper group assignment.
Memory Tip
One agent, one group = auto-fill. If there is only one option, ServiceNow picks it for you. Multiple groups = prompt needed, single group = automatic.
Real-World Example
A help desk analyst belongs only to the "Service Desk" group. They see an unassigned incident and click "Assign to me." The Assigned to field shows their name and the Assignment Group automatically fills with "Service Desk."
- ACreation and Classification
- BInvestigation and Diagnosis
- CResolution and Closure
- DPrioritization and Scheduling
- EFeedback and Improvement
Show full explanation
Correct Answer
A - Creation and Classification, B - Investigation and Diagnosis, C - Resolution and Closure
Source
ServiceNow Zurich Documentation - Incident Management Process
Expert Explanation
The Incident Management lifecycle in ServiceNow follows three main stages: Creation and Classification (logging and categorizing), Investigation and Diagnosis (finding the cause or workaround), and Resolution and Closure (applying the fix and closing the ticket). These stages map to the ITIL incident management process and align with the incident state model in the platform.
Why the Others Are Wrong
Prioritization and Scheduling is not a standalone stage - prioritization happens during Creation and Classification. Feedback and Improvement is a continual improvement activity, not a defined stage in the incident lifecycle.
Memory Tip
Think of the three C's in order: Create it, Check it (investigate), Close it. C-C-C = Creation, (Investigation as) Checking, Closure.
Real-World Example
A user reports a broken printer. Stage 1 (Creation and Classification): the ticket is logged as a Hardware/Printer issue with medium impact. Stage 2 (Investigation and Diagnosis): the technician discovers a firmware bug. Stage 3 (Resolution and Closure): the firmware is updated, the user confirms it works, and the incident is closed.
- AExecution Plans
- BContent Items
- CCatalog Items
- DRecord Producers
Show full explanation
Correct Answer
D - Record Producers
Source
ServiceNow Zurich Documentation - Record Producers
Expert Explanation
Record Producers are a Service Catalog capability that generates records on any target table based on user input. Unlike standard Catalog Items (which create RITMs), Record Producers create records directly on tables like Incident, Problem, or custom tables. This makes them ideal for end-user inquiries that should result in task-based records rather than service requests.
Why the Others Are Wrong
Execution Plans handle post-submission fulfillment tasks. Content Items are informational only and produce no records. Catalog Items create RITMs and catalog tasks, not direct task-based records on other tables.
Memory Tip
Record Producers "produce records" on target tables. The name tells you exactly what they do. Inquiry from user = record produced on a task table.
Real-World Example
An IT department wants end users to report network issues through the Service Catalog. They create a Record Producer that collects the user's location, symptoms, and urgency, then generates an Incident record on the Incident table with those details pre-filled.
- AMake sure Notification requirements and test plans are in the project scope from the start
- BGet input from Marketing department, regarding format of customer/caller facing notifications
- CUse templates to ensure consistency and ease of configuration
- DUse incident.itil.role template as the master template to build all other ITSM templates
- EWhen possible, maximize the quantity of email updates to customers
Show full explanation
Correct Answer
A - Make sure Notification requirements and test plans are in the project scope from the start, B - Get input from Marketing department, regarding format of customer/caller facing notifications, C - Use templates to ensure consistency and ease of configuration
Source
ServiceNow Zurich Documentation - ITSM Notifications
Expert Explanation
Notification best practices in ServiceNow implementations include scoping requirements early, involving stakeholders like Marketing for brand-consistent messaging, and using templates for maintainability. These practices ensure notifications are professional, tested, and sustainable. Over-notifying users should be avoided as it causes notification fatigue.
Why the Others Are Wrong
incident.itil.role is not a valid notification template name in ServiceNow. Maximizing notification quantity contradicts best practices - the goal is to send the right notifications to the right people, not to flood inboxes.
Memory Tip
Good notifications follow the "P-M-T" approach: Plan them in scope (P), get Marketing input (M), and use Templates (T). Avoid flooding inboxes.
Real-World Example
During a ServiceNow implementation, the project team includes notification requirements in the design phase, works with Marketing to create branded email templates, and tests all notifications in a sub-production instance before deploying to production.
- AChange requests meeting different conditions, like Risk level or Type
- BChange requests planned within a certain date range
- CUse any of the options on the Agenda Criteria Tab
- DChange requests for a certain Change Flow Definition
Show full explanation
Correct Answer
A - Change requests meeting different conditions, like Risk level or Type, B - Change requests planned within a certain date range
Source
ServiceNow Zurich Documentation - CAB Workbench
Expert Explanation
The CAB (Change Advisory Board) workbench provides two main ways to identify changes for a meeting agenda. First, condition-based filtering lets the CAB manager select changes based on attributes like risk level, change type, or category. Second, date range filtering identifies changes planned within a specific timeframe. Together, these filters help the CAB manager build a focused meeting agenda.
Why the Others Are Wrong
"Use any of the options on the Agenda Criteria Tab" is too vague and not entirely accurate. Change Flow Definition is not a standard filter criterion in the CAB workbench.
Memory Tip
CAB meetings care about two things: "What kind of change?" (conditions like risk/type) and "When is it happening?" (date range). Conditions + Dates = CAB agenda criteria.
Real-World Example
The CAB manager prepares for next week's meeting by filtering for all Normal changes with High risk planned between Monday and Friday. This surfaces 12 changes that need board discussion, while low-risk standard changes are excluded.
- AService Portal
- BService Dashboard
- CService Map
- DService One Stop Shop
- EService Catalog
Show full explanation
Correct Answer
E - Service Catalog
Source
ServiceNow Zurich Documentation - Service Catalog Management
Expert Explanation
The Service Catalog is the centralized repository of all services an organization offers. It contains structured information about each service including what is delivered, available options, pricing, expected delivery timelines, and performance targets (SLAs). It serves both internal employees and external customers as the single source of truth for available services.
Why the Others Are Wrong
Service Portal is the delivery channel, not the content repository. Service Dashboard shows analytics, not service details. Service Map shows CI relationships. Service One Stop Shop is not a standard ServiceNow concept.
Memory Tip
Think of a shopping catalog - it lists products (services), their options, and prices. The Service Catalog does exactly that for IT and business services.
Real-World Example
An employee browses the Service Catalog and finds "New Laptop Request" with options for standard or high-performance models, prices for each, expected delivery in 3 business days, and a description of what is included (setup, software, accessories).
- AConflict with Assignee Shift Schedule
- BConflict with Blackout Schedule
- CConflict with Company Holiday Schedule
- DAnother change for the same CI, at the same time
- EConflict with Maintenance Window
Show full explanation
Correct Answer
B - Conflict with Blackout Schedule, D - Another change for the same CI, at the same time, E - Conflict with Maintenance Window
Source
ServiceNow Zurich Documentation - Change Conflict Detection
Expert Explanation
ServiceNow Change Management automatically detects three types of scheduling conflicts: blackout schedules (periods when changes are prohibited), overlapping changes for the same CI (two changes targeting the same component at the same time), and maintenance window conflicts (changes scheduled outside approved maintenance periods). These checks help prevent unplanned outages and change collisions.
Why the Others Are Wrong
Assignee Shift Schedule is not part of automatic conflict detection - the system does not cross-reference individual work schedules. Company Holiday Schedule is also not checked automatically by the change conflict engine.
Memory Tip
Remember "B-C-M" - Blackout, CI overlap, Maintenance window. These are the three automatic conflict checks. Shift schedules and holidays are HR concerns, not change conflicts.
Real-World Example
A network engineer schedules a router firmware upgrade during a blackout window (month-end freeze). The system flags a blackout conflict. They also discover another team has a change planned for the same router - a CI overlap conflict. Both must be resolved before the change can proceed.
- Acatalog_admin
- Bsc_catalog_admin
- Ccatalog_editor
- Dsn_catalog_homepage_write
- Eadmin
Show full explanation
Correct Answer
A - catalog_admin, E - admin
Source
ServiceNow Zurich Documentation - Service Catalog Roles
Expert Explanation
Modifying the Service Catalog home page - adding, removing, and rearranging categories - requires either the catalog_admin role or the admin role. catalog_admin provides full catalog administration capabilities, while admin has unrestricted platform access. Other roles like catalog_editor can manage items but cannot restructure the catalog home page layout.
Why the Others Are Wrong
sc_catalog_admin and sn_catalog_homepage_write are not valid out-of-box roles. catalog_editor can edit catalog content but lacks permission to modify the home page layout and category arrangement.
Memory Tip
For catalog home page changes, you need "admin" in the role name - either catalog_admin (specific) or admin (global). catalog_editor can edit items but not the home page structure.
Real-World Example
The IT service manager wants to reorganize the Service Catalog to feature "Hardware Requests" prominently. A user with the catalog_admin role opens the catalog home page editor, moves the Hardware category to the top, and removes an outdated "Legacy Systems" category.
- A104
- B"Fix in Progress"
- CProblemState.STATES.FIX_IN_PROGRESS
- D104.ProblemState.STATES.FIX_IN_PROGRESS
Show full explanation
Correct Answer
C - ProblemState.STATES.FIX_IN_PROGRESS
Source
ServiceNow Zurich Documentation - Problem Management States
Expert Explanation
When scripting state transitions in ServiceNow, best practice is to use state constants rather than numeric values or string labels. Constants like ProblemState.STATES.FIX_IN_PROGRESS are upgrade-safe, self-documenting, and maintained by the platform. If the underlying numeric value changes in a future release, scripts using constants continue to work without modification.
Why the Others Are Wrong
The numeric value 104 is fragile and can change between releases. The label "Fix in Progress" can be customized or localized, breaking scripts that depend on it. The combined format 104.ProblemState.STATES.FIX_IN_PROGRESS is invalid JavaScript/GlideScript syntax.
Memory Tip
Constants are "constant" - they do not change across upgrades. Always use the CONSTANT over numbers or labels. Think: Constants = Consistent = Correct choice for scripts.
Real-World Example
A developer writes a script to require a "Fix Group" field before moving out of Fix in Progress. Using ProblemState.STATES.FIX_IN_PROGRESS ensures the script survives platform upgrades, unlike hard-coding 104, which could silently break if ServiceNow remaps the value.
Free exam updates. No spam. Unsubscribe anytime.
Prefer to skip the email? Get all 198 questions on Udemy. 30-day money-back guarantee.
You scored 0/15 on the 15-question preview.
The full course keeps the same answer breakdown style across all 198 questions.
A failed exam attempt costs $225 to retake.
Many students also study:
Compare all 18 practice tests, or use the cert quiz to plan what to study next.
Common questions
How many questions are in the full ITSM practice test?
The full course has 198 questions on Udemy. Every answer option has its own explanation, and the explanations link to official ServiceNow documentation.
Is there a refund if the course is not right for me?
Yes. Udemy courses come with a 30-day money-back guarantee.
Will this practice test guarantee I pass?
No. Practice tests show you where you are weak. They do not replace hands-on work, so pair them with a free ServiceNow Personal Developer Instance.
How much does the real ITSM exam cost?
The exam costs $450 for a first attempt and $225 for a retake. Fees can change, so check ServiceNow University before you register.
Do I need CIS-DF before ITSM?
Yes. From January 1, 2027 you cannot register for this exam without CIS-DF. If you already hold this certification, you must pass CIS-DF by December 31, 2026. See the CIS-DF practice test.
Which certification should I take first?
Most people start with CSA. If you are unsure, take the 2-minute recommendation quiz or read the certification path guide.
Read the full ITSM study guide for domain weights, a study plan, and common mistakes.
Next step after ITSM: CIS Data Foundations / CSDM. Not the right exam? Take the 2-minute quiz or compare all 18.
Browse all 18 practice tests →