What is the purpose of ServiceNow Discovery? - ANSWER-Discovery provides complete visibility into a customer's on -premise and cloud resources. It keeps track of changes occurring within on -premise, cloud, and server less infrastructure in the Configuration Management Database (CMDB).
How does ServiceNow Discovery set a strong foundation for? - ANSWER-By providing a strong foundation with accurate data and relationship views for ITSM change management, Software Asset Management, Customer Service Management, Security Operations, and more.
What is ServiceNow Discovery? - ANSWER-Discovery finds computers, servers, printers, and a variety of IP-enabled devices, and the applications that run on them. It can then update the CIs in your CMDB with the data it collects.
What are Probes and Sensors? - ANSWER-Probes and sensors are scripts that collect data on the host, process it, and update the CMDB. Probes and sensors are customizable and highly modular.
What are Patterns? - ANSWER-Patterns are a series of operations that also collect data
on a host, process it, and update the CMDB, just as probes and sensors do. Patterns are GUI based, very intuitive, and minimize the need for scripting. Patterns are customizable and highly modular.
What are Schedules? - ANSWER-A Discovery schedule determines what the discovery run will search for, when it will perform the discovery and which MID Servers the discovery will use. Use the Discovery Schedule module to run Discovery on a regular, reoccurring basis, or even on demand.
What does Discovery find? - ANSWER-Computers, servers, printers, a variety of IP-
enabled devices, and the applications that run on them.
What can Discovery do after it finds a device? - ANSWER-It can update the CIs in your CMDB with the data it collects. A successful Discovery implementation populates the CMDB with relevant data, in a timely manner with as little overhead as possible.
What are the five (5) phases for planning and maintaining a deployment? - ANSWER-1. Identify important data
2. Gather Credentials
3. Plan MID Servers