Your customer complains that when their users click on the Configuration Item magnifier from the Incident form, that they are overwhelmed by the volume of CIs to choose from. They want to exclude certain types of CIs from the CI lists on the Incident. Problem and Change forms. What do you recommend to your customer?
Answer(s): B
The correct answer is B. Use the Principal CI class checkbox, to identify the CI classes that they want visible on the Incident, Problem, and Change forms.Here's a detailed justification:The ServiceNow platform provides a built-in mechanism to control which CI classes are displayed in the reference lookup on Incident, Problem, and Change forms using the "Principal CI class" checkbox on the CI Class Manager. This is the most direct and maintainable approach to address the customer's requirement. When the Principal CI class checkbox is checked for a CI class, only CIs belonging to that class or its subclasses will be shown when users use the Configuration Item lookup on those forms. This functionality avoids customization and reduces the complexity of the solution.Option A involves adding a custom field ("Show") to the base cmdb table and using a reference qualifier. While technically feasible, this requires schema changes and adds custom logic to the platform, which increases maintenance overhead and potential for future compatibility issues. Reference qualifiers can impact performance if not properly designed and used. Moreover, it doesn't leverage built-in functionality.Option C, creating an Access Control List (ACL), is primarily for controlling read/write access to data, not for filtering the results in a reference lookup. ACLs control who can see records, not which records appear in a list. Using ACLs to hide CIs would completely restrict access to those CIs for ITIL users, which isn't the stated goal. The customer only wants to filter the lookup list.Option D, a UI Action, would require custom scripting to filter the lookup list on the client-side. This adds unnecessary complexity and is less performant than using the platform's built-in functionality. UI Actions are best used for performing actions on records, not altering the display of reference lookups. Also, UI Actions are client-side and can be bypassed more easily.By using the "Principal CI class" checkbox, the customer can easily define which CI classes are relevant to Incident, Problem, and Change management, improving the user experience without resorting to customization. This approach is clean, maintainable, and leverages the native capabilities of ServiceNow. It's also less likely to be affected by ServiceNow upgrades than custom solutions.For more information on the CI Class Manager and Principal CI class, refer to the official ServiceNow documentation:ServiceNow Docs: CI Class Manager : https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/product/configuration-management/concept/c_CIClassManager.html
Incidents are stored in what table?
The correct answer is B. Incident [incident]. Here's why:In ServiceNow, the core table where incident records are stored is the "incident" table. This is the foundation of the Incident Management module.B: Incident [incident]: This is the direct and correct reference to the "incident" table within the ServiceNow platform. The "[incident]" notation specifically denotes the system name of the table. When you create an incident record, the data related to that incident is stored in this table.The other options are incorrect:A: Incident [sn_task_incident]: This table name is incorrect, while the prefix 'sn_' indicates a scoped application table, the correct scoped incident table name is not 'sn_task_incident'. C. Incident [task_incident]: The "task_incident" table does not exist as a standard, core table for incident storage in ServiceNow. D. Incident [sn_incident]: This table name is incorrect. 'sn_' indicates a scoped application table, the correct scoped incident table name is not 'sn_incident'.The "incident" table extends the "task" table, which provides common fields and functionalities shared across different process tables like Problem, Change Request, and Request. This inheritance is a core concept within ServiceNow's data model, promoting reusability and consistency. The "task" table contains fields like number, short description, assignment group, assigned to, state, and priority. The "incident" table then adds specific fields relevant to incidents, such as impact, urgency, and service.This standardized structure allows for reporting, workflows, and automation to be applied consistently across various IT service management processes within the ServiceNow platform. Understanding the correct table names is crucial for scripting, reporting, and customization within the ServiceNow environment.Here are some authoritative links for further research:ServiceNow Documentation - Tables: https://developer.servicenow.com/dev.do#!/reference/api/glide-platform/g_GlideRecordAPI (Search within the documentation for "incident" table) ServiceNow Community: https://community.servicenow.com/ (Search the community for discussions on the "incident" table)
Incidents can be created and managed in the workspace, using UI layouts that are tailored to different personas, processes, and interfaces. Examples include: •Default •Major incidents •Self Service •Mobile What are these UI layouts called in the Now Platform?
Answer(s): E
The correct answer is E. Views. Here's why:Views in ServiceNow control the arrangement and visibility of fields and sections on a form. They provide different layouts of the same record for different users or purposes. The question describes various tailored layouts for incident management (Default, Major Incidents, Self Service, Mobile). This aligns perfectly with the purpose of Views. These views optimize the interface based on the role or context of the user, thus improving the overall user experience.Form Layouts (A) and Form Designs (D) are primarily used for customizing the fields and their properties within a single form layout. While they contribute to how a view looks, they don't represent the overall UI layout concept described in the question.Workspaces (B) are broader environments designed for specific roles, encompassing multiple tools and functionalities, not just different layouts of a single form like an incident.Forms (C) are the basic containers for data entry and display in ServiceNow, but the question is specifically asking about the different layouts for incidents.Therefore, Views are the most appropriate answer as they directly address the creation of customized UI layouts catering to different personas, processes, and interfaces for managing incidents within the ServiceNow platform. They efficiently provide tailored displays of the incident record depending on the context.For more information, refer to the ServiceNow documentation on Views:ServiceNow Docs - Configure form views
The Major Incident Management (MIM) application is linked to the Incident management process, but the records have an additional set of States. What are these MI States?
Answer(s): A
Here's a detailed justification for why option A is the most likely correct answer regarding Major Incident Management (MIM) states in ServiceNow, along with supporting concepts and links:Option A: "Proposed, Accepted, Rejected, Cancelled" reflects the workflow of evaluating a potential major incident before it's officially declared as such. Major Incident Management, while integrated with Incident Management, has a distinct process focused on minimizing impact and resolving high-priority disruptions swiftly. Before an incident is promoted to a Major Incident, it often undergoes an initial assessment.Proposed: An incident is flagged as potentially major. Accepted: The incident is confirmed to meet the criteria for a major incident. Rejected: The incident does not meet the criteria for a major incident and remains a standard incident. Cancelled: The Major Incident is stopped, and the incident workflow returns to normal.Options B, C, and D, although containing states that might be associated with incident or problem management, don't accurately represent the additional states specific to the major incident promotion process. They may overlap with states used within the core incident workflow but miss the crucial evaluation phase.Major Incident Management in ServiceNow leverages automation and streamlined communication. Before invoking the full-fledged MIM process, it's crucial to determine if an incident qualifies based on pre-defined criteria (like number of users affected, business impact, or system outage). This is where the "Proposed, Accepted, Rejected" states come into play. The "Cancelled" state allows to roll back from a MI in some cases.In summary, the initial states within the Major Incident Management application's workflow primarily deal with the assessment of an incident's severity and whether it warrants the resources and processes associated with a major incident. Option A best reflects this evaluation process and is linked to common ITSM practices around escalating and managing urgent situations.Authoritative Links:ServiceNow Major Incident Management: While specific state details may vary across ServiceNow versions and implementations, understanding the overall process is key. Look for documentation on major incident management setup and configuration within your ServiceNow instance's help documentation. ITIL 4 Practice Guide - Incident Management: This document provides a general understanding of Incident Management within ITIL 4 framework. ( https://www.axelos.com/ )
What would you use to create Incident records, based on email sent by users or systems?
The correct answer is B. Inbound Flow Action. Here's a detailed justification:Inbound Flow Actions in ServiceNow are designed specifically to process incoming emails and trigger automated workflows based on the email content. They are the primary mechanism for handling email interactions within the platform, enabling functionalities such as creating or updating records. They allow administrators to define conditions and actions to be taken when an email matches specific criteria.When an email is received, ServiceNow's email engine processes it. If an inbound flow action is configured to match the email (based on sender, subject, body content, etc.), the flow is triggered. This flow can then parse the email content, extract relevant data (like the subject, body, and sender), and use this data to create or update records, like incidents.While Record Producers (A) are used to create records from the Service Portal, they don't directly process incoming emails. They're primarily user-driven and are accessed through a web interface. Data Collection Jobs (C) are used to import data from external sources, but they are not designed to monitor and react to incoming emails in real-time. Transform Maps (D) are used to map fields from an import set to a target table, often used after data has been imported from an external source, but they are not the initial processing point for emails.Inbound Flow Actions provide a flexible and powerful way to automate incident creation from emails, enabling faster response times and improved service management. They can handle various scenarios, such as creating incidents from automated system alerts or user-submitted requests via email. The ability to script within the flow allows for custom logic to handle complex email parsing and record creation scenarios.For further research, consult the official ServiceNow documentation on Inbound Actions and Flow Designer:Inbound Actions: https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/email-notifications/concept/c_InboundEmailActions.html Flow Designer: https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/administer/flow-designer/concept/flow-designer.htmlThese resources will provide in-depth information on configuring and utilizing Inbound Flow Actions for various email processing tasks in ServiceNow.
What tools are available to the assignee to help resolve an incident? (Choose two.)
Answer(s): A,B
The correct answer is A and B: Knowledge Articles and Known Errors.Justification:When an incident is assigned to a technician, the primary goal is to resolve it quickly and efficiently. ServiceNow provides several tools to assist with this.Knowledge Articles: These articles contain documented solutions to common problems or frequently asked questions. When resolving an incident, technicians can search the knowledge base for existing articles related to the issue. If a matching article is found, the technician can follow the documented steps to resolve the incident, saving time and ensuring consistent solutions. Accessing and utilizing knowledge articles promotes knowledge sharing and re-use within the IT service management framework. Known Errors: A known error is a problem that has a documented root cause and a workaround. When a technician encounters an incident, they can check if it's related to a known error. If it is, the technician can apply the workaround until a permanent fix is implemented, minimizing the impact of the incident. Using known errors is a proactive approach to incident management, addressing recurring issues efficiently.Why the other options are not the best fit:CI Class Manager: While important for understanding the configuration items (CIs) involved in an incident, the CI Class Manager's primary function is managing the CI hierarchy and not direct incident resolution. Enterprise CMDB Dashboard: This dashboard provides a broad overview of the Configuration Management Database (CMDB), including relationships between CIs. While helpful for understanding dependencies, it is not a direct tool for resolving individual incidents. Incident Overview Dashboard: This dashboard provides an overview of incident trends and metrics, useful for overall incident management but not for directly resolving a specific incident.In essence, Knowledge Articles and Known Errors directly assist technicians in resolving incidents by providing pre-existing solutions or workarounds, while the other options offer more broad, management-oriented information.Authoritative Links:ServiceNow Knowledge Management: https://docs.servicenow.com/bundle/vancouver-servicenow-platform/page/product/knowledge-management/concept/c_KnowledgeManagement.html ServiceNow Problem Management: https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/problem-management/concept/c_ProblemManagement.html
When you activate the ITSM Roles plugin, what additional granular roles are created for the Incident application? (Choose two.)
Answer(s): B,C
The activation of the ITSM Roles plugin in ServiceNow introduces more refined control over access to ITSMapplication functionalities, including Incident Management. Specifically, it creates granular roles tailored for specific actions.sn_incident_read is created to allow users to read or view incident records without the ability to modify them.This facilitates information accessibility for users who need to be informed about incidents but shouldn't make changes.sn_incident_write enables users to modify existing incident records. This is crucial for incident analysts,specialists, and managers who need to update incident details, statuses, assignments, and resolutions. It’s different from creating new incident records (which usually requires a more generic role, or is controlled through record producers).sn_incident_update and sn_incident_insert are not the roles specifically created by activating the ITSM Roles plugin for the Incident application.Therefore, sn_incident_read and sn_incident_write are the additional granular roles for the Incident application created with the ITSM Roles plugin activation. These roles provide more precise access control compared to broader roles and contribute to a more secure and well-governed ITSM environment.Further details on granular roles and ITSM roles plugin:ServiceNow Docs: ITSM Roles ServiceNow Community: Incident Management Roles
What are some good practices for guiding your customers' use of Notifications? (Choose three.)
Answer(s): A,B,C
The answer ABC is the most appropriate because it reflects practical and effective strategies for managing notifications during a ServiceNow ITSM implementation.A: Make sure Notification requirements and test plans are in the project scope from the start: Including notifications early ensures they align with business needs. A properly planned notification system is crucial for user satisfaction and adoption. Early inclusion also allows time for thorough testing, preventing disruptive surprises later. A well-defined scope reduces the chances of missed requirements or scope creep.B: Get input from Marketing department, regarding format of customer/caller facing notifications: The Marketing department has expertise in communication and branding. Their input can help create notifications that are professional, consistent with the company's image, and easily understood by users. Consistent branding helps in user confidence. The Marketing department also helps in using the company's voice in customer communications.C: Use templates to ensure consistency and ease of configuration: Templates promote consistency in content and structure, reducing errors. They streamline the configuration process and make it easier for administrators to maintain the notification system. Templates can be customized for different types of notifications while still adhering to a standard format.Why the other options are less suitable:D: Use incident.itil.role template as the master template to build all other ITSM templates: While leveraging existing templates is good, the incident.itil.role template is specific to incidents and ITIL roles. It's not a suitable base for all ITSM notification templates, as other modules (e.g., change, problem) may require different information and layouts. This approach would limit flexibility. E. When possible, maximize the quantity of email updates to customers: Bombarding users with emails is not a good practice. It can lead to information overload, decreased user engagement, and increased support requests. A well-designed notification system should send targeted, relevant updates at appropriate intervals.In conclusion: A proactive approach to notification requirements, collaboration with marketing, and the utilization of templates contribute to a well-defined and user-friendly notification system within ServiceNow ITSM.Authoritative Links:ServiceNow Documentation on Notifications: https://docs.servicenow.com/ (Search for "Notifications" and "Email Notifications")
Post your Comments and Discuss ServiceNow CIS-ITSM exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CIS-ITSM content, but please register or login to continue.