SERVICENOW CIS DISCOVERY
PRACTICE SOLUTION PACK 2026
TESTED QUESTIONS WITH FULL
ANSWERS
◉ Server-less Discovery.
Answer: Discovery can find applications on host machines without the
need to discover the host first.
Two types:
1. Standard server-less discovery
2. Host-based server-less discovery
◉ Discovery Dashboard displays.
Answer: 1. The current progress (status) of the actively running
Discovery schedules.
2. Newly discovered devices and applications, by time discovered.
3. Existing devices and applications not updated by Discovery.
4. Errors that occurred during a Discovery schedule that has run.
5. Credentials that were either not required or unused by a Discovery
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 Discovery Status form.
◉ What are the Discovery Status reference lists?.
Answer: 1. Discovery Log: Classification failures, CMDB updates, and
authentication failures.
2. Devices: Summary of all the devices scanned during discovery, and
what action sensors took on the CMDB.
3. ECC Queue: Connected flow of probe and sensor activity, actual
XML payload.
◉ Include Alive.
Answer: Indicates that this Discovery includes devices on which one
port responded to the scan, but no ports are open. Such a device is
considered to be alive. If this check box is not selected, only active
devices with one or more open ports that Discovery can query are
displayed.
◉ Discovery Log.
Answer: The Discovery Log shows information such as classification
failures, CMDB updates, and authentication failures. A Discovery Log
record is created for each action associated with a discovery status.
◉ Discovery Pattern Log.
,Answer: The Pattern Discovery log 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, as
well as the actual XML payload.
◉ MID Server Fail-Over Behavior in a Cluster.
Answer: MID Servers in a fail-over cluster each have a configured order
that the platform uses to determine which MID Server to use next in case
of failure. MID Servers in a fail-over cluster work independently and do
not load balance with other MID Servers in that cluster (although they
might also be members of load balancing clusters). When a MID Server
fails, the MID Server Cluster Management business rule selects the
highest available MID Server in the order to take over the work. The
selected MID Server checks the ECC Queue and starts with jobs that are
either Processing or Ready.
◉ Where can you set the Shazzam batch size?.
Answer: In the Discovery Schedule.
◉ What is the default batch size for Shazzam?.
Answer: 5000
, ◉ When NOT to use MID server clusters?.
Answer: For performance and reliability reasons, these data sources
should not be used with MID Server clusters. These external data
sources should only be used with dedicated MID Servers.
1. LDAP
2. Export sets
3. JDBC data sources
◉ When can a MID server specifically cause duplicate data?.
Answer: If a MID Server in a cluster fails, the fail-over MID Server
starts over at the beginning of the ECC queue task even if much of the
information from the JDBC data source was already returned. This can
result in duplicate data.
◉ What are MID Server Capabilities?.
Answer: MID Server capabilities define the specific functions of a MID
Server within an IP address range.
Several applications, such as Discovery, Service Mapping, Cloud
Management, and Orchestration can use capabilities, IP ranges, and
MID Server selection to narrow the pool of MID Servers the
applications need.
◉ What MID Server Capabilities are available by default?.
Answer: All
PRACTICE SOLUTION PACK 2026
TESTED QUESTIONS WITH FULL
ANSWERS
◉ Server-less Discovery.
Answer: Discovery can find applications on host machines without the
need to discover the host first.
Two types:
1. Standard server-less discovery
2. Host-based server-less discovery
◉ Discovery Dashboard displays.
Answer: 1. The current progress (status) of the actively running
Discovery schedules.
2. Newly discovered devices and applications, by time discovered.
3. Existing devices and applications not updated by Discovery.
4. Errors that occurred during a Discovery schedule that has run.
5. Credentials that were either not required or unused by a Discovery
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 Discovery Status form.
◉ What are the Discovery Status reference lists?.
Answer: 1. Discovery Log: Classification failures, CMDB updates, and
authentication failures.
2. Devices: Summary of all the devices scanned during discovery, and
what action sensors took on the CMDB.
3. ECC Queue: Connected flow of probe and sensor activity, actual
XML payload.
◉ Include Alive.
Answer: Indicates that this Discovery includes devices on which one
port responded to the scan, but no ports are open. Such a device is
considered to be alive. If this check box is not selected, only active
devices with one or more open ports that Discovery can query are
displayed.
◉ Discovery Log.
Answer: The Discovery Log shows information such as classification
failures, CMDB updates, and authentication failures. A Discovery Log
record is created for each action associated with a discovery status.
◉ Discovery Pattern Log.
,Answer: The Pattern Discovery log 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, as
well as the actual XML payload.
◉ MID Server Fail-Over Behavior in a Cluster.
Answer: MID Servers in a fail-over cluster each have a configured order
that the platform uses to determine which MID Server to use next in case
of failure. MID Servers in a fail-over cluster work independently and do
not load balance with other MID Servers in that cluster (although they
might also be members of load balancing clusters). When a MID Server
fails, the MID Server Cluster Management business rule selects the
highest available MID Server in the order to take over the work. The
selected MID Server checks the ECC Queue and starts with jobs that are
either Processing or Ready.
◉ Where can you set the Shazzam batch size?.
Answer: In the Discovery Schedule.
◉ What is the default batch size for Shazzam?.
Answer: 5000
, ◉ When NOT to use MID server clusters?.
Answer: For performance and reliability reasons, these data sources
should not be used with MID Server clusters. These external data
sources should only be used with dedicated MID Servers.
1. LDAP
2. Export sets
3. JDBC data sources
◉ When can a MID server specifically cause duplicate data?.
Answer: If a MID Server in a cluster fails, the fail-over MID Server
starts over at the beginning of the ECC queue task even if much of the
information from the JDBC data source was already returned. This can
result in duplicate data.
◉ What are MID Server Capabilities?.
Answer: MID Server capabilities define the specific functions of a MID
Server within an IP address range.
Several applications, such as Discovery, Service Mapping, Cloud
Management, and Orchestration can use capabilities, IP ranges, and
MID Server selection to narrow the pool of MID Servers the
applications need.
◉ What MID Server Capabilities are available by default?.
Answer: All
