ServiceNow CIS - Discovery (NewYork) Questions and Answers 100% Verified!
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: 1. Service account cloud discovery
2. Cloud application discovery
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
Cloud Management
Nmap
PowerShell Resolve DNS
REST
SNMP
SOAP
SSH
VMware
WMI
Where can you validate Discovery results? - ANSWER-1. Accessing the ECC queue
2. Analyzing the XML payload
3. Checking the Discovery log
What happens when you cancel an active Discovery? - ANSWER-Any associated sensor transactions are immediately terminated and any scheduled sensor jobs are deleted from the system. After cancellation, the cleanup Status shows the Completed count and the cancellation is logged in the Discovery log.
When should you run Network Discovery? - ANSWER-It is intended for organizations that do not have complete knowledge of the IP addresses available for Discovery in their networks.
If you already know the IP address ranges in your network, it is not necessary to run Network Discovery.
What is the result of Network Discovery? - ANSWER-Network Discovery, converts the IP networks it finds into IP address Range Sets that you use in Discovery schedules to discover configuration items (CI).
The MID Server uses the router tables on the starting routers to discover other routers in the network. The MID Server then spreads out through the network, using router tables it finds to discover other routers. It continues until all the routers and switches have been explored.
What are some high level Discovery troubleshooting areas? - ANSWER-1. Connectivity
2. Permissions
3. Configuration
4. Probes, Sensors, Process Classifiers
Under which account does the MID server run? - ANSWER-Local Admin Account
If there are no working credentials for a device, which credentials are used? - ANSWER-MID Server Service Account
Credentials for SSH are for? - ANSWER-Unix/Linux
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: 1. Service account cloud discovery
2. Cloud application discovery
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
Cloud Management
Nmap
PowerShell Resolve DNS
REST
SNMP
SOAP
SSH
VMware
WMI
Where can you validate Discovery results? - ANSWER-1. Accessing the ECC queue
2. Analyzing the XML payload
3. Checking the Discovery log
What happens when you cancel an active Discovery? - ANSWER-Any associated sensor transactions are immediately terminated and any scheduled sensor jobs are deleted from the system. After cancellation, the cleanup Status shows the Completed count and the cancellation is logged in the Discovery log.
When should you run Network Discovery? - ANSWER-It is intended for organizations that do not have complete knowledge of the IP addresses available for Discovery in their networks.
If you already know the IP address ranges in your network, it is not necessary to run Network Discovery.
What is the result of Network Discovery? - ANSWER-Network Discovery, converts the IP networks it finds into IP address Range Sets that you use in Discovery schedules to discover configuration items (CI).
The MID Server uses the router tables on the starting routers to discover other routers in the network. The MID Server then spreads out through the network, using router tables it finds to discover other routers. It continues until all the routers and switches have been explored.
What are some high level Discovery troubleshooting areas? - ANSWER-1. Connectivity
2. Permissions
3. Configuration
4. Probes, Sensors, Process Classifiers
Under which account does the MID server run? - ANSWER-Local Admin Account
If there are no working credentials for a device, which credentials are used? - ANSWER-MID Server Service Account
Credentials for SSH are for? - ANSWER-Unix/Linux
