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

Source Instance

Metric Name

Node

Resource

445

161

443

143

Alert management rules

Task rules

Event rules

Alert correlation rules

Severity of -1/OK

Type of Clear

Resolution State of Closing

Resolution State of Clear

Severity of 0/Clear

{"CPU":100}

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

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

{"CPU":"100"}

After 7 days

After 14 days

After 30 days

Never

Events

Checks

Parameters

Policies

Metrics

Scripts

The CMDB is a series of tables that contain only key hardware components located in critical paths within your platform that must be managed.

The CMDB is a dynamic list that tracks both the CIs within your platform and the relationship between those items.

All CIs stored in the CMDB must have an assigned IP address within your infrastructure.

A CI is any component within your infrastructure that needs to be managed in order to deliver Services.

To change the value of the message key

To create a custom action within a subflow

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

To automatically create an incident

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

Metric Registration

Metric Config Rules

Metric Type Actions

Metric to CI

No correlation rules have been defined

No event management rules have been defined

Application services are not operational

No CMDB is configured

The alert correlation property that enables grouping is set to false

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.

OpenVMS System

Microsoft Windows Server

Linux System

Microsoft Windows Desktop

Any system inside the customer firewall

Mac OS X System

1

2

3

4

evt_mgmt_integration

evt_mgmt_user

evt_mgmt_operator

evt_mgmt_admin

CI name, Fully qualified domain name, IP or MAC address

CI name, Webserver name, IP or MAC address

CI name, Fully qualified domain name, SSH public host keys

System class name, Fully qualified domain name, IP or MAC address

Two rules for every event

As many rules as possible

As few rules as possible

One rule for every event

Third-party monitoring tool connectors with out-of-box alert rules

GenAI and the ServiceNow large language model

Basic keyword matching in the alert description and tags

The unified service map and link view topology

Icinga

Sensu

SolarWinds

Nagios

Zabbix

Event Rules

Message Key

Alert Priority

Severity

XML

JSON

YAML

Comma separated

Enable multi-node processing

Increase the source polling interval

Ensure the bucket value in the event table is greater than 0

Increase the number of scheduled jobs processing events

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

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

Service level data model

Business service data model

Application service data model

Common service data model

Metric Name

Message Key

Type & Node

Description

Correlation ID

Node

Source

Severity

Message Key

Resource

Critical

Error

Major

Minor

Warning

Clear

5 seconds

30 seconds

60 seconds

120 seconds