SERVICENOW DISCOVERY FINAL
PREP GUIDE 2026 VERIFIED
QUESTIONS GRADED A+
◉ Cloud discovery.
Answer: Cloud discovery finds resources in AWS and Azure clouds, and
then populates the CMDB with the relevant CIs and relationships. Two
types: Service account cloud discovery & Cloud application discovery;
◉ Serverless discovery.
Answer: Discovery can find applications on host machines without the
need to discover the host first. Two type: Standard serverless discovery
& Host-based serverless discovery;
◉ Discocery Dashboard displays.
Answer: The Discovery Dashboard displays:
1 The current progress of the actively running schedules.
2 Discovered devices, by category and time discovered.
3 Errors that occurred during a schedule that has run.
4 Credentials that were either not required or unused by a schedule
◉ Discovery status.
Answer: The Discovery status provides a summary of a Discovery
launched from a schedule. You can also cancel a Discovery that is in
progress from the status form
,◉ Discovery status reference lists.
Answer: * Discovery Log: classification failures, CMDB updates, and
authentication failures
* ECC queue entried: connected flow of probe and sensor activity,
actual XML payload.
* Device history: summary of all the devices scanned during discovery,
and what action sensors took on the CMDB
◉ Include alive.
Answer: includes devices on which one port responded to the scan, but
no ports are open
◉ Discovery Log.
Answer: classification failures, CMDB updates, and authentication
failures
◉ Discovery Pattern Log.
Answer: includes Horizontal Discovery log records, which display
information about discoveries that were performed with patterns. A
horizontal discovery log record is created for an entire horizontal
discovery run, which includes the results of all the operations specified
in the pattern.
◉ Why use Discovery status?.
, Answer: to see a summary of a Discovery, access the ECC queue (shows
probe and sensor activity), as well as the actual XML payload
◉ Why use Discovery dashboard?.
Answer: to monitor ongoing Discovery operations
◉ Why use Discovery CI schedule manager?.
Answer: to access a report of all discovered devices, see any errors that
might have occurred, and view discovery trends. This manager interface
shows data for Configuration Item type discoveries.
◉ What are the steps for: MID Server auto selection.
Answer: 1 appropriate IP range configured
2 ALL application and appropriate IP range configured
3 more then 1, then first that is Up else random
4 none are up, default MID Server specified for the Discovery
application
5 no default MID Server, then default MID Server specified for the ALL
application, assuming it is up.
6 If no default MID Server is specified, cycles through the previous
steps and looks for MID Servers with the status of Paused or Upgrading
◉ Auto select steps for MID Server clusters in load balanced.
Answer: 1 first MID Server in the cluster that it finds with the status of
Up
PREP GUIDE 2026 VERIFIED
QUESTIONS GRADED A+
◉ Cloud discovery.
Answer: Cloud discovery finds resources in AWS and Azure clouds, and
then populates the CMDB with the relevant CIs and relationships. Two
types: Service account cloud discovery & Cloud application discovery;
◉ Serverless discovery.
Answer: Discovery can find applications on host machines without the
need to discover the host first. Two type: Standard serverless discovery
& Host-based serverless discovery;
◉ Discocery Dashboard displays.
Answer: The Discovery Dashboard displays:
1 The current progress of the actively running schedules.
2 Discovered devices, by category and time discovered.
3 Errors that occurred during a schedule that has run.
4 Credentials that were either not required or unused by a schedule
◉ Discovery status.
Answer: The Discovery status provides a summary of a Discovery
launched from a schedule. You can also cancel a Discovery that is in
progress from the status form
,◉ Discovery status reference lists.
Answer: * Discovery Log: classification failures, CMDB updates, and
authentication failures
* ECC queue entried: connected flow of probe and sensor activity,
actual XML payload.
* Device history: summary of all the devices scanned during discovery,
and what action sensors took on the CMDB
◉ Include alive.
Answer: includes devices on which one port responded to the scan, but
no ports are open
◉ Discovery Log.
Answer: classification failures, CMDB updates, and authentication
failures
◉ Discovery Pattern Log.
Answer: includes Horizontal Discovery log records, which display
information about discoveries that were performed with patterns. A
horizontal discovery log record is created for an entire horizontal
discovery run, which includes the results of all the operations specified
in the pattern.
◉ Why use Discovery status?.
, Answer: to see a summary of a Discovery, access the ECC queue (shows
probe and sensor activity), as well as the actual XML payload
◉ Why use Discovery dashboard?.
Answer: to monitor ongoing Discovery operations
◉ Why use Discovery CI schedule manager?.
Answer: to access a report of all discovered devices, see any errors that
might have occurred, and view discovery trends. This manager interface
shows data for Configuration Item type discoveries.
◉ What are the steps for: MID Server auto selection.
Answer: 1 appropriate IP range configured
2 ALL application and appropriate IP range configured
3 more then 1, then first that is Up else random
4 none are up, default MID Server specified for the Discovery
application
5 no default MID Server, then default MID Server specified for the ALL
application, assuming it is up.
6 If no default MID Server is specified, cycles through the previous
steps and looks for MID Servers with the status of Paused or Upgrading
◉ Auto select steps for MID Server clusters in load balanced.
Answer: 1 first MID Server in the cluster that it finds with the status of
Up
