SERVICENOW-CIS-DISCOVERY Mid Server Management — 40 Questions

Question 1

You have a MID Server that must connect through an authenticated proxy. Where do you configure the proxy credentials?

Accepted Answer

In the config.xml file under proxy parameters.. Proxy settings, including credentials, are configured in the config.xml file on the MID server host.

Answer

In the ServiceNow Credential store.

Answer

Via a MID Server Script File.

Answer

In the 'Proxy' related list on the MID Server record.

Question 2

Which user role is required to modify MID Server configuration settings within the ServiceNow instance?

Accepted Answer

mid_server. The 'mid_server' role is specifically required to manage and configure MID Servers.

Answer

itil

Answer

discovery_admin

Answer

admin

Question 3

When upgrading a MID Server, what is the best practice for a manual upgrade process?

Accepted Answer

Use the 'Upgrade' UI action on the MID Server record.. The recommended practice is to trigger the upgrade from the MID Server record in the instance to ensure synchronization.

Answer

Delete the entire agent folder and reinstall.

Answer

Manually replace the agent JAR files.

Answer

Change the version in config.xml.

Question 4

Which THREE of the following are valid methods to troubleshoot a MID Server that is not appearing in the 'MID Servers' list in the instance?

Accepted Answer

Verify the MID Server has the correct instance URL in the config.xml.. Connectivity, firewall, and authentication are the primary culprits for registration issues.

Answer

Restart the database server.

Answer

Change the MID Server to 'Debug' mode in the instance.

Question 5

A MID Server is installed behind a proxy. Which file must be modified to ensure the MID Server can reach the instance?

Accepted Answer

agent.config. The agent/conf/agent.config file contains the network proxy settings required for the MID Server to tunnel traffic to the instance.

Answer

proxy.xml

Answer

mid_server.properties

Answer

wrapper.conf

Question 6

You have two MID Servers in a cluster. You want to ensure one takes over if the other fails. What setting must be configured?

Accepted Answer

Add both to a MID Server Cluster with 'Failover' behavior. Load balancing and failover are managed through the MID Server Cluster record.

Answer

Set the 'Cluster' property in the MID Server system properties

Answer

Configure the 'Primary' flag on the MID Server record

Answer

Set the 'Load Balance' flag on the MID Server record

Question 7

An administrator needs to deploy a MID Server on a Windows host using a specific service account. Where should the credentials be stored to allow the MID Server to perform discovery?

Accepted Answer

In the ServiceNow Instance Credentials table. Credentials used by the MID Server for scanning are stored in the ServiceNow instance, not locally on the MID Server host.

Answer

In the agent.config file

Answer

In the wrapper.conf file

Answer

In the local Windows Credential Manager

Question 8

Which parameter in the 'agent.config' file specifies the interval the MID Server uses to check the ECC Queue?

Accepted Answer

mid.poll.time. The mid.poll.time parameter dictates how frequently the MID Server polls the instance for new tasks.

Answer

mid.heartbeat.frequency

Answer

mid.task.interval

Answer

mid.ecc.timeout

Question 9

Which user role is required to manage MID Server records?

Accepted Answer

mid_server_admin. The mid_server_admin role provides the necessary permissions to configure and manage MID Servers.

Answer

discovery_admin

Answer

admin

Answer

itil

Question 10

How do you verify if a MID Server is using the correct Java version?

Accepted Answer

Check the 'Java version' field on the MID Server record. The MID Server record provides a 'Java version' field or the wrapper log shows the environment details.

Answer

Check the Discovery Schedule

Answer

Check the MID Server System Properties

Answer

Check the ECC Queue Input

Question 11

A MID Server is configured to scan a network segment but the scan fails with an 'Access Denied' error. Where should you look to ensure the MID Server is using the correct credentials?

Accepted Answer

Discovery Logs. When a Discovery scan fails with 'Access Denied,' the Discovery Logs are the first place to check because they record credential usage and authentication failures for each device. The logs show which credential was attempted, whether it succeeded, and the exact error, allowing you to verify the MID Server is using the correct credentials. This is the standard troubleshooting step for credential-related discovery failures.

Answer

Service Mapping Logs

Answer

MID Server Logs

Answer

Credential Store

Question 12

Where do you go to see a list of all available MID Servers in your instance?

Accepted Answer

MID Servers > Servers. The MID Server list view is available under the MID Server module.

Answer

ECC Queue

Answer

System Properties

Answer

Discovery Dashboard

Question 13

When should you use a MID Server Cluster?

Accepted Answer

When you want to increase scanning speed. Clusters are used for high availability and load balancing of discovery tasks.

Answer

When you need to store more data

Answer

When you want to secure the network

Answer

When you have only one MID Server

Question 14

You need to restrict a MID Server to only access specific IP ranges. How can this be done?

Accepted Answer

By assigning the MID Server to an IP Range in the MID Server record. The MID Server record in ServiceNow contains an 'IP range' field (related to the IP Range table) that restricts which IP addresses the MID Server is allowed to communicate with during discovery. Assigning the MID Server to a specific IP Range scopes its discovery and access to only those addresses, which is the supported, native mechanism for this restriction. This is configured directly on the MID Server form, not through external means.

Answer

By deleting the discovery credentials

Answer

By blocking ports on the firewall

Answer

By modifying the agent.config file

Question 15

Which property controls the number of concurrent threads a MID Server uses?

Accepted Answer

mid.thread.max. The mid.thread.max property defines the maximum number of simultaneous discovery jobs.

Answer

mid.job.count

Answer

mid.concurrency.limit

Answer

mid.max.discovery

Question 16

If a MID Server is behind a load balancer, what configuration might be required?

Accepted Answer

Configure the MID Server to trust the Load Balancer's certificate. The load balancer may terminate SSL or require specific headers, which must be accounted for in the MID Server configuration.

Answer

Reduce the polling time

Answer

Disable the MID Server firewall

Answer

Set the MID Server to 'Internal' mode

Question 17

Which platform can a MID Server be installed on?

Accepted Answer

Windows, Linux, and macOS. ServiceNow supports running MID Servers on Windows, Linux, and other Java-supported OS environments.

Answer

Android

Answer

Only Windows

Answer

Only Linux

Question 18

What module allows you to monitor the status of all MID Servers at a glance?

Accepted Answer

MID Servers > Servers (List view). The MID Server dashboard or list view provides a quick overview of status.

Answer

System Logs

Answer

ECC Queue

Answer

Discovery Dashboard

Question 19

Which TWO file types are typically located in the MID Server 'agent' directory?

Accepted Answer

Configuration files (e.g., agent.config). The agent directory contains configuration files and the binary scripts for starting the service.

Answer

User session tokens

Answer

Discovery results

Answer

Database files

Question 20

Which THREE logs should you investigate when troubleshooting a failing discovery task?

Accepted Answer

Discovery log. The Discovery log (B) is the primary record of the discovery process itself, capturing scan scheduling, probe execution, classification, and errors specific to the failing discovery task. The Agent log (C) is relevant because discovery in many platforms is performed by an agent or mid-server process, and its log records agent-side failures such as connection issues, credential problems, or probe execution errors that would cause discovery to fail. The Wrapper log (E) records the startup, shutdown, and execution of the underlying service/process wrapper that launches discovery and related components, so it reveals crashes, JVM or process-level failures, and restart loops affecting the discovery task. The System log (A) and Event log (D) are general OS-level logs that may show unrelated system activity and are not the targeted logs used to diagnose a failing discovery task, so they are not among the three to investigate.

Answer

System log

Answer

Event log