CCNA Change Management Questions — Page 2 of 2

Multi-Selectmedium

Which TWO of the following settings are required for the CAB Workbench to function correctly?

Select 2 answers

A.A dedicated CI for the CAB

B.An assigned ITIL manager

C.Scheduled CAB meetings

D.An active workflow for every change

E.A defined CAB Definition

AnswersC, E

Scheduled CAB meetings supply the change calendar entries the Workbench aggregates and displays, satisfying the requirement that upcoming change windows be visible to approvers. Without defined meeting records, the Workbench cannot render the agenda or associate changes with a review slot, so this setting is mandatory for correct operation.

Why this answer

Option C is correct because the CAB Workbench is driven by scheduled CAB meetings; the workbench aggregates the change records that are linked to a CAB meeting's agenda, so without scheduled meetings there is nothing for the workbench to display or manage. Option E is correct because a CAB Definition record is the configuration that tells the CAB Workbench which table, fields, and meeting-related settings to use, so the workbench cannot render or function without a defined CAB Definition. Option A is not required, since the CAB Workbench does not depend on a dedicated CI for the CAB; it works from CAB definitions and meetings rather than a specific configuration item.

Option B is not required, as the workbench does not mandate an assigned ITIL manager role to operate. Option D is not required, because an active workflow for every change is a change-management process concern and is not a prerequisite for the CAB Workbench to function.

Exam trap

CIS-ITSM often tests the prerequisites for the CAB Workbench, so the trap is selecting plausible-sounding but unnecessary items like a dedicated CI or an ITIL manager, when the actual requirements are the CAB Definition and scheduled meetings.

Practice this question →

MCQhard

An administrator needs to modify the window of time considered by the Conflict Detection engine when checking for overlapping changes on the same Configuration Item (CI). Where is this conflict time window configured?

A.The ConflictFinderSNC script include hardcoded constants

B.CI Relationship types table

C.Change Properties module under 'Conflict' tab

D.System Properties (prefix com.snc.change_management.conflict)

AnswerD

The conflict detection window is governed by system properties under the com.snc.change_management.conflict prefix, which define the look-back and look-ahead periods for overlapping changes on a CI. Editing these properties directly modifies the time window the engine considers.

Why this answer

The conflict detection time window is configured in System Properties with the prefix com.snc.change_management.conflict. These properties define the window before and after a change during which overlapping changes on the same CI are flagged. Administrators adjust these values to control how far apart changes must be to avoid conflicts.

Exam trap

The trap is assuming the conflict window is hardcoded in a script include or configured in a module, when it is actually controlled via system properties with the com.snc.change_management.conflict prefix.

How to eliminate wrong answers

Option A is wrong because the ConflictFinderSNC script include does not contain hardcoded constants for the time window; it reads from system properties. Option B is wrong because CI Relationship types define how CIs relate, not conflict timing. Option C is wrong because there is no 'Conflict' tab under Change Properties; the settings are in System Properties.

Practice this question →

Multi-Selectmedium

A change manager is configuring the Change Management process to meet audit requirements. The auditor requests evidence that changes are properly authorized and that the risk of changes is assessed before implementation. Which TWO configurations should the change manager verify are in place? (Choose two.)

Select 2 answers

A.The Change model includes a mandatory approval step before the change can move to Implement.

B.The Change request is automatically assigned to the change manager's assignment group.

C.The Change request has a post-implementation review task created automatically.

D.The Change request form includes a mandatory field for the implementation plan.

E.The Risk Assessment is completed and the Risk field is populated before the change is approved.

AnswersA, E

A mandatory approval step ensures that changes cannot proceed to implementation without explicit authorization. This provides auditable evidence that changes are reviewed and approved by the appropriate authority, directly satisfying the auditor's requirement for proper authorization.

Why this answer

To satisfy the auditor, the change process must enforce authorization and risk assessment before implementation. A mandatory approval step ensures changes are authorized, and a completed risk assessment with a populated Risk field shows that risk was evaluated. Together, these provide the necessary audit evidence.

Exam trap

The trap here is confusing general good practices like implementation plans or post-implementation reviews with the specific evidence needed for authorization and risk assessment.

Practice this question →

Multi-Selectmedium

Which TWO actions can a change coordinator perform within the CAB Workbench during an active meeting? (Choose two.)

Select 2 answers

A.Add ad-hoc change requests to the meeting agenda

B.Automatically deploy software packages to production servers

C.Record votes and decisions for change requests on the agenda

D.Modify global system properties for risk calculation

E.Initiate ITOM Discovery scans across the entire network

AnswersA, C

Adding ad-hoc change requests to the agenda is a core CAB Workbench capability, letting the coordinator inject unplanned changes mid-meeting without ending the session. This satisfies the stem's "during an active meeting" constraint, since the workbench supports live agenda modification rather than requiring changes to be scheduled beforehand.

Why this answer

Option A is correct because the CAB Workbench allows a change coordinator to add ad-hoc change requests to the meeting agenda during an active meeting, enabling last-minute items to be discussed and reviewed. Option C is correct because the change coordinator can record votes and decisions for change requests on the agenda, capturing CAB approvals or rejections directly in the workbench. Option B is incorrect because deploying software packages to production servers is a fulfillment/release activity, not a CAB Workbench meeting action.

Option D is incorrect because modifying global system properties for risk calculation is an administrative configuration task outside the CAB Workbench meeting workflow. Option E is incorrect because initiating ITOM Discovery scans is a discovery/operations function, not a change coordination meeting action.

Exam trap

CIS-ITSM often tests the distinction between meeting facilitation actions (adding agenda items, recording votes) and broader administrative or operational tasks (system property changes, discovery scans, deployments), so candidates must recognize that the CAB Workbench is strictly for meeting management.

Practice this question →

Multi-Selectmedium

Which TWO factors are typically evaluated by the ServiceNow Conflict Detection engine when checking a change request? (Choose two.)

Select 2 answers

A.User password complexity and security compliance

B.Schedule overlaps with other change requests on the same CI

C.Service Catalog item fulfillment costs

D.Blackout schedules prohibiting changes during specific critical periods

E.CMDB hardware depreciation schedules

AnswersB, D

Conflict Detection compares the change's planned start and end times against other change requests targeting the same configuration item, flagging overlapping windows. This satisfies the stem by identifying schedule overlaps on shared CIs before approval.

Why this answer

The ServiceNow Conflict Detection engine evaluates whether a change request's planned window collides with other scheduled changes affecting the same configuration item, so option B (schedule overlaps with other change requests on the same CI) is correct because overlapping maintenance windows on a shared CI create operational risk. Option D (blackout schedules prohibiting changes during specific critical periods) is also correct because the engine checks the change against defined blackout/maintenance windows to prevent changes during frozen or critical business periods. Options A, C, and E are not part of conflict detection: password complexity and security compliance are handled by security/audit controls, Service Catalog fulfillment costs relate to financial/request management, and CMDB hardware depreciation is an asset-financial concept, none of which the Conflict Detection engine evaluates.

Exam trap

CIS-ITSM often tests whether candidates conflate change conflict detection with unrelated CMDB or catalog attributes — the trap is picking plausible-sounding but functionally unrelated options like depreciation or fulfillment cost.

Practice this question →

Multi-Selectmedium

Which TWO actions happen when a conflict is detected during the change scheduling process? (Choose two.)

Select 2 answers

A.Conflict status indicators provide visibility into soft or hard conflicts

B.An automated email is broadcast to all company employees

C.The configuration item is automatically retired from service

D.The change request is automatically deleted from the database

E.Conflict records are generated and displayed in the Conflicts related list

AnswersA, E

Conflict status indicators distinguish soft from hard conflicts directly on the change schedule, satisfying the requirement to surface detected clashes during scheduling. Soft conflicts flag overlaps needing review, while hard conflicts block conflicting changes outright, giving schedulers immediate visibility of the conflict type before approval proceeds.

Why this answer

Option A is correct because conflict status indicators are the mechanism that surfaces whether a detected scheduling clash is a soft conflict (a warning that can often be resolved by rescheduling) or a hard conflict (a genuine overlap that must be addressed before the change can proceed), giving change managers the visibility needed to act. Option E is correct because when the scheduling process detects a conflict, it creates conflict records that are stored and shown in the Conflicts related list on the change request, providing an auditable, actionable record of the clash. The remaining options do not belong: B is wrong because conflict detection does not trigger a company-wide email broadcast, C is wrong because a scheduling conflict never automatically retires the affected configuration item from service, and D is wrong because the change request is not deleted from the database — it is retained and flagged so the conflict can be resolved.

Exam trap

CIS-ITSM often tests whether candidates know that conflict detection produces visibility artifacts (indicators and related-list records) rather than destructive or organization-wide actions, so options implying deletion or mass notification are distractors.

Practice this question →

MCQmedium

A Change Manager wants to ensure that all changes hitting a specific production database CI require a Risk Assessment. Where is this association between CI classes or specific CIs and Risk Assessment criteria defined?

A.Business Service Portfolio settings

B.CI Relationship Rules

C.Risk Conditions (risk_conditions table)

D.Change Model state transition maps

AnswerC

Risk Conditions in the risk_conditions table define the criteria that trigger a Risk Assessment, and these conditions can be scoped to specific CI classes or individual CIs. Associating the production database CI with a Risk Condition ensures every change affecting it automatically requires assessment, satisfying the Change Manager's constraint.

Why this answer

Risk Conditions (the risk_conditions table) in ServiceNow Change Management define the criteria that determine when a risk assessment is required for a change. Administrators configure conditions based on CI class or specific CI, and if the change matches, a risk assessment is triggered.

Exam trap

The trap is confusing risk conditions with change models or CI relationships — candidates may pick CI Relationship Rules because it mentions CIs, but risk assessment criteria are specifically in the risk_conditions table.

How to eliminate wrong answers

Option A is wrong because Business Service Portfolio settings define business services and their relationships, not risk assessment criteria. Option B is wrong because CI Relationship Rules define how CIs relate to each other, not risk conditions. Option D is wrong because Change Model state transition maps define the states and transitions for change models, not risk assessment triggers.

Practice this question →

MCQhard

An enterprise requires that whenever a change request's risk is calculated as 'High', the change model automatically enforces an additional approval from the Security Operations team. How can this requirement be met?

A.Adding Security Operations as the primary assignment group

B.Writing a client script on the Risk Assessment form

C.Configuring Change Approval Policies or Approval Definitions tied to the Change Model based on risk criteria

D.Modifying the system date/time format

AnswerC

Change Approval Policies and Approval Definitions attach approval logic to a change model and can evaluate risk criteria. Binding a Security Operations approval to the High-risk condition makes the extra sign-off automatic, satisfying the requirement without manual intervention.

Why this answer

Change Approval Policies or Approval Definitions in ServiceNow allow you to define conditional approvals based on risk. By tying a policy to the Change Model and setting conditions such as risk = High, the system automatically enforces an additional approval from the Security Operations group. This is the standard, declarative way to meet the requirement without custom code.

Exam trap

The trap is thinking that any approval-related configuration (like assignment group) will automatically enforce approvals. Candidates often confuse assignment groups with approval groups, or they resort to client scripts when declarative policies are the correct tool.

How to eliminate wrong answers

Option A is wrong because adding Security Operations as the primary assignment group does not automatically enforce an additional approval; it only changes who is assigned to work on the change. Option B is wrong because a client script on the Risk Assessment form runs on the client side and is not the appropriate mechanism to enforce approval workflows; client scripts are for UI behavior, not for orchestrating approvals. Option D is wrong because modifying the system date/time format has no relevance to approval logic.

Practice this question →

MCQeasy

Which role is required to create a new Standard Change proposal?

A.discovery_admin

B.catalogue_builder

C.itil

D.security_admin

AnswerC

The itil role grants the permissions needed to draft and submit a Standard Change proposal, satisfying the stem's requirement to create one. Standard Change proposals are authored by users holding itil, since that role carries the change-management write access, whereas non-itil roles such as sn_change_read or approver roles cannot initiate proposals.

Why this answer

The itil role is required to create a new Standard Change proposal in ServiceNow ITSM. Standard Changes are pre-approved, low-risk changes, and the itil role grants the necessary access to the Change Management application to propose them. Users without itil cannot access the change creation workflow.

Exam trap

The trap is confusing application-specific admin roles (discovery_admin, catalogue_builder, security_admin) with the process role (itil) that actually grants Change Management access — candidates pick a role that sounds administrative but is unrelated to changes.

How to eliminate wrong answers

Option A is wrong because discovery_admin is for Discovery and Service Mapping administration, unrelated to Change Management. Option B is wrong because catalogue_builder is for building service catalog items, not for creating change proposals. Option D is wrong because security_admin is for managing security ACLs and related security configuration, not for Change Management tasks.

Practice this question →

MCQeasy

What is the primary function of the 'Review' state in the change lifecycle?

A.Conducting Post Implementation Review (PIR) and assessing success

B.Approving standard change proposals

C.Running automated risk assessments

D.Performing initial conflict detection checks

AnswerA

The Review state exists to conduct the Post Implementation Review, confirming the change achieved its objective and assessing success before closure. It sits after implementation, so the change record is evaluated for effectiveness rather than being actively deployed or authorised.

Why this answer

The 'Review' state in the change lifecycle is used to conduct the Post Implementation Review (PIR) after a change has been implemented. During this state, the change manager and stakeholders assess whether the change was successful, if it met its objectives, and if any follow-up actions are needed. This is a distinct phase that occurs after implementation and before closure.

Exam trap

CIS-ITSM often tests the sequence of change states, and candidates may confuse 'Review' with 'Authorize' or 'Assess', incorrectly associating it with approval or risk assessment rather than post-implementation evaluation.

How to eliminate wrong answers

Option B is wrong because approving standard change proposals occurs during the 'Authorize' or 'Approve' state, not 'Review'. Option C is wrong because automated risk assessments are typically run during the 'Assess' state or when the change is created. Option D is wrong because initial conflict detection checks are performed during the 'Assess' or 'Authorize' states, not during 'Review'.

Practice this question →

Multi-Selecteasy

Which TWO of the following are primary benefits of utilizing Standard Changes in ServiceNow? (Choose two.)

Select 2 answers

A.They require mandatory manual risk assessment questionnaires for every execution

B.They automatically trigger emergency incident swarming

C.They bypass traditional CAB approval because they are pre-approved

D.They are designed for major, high-risk infrastructure overhauls

E.They provide a repeatable, consistent method for implementing frequent, low-risk changes

AnswersC, E

Standard Changes carry pre-authorised approval, so they skip the traditional CAB review that normal and emergency changes require. This satisfies the stem by removing the approval bottleneck for frequent, low-risk work already vetted through the change model.

Why this answer

Option C is correct because Standard Changes are pre-approved by the Change Management process, so they do not require individual CAB review or approval each time they are executed, which speeds up delivery. Option E is correct because Standard Changes follow a documented, repeatable procedure for frequent, low-risk changes, ensuring consistency and reducing administrative overhead. Option A is incorrect because Standard Changes are low-risk and pre-authorized, so mandatory manual risk assessment questionnaires for every execution are not a primary benefit and would defeat their purpose.

Option B is incorrect because emergency incident swarming is associated with major incidents or emergency changes, not routine Standard Changes. Option D is incorrect because Standard Changes are intended for low-risk, routine changes, whereas major, high-risk infrastructure overhauls would typically follow Normal or Emergency Change processes.

Exam trap

The trap is assuming Standard Changes still require per-execution risk assessment or CAB approval, when their defining feature is pre-approval and repeatability for low-risk work.

Practice this question →

MCQeasy

Which ServiceNow table stores CAB meeting records?

A.sys_user_group

B.wm_meeting

C.std_change_proposal

D.change_request

AnswerB

CAB meeting records are stored in the wm_meeting table, which underpins the CAB Workbench. This satisfies the stem's requirement for the specific table holding meeting data, distinct from change_request or task tables that hold the changes themselves.

Why this answer

The ServiceNow table that stores CAB meeting records is wm_meeting. This table is part of the Change Management application and is specifically designed to hold meeting details such as agenda, attendees, and minutes for Change Advisory Board (CAB) meetings. It is distinct from tables that store user groups, change proposals, or change requests.

Exam trap

CIS-ITSM often tests the distinction between tables that store configuration items versus those that store process records, and candidates may confuse CAB meeting records with change request records or user groups.

How to eliminate wrong answers

Option A is wrong because sys_user_group stores user group definitions (e.g., CAB groups) but not meeting records. Option C is wrong because std_change_proposal stores standard change proposal templates, not meeting records. Option D is wrong because change_request stores individual change requests, not CAB meeting records.

Practice this question →