CIS-ITSM Practice Questions

ServiceNow provides multiple built-in mechanisms for users to provide feedback on knowledge articles, which is crucial for maintaining a healthy and accurate knowledge base. The standard methods include:

1. Helpful?: A binary (Yes/No) option allowing users to quickly indicate an article's utility.

2. 5 Star scale: A quantitative rating system for users to express their satisfaction with the article's quality.

3. Comment on Article: A qualitative feedback option where users can leave detailed text-based comments.

4. Flag Article: A function for users to report specific issues, such as incorrect information or outdated content, which can trigger a review workflow.

These feedback mechanisms are essential for the continual improvement process within Knowledge Management.

B. 10 Star scale: The out-of-the-box knowledge article rating system in ServiceNow uses a 5-star scale, not a 10-star scale.

D. Pin Article: Pinning an article is a personalization feature that allows a user to bookmark it for quick access; it does not provide feedback to the article author or knowledge manager.

1. ServiceNow Product Documentation - Knowledge article feedback: This official document explicitly lists the primary feedback methods. It states

"Users can provide feedback on knowledge articles by rating them

marking them as helpful or not helpful

flagging them

and posting comments." This directly supports options A

C

E

and F.

Source: ServiceNow Product Documentation

Washington D.C. Release

Document ID: KB0715881

Section: "Knowledge article feedback".

2. ServiceNow Product Documentation - Rate a knowledge article: This page details the 5-star rating system. It confirms

"You can rate a knowledge article on a scale of one to five stars to provide feedback on its quality." This supports option E and refutes option B.

Source: ServiceNow Product Documentation

Washington D.C. Release

Document ID: d23562d5c311301000a12c6c64d3ae3d

Section: "Rate a knowledge article".

3. ServiceNow Product Documentation - Pin a knowledge article: This document clarifies the purpose of pinning

stating

"Pin articles that you want to access frequently from the knowledge homepage." This confirms pinning is for accessibility

not feedback

refuting option D.

Source: ServiceNow Product Documentation

Washington D.C. Release

Document ID: d23562d5c311301000a12c6c64d3ae3d

Section: "Pin a knowledge article".

The interval frequency for detecting unauthorized changes is controlled by a scheduled job. A change manager or administrator can configure this frequency in the Unauthorized Change Properties module. This module provides access to the system property, "Run the unauthorized change detection process every," where the specific interval (in days, hours, and minutes) for the job can be set. This ensures the system periodically scans for CI updates that are not linked to an approved change request, aligning with the organization's governance policies.

A. The ci.change unplanned business rule: This business rule is part of the logic that creates an unauthorized change record after a change is detected, not for configuring the detection schedule.

B. Event Processing Properties module: This module is used for configuring Event Management (EM) settings, which is a separate process from ITSM Change Management's unauthorized change detection.

D. Unauthorized change flow: While a flow may execute the detection logic, the user-facing configuration for the interval is managed via the dedicated properties module, not a module named "Unauthorized change flow".

1. ServiceNow Product Documentation (Washington): Change Management properties. This document details the configuration settings for the Change Management application. Under the "Unauthorized change request properties" section

it lists the property: "Run the unauthorized change detection process every [change.unauthorized.executefrequency]

" which directly controls the interval.

2. ServiceNow Product Documentation (Washington): Unauthorized change requests. This document explains the feature and states

"The Unauthorized Change Request scheduled job runs periodically to detect any unauthorized changes." This confirms the use of a scheduled job

whose frequency is set in the properties module. The navigation path provided is Change > Administration > Unauthorized Change Properties.

In the ServiceNow Platform, the ability to create, edit, and delete user-criteria records that control access to Service Catalog items is restricted to the catalogadmin role (or usercriteriaadmin, which is not listed here). Possession of catalogadmin grants full administration of catalog metadata, including user-criteria rules stored in the User Criteria [scusercriteria] table. Without this role, a user can only view criteria applied to items they administer; they cannot create or manage those criteria.

A. catalogcriteriaadmin – no such base-system role exists; therefore confers no rights.

C. itiladmin – governs incident/change administration, not catalog security or user criteria.

D. caIalogcriteriamanager – non-existent role; spelled with capital “I” instead of “l.”

E. catalogmanager – can manage items within assigned catalogs but lacks rights to create user-criteria records.

1. ServiceNow Product Documentation

“User criteria for Service Catalog

” Utah release

Section: “Create user criteria – Role required

” paragraph 1 (states role required: catalogadmin or usercriteriaadmin).

2. ServiceNow Product Documentation

“Role reference—Service Catalog

” Utah release

Table listing catalogadmin capabilities

row “User Criteria administration.”

3. ServiceNow Platform Security Guide

San Diego release

ch. “Access controls in Service Catalog

” p. 12

notes catalogadmin required for scusercriteria table CRUD actions.

In the standard ServiceNow Normal Change Model, the 'Authorize' state represents the formal approval stage. From this state, there are three primary transitions defined. If the change is approved, it moves to the 'Scheduled' state to be planned for implementation. If the change is rejected but requires rework, it can be moved back to the 'New' state for the requester to modify and resubmit. If the change is rejected outright or is no longer required, it can be moved to the 'Canceled' state. These transitions represent the key decision outcomes at the authorization phase.

A. The 'Review' state occurs after implementation and cannot be transitioned to directly from 'Authorize'. The 'Draft' state is typically an initial state, not a destination from 'Authorize'.

B. A Normal Change must be scheduled before it can be implemented. Transitioning directly from 'Authorize' to 'Implement' or 'Review' bypasses critical process steps.

D. A change cannot be moved directly to the 'Closed' state from 'Authorize'. The implementation and post-implementation review must be completed first.

1. ServiceNow Product Documentation - Change Management state model and transitions: The official documentation provides a state model diagram and a table detailing the transitions for different change types. For a Normal change

the documented transitions from the 'Authorize' state are to 'Scheduled'

'New'

or 'Canceled'. (ServiceNow Vancouver Release

Doc ID: KB1123423

Section: "Normal change request state model and transitions").

2. ServiceNow Now Learning - ITSM Fundamentals On Demand: The courseware explains the lifecycle of a Normal Change Request. It details that after the 'Assess' state

the change moves to 'Authorize'. Upon approval

it proceeds to 'Scheduled'. If rejected

it can be sent back for rework ('New') or canceled. (Module: Change Management

Topic: Change Models and Lifecycles).

The CI Class Manager is the centralized and dedicated tool within the ServiceNow platform designed for managing the Configuration Management Database (CMDB). It provides a user interface to explore the entire class hierarchy in a tree-like structure, view class definitions, manage attributes, define identification and reconciliation rules, and modify the CMDB data model. It is the primary tool for CMDB administrators to perform the tasks described in the question.

A. Application Menus are navigation elements used to access lists, forms, and modules, not to explore the hierarchical structure of database tables.

B. Reports are used to visualize and analyze data contained within tables, not to view or manage the underlying table definitions and class hierarchy.

D. Dependency View is a graphical tool that displays the relationships between specific configuration item (CI) records, not the class structure of the CMDB itself.

1. ServiceNow Product Documentation: "The CI Class Manager is the centralized place to explore the CI class hierarchy

the attributes of the classes

and the class identification rules."

Source: ServiceNow Product Documentation

"CI Class Manager

" CMDB and CSDM

Quebec release (and later).

2. ServiceNow Product Documentation: "Use the CI Class Manager to view a list of all CI classes in a hierarchy

with the Configuration Item [cmdbci] class at the top level."

Source: ServiceNow Product Documentation

"View CI class hierarchy

" CMDB and CSDM

Washington DC release.

The problemadmin role is required to delete problem records in ServiceNow. This role provides administrative-level access to the Problem Management application, including the ability to manage properties and perform destructive actions like deleting problem, problem task, and known error article records. This privilege is intentionally separated from process-focused roles like problemmanager or problemcoordinator to prevent accidental data loss and maintain data integrity. The user in the scenario requires this specific administrative role to clean up the accidentally created records.

B. problemcoordinator: This role is responsible for managing and working on problem tasks but lacks the administrative rights to delete entire problem records.

C. soproblemdelete: This is not a standard, out-of-the-box role provided with the ServiceNow Problem Management application.

D. RHmanager: This is not a recognized base system role within the ServiceNow ITSM suite and is irrelevant to Problem Management.

E. problemmanager: This role oversees the Problem Management process but, by default, does not have permissions to delete problem records; this is reserved for the problemadmin.

1. ServiceNow Product Documentation (Washington DC): Components installed with Problem Management. This official document explicitly states the function of the problemadmin role: "Can manage all problem management properties

and can delete problem

problem task

and known error article records." The descriptions for problemmanager and problemcoordinator do not include deletion privileges.

2. ServiceNow Product Documentation (Washington DC): Problem Management roles and personas. This guide outlines the responsibilities for each role

confirming that administrative tasks

including deletion

are assigned to the problemadmin persona

distinct from the process-focused problemmanager and problemcoordinator personas.

The standard and recommended method for managing change approvals in ServiceNow is through Change Approval Policies, which are part of the change state model. To introduce a new, conditional approval for a specific service within an existing change model (e.g., Normal), you add a new 'Decision' to the corresponding Change Approval Policy. This Decision will contain the condition (e.g., Configuration Item or Service is 'SAP Enterprise Services') and will trigger the specific approval definition (the new approval group or user) when that condition is met.

A. Add a new Policy Input to the Normal Change Approval Policy: A Policy Input only makes a field from the change record available for evaluation; it does not create the approval rule or logic itself.

C. Add a new Change Approval Policy: A new policy is typically created for an entirely new change model or type, not for adding a conditional approval to an existing one.

D. Add a new Decision to the Normal Change Workflow: Modifying the legacy workflow is not the current best practice. Change Approval Policies are designed to handle this requirement without customizing baseline workflows.

1. ServiceNow Product Documentation - Create or modify a change approval policy: "Add decisions to your policy to define the conditions under which an approval is required. For each decision

you can define one or more approval definitions." This directly supports that a 'Decision' is the component used to add conditional approval logic. (ServiceNow Product Documentation

Utah release

"Change Management

" Doc ID: taskcreate-modify-change-approval-policy).

2. ServiceNow Product Documentation - Change approval policies: "A change approval policy is a container for one or more approval definitions and their corresponding decisions... The base system includes approval policies for normal

standard

and emergency changes." This confirms that for a "Normal" change

you modify its existing policy. (ServiceNow Product Documentation

Utah release

"Change Management

" Doc ID: conceptchange-approval-policies).

3. ServiceNow Now Learning - ITSM Implementation On-Demand Course: The "Change Management Configuration" module explains that Change Approval Policies are the mechanism to control approvals. It details how to add 'Decisions' to a policy to create conditional paths for approvals based on attributes of the Change Request

such as the associated service.

The additional columns that appear in the auto-complete dropdown (lookup select box) for a reference field are defined by the refaccolumns dictionary attribute. This attribute is configured on the dictionary entry of the specific reference field, in this case, the callerid field on the Incident table. By specifying a comma-separated list of field names from the referenced table (e.g., sysuser), an administrator can display more contextual information, such as an email address or employee number, alongside the user's name. This enhances usability by helping users select the correct record without opening the full lookup list.

A. The refcontributions attribute is used to add UI macros, such as clickable icons, next to a reference field, not to modify the lookup columns.

C. The configuration is applied to the dictionary entry of the reference field on the consuming table (Incident), not on the referenced table (sysuser).

D. Form design or form layout is used to configure the fields and their arrangement on a standard form view, not the columns in an auto-complete dropdown.

1. ServiceNow Product Documentation - Dictionary attributes: The official documentation lists refaccolumns and describes its function: "Specifies additional columns to be displayed in the auto-complete list for this reference field." This directly supports the correct answer. (ServiceNow Product Documentation

Platform Administration > Data dictionary > Dictionary attributes).

2. ServiceNow Developer Site - Dictionary Attributes: The developer portal provides a technical reference for dictionary attributes

confirming that refaccolumns is used to "Add columns to the auto-complete list for a reference field." (ServiceNow Developer Documentation

API Reference > Dictionary Attributes).

In ServiceNow's out-of-the-box configuration, when a Configuration Item (CI) is selected on a Problem record, a business rule named "Problem Populate from CI" is triggered. This rule automatically populates the 'Assignment group' field on the Problem record with the value from the 'Support group' field of the selected CI. This automation ensures that the problem is routed to the team responsible for supporting the affected service or infrastructure component, streamlining the problem management process.

A. Change group: This field on the CI record is used to auto-populate the assignment group for Change Requests, not for Problems.

C. Managed: 'Managed by' is a standard CI field that refers to an individual user, not a group, and is not used for problem assignment.

D. Approval group: This field on the CI record is designated for the approval workflow of associated Change Requests, not for problem assignment.

1. ServiceNow Product Documentation - Problem Management: The process of creating a problem record often involves associating a CI. The system logic is designed to use the CI's support details for assignment. The "Problem Populate from CI" business rule explicitly sets this relationship. (ServiceNow Product Documentation

Vancouver Release

"Create a problem record in UI16").

2. ServiceNow Product Documentation - Base Configuration Item fields: The documentation for the Configuration Management Database (CMDB) defines the purpose of key fields on the base Configuration Item [cmdbci] table. It specifies that the Support group (supportgroup) field is "The group that supports the CI

" making it the logical source for task assignment. In contrast

the Change group (changecontrol) is for change management

and the Approval group (approvalgroup) is for change approvals. (ServiceNow Product Documentation

Vancouver Release

"Configuration Item form").

The relationship between Incident and Change Management is a core concept in ITSM. A change, especially if it fails or has unintended consequences, can directly cause an incident (e.g., a server patch causes an application to stop working). This is represented by the "Caused by Change" relationship. Conversely, to resolve an incident that requires a modification to a Configuration Item (CI), a formal change request must be raised. This ensures the fix is planned, approved, and documented, thereby resolving the incident and its underlying cause. This is often initiated via the "Create Change" action on an incident record.

A. An incident owner's role does not inherently place them in the change approval workflow; approvals are typically managed by change approvers or the CAB.

D. This is not out-of-the-box functionality. An incident requires its own closure process, including user confirmation, and does not automatically close with a related change.

1. ServiceNow Product Documentation: "Create a change request from an incident." This document explicitly states

"You can create a change request from an incident to resolve the incident." This directly supports option C.

2. ServiceNow Product Documentation: "Relate an incident to a change request." This document details the "Caused by Change" field on the Incident form

which is used to link an incident that was a result of a change implementation. This directly supports option B.

3. ServiceNow Product Documentation: "Incident Management state model." The documentation on the incident lifecycle shows that moving to a 'Closed' state requires specific conditions or manual action after resolution. It does not mention automatic closure based on a related change

which invalidates option D.

4. ServiceNow Product Documentation: "Change Management approvals." The documentation outlines that approvals are configured based on user roles

groups (like the Change Advisory Board)

and specific individuals

not automatically based on the "owner" of a related incident. This invalidates option A.