10 free sample questions from a bank of 169, with the correct answers and explanations. No signup required — start practising right now.
1When creating an alert management rule, where would you specify a workflow to resolve a given condition?
From the Remediation tab
From the Actions tab
From the Launcher tab
In the Related Links section
Answer: B
The short version
B — Actions tab hosts remediation for alert rules. Alert management rules apply automated responses from the Actions tab, where remediation subflows and related responses are configured for matching alerts.
Key concepts in this question
Alert management rule: automation that evaluates alerts after creation and applies enrichment, task creation, or remediation based on filter conditions.
Actions tab: rule section that defines what happens when the filter matches, including remediation subflows, workflows, and notification behavior.
Remediation subflow: Flow Designer subflow launched to fix the underlying condition, such as restarting a service or running a diagnostic sequence.
Alert Info and Alert filter tabs: sections that define the rule identity plus the conditions selecting which alerts qualify, not the response itself.
Launcher and Related Links: UI elements for starting associated content or navigating to related records, not for binding remediation logic.
Why B is correct
ServiceNow documents three tabs for an alert management rule, with the Actions tab containing the remediation subflows section. That section is where an author selects the workflow or subflow to resolve the given condition. Choosing the Actions tab therefore places the remediation exactly where the platform executes it during alert processing.
Why the others are wrong
A. Remediation tab does not exist as a rule tab and confuses the Actions tab remediation section with a separate tab.
C. Launcher tab is not part of alert management rule configuration and does not hold remediation bindings.
D. Related Links section provides navigation shortcuts on the form, not a place to specify executable remediation logic.
CIS-EM exam tip
Remember Actions equals action: filter selects the alert, Actions fixes the alert with a subflow.
2What feature would you use to trigger a workflow or automatically generate tasks via templates?
Event rules
Task rules
Alert management rules
Alert correlation rules
Answer: C
The short version
C — Alert management rules trigger workflows and templated tasks. When an alert matches the rule filter, the Actions configuration can launch a remediation flow or auto-generate tasks from templates for operators.
Key concepts in this question
Alert management rule: post-alert automation layer that enriches alerts, assigns them, creates tasks, and launches remediation for matching conditions.
Workflow and task templates: reusable definitions that standardize response steps so each matching alert produces consistent follow-up work.
Event rule: pre-alert processing that normalizes events, sets severity and binding, and decides whether an alert should be created at all.
Task rule: narrower legacy concept sometimes confused with alert-driven task creation, but not the documented feature for workflow triggering.
Alert correlation rule: grouping logic that bundles related alerts together, rather than launching remediation or generating tasks.
Why C is correct
The documented purpose of alert management includes executing remediation workflows and automatically generating tasks via templates when alert conditions match. Event rules operate earlier on raw events, and correlation rules group alerts, so neither is the workflow trigger. Alert management rules are therefore the feature the question describes.
Why the others are wrong
A. Event rules transform and filter events before alert creation and do not launch alert remediation workflows.
B. Task rules is not the Event Management feature that binds workflows and task templates to alerts.
D. Alert correlation rules group related alerts for noise reduction instead of triggering workflows or tasks.
A — Idle alerts auto-close after 7 days by default. The platform does not keep stale open alerts forever, and the out-of-box idle threshold is one week, not two weeks or thirty days.
Key concepts in this question
Idle alerts: Alerts in Open state with no new matching events updating them for a sustained period, considered stale and eligible for automatic closure.
Automatic closure: Background processing that moves long-idle alerts to Closed without operator action to keep the Alert Console actionable and metrics clean.
Default threshold: The baseline number of days of inactivity that triggers closure before any administrator customization, defined in Event Management properties.
Alert lifecycle hygiene: Regular closure of stale alerts prevents console clutter, distorts fewer availability calculations, and focuses operators on active issues.
Why A is correct
A is correct because ServiceNow Event Management closes idle alerts after 7 days out of box. The timer tracks time since last update to the alert, and once seven full days pass with no new correlated event, the alert is closed automatically. Administrators can adjust the property, but the exam tests the default, which is consistently seven days across current releases.
Why the others are wrong
B. After 14 days describes a plausible retention window but is twice the actual default and applies to no out-of-box idle closure timer.
C. After 30 days is a common monthly cleanup interval in other tools, but ServiceNow uses a much shorter weekly default for idle alerts.
D. Never is incorrect because automatic closure is enabled by default, so stale alerts do not remain open indefinitely unless the property is disabled.
CIS-EM exam tip
Remember idle equals 7: one quiet week closes the alert unless your admin changed the default.
4What is used to correctly bind an alert to an application?
Correlation rules
Workflows
Classifiers
CI identification rules
Answer: D
The short version
D — CI identification rules correctly bind an alert to an application. Binding means resolving which configuration item and service the alert belongs to, and only identification logic provides authoritative, CMDB-aware resolution for application services.
Key concepts in this question
Alert binding: The process of populating the CI and application service fields on an alert from event data so impact, priority, and service mapping work correctly.
CI identification rules: IRE-based rules that use identifiers, reconciliation, and class hierarchy to match a discovered node to exactly one authoritative CI in the CMDB.
Correlation rules: Logic that groups related alerts into correlated groups to reduce noise, but does not determine which application a single alert belongs to.
Classifiers versus workflows: Classifiers help categorize events during processing, while workflows automate tasks, and neither performs authoritative CI-to-application resolution.
Why D is correct
D is correct because Event Management relies on CMDB identification to bind alerts to applications. When an event arrives, node data is matched through identification rules, ensuring the alert lands on the correct CI and inherits its service relationships.
Why the others are wrong
A. Correlation rules group already-bound alerts together and never decide the primary CI or application for an individual alert.
B. Workflows orchestrate response actions after binding, such as creating incidents, but do not resolve CI identity.
C. Classifiers assist event processing and categorization, yet they lack CMDB identification authority to bind to an application.
CIS-EM exam tip
Binding equals identification: if the question asks what ties an alert to an app, choose CI identification rules.
5If you wanted to create a quick response alert rule to open an Ask Jeeves search on the description of the alert, where would it configured?
Launch Applications
Remediation Workflows
Remediation SubFlows
Operator Workspace
Answer: A
The short version
Banked answer C is flipped to A after docs check. Launch Applications is the alert management action that opens a browser or search with alert description content, while remediation subflows run automated remediation logic and do not open interactive searches.
Key concepts in this question
Alert management rules separate filter logic from response actions. Filters decide which open updated alerts qualify. Actions include running subflows, remediation, opening incidents, launching applications, and launching URLs. Quick response that opens Ask Jeeves or web search is a client navigation action, not background remediation. Understanding this split is central to CIS-EM rule design.
Why A is correct
A Launch Applications is correct because docs list launching an application or URL in a browser as a supported alert management action, with the worked example of opening a search engine to search for data according to the description field. That matches the stem exactly, asking to open Ask Jeeves search on description. Vendor prose also says A Launch Applications, and community vote is unanimous for A.
Why the others are wrong
B Remediation Workflows is deprecated and workflow based remediation does not open browser search; docs advise using subflows instead of workflows for performance. C Remediation SubFlows executes base system subflows like acknowledge, close, or create incident, not interactive browser navigation. D Operator Workspace is a working environment for viewing alerts, not an alert rule action location for quick response configuration.
CIS-EM exam tip
On CIS-EM, link search or URL opening stems to Launch Applications or launch URL. Link auto acknowledge, close, or incident creation stems to Remediation SubFlows. When stem mentions description search, choose the browser navigation action immediately and move on.
6Where would you find the Priority Breakdown for an Alert?
Under the More Information section
Under the Activities section
Under the History section
Under the CI Problems section
Answer: A
The short version
A — Priority Breakdown lives under the More Information section. Alert Priority is a computed score with weighted contributors, and the console exposes its itemized math in More Information, not in activity or history streams.
Key concepts in this question
Alert Priority score: A numeric ranking computed from weighted factors such as business service, severity, CI type, and role that orders which alerts deserve attention first.
Priority Breakdown: The itemized view showing each contributing category, its score, and its weight, so operators can audit why one alert outranks another.
More Information section: The alert form area that surfaces computed diagnostics and enrichment details beyond the core state and assignment fields.
Activities and History: Timeline-oriented sections showing work notes, state changes, and updates, not the scoring formula behind priority.
Why A is correct
A is correct because ServiceNow places the Priority Breakdown in More Information on the alert record. Opening that section reveals the ordered contributors with score-times-weight math that produced the final priority value. This placement keeps diagnostic scoring separate from operational timelines, and the exam consistently tests this exact location for priority audit questions.
Why the others are wrong
B. Activities section shows journal-style collaboration and updates, never the weighted priority calculation.
C. History section shows field change audits over time, not the current priority factor decomposition.
D. CI Problems section relates to problem records linked to the CI, not to the internal priority scoring details.
CIS-EM exam tip
To audit priority math, look under More Information, never in Activities or History.
7Where does an operator give feedback on an automated alert grouping?
Feedback attribute on the virtual alert record
Feedback attribute on the child alert record
Feedback attribute on the event record
Feedback attribute on the alert record
Dropdown box on the alert group record
Answer: D
The short version
Banked answer C is flipped to D after docs check. Operator feedback on automated grouping is given on the parent alert record through the Feedback attribute, which only appears when the alert being modified is a parent alert and rates accuracy and usefulness of the group.
Key concepts in this question
Automated, CMDB, text, and tag grouping create a primary or virtual parent alert with secondary child alerts. Feedback trains and evaluates grouping quality. ServiceNow places that control on the parent, not on each child, event, or separate group record. Knowing where grouping metadata lives helps operators give correct feedback and helps admins troubleshoot grouping behavior in CIS-EM scenarios.
Why D is correct
D Feedback attribute on the alert record is correct because official view alert docs state the Feedback field appears only if the alert being modified is a parent alert, and the response provides feedback about accuracy and usefulness of the group. Vendor prose repeats the same parent alert condition. That directly matches giving feedback on an automated alert grouping from the operator view.
Why the others are wrong
A virtual alert record feedback is wrong because virtual primary is a grouping construct, docs place the field on the parent alert form itself. B child alert record is wrong because secondaries inherit group context and do not carry the group feedback control. C event record is wrong because events are pre alert raw inputs and have no grouping accuracy field. E dropdown on alert group record is wrong because no such separate group record control is documented for this feedback.
CIS-EM exam tip
For grouping feedback questions, look for parent alert wording. If an option mentions parent alert record or Feedback field on alert only for parent, choose it. Do not pick event, child, or virtual variants under time pressure.
8In your environment, no alert CMDB, automated, or text based grouping is occurring. What is most likely the problem?
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
Answer: E
The short version
E — The global grouping property is set to false, so no grouping occurs. When CMDB, automated, and text-based grouping all fail together, the shared switch that enables correlated alert groups is the most likely culprit, not missing individual rules.
Key concepts in this question
Correlated alert groups: Collections of related alerts joined by CMDB topology, automated similarity, or text similarity to reduce operator noise.
Global grouping switch: An Event Management property that must be true for any correlation engine to create groups, acting as a master enablement control.
Correlation rules: Individual definitions for CMDB, automated, and text grouping that only execute when the master switch permits grouping.
Common-cause diagnosis: When every grouping type fails at once, look for a platform-level control rather than three independent rule failures.
Why E is correct
E is correct because one false property explains total absence of all grouping. When the grouping switch is false, no CMDB, automated, or text groups form even if rules exist.
Why the others are wrong
A. No correlation rules defined would require all three rule families to be simultaneously absent, which is less likely than one disabled master switch.
B. No event management rules defined would break event-to-alert processing broadly, not selectively suppress only grouping while alerts still exist.
C. Application services not operational affect service impact calculation, but grouping can still occur on CI and text similarity without them.
D. No CMDB configured would break CMDB grouping only, while automated and text grouping could still function on event attributes.
CIS-EM exam tip
All grouping dead at once means check the master grouping property first.
9The additional information field is a JSON string that gives more information about an event. An example of a supported JSON string is:
{"CPU":100}
{"CPU":100,’Status":3}
{"CPU":"100","Status":3}
{"CPU":"100"}
Answer: D
The short version
D — Simple string-valued JSON with one key is the supported example. The additional information field accepts a JSON object string, and the clean single-pair form with a string value parses reliably for event ingestion.
Key concepts in this question
Additional information field: free-form JSON string on the event that carries extra context such as performance counters or custom attributes.
JSON string validity: the payload must be well-formed object syntax with correctly paired delimiters and consistent quoting around keys and string values.
Type coercion risk: mixing quoted and unquoted values or breaking quote pairing causes parse failure during web service or connector intake.
Event ingestion: ServiceNow validates incoming event fields against integration requirements before the event can proceed through processing.
Documentation example: the reference pattern shows a minimal object with one metric mapped to a string value as the safe baseline.
Why D is correct
The settled key selects the minimal well-formed object with a single string value, which satisfies the integration requirement for additional info without syntax errors. Options with mismatched quotes fail parsing, and multi-key variants shown here introduce formatting faults in the exam stem. The single-pair string-valued form is therefore the supported example among the choices.
Why the others are wrong
A. Numeric-only value form is not the documented supported example and risks type handling issues in this question set.
B. Mixed quoting with mismatched delimiters is invalid JSON and is rejected during event intake.
C. Multi-attribute variant shown here carries a quoting inconsistency and does not match the clean documented example.
CIS-EM exam tip
For additional info, picture a tiny clean object: one key, string value, perfect braces.
10In order for SNMP trap notifications to appear in ServiceNow as events, what option must be enabled in the required MID server?
MID SNMP trap listener
SNMP event manager module for MID
Event collector MID server extension
SNMP agent for MID
Answer: A
The short version
A — Enable the MID SNMP trap listener for traps to become events. Traps are pushed asynchronously from devices, so the MID Server needs an active listener to receive, normalize, and forward them to the instance event table.
Key concepts in this question
SNMP traps: Unsolicited UDP notifications sent by network devices on faults or state changes, requiring a listening receiver rather than polling.
MID Server role: The on-premise broker that bridges the customer network and the ServiceNow cloud for discovery, polling, and trap reception.
Trap listener: A MID capability that binds to the trap port, parses trap payloads, and forwards structured events into Event Management.
Event creation path: Listener output flows through connectors into the event table where event rules then bind, deduplicate, and promote to alerts.
Why A is correct
A is correct because ServiceNow documentation for SNMP trap events explicitly requires enabling the MID SNMP trap listener on the designated MID Server. Without that listener running, traps arrive at the host but are never captured or sent to the instance, so no events appear. Enabling it activates the receive path, after which traps show up as events ready for rule processing.
Why the others are wrong
B. SNMP event manager module for MID is not a named ServiceNow capability, and trap ingestion is handled by the listener feature.
C. Event collector MID server extension describes a generic collection idea but is not the documented trap listener switch.
D. SNMP agent for MID reverses the roles, since devices host agents and the MID hosts the trap receiver, not another agent.
CIS-EM exam tip
Traps need a listener: no MID trap listener means no trap events in ServiceNow.