Text preview & study summary

ServiceNow CIS-ITSM - IT Service Management Implementation - Incident Problem Change CMDB SLA Catalog

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

A company wants to implement a major incident process where P1 incidents automatically notify senior management and create a dedicated communication bridge. Which ServiceNow ITSM features should be configured?

Answer choices

  • A. A business rule that sends emails and creates a conference bridge record when priority = 1

  • B. Major Incident Management workflow with automatic escalation, stakeholder notification groups, and a communication plan record linked to the major incident (Correct)

  • C. An SLA definition that triggers when P1 incidents breach their response time

  • D. A Change Management emergency change linked to the P1 incident

Explanation

ServiceNow's Major Incident Management process (part of ITSM Pro) includes dedicated features: (1) Major Incident criteria that auto-promotes incidents to Major Incident status based on conditions; (2) Automatic creation of a communication plan with predefined stakeholder groups; (3) Major Incident workbench for coordinating response; (4) Automated notification workflows to executives and senior management; (5) Audit trail of all response activities. Simple business rule emails (option A) lack the structured coordination features. SLAs measure timelines but don't coordinate response. Emergency Change Management may be linked but isn't the primary tool for incident response coordination.

Question 2

A ServiceNow ITSM implementation needs to support a "Virtual Agent" chatbot that can help users create incidents and check the status of their requests. What configuration is required?

Answer choices

  • A. Deploy a custom-coded chatbot using third-party platforms and integrate via REST API

  • B. Configure Virtual Agent Designer (NLU topics, conversation flows, fulfillment actions) within ServiceNow, connecting to ITSM tables and flows (Correct)

  • C. Create a simple FAQ widget on the Service Portal

  • D. Configure an email autoresponder for common incident types

Explanation

ServiceNow Virtual Agent is a native platform capability (part of Now Intelligence). Configuration includes: (1) Virtual Agent Designer — create conversation Topics (intents like "Create Incident" or "Check Request Status") using NLU (Natural Language Understanding); (2) Conversation flow nodes — capture user information through dialogue; (3) Fulfillment — connect to FlowAPI, GlideRecord, or ServiceNow Spoke actions to create/query records; (4) Integration channels — deploy on Teams, Slack, web, mobile. No third-party development is needed. The Virtual Agent integrates natively with ITSM workflows and provides 24/7 self-service. Third-party chatbots (option A) require significant integration effort.

Question 3

A company is implementing the Service Portal and wants the incident creation form to automatically populate the "Affected User" field with the logged-in user's information. What is the MOST appropriate way to implement this?

Answer choices

  • A. A business rule on the incident table that sets the caller after insertion

  • B. A Default Value on the Affected User field in the Incident table definition set to `javascript:gs.getUserID()` (Correct)

  • C. A Client Script on the Portal form that reads `g_user` and sets the field

  • D. A Transform Map that maps the user during import

Explanation

Setting a Default Value on the `caller_id` (Affected User) field in the Incident table definition is the cleanest approach. In the field's Default Value, you enter `javascript:gs.getUserID()` — this server-side script runs when a new incident record is created and automatically sets the caller to the current user's sys_id. This works across all entry points: the main UI, Service Portal, mobile app, and API calls when session context is available. A Client Script (option C) would only work in the browser UI and would need to handle the g_user object. Default values are the standard platform mechanism for auto-populating fields with user context.

Question 4

A company has implemented Knowledge Management and wants to measure the effectiveness of their knowledge base. The Knowledge Manager asks: "How many incidents were resolved using a knowledge article, and which articles are used most?" How can this be reported in ServiceNow?

Answer choices

  • A. Count knowledge articles and cross-reference with resolved incidents manually

  • B. Use the "Linked Knowledge" feature where agents attach KB articles to incidents; report on `m2m_incident_kb_knowledge` (or similar) relationship table and kb_knowledge usage statistics (Correct)

  • C. Review agent work notes for article references

  • D. Export both tables to Excel and use VLOOKUP to match

Explanation

ServiceNow tracks knowledge usage through relationship records. When an agent links a KB article to an incident (via "Knowledge" related list or the Knowledge Search widget), a many-to-many relationship record is created. The `kb_knowledge_task_mtom` table tracks these links. ServiceNow also tracks article views and ratings in `kb_use` and `kb_feedback` tables. You can create reports showing: (1) Number of incidents per article (most-used articles); (2) Incidents resolved after KB article was linked (deflection rate); (3) Article usefulness ratings. The ServiceNow Knowledge Analytics dashboard provides these metrics natively. Manual work notes analysis (option C) is not scalable or reliable.

Question 5

During an ITSM implementation, the client asks whether ServiceNow supports integration with monitoring tools like Nagios or Dynatrace to automatically create incidents when alerts fire. What is the recommended integration pattern?

Answer choices

  • A. Configure monitoring tools to send emails to ServiceNow, creating incidents via email inbound actions

  • B. Use ServiceNow IT Operations Management (ITOM) Event Management with the monitoring tool's REST or SNMP integration to receive events, deduplicate them, and auto-create/update incidents based on alert policies (Correct)

  • C. Have an operations team manually create incidents for each monitoring alert

  • D. Install the monitoring agent on the ServiceNow application server

Explanation

ServiceNow IT Operations Management (ITOM) Event Management is designed for this integration pattern: (1) Monitoring tools (Nagios, Dynatrace, Zabbix, PagerDuty) send events to ServiceNow via REST, SNMP, or native connectors; (2) Event Management deduplicates and correlates events (preventing alert storms from creating thousands of incidents); (3) Alert rules convert significant events into Alerts; (4) Alert Action policies automatically create, update, or resolve incidents based on alert conditions; (5) CMDB CI lookup adds CI context to incidents. This reduces false-positive incidents, correlates related alerts, and provides CI-enriched context. Email-based integration (option A) lacks structured data and deduplication. Manual creation (option C) introduces lag and human error.