SERVICENOW-CIS-DISCOVERY Discovery Configuration Practice Test 4 — 15 Questions

Question 1

What is the role of the 'ECC Queue' in Discovery?

Accepted Answer

To act as a message queue for commands and results between instance and MID Server.. The ECC Queue (External Communication Channel) is a key component in ServiceNow Discovery that acts as a message queue for commands and results between the ServiceNow instance and MID Servers. It facilitates asynchronous communication, where the instance queues commands for MID Servers to execute and MID Servers post results back.

Answer

To schedule Discovery scans.

Answer

To store the final CMDB data.

Answer

To provide credentials for discovery.

Question 2

If a MID Server is 'Down', what happens to Discovery schedules assigned to it?

Accepted Answer

The discovery job will fail or not execute.. If a MID Server is down, any Discovery schedules assigned to it will not execute because the MID Server is the component that performs the discovery. The discovery job will either fail or remain in a pending state until the MID Server is available, but it will not automatically switch to another MID Server.

Answer

The discovery remains in a 'Ready' state.

Answer

The schedule automatically switches to another MID.

Answer

The schedule runs on the next available MID Server.

Question 3

What is the purpose of the 'Classification' phase?

Accepted Answer

To identify the O/S or device type.. Classification determines what the device is (e.g., Windows Server, Router) based on probe responses.

Answer

To run reconciliation rules.

Answer

To scan for open ports.

Answer

To update the CMDB attributes.

Question 4

How do you associate a specific MID Server with a Discovery Schedule?

Accepted Answer

By selecting it in the 'MID Server' field on the Discovery Schedule.. The MID Server is selected on the Discovery Schedule record directly.

Answer

Through a Discovery Behavior.

Answer

Via a credential alias.

Answer

By modifying the IP Range.

Question 5

Which of the following would be the best reason to create a custom Discovery Behavior?

Accepted Answer

To control which probes are run for a specific type of device.. A custom Discovery Behavior is created to control which probes are run for a specific type of device. This allows you to tailor the discovery process to different device classes, ensuring that only relevant probes are executed. This is the primary reason to create a custom behavior, as it provides flexibility in discovery execution.

Answer

To define the IP range for a subnet.

Answer

To manage MID Server credentials.

Answer

To schedule discovery at a different time.

Question 6

You are performing Discovery and notice that the 'Discovery Status' shows 'Success', but the CI record was not updated. What is the most likely cause?

Accepted Answer

The Identification rules are preventing the update.. The Discovery Status showing 'Success' indicates that the discovery phases (e.g., Shazzam, Classification, Identification) completed without errors. However, if the CI record was not updated, the most likely cause is that the Identification rules did not match the discovered data to an existing CI, or they matched but the update was blocked due to reconciliation rules. Identification rules determine whether a discovered item is a new CI or an existing one; if they fail to identify, the CI may not be updated or created.

Answer

The MID Server is down.

Answer

The credential had no access.

Answer

The Shazzam phase failed.

Question 7

When troubleshooting a specific device, how can you see exactly what was returned by the probes?

Accepted Answer

View the ECC Queue records related to the status.. The Discovery Status record allows you to drill down into the 'Devices' and 'ECC Queue' to see the raw input data.

Answer

Run the discovery again.

Answer

Check the MID Server logs.

Answer

View the CI record.

Question 8

What is the maximum number of times a Discovery Schedule can run?

Accepted Answer

Unlimited, based on system configuration.. Discovery schedules can be configured to run as often as required by the system capability.

Answer

100 times total.

Answer

Once per day.

Answer

Only once.

Question 9

What does the 'Discovery Status' field 'Completed' mean?

Accepted Answer

The discovery process has finished executing.. It indicates that all phases of the discovery process for that specific status record have finished.

Answer

No errors occurred.

Answer

The CMDB is now up-to-date.

Answer

All devices were successfully updated.

Question 10

A customer needs to discover devices across a firewall. What is the standard configuration to allow this?

Accepted Answer

Place a MID Server inside the network segment of the target devices.. The standard and recommended approach for discovering devices across a firewall is to place a MID Server inside the target network segment. The MID Server initiates outbound connections to the ServiceNow instance, so only outbound HTTPS (443) needs to be allowed through the firewall — no inbound ports need to be opened to the instance. This is the architecturally correct and secure pattern.

Answer

Open all ports on the firewall.

Answer

Use a VPN connection on the instance.

Answer

Enable 'External Discovery' in the instance.

Question 11

What is the purpose of an 'IP Service' in Discovery?

Accepted Answer

To define a set of ports and protocols for scanning.. IP Services group ports and protocols together for use in port scanning, making it easier to define what to scan.

Answer

To assign a MID Server.

Answer

To define the IP range.

Answer

To provide credentials.

Question 12

When a discovery scan is running very slowly, which configuration adjustment might improve performance?

Accepted Answer

Increasing the number of concurrent tasks on the MID Server.. Discovery performance is often bottlenecked by the MID Server's worker pool — the number of concurrent probes it can execute. Increasing the 'Max concurrent tasks' (or equivalent concurrency setting) on the MID Server allows more probes to run in parallel, which can significantly speed up a slow scan, provided the MID Server has sufficient CPU, memory, and network bandwidth.

Answer

Adding more IP ranges to the schedule.

Answer

Deleting all existing CI records.

Answer

Changing the Discovery schedule to 'Weekly'.

Question 13

What is the consequence of deleting a Discovery Schedule?

Accepted Answer

It prevents future automated runs of that schedule.. Deleting a Discovery Schedule removes the schedule record itself, so the scheduler no longer has anything to trigger — future automated runs of that schedule will not occur. However, the CIs and discovery history already collected remain in the CMDB; only the schedule definition is destroyed.

Answer

It breaks the MID Server.

Answer

It forces a full re-discovery.

Answer

It deletes all previously discovered CIs.

Question 14

What is the primary way to check if a MID Server is communicating correctly with the ServiceNow instance?

Accepted Answer

Check the 'MID Server' list status.. The MID Server status on the 'MID Server' list view shows 'Up' if it is connected.

Answer

Check the Discovery log.

Answer

Ping the MID Server from your computer.

Answer

Check the CMDB.

Question 15

If you need to ensure that a Discovery scan does not impact network traffic, what is a recommended best practice?

Accepted Answer

Distribute discovery scans across multiple schedules and MID servers.. Staggering discovery schedules and using IP ranges to distribute the load across time and MID servers is the standard practice.

Answer

Set the discovery to run at night.

Answer

Disable the Shazzam phase.

Answer

Limit the scan to one IP per hour.