Problem management provides what benefits for Incident management? (Choose two.)
Answer(s): A,B
The correct answer is A and B. Problem Management, when integrated with Incident Management in ServiceNow, offers significant benefits related to reducing future incidents and providing faster incident resolution.Option A, "Solutions implemented reduce future incidents," is accurate because Problem Management aims to identify the root cause of recurring incidents. By resolving these underlying problems and implementing permanent fixes, the likelihood of similar incidents occurring in the future decreases substantially. This proactive approach reduces the overall incident volume, minimizes disruptions, and improves service stability. The Problem Management process ensures that the root cause is investigated, documented, and addressed, ultimately leading to more reliable services.Option B, "Published workarounds help quickly resolve incidents," is also correct. During the problem investigation process, temporary solutions or workarounds are often identified to mitigate the impact of the problem while a permanent fix is being developed. These workarounds are documented and made available to Incident Management teams. When a new incident arises that is related to the known problem, Incident Management staff can quickly apply the published workaround to restore service rapidly, minimizing downtime and user impact.Option C, "Problem investigations automatically triggered for multiple user incidents," is not typically a direct benefit. While multiple related incidents might suggest the need for a problem investigation, it's not usually an automatic trigger within the standard ServiceNow implementation. Instead, incident thresholds or human analysis often prompt the creation of problem records.Option D, "Incident managers authorize problem investigations," is incorrect. Typically, Problem Managers or designated roles within the Problem Management process initiate and authorize problem investigations based on incident trends, severity, and potential impact. Incident Managers generally focus on restoring service through Incident Management processes.Therefore, the key benefits of Problem Management for Incident Management are the long-term reduction of incident volume through root cause resolution and the short-term improvement of incident resolution speed through readily available workarounds.Authoritative links:ServiceNow Documentation - Problem Management: https://docs.servicenow.com/bundle/utah-it-service-management/page/product/problem-management/concept/c_ProblemManagement.html ITIL 4 Problem Management Practice Guide: Search for ITIL 4 Problem Management practice guide, available from various sources including AXELOS. This guide provides a comprehensive overview of the Problem Management practice and its benefits.
A tester reports a bug, because they submitted a Known Error article from a Problem record, but it is not visible from the Known Error database. What could cause this?
Answer(s): A
The correct answer is A. The article is in draft state, but has not been published.Here's why:Known Error articles, like other Knowledge Base articles in ServiceNow, typically have a lifecycle. When an article is created from a Problem record, it often starts in a "Draft" state. In this state, it's not yet visible to end-users or even ITIL users in the wider Knowledge Base. It requires review, approval, and publication before it becomes generally available. This ensures quality control and prevents premature or incorrect information from being disseminated.Option B is incorrect because the "Problem Management Best Practice - Madrid - Knowledge Integration" plugin enables integration between Problem and Knowledge, enabling creation of Knowledge articles from Problems. If it wasn't active, the article might not have been created from the problem record in the first place, but the question states that it was created. This plugin doesn't control the visibility of draft articles.Option C is less likely because User Criteria restricts access to published articles. If the article was published but the user criteria were incorrect, then the tester would have access problems for any published article in that particular Knowledge Base, rather than just the one they submitted. This is highly specific to one article, therefore the problem likely lies with the article itself rather than the global knowledge base.Option D is incorrect because being an itil user usually grants access to create and view most Knowledge Base articles. The problem is the article's visibility, not the tester's permissions (which could overlap if the article wasn't published).Therefore, the most probable cause is that the Knowledge Article associated with the Known Error is in a draft state and requires to be published before it is visible in the Knowledge Base.Further research on ServiceNow Knowledge Management and Knowledge Article states can be found here:ServiceNow Docs - Knowledge Management ServiceNow Community - Knowledge Article Workflow
Where can a change manager define the conditions that must be met before a change request can move from one state to another?
The correct answer is A. Model State Transition Conditions .Model State Transition Conditions within ServiceNow's IT Service Management module provide the functionality to enforce specific requirements before a change request transitions from one state to another. These conditions act as gates, ensuring that crucial criteria are fulfilled, thereby improving the overall quality and control of the change management process.By configuring these conditions, Change Managers can define granular rules based on various factors, such as mandatory fields being populated, specific approvals being obtained, risk assessments being completed, or related tasks reaching a particular status. This enables a structured and consistent approach to change execution, minimizing the risk of premature or incomplete transitions.For example, you might define a condition that a change request cannot move from "Assess" to "Authorize" unless the risk and impact assessments are marked as "Complete" and a CAB approval is granted. This prevents the change from proceeding without the necessary due diligence and approvals.Dictionary Overrides (B) are primarily used to customize field properties, such as making a field read-only or mandatory, but do not govern state transitions. State Choices (C) define the available states for a change request, but not the conditions for transitioning between them. State Conditions (D), while related to state transitions, generally offer less granular and systematic control compared to Model State Transition Conditions. Therefore, while State conditions can technically contribute, the most direct and purpose-built feature for enforcing these conditions is Model State Transition Conditions.Using Model State Transition Conditions aligns with best practices in ITIL and promotes standardization and accountability within the change management workflow, leading to more successful and well-managed changes.Further reading on change management and state model customization in ServiceNow can be found in the official ServiceNow documentation:ServiceNow Docs - Change Management : https://docs.servicenow.com/bundle/utca-change-management/page/product/change-management/concept/change-management.html ServiceNow Community: (Search for Change Management Best Practices or State Model Customization) https://community.servicenow.com/
Where can a change manager define the interval frequency for unauthorized change detection?
Answer(s): C
The correct answer is C: Unauthorized Change Properties module.The question asks about where a change manager can configure the frequency of unauthorized change detection. This directly relates to settings governing the automated detection process. The "Unauthorized Change Properties module" is the logical place for such configuration. It's designed to specifically control parameters related to identifying and handling changes that haven't gone through the proper authorization channels.Let's consider why the other options are incorrect:A: The ci.change.unplanned business rule: While business rules can automate processes, this specific business rule is likely involved in reacting to an unplanned change, not setting the detection interval. Modifying a business rule for this would be an indirect and potentially messy approach. B. Event Processing Properties module: Event Processing is broader and covers many aspects of event management. It's less likely to focus specifically on the unauthorized change detection frequency. D. Unauthorized change flow: Flows automate processes. A flow might be triggered after an unauthorized change is detected, but the frequency of the detection is a property, not part of the flow's design.The Unauthorized Change Properties module is the most direct and appropriate location for setting the frequency of the automated detection process. It provides a centralized and easily manageable setting that change managers can access.Justification:The ServiceNow platform provides configurable properties that directly influence the system's behavior related to specific areas. Unauthorized change detection is a critical aspect of IT Service Management (ITSM), necessitating dedicated configuration options. These options are logically grouped within the "Unauthorized Change Properties" module, offering settings to adjust how often the system scans for unauthorized changes. The frequency determines how often the detection mechanism runs to identify deviations from approved changes. Options A, B, and D are related to processes triggered by detected changes or general event processing and therefore are the wrong choice. Using the Unauthorized Change Properties module centralizes and simplifies the management of unauthorized change detection.
Prior to Quebec, when you click Change > Create New, which page is displayed?
Answer(s): E
The correct answer is E, Change Interceptor. Before the Quebec release of ServiceNow, clicking "Change > Create New" would not directly present the Change form. Instead, it would display the Change Interceptor.The Change Interceptor is a page that presents the user with options to select the type of change they want to create (e.g., Normal, Standard, Emergency). It acts as a preliminary filter, directing users to the appropriate Change form based on their specific need.This behavior was designed to ensure users were guided to the correct workflow and process for their particular change request. Different change types often require different approvals, tasks, and documentation. The Change Interceptor streamlined this process by pre-categorizing the change request.Options A, B, C, and D are incorrect. The Change Landing Page (A) is a dashboard-like view that provides an overview of change management activities, not the initial creation screen. The Change Form (B) is the actual form used to document the change, but it wasn't directly presented initially. The Change Catalog (C) is related to Request Management, not Change Management. The Change Wizard (D) is also incorrect; a wizard might have existed in specific implementations but wasn't a standard pre-Quebec feature.Since Quebec, ServiceNow has simplified this flow in most instances, often bypassing the interceptor and taking the user directly to the appropriate change form based on configured defaults or user-specific settings. However, prior to Quebec, the Change Interceptor was the standard behavior.Here are some resources that corroborate this:ServiceNow Documentation (Historical versions prior to Quebec): Searching for information related to Change Management and the process of creating new changes in ServiceNow versions prior to Quebec will usually mention the Change Interceptor. Note: Exact documentation links for specific old versions are challenging to provide due to ServiceNow's documentation updates over time.ServiceNow Community Forums: Discussions about creating changes in pre-Quebec versions often reference the Change Interceptor. You can find such discussions by searching the ServiceNow Community forums using keywords like "ServiceNow Change Interceptor" and "Create New Change Quebec."
Inside a change flow, you can automate a task with a sequence of related steps, like looking up a record, creating a record, or applying a policy. What is this component of the flow called?
The provided answer, A. Flow Actions , is the most accurate choice for describing the component of a change flow used to automate tasks involving sequences of related steps like record lookup, creation, or policy application within ServiceNow ITSM.Here's a detailed justification:Flow Designer in ServiceNow is a powerful automation platform that allows users to automate processes across the ServiceNow platform. It provides a drag-and-drop interface for designing and building workflows without requiring extensive coding. Within Flow Designer, the fundamental building blocks of a flow are Actions .Actions are reusable operations that perform specific functions, such as retrieving data, creating records, sending notifications, or executing scripts. They encapsulate a series of related steps to achieve a particular task. When you create an action, you define the inputs it requires and the outputs it generates.Flow Activities are broader terms, often used to describe logical groupings within a flow, but are not the primary component that executes individual steps like looking up or creating records.Flow Steps are individual operations within an action, not the encompassing structure. An action contains steps.Action Pills are visual representations of data elements (variables, field values) used within actions, not the action itself.Flow Tasks are activities assigned to users for manual intervention or approval processes, not automated sequences of steps.Think of it this way: a Flow is like a recipe. The overall recipe might be "Change Management Flow". Within that recipe are several Actions. One Action might be "Create Change Task", and within that Action are individual steps: (1) Look up assignment group, (2) Create task record, (3) Set task priority.By using Actions, you can create modular and reusable automation components that can be incorporated into multiple flows, promoting efficiency and reducing redundancy. The "sequence of related steps, like looking up a record, creating a record, or applying a policy" directly describes the functionality provided by a Flow Action.Therefore, 'Flow Actions' accurately describes the component used to automate tasks involving a series of related steps inside a ServiceNow change flow.For further research and clarification, refer to the official ServiceNow documentation on Flow Designer and Actions:ServiceNow Flow Designer Documentation ServiceNow Flow Designer Actions
On the Release record, what are the available options on the Release phase list?
Answer(s): D
The correct answer is D: Requirement Gathering, Design, Development, Build, Deployment, QA, User Acceptance.Here's the justification: The Release Management process in ServiceNow IT Service Management (ITSM) focuses on planning, scheduling, and controlling the movement of releases to test and production environments. A well-defined release phase list guides the release through various stages, ensuring quality and minimizing disruption. Option D reflects a logical sequence of activities commonly performed in a software or service release lifecycle.Let's break down why each phase is crucial:Requirement Gathering: This phase involves collecting and documenting the specific needs and expectations for the release. Without clearly defined requirements, the release might not meet the intended purpose. Design: Based on the requirements, the design phase outlines the technical architecture, functionalities, and user interface of the release. Development: This is where the actual coding or configuration of the release occurs. It translates the design into a working system. Build: The build phase assembles the developed components into a deployable package. Deployment: The deployable package is implemented and tested, then deployed to production. QA (Quality Assurance): QA involves rigorous testing to identify and fix defects before the release is made available to end-users. This minimizes the risk of issues impacting users. User Acceptance: In this phase, end-users test the release to ensure it meets their requirements and expectations. Successful user acceptance indicates the release is ready for wider adoption.Options A, B, and C are not accurate representations of standard release phases. They contain terms that might be used within specific sub-phases, but they do not follow a comprehensive lifecycle in the way D does.For further reading on ServiceNow Release Management and best practices, you can refer to the official ServiceNow documentation:ServiceNow Release Management Documentation ITIL 4 Release Management Practices (ITIL provides a widely adopted framework for IT service management, which includes guidance on release management practices).
You have created a new Change model and added a new Approval Policy for that model. But the newly defined approval is not triggering. What could cause this issue?
Answer(s): B
The correct answer is B. The "Apply Change Approval Policy" action in the flow created for the new change model does not reference the new Approval Policy.Here's a detailed justification:ServiceNow's ITSM implementation leverages Flows to automate processes, including change management workflows. Change Models, introduced to standardize change processes, often use Flows to define the different stages and actions. A critical part of the change process is the approval process, which is handled via Approval Policies.When a new Change Model is created and a corresponding Approval Policy is defined, it's crucial to connect them within the Flow. The "Apply Change Approval Policy" action within the Flow is specifically designed to evaluate and trigger the appropriate Approval Policy based on the change request's attributes and the defined policy rules.If this "Apply Change Approval Policy" action in the associated Flow doesn't explicitly reference the new Approval Policy, the system won't know to evaluate it. The action needs to be configured to consider the new Approval Policy for the new Change Model. Without this connection, the system falls back to default or pre-existing Approval Policies, explaining why the new policy isn't triggered.Option A is incorrect because the "Apply approval policy" business rule typically evaluates and applies policies generically based on conditions, it doesn't usually require explicit updates for each new Approval Policy. Option C is incorrect because Flows, not Workflows through the legacy Workflow Editor, are the primary mechanism for modern Change Model automation. Option D is incorrect as "glide.ui.approval.policies" is related to UI related policies and not for Change Approval Policies.Therefore, ensuring the Flow associated with the new Change Model correctly references the newly created Approval Policy within the "Apply Change Approval Policy" action is vital for proper functionality.Authoritative Links for further research:ServiceNow Docs: Change Management: https://docs.servicenow.com/bundle/vancouver-it-service-management/page/product/change-management/concept/c_ChangeManagement.html ServiceNow Docs: Flow Designer: https://docs.servicenow.com/bundle/vancouver-platform/page/administer/flow-designer/concept/flow-designer.html ServiceNow Community: Search for "Change Approval Policy not triggering" to find relevant discussions and solutions.
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.