A Discovery schedule that runs all night and still returns bad data is the exact problem this credential is built around: devices that never get classified, the same server arriving twice under two names, patterns that stop at the connection step. The ServiceNow CIS-Discovery exam asks whether you can trace that back to a cause and fix it, across 60 questions in 90 minutes.

CIS-Discovery, exam code CIS-DISCO, is the ServiceNow Certified Implementation Specialist - Discovery credential. It sits inside IT Operations Management and it is deliberately practical. The questions describe a schedule, an error message, a pattern step or a MID Server condition, and ask what you would change. Reading about Discovery is not enough; the exam is written for people who have watched a discovery run and read its logs.
This guide walks through what the blueprint weights, how a probe turns into a configuration item, what the MID Server has to do with all of it, and which experiments in a personal developer instance teach the rest.
What goes wrong when a Discovery schedule returns bad data?
Almost every scenario on the exam starts from a symptom an implementer would actually see. Learning to read those symptoms backwards is the single most useful preparation habit, because the answer options are usually all plausible and only one matches the real cause.
Here are the ones that come up most, and the part of the platform each belongs to: