Where do you enable the Search as feature for an incident?
Answer(s): C
The correct answer is C. Related Search Results table configuration . Here's why:The "Search As" feature in ServiceNow's Incident Management is enabled by configuring the Related Search Results table. This table defines which knowledge bases and search sources are used to provide relevant search results to users creating or viewing incidents. These results are displayed on the incident form, helping users quickly find solutions and resolve incidents faster, potentially deflecting them by directing to existing knowledge.Here's a detailed justification:1. Related Search Results Configuration: This is the central location for defining how search is performed within the context of an incident. This includes specifying which knowledge bases, catalogs, or other search sources are consulted. It directly controls what results are displayed to the user while working on an incident.2. Incident Deflection: Enabling relevant search results is a key component of incident deflection. By surfacing relevant knowledge articles or service catalog items, users might be able to resolve their issue themselves, thereby preventing the need to create a new incident or expediting the solution of existing ones.3. incident.deflection system property: This system property may control whether incident deflection generally occurs, but it doesn't dictate what sources are searched to find possible solutions. It is more of a global on/off switch for the overall deflection functionality.4. Incident Properties application: While the Incident Properties application contains settings related to incident management, it is unlikely to specifically manage search result configurations. It deals with broader configurations such as assignment rules and SLAs.5. Incident form design: While the incident form design controls the layout and fields displayed on the incident form, it doesn't control the underlying search query or source of the related search results. It only controls where the results are displayed, not how they are generated.In summary, the "Search As" feature in ServiceNow Incident Management is directly managed through the Related Search Results table configuration. This configuration allows administrators to specify which knowledge bases and search sources are consulted to provide relevant search results to users, enabling incident deflection.Authoritative Links:ServiceNow Documentation on Contextual Search: https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/contextual-search/concept/c_ContextualSearch.html ServiceNow Documentation on Incident Deflection: (Search ServiceNow Documentation for "Incident Deflection")
If the Assignment group is empty on an incident record, what happens when an agent that is a member of a single user groups clicks the Assign to me UI action?
Answer(s): B
The correct answer is B. The Assignment group field is populated with agent’s user group.Here's a detailed justification:ServiceNow's "Assign to me" UI Action is designed to streamline incident assignment. When the Assignment group field is empty, and an agent clicks "Assign to me," the system attempts to automatically assign the incident to a relevant group and the agent. The system checks if the agent is a member of one group, then that group is automatically assigned, and the incident is assigned to the agent simultaneously. This is a core feature that enhances efficiency by reducing manual effort and improving response times.The behavior is hardcoded within the system's UI Action script and assignment rules that drive the default "Assign to Me" functionality. The ServiceNow platform prioritizes intelligent automation to improve operational effectiveness. If the agent were part of multiple assignment groups, the behaviour would prompt the agent to select from which group to assign as that's not the case in the given question context.Options A and C are incorrect because the system is designed to automate the process where possible. Option A incorrectly implies a manual selection process even when only one group exists for the agent. Option C is also incorrect because, by default, the system does not simply return an error; instead, it attempts to find the right assignment for the given incident. Option D is incorrect because the system will populate the Assignment Group field to the agent's single user group membership.
A problem record is the Parent to what record?
Answer(s): D
The correct answer is Problem Task.A Problem record in ServiceNow is designed to investigate the root cause of one or more incidents. To effectively manage this investigation, the Problem record can be broken down into smaller, manageable units of work. These units of work are represented by Problem Tasks. Each Problem Task can be assigned to different individuals or teams, focusing on specific aspects of the problem investigation, such as data gathering, testing, or code review. A Known Error article documents the identified root cause and a workaround (if available), but it's an outcome of the Problem investigation, not a child record. A Workaround provides a temporary solution to an incident, but it's typically associated with incidents directly, or possibly documented within a Known Error article, but isn't directly parented by a Problem record. While a Problem can be created as a result of a Major Incident or be related to Incidents, Major Incident and Related Incidents are not child records of Problem.Therefore, Problem Tasks are directly associated with and dependent on the parent Problem record. The lifecycle of a Problem Task contributes to the overall lifecycle of the Problem record, ultimately aiming to resolve the underlying issue and prevent future incidents. Problem Tasks enable a structured approach to problem management within ServiceNow's IT Service Management (ITSM) framework.Further research:ServiceNow Problem Management Documentation: https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/problem-management/concept/problem-management.html
When you create a problem from an incident, impact, urgency and priority are automatically populated, from the incident record. Your problem management process owner wants the problem manager to be responsible for assessing the impact and urgency on the problem, so they don't want the values from incident to be copied over. What module would you use to make this adjustment?
The correct answer is B. Problem > Administration > Problem Properties . Here's why:The scenario requires modifying the system's behavior when creating a Problem record from an Incident record, specifically regarding the automatic population of Impact and Urgency fields. We need to control the data transfer between these two record types.Option A (System Policy > Rules > Priority Lookup Rules) is incorrect because Priority Lookup Rules determine the priority of a task based on Impact and Urgency, but don't govern the initial data transfer from an Incident to a Problem.Option B (Problem > Administration > Problem Properties) is the correct answer because this module is specifically designed to configure settings related to the Problem Management module. It provides settings to control how Problem records are created, managed, and processed. Critically, it contains properties governing the automatic population of fields when creating a Problem from other records like Incidents. You can typically find settings to disable the copying of specific fields from the Incident record.Option C (ITSM > Administration > Properties) is a more general area for ITSM properties, but it's less likely to contain granular settings specifically governing the interaction between Incidents and Problems.Option D (Incident > Administration > Incident Properties) deals with configurations for the Incident Management module, not the Problem Management module. It focuses on how Incidents are created and managed, but doesn't control how Problems are populated from Incidents.Therefore, to control the automatic population of Impact and Urgency when creating a Problem from an Incident, the "Problem Properties" module is the most appropriate place to make this adjustment. It provides the specific configuration settings to customize the behavior of the Problem Management module to meet the process owner's requirements.Further research:ServiceNow Product Documentation on Problem Management Configuration: https://docs.servicenow.com/ (Search for "Problem Management Properties" or "Configure Problem Management")
As of Quebec, Problem task records will move automatically from one state, to another state, provided the required fields are filled. What are those states?
The correct answer is C. New to Assess . Here's why:In ServiceNow's IT Service Management (ITSM) module, specifically within the Problem Management workflow as of the Quebec release, a Problem task record automatically transitions from the "New" state to the "Assess" state when the necessary required fields are populated. This design facilitates a smooth and automated progression within the initial stages of the problem task lifecycle. The automation is driven by workflow configurations within the ServiceNow platform.The transition from "New" to "Assess" signifies the commencement of the initial evaluation and impact assessment of the problem task. Required fields ensure that essential information is gathered before the assessment phase begins. This helps streamline the assessment process. The other options are incorrect because they do not represent the standard first step in the automatic workflow transition for Problem tasks upon initial data entry. The system expects that before any action is taken, an assessment of the problem task is needed.The "Assess" state involves analyzing the problem task to understand its scope, impact, and priority. This assessment informs subsequent steps, such as assigning the task to the appropriate team or individual and determining the necessary actions to resolve the issue. This automation reduces manual steps and ensures a consistent process for handling problem tasks.For further information on ServiceNow ITSM and Problem Management workflows, consult the official ServiceNow documentation:ServiceNow Product Documentation: https://docs.servicenow.com/ ServiceNow Community Forums: https://community.servicenow.com/
A new problem manager wants to know how to create reports for monitoring problem management activities. What do you recommend they do before creating new reports?
The correct answer is C. Go to Reports > View/Run > All, then search for Problem reports.Here's why: Before creating new reports, the problem manager should first explore the existing reports. ServiceNow provides a robust reporting engine, and many standard reports related to problem management already exist. Navigating to Reports > View/Run > All allows the user to access all available reports. Searching for "Problem reports" will filter the list to show relevant reports that are pre-configured. This approach helps avoid redundant effort and provides a baseline understanding of the available data and reporting capabilities. The problem manager can then determine if an existing report can be modified to meet their needs or if a completely new report is truly necessary. Option A (Service Catalog) is generally used for requesting new services or applications, not reports. Option B (Performance Analytics) is useful for more advanced analysis and trending, but it is premature before exploring existing reports. Option D (sn_report_creator role) might be required eventually, but it's not the first step. Option E (data collection jobs) is more relevant to ensuring data is being collected for reporting, but not essential as an initial step. Therefore, exploring pre-existing reports is the most logical starting point.ServiceNow Documentation - Reports: https://docs.servicenow.com/bundle/utah-platform-administration/page/use/reporting/concept/c_Reporting.html
Your customer wants to know why users with the problem_coordinator role can Communicate workarounds, and fixes; but users with problem_task_analyst cannot. How do you explain this?
Answer(s): A
The most appropriate answer is A. The problem_coordinator role in ServiceNow IT Service Management (ITSM) is typically assigned to individuals responsible for managing the overall problem management process, including communication. They are responsible for conveying accurate and helpful information to users regarding workarounds and fixes.The problem_task_analyst role, on the other hand, is often focused on the technical investigation and resolution of problem tasks. While they possess valuable technical knowledge, their communication may not be appropriately tailored for end-users. Sharing raw technical details directly with end-users may lead to confusion and frustration, rather than providing helpful workarounds or updates. Therefore, it's logical that the problem_coordinator acts as the gatekeeper for such communications, filtering and translating technical information into user-friendly language. This approach ensures clarity and prevents the dissemination of potentially confusing or irrelevant data to end-users. The problem coordinator ensures the communicated workaround or fix is approved and ready for dissemination.Options B, C, and D are less likely to be the primary reason. Role-based access control in ServiceNow dictates what users can do, and for effective communication with the end-users, Problem Coordinators are generally given this responsibility.For further reading, refer to ServiceNow's official documentation on roles and responsibilities within the Problem Management process:ServiceNow Docs: https://docs.servicenow.com/ (Search for "Problem Management roles" within the documentation)
A user wants to know what makes the Known Error knowledge base in ServiceNow different from all other knowledge bases. How should you respond?
Here's a detailed justification for why option D is the most accurate answer:Option D, "The Known Error knowledge articles use a template, which includes the Workaround and the Cause," correctly highlights the key distinguishing feature of the Known Error knowledge base. Known Error articles are specifically structured to document not just the symptoms or problems (as might be found in other knowledge bases), but critically, to capture a Workaround (a temporary solution to mitigate the problem) and the underlying Cause (the identified root cause of the problem). This targeted structure sets it apart.Options A, B, and C are less accurate or misleading. While A touches on problems under investigation, it fails to emphasize the critical element of the Workaround that defines a Known Error. B incorrectly highlights that the sn_known_error_write role grants the ability to create and modify Known Error records, not just articles. C incorrectly states that the sn_problem_write role is needed to create known error articles. While ProblemManagement processes often trigger the creation of Known Error articles, permission is determined by the sn_known_error_write role, and users with write access can create general knowledge articles if they have the proper roles and permissions.The structured template for Known Error articles, including fields for Workaround and Cause, is fundamental to its purpose within IT Service Management. This structure facilitates rapid problem resolution and knowledge sharing, enabling service desk agents and other users to quickly find temporary fixes and understand the underlying root cause, even before a permanent fix is deployed. This makes option D the most comprehensive and accurate differentiation.Further research:ServiceNow Documentation on Known Error Management: Search the ServiceNow documentation portal for "Known Error Management" to find detailed information about the feature and its configuration.The Known Error knowledge base's specific structure is key to its function in proactive problem management and quick resolution.
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.