CIS-EM Certified Implementation Specialist - Event Management Exam Questions and Answers

The number of unique nodes that can send events to the instance

The number of connectors and listeners it will collect data from

The number of connectors it will collect data from

The number of CIs in the CMDB that it will be monitoring

To automatically generate incidents from linked alerts

To manage user permissions across teams

To visualize tag-based alert groups

To update the CMDB dependency map

It is a connection point between a ServiceNow instance and the MID Server.

It contains probe records to be executed on the customer’s network.

It holds jobs that the MID Server needs to perform.

It is a connection point between a hardware CI on a customer’s network and the MID Server.

It contains records of CIs that the ServiceNow admin has submitted for entry into the CMDB.

Resource

Message Key

Node

Metric Name

XML

JSON

YAML

Comma separated

Service level data model

Business service data model

Application service data model

Common service data model

Ensure all Event Management – process events jobs are set to a Ready state

Verify that the Bucket field in the event table is set to zero (0)

Add additional event processor jobs

Ensure multi-node event processing is disabled

Alert groups

Manual application services

Discovered application services from Service Mapping

Correlation groups

Technical services

{"CPU":100}

{"CPU":100,’Status":3}

{"CPU":"100","Status":3}

{"CPU":"100"}

Every 120 seconds

Every 5 seconds

Every 40 seconds

Every 60 seconds

Every 10 seconds

Assign a MID Server to the connector

Enter credentials for the connector

Debug the connector

Test the connector

Activate the connector

Communication with the MID server is lost

The amount of host memory being used by the agent exceeds a threshold

Communication with the ServiceNow instance is lost

The amount of host disk space used by the agent exceeds a threshold

The amount of host CPU being utilized by the agent exceeds a threshold

The Alert Priority score 3106020.001 was calculated according to the following factors, ordered by their respective priority (2018-06-01 19:34:01 GMT) Category (Score, Weight)

1. Business services – (3.0, 1000000)

2. Severity – (1.0, 100000)

3. CI type – (60.0, 100)

4. Role – (2.0, 10)

5. Secondary – (0)

6. State – (1.0, 0.001)

The Alert Priority score 4406020.001 was calculated according to the following factors, ordered by their respective priority (2018-05-31 20:04:47 GMT) Category (Score, Weight)

1. Business services – (4.0, 1000000.0)

2. Severity – (4.0, 100000.0)

3. CI type – (60.0, 100.0)

4. Role – (2.0, 10.0)

5. Secondary – (0)

6. State – (1.0, 0.001)

The Alert Priority score 3306020.001 was calculated according to the following factors, ordered by their respective priority (2018-05-31 19:56:54 GMT) Category (Score, Weight)

1. Business services – (3.0, 1000000.0)

2. Severity – (3.0, 100000.0)

3. CI type – (60.0, 100.0)

4. Role – (2.0, 10.0)

5. Secondary – (0)

6. State – (1.0, 0.001)

They should be processed in the order in which they were received.

Additional_info

Message_key

Metric_name

Short_description

Every 30 seconds

Every 2 minutes

Every 10 minutes

Every 1 minute

Every 5 minutes

After 7 days

After 14 days

After 30 days

Never

The MID Web Server needs to be Restarted

The MID Web Server needs to be Started

An invalid secret key is being passed in the header information of the URL for the REST request

An invalid password is set in the MID Web Server Context

Python

Regex

sed/awk

JavaScript

Alert management rules

Event action rules

Event rules

Scheduled jobs

Java and Groovy scripts

A business service

A technical service

An application service

A manual service

A scoped service

The service is a manual service

The service is not set to operational

The service was created through Service Mapping

The service is a technical service

Alert00l0042

Alert0010003

Alert00l0075

Alert00l0074

ServiceNow is installed within your datacenter providing you complete control

All applications are built on the Oracle database standard, providing uniformity across products

All applications that are built by ServiceNow utilize the same data model and code base

ServiceNow runs on supported Windows servers and is managed through Windows Update

A single table houses all data elements within ServiceNow

ServiceNow utilizes the AWS MariaDB cloud database structure, providing a single system of record

To populate events with more meaningful information

To manage team roles and permissions

To transform and compose event rules

To generate alerts populated with more meaningful information

JavaScript

Groovy script

PowerShell script

Regex statement

Missing CMDB data

Defects

Alert correlations

Orphaned CIs

Anomalies

The process responsible for defining, analyzing, planning, measuring, and improving all aspects of the availability of IT services

The process responsible for ensuring the capacity of IT Services and IT infrastructure is able to deliver agreed upon service level targets in a cost-effective manner

The process responsible for recovery action and planning through machine learning

The process responsible for monitoring all abnormal occurrences throughout the IT infrastructure, allowing for normal operations, and detecting and escalating exception conditions

Check definitions

Check models

Check clones

Check mirrors

Check instances

To create a customized pull connector to retrieve events on behalf of an event source

To automatically populate the Configuration Management Database (CMDB)

To parse a nodename out of your raw event data in an event rule

To run as part of a remediation workflow for IT alerts that fail to execute

All Primary, Open alerts and anomaly alerts with a Severity of Critical, Major, Minor, and Warning that are not in Maintenance mode

All Primary and Secondary Open alerts and anomaly alerts with a Severity of Critical, Major, Minor, and Warning that are not in Maintenance mode

All Primary alerts with a Severity of Critical, Major, Minor, Warning that are not in Maintenance mode

All Primary, Open alerts with a Severity of Critical, Major, Minor, and Warning that are not in Maintenance mode

All Primary and Secondary Open alerts with a Severity of Critical, Major, Minor, and Warning that are not in Maintenance mode

To improve service availability by helping IT staff pinpoint service issue causes and evaluate the impact of planned changes.

To increase service agility and produce fast, predictable results by automating manual, routine, error-prone tasks.

To rapidly configure and launch secure, agentless discovery of hardware and software resources and their relationships.

To proactively warn against possible service outages using a range of advanced predictive machine learning methods.