SERVICENOW-CIS-DISCOVERY Mid Server Management Practice Test 6 — 15 Questions

Question 1

Which TWO factors are used to configure a MID Server Cluster?

Accepted Answer

Member MID Servers. In ServiceNow, a MID Server Cluster is configured by defining two things: the Member MID Servers (option C), which are the individual MID Server records that are added to the cluster and that must all be up and validated, and the Cluster behavior (option D), which determines how the cluster load-balances and fails over jobs among its members (for example, using the cluster's load-balancing and failover capabilities). These two factors are the essential configuration elements of a MID Server Cluster record. Proxy settings (option A) are configured on individual MID Server records or via MID Server properties, not as a cluster-defining factor. Network firewall ports (option B) are an infrastructure prerequisite for MID Server connectivity but are not a cluster configuration parameter. Discovery Schedule (option E) is a separate Discovery configuration item that determines what and when to discover, and it is not used to configure a MID Server Cluster.

Answer

Proxy settings

Answer

Network firewall ports

Answer

Discovery Schedule

Question 2

Which TWO actions should you perform if a MID Server is not showing 'Up' in the instance?

Accepted Answer

Verify the MID Server service is running on the host. Checking the service status on the host and the ECC Queue for connectivity errors are the two initial troubleshooting steps.

Answer

Change the proxy server settings

Answer

Create a new discovery schedule

Answer

Update the MID Server version

Question 3

Which TWO settings can be managed via the MID Server 'Capabilities' feature?

Accepted Answer

Filtering scan types (e.g., WMI, SNMP). Option B (Filtering scan types such as WMI and SNMP) is correct because MID Server capabilities are used to control which discovery/scanning probes and protocols a MID Server is allowed to run, so you can restrict a MID Server to specific scan types like WMI or SNMP. Option D (Restricting discovery work) is correct because capabilities determine what kinds of discovery and orchestration jobs a MID Server is eligible to execute, effectively limiting the discovery workload it can be assigned. Options A, C, and E are not managed through the Capabilities feature: user access is governed by roles/ACLs, proxy connections are configured in MID Server properties, and memory limits are set via the MID Server's wrapper/JVM configuration, not capabilities.

Answer

Managing user access

Answer

Configuring proxy connections

Answer

Setting the memory limit

Question 4

Which THREE pieces of information are required for a MID Server to communicate with the ServiceNow instance?

Accepted Answer

Instance URL. Option B (Instance URL) is required because the MID Server's config.xml must point to the ServiceNow instance endpoint (e.g., https://<instance>.service-now.com) so it knows where to establish its outbound connection. Option C (MID Server record validation) is required because the MID Server must be registered as a MID Server record in the instance and validate itself against that record (name/user/password) before it is authorized to pull and execute jobs. Option E (Network connectivity to the instance) is required because the MID Server initiates outbound HTTPS (port 443) connections to the instance; without reachable network/DNS/firewall paths, no communication can occur. Option A (Admin password for the host) is not required, since the MID Server runs as a service under a local service account and does not need host admin credentials for instance communication. Option D (Database credentials) is not required, because the MID Server never connects directly to the ServiceNow database; all interaction occurs through the instance's REST/SOAP APIs.

Answer

Admin password for the host

Answer

Database credentials

Question 5

Which TWO actions can be triggered from the MID Server record's related links?

Accepted Answer

Restart the MID server. Option C (Restart the MID server) is correct because the MID Server record's related links include a Restart action that lets an administrator remotely restart the MID Server service on its host, which is essential for applying configuration changes or recovering a stuck MID Server. Option E (Validate the MID server) is correct because the related links also provide a Validate action that runs a diagnostic check against the MID Server to confirm connectivity, credentials, and capability status with the ServiceNow instance. Option A (Upgrade the database) is not a MID Server related link, as database upgrades are handled through instance upgrade processes, not from a MID Server record. Option B (View the CMDB records) is not a MID Server related link; CMDB data is accessed through CMDB modules and CI records, not the MID Server record's related links. Option D (Delete the instance) is not a MID Server related link, since deleting an instance is an administrative action performed from the instance management console, not from a MID Server record.

Answer

Upgrade the database

Answer

View the CMDB records

Answer

Delete the instance

Question 6

Which TWO types of discovery probes can a MID Server execute?

Accepted Answer

WMI probes. A MID Server in ServiceNow Discovery can execute WMI probes, which use Windows Management Instrumentation over DCOM/RPC to collect hardware, software, and configuration data from Windows hosts, making option A correct. It can also execute SSH probes, which connect to Linux/Unix and network devices over TCP port 22 to run commands and gather inventory data, making option E correct. Hardware replacement probes (B) are not a Discovery probe category—Discovery identifies and classifies CIs but does not perform hardware replacement actions. User creation probes (C) are likewise not a Discovery probe type; user provisioning is handled by orchestration/fulfillment workflows, not Discovery. SQL injection probes (D) are attack techniques, not legitimate Discovery probes, and have no place in the MID Server probe library.

Answer

Hardware replacement probes

Answer

User creation probes

Answer

SQL injection probes

Question 7

Which THREE factors should be considered when planning a MID Server installation?

Accepted Answer

Network access to the instance. When planning a MID Server installation, network access to the instance (B) is essential because the MID Server must be able to reach the ServiceNow instance over the required outbound ports (typically HTTPS/443) to register, receive jobs, and return results. Hardware resource availability (C) must be evaluated because the MID Server host needs sufficient CPU, memory, and disk to run the Java-based MID Server process and handle the discovery/integration workloads assigned to it. Operating system compatibility (D) is also required since the MID Server is only supported on specific OS versions (for example, certain Windows Server and Linux distributions) and must match the supported Java runtime. Database version (A) is not a MID Server installation factor because the MID Server does not host or require a local database, and user browser settings (E) are irrelevant since the MID Server runs as a background service without a browser interface.

Answer

Database version

Answer

User browser settings

Question 8

Which TWO ways can you view MID Server logs?

Accepted Answer

Directly on the MID Server host file system. You can view them via the agent directory on the host or through the MID Server record in the instance if configured.

Answer

Via the System Mail log

Answer

Via the user profile

Answer

Via the Discovery Dashboard

Question 9

Which TWO files or folders are most critical for backing up a MID Server configuration?

Accepted Answer

The keystore folder. The keystore folder (C) is critical because it stores the MID Server's certificates and private keys used for secure authentication and encrypted communication with the ServiceNow instance, so losing it would break the MID Server's trusted connection. The agent.config file (E) is also essential since it holds the MID Server's core configuration parameters — such as instance URL, user credentials, and connection settings — that define how the MID Server operates and connects. The database folder (A) is not part of a MID Server backup because the MID Server does not maintain its own database; data resides on the ServiceNow instance. The temporary file folder (B) only holds transient working files that can be regenerated, and the logs folder (D) contains diagnostic output useful for troubleshooting but not required to restore the MID Server's configuration.

Answer

The database folder

Answer

The temporary file folder

Answer

The logs folder

Question 10

Which TWO categories are commonly found in the 'Capabilities' list for a MID Server?

Accepted Answer

Discovery. In ServiceNow, a MID Server's Capabilities list determines which jobs the MID Server is allowed to execute, and Discovery (option D) is a core capability because the MID Server performs the horizontal and vertical discovery probes, sensors, and patterns that populate the CMDB. Service Mapping (option E) is likewise a standard MID Server capability, since the MID Server runs the traffic-based and pattern-based mapping probes needed to build service instances and their relationships. Reporting (A) is a platform/UI function performed by users and scheduled jobs, not a MID Server capability, and User Management (B) is handled by the platform's user administration and roles, not by a MID Server. Database Maintenance (C) is not a MID Server capability either; database-level tasks such as table maintenance and cleanup are executed by the instance's database jobs, not by a MID Server.

Answer

Reporting

Answer

User Management

Answer

Database Maintenance

Question 11

Which THREE conditions must be met for a MID Server to be considered 'Up'?

Accepted Answer

The MID Server is not paused. A MID Server is reported as 'Up' in ServiceNow when three conditions are satisfied: the MID Server is not paused (B), meaning an administrator has not manually set its status to Paused, which would suppress its availability; the MID Server service is running (C), i.e., the Windows service or Linux daemon process is active and executing; and the heartbeat is within the allowed interval (E), meaning the MID Server has checked in with the instance within the configured heartbeat threshold (typically around 60 seconds, with a missed-heartbeat tolerance) so the instance considers it reachable. Options A and D are not requirements: a MID Server does not need 100% free CPU (it only needs adequate resources to run), and it can run on either Windows or Linux, so the operating system is irrelevant to the 'Up' status.

Answer

The MID Server has 100% CPU free

Answer

The MID Server is running on Linux

Question 12

A MID Server has been installed on a Windows host, but it is not appearing in the 'MID Servers' list in the ServiceNow instance. What is the first place you should check to identify the cause?

Accepted Answer

The agent log file located in the agent/logs directory on the host. When a MID Server is installed but does not appear in the instance's MID Servers list, the first diagnostic step is to check the agent log file in the agent/logs directory on the host. The log will show startup errors, connection failures, or authentication issues that prevent the MID from registering with the instance.

Answer

The 'ECC Queue' table

Answer

The 'MID Server Issues' related list on the Discovery Dashboard

Answer

The 'Credential Store' module

Question 13

You need to ensure that a specific MID Server only performs WMI discovery and ignores SSH tasks. How do you configure this?

Accepted Answer

Assign only the 'WMI' capability in the 'Capabilities' related list. Capabilities are used to restrict the types of tasks a MID Server will accept. Removing the SSH capability ensures the MID Server ignores those jobs.

Answer

Create an Access Control List (ACL) on the ECC Queue

Answer

Set the 'Discovery Source' field to 'WMI'

Answer

Modify the 'Supported Protocols' field on the MID Server record

Question 14

You are troubleshooting a MID Server that is stuck in the 'Validated' state but not picking up jobs. You notice the 'MID Server Issues' list reports a 'Clock drift' error. What is the recommended resolution?

Accepted Answer

Synchronize the MID Server host time with an NTP server. Clock drift indicates that the MID Server host's time is not synchronized with the ServiceNow instance's time, causing authentication and job processing failures. The recommended resolution is to synchronize the host time with an NTP server to ensure accurate time alignment.

Answer

Update the 'MID Server' record to 'Down' and back to 'Up'

Answer

Increase the 'ECC Queue' processing timeout

Answer

Restart the MID Server service

Question 15

What is the purpose of the 'MID Server User' assigned to a MID Server record?

Accepted Answer

To authenticate the MID Server to the ServiceNow instance. The MID Server user is the account the MID Server service uses to authenticate with the ServiceNow instance to pull and push ECC Queue records.

Answer

To perform Discovery scans on target devices

Answer

To access the MID Server's local configuration files

Answer

To log in to the MID Server host via SSH