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

Only the event rule with the highest Order of execution number will run.

Only the event rule with the lowest Order of execution number will run.

All event rules will run, from the lowest to the highest Order of execution numbers.

All event rules will run, from the highest to the lowest Order of execution numbers.

This requires a minimum of three MID Servers - two for Event Management and one additional MID Server dedicated for use by Operational Intelligence (OI).

This requires a MID Web Server in addition to the MID Server.

Nothing additional is required; this is handled by the MID Server.

This requires a minimum of two MID Servers - one for Event Management and one additional MID Server dedicated for use by Operational Intelligence (OI).

Source, type. node, resource, and metric name

Source, source instance, node, and resource

Source, type. node, and metric name

Source, source instance, node, and type

Source, type. node, resource, and time of event

CI Name, DNS, IP, MAC Address

System class name, FQDN, IP or MAC address

CI name, FQDN, SSH public host keys

CI Name, FQDN, IP, MAC Address

Ready

Ignored

Error

Processing

Transform and compose alert output

Event filter

Event options

Threshold

Assign a MID Server to the connector

Enter credentials for the connector

Debug the connector

Test the connector

Activate the connector

Event field mapping

Event processing jobs

Transforms

Event Filler

Inbound actions

Every 120 seconds

Every 5 seconds

Every 40 seconds

Every 60 seconds

Every 10 seconds

Event Connectors, Metric Policies, Log Data Inputs

Event Management, Metric Policies. Log Monitoring

Event Management, Metric Intelligence, Log Monitoring

Event Connectors, Metric Intelligence, Log Data inputs

Node

Source

Severity

Message Key

Resource

Event Management and Operational Intelligence

ITOM Visibility

Discovery and Service Mapping

Cloud Management

The value of the alert’s category and its relative weight

The value of the alert’s category and its Priority Group

The value of the alert’s Severity and its Priority Group

The value of the alert’s Severity and its relative weight

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

Fluctuating

Swinging

Flipping

Flapping

Icinga

Sensu

SolarWinds

Nagios

Zabbix

Metric Registration

Metric Config Rules

Metric Type Actions

Metric to CI

In the right-click menu of an alert list, select Open in Workspace

By appending/workspace to your instance URL

The application navigator Alerts Console menu item

The application navigator Alert Intelligence menu item

Within an open alert record, click the Open in Workspace button

Select the Lists tab in operator workspace

Transform and Compose Alert Output lab

Event rule info tab

CI Binding tab

Event Filter tab

CMDB identification and reconciliation engine (IRE)

Unified service map

Dependency view map

CMDB class manager

win-ces882ierw is one of your hottest Configuration Items (CIs) that is currently experiencing a high probability of anomalies and should be checked immediately

win-ces882ierw is one of your hottest Configuration Items (CIs), but is currently experiencing a low probability of anomalies

win-ces882ierw is one of your customized list of monitored Configuration Items (CIs) that is currently experiencing a high probability of anomalies and should be checked immediately

win-ces882ierw is one of your customized list of monitored Configuration Items (CIs), but is currently experiencing a low probability of anomalies

Execute remediation subflows

Execute remediation workflows

Launch applications

Evaluate business rule

Create a service catalog request

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.

5 seconds

30 seconds

60 seconds

120 seconds

Alert management rules

Event action rules

Event rules

Scheduled jobs

Java and Groovy scripts

Every 30 seconds

Every 2 minutes

Every 10 minutes

Every 1 minute

Every 5 minutes

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

Metric Name

Source

Classification

Node

Severity

.*(\w+\.\w+\.\w+).*

The server (.*)\s.*

.*\s(\w+\.\w+\.\w+).*

the server (.*).*

Alert Insights

Incident List View

CMDB Health Dashboard

Event Management Overview page

In the event rule, set the Severity to 0

In the alert rule, set the Severity to 0

In the alert rule, set the Severity to -1

In the event rule, set the Severity to -1