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

Check definitions

Check models

Check clones

Check mirrors

Check instances

{"CPU":100}

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

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

{"CPU":"100"}

Missing CMDB data

Defects

Alert correlations

Orphaned CIs

Anomalies

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

Transform and compose alert output

Event filter

Event options

Threshold

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.

An alarm

An alert

An incident

A notice

An event

A metric

evt_mgmt_integration

evt_mgmt_user

evt_mgmt_operator

evt_mgmt_admin

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

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.

Source, Type, Node, Resource, Metric Name

Source, DNS, Node, Additional info, Metric Name

Source, Type, DNS, Additional info, Metric Name

Source, Source Instance, Node, Type, Resource

Flapping

Closed

Reopen

Processed

Open, Reopen, Flapping, Closed

New, Updating, Waiting, Complete

Open, Updating, Swinging, Closed

Open, Warning, Flapping, Clear

Alert management rules

Task rules

Event rules

Alert correlation rules

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

Every 5 seconds

Depends on connectors Used

Every minute via a scheduled job

As soon as the event record is inserted via a business rule

All alert management rule will run, from the highest to the lowest Order of execution numbers.

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

All alert management rule will run, from the lowest to the highest Order of execution numbers.

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

alert_operator

evt_mgmt_user

evt_mgmt_operator

alert_user

Resource

Description

Source

Additional Information

Cloud Provisioning and Governance

Health Log Analytics

Agent Client Collector

Discovery

Service Mapping

Event Management

Critical

Error

Major

Minor

Warning

Clear

Every 30 seconds

Every 2 minutes

Every 10 minutes

Every 1 minute

Every 5 minutes

The server (.*)\..*

.*(\w+\Aw+VAw+).*

The server (.*)\s.*

The server (.*?)\„*

Metric_name

Message_key

Short_description

Additional_info

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.

Management, Instrumentation, and Discovery

Messaging, Integration, and Data

Monitoring, Insight, and Domain

Maintenance, Information, and Distribution

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

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

Once every minute

Every 2 minutes

Twice every minute

Every 5 minutes

Service level data model

Business service data model

Application service data model

Common service data model

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