Free ServiceNow CIS-ITSM Practice Exam with Questions & Answers

Reviewed code for UI Action in Tokyo/Utah/Vancouver. It just prints an error message and does nothing, so answer is A.

if (current.assignment_group.nil()) {

var memberGroups = new global.IncidentUtils().getMemberGroups(gs.getUserID(), 2);

if (memberGroups.length > 1) {

gs.addErrorMessage(gs.getMessage("Assigned to user {0} is member of multiple groups, please select one as Assignment group ", [gs.getUserDisplayName()]));

return;

}

https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/administer/contextual-search/task/t_DefineContextualSearchForForm.html

In Change Management, specifically when using the Change Model framework (introduced in the Rome release to provide more flexibility than legacy workflows), state transitions are governed by specific conditions. For a Change Request to move from the Authorized state (where it has been vetted by the CAB or technical leads) to the Scheduled state (where it is ready for implementation), the system must verify that the necessary approvals have been granted. Therefore, the "Requires" field is set to Task is Approved to ensure that the transition only occurs once the approval engine returns a positive result.

In ServiceNow's Problem Management application, state transitions and their associated logic are governed by Script Includes. Following ServiceNow's architectural best practices, the logic is split into two parts:

ProblemStateUtilsSNC: This contains the read-only, "out-of-the-box" (OOTB) logic provided by ServiceNow.

ProblemStateUtils (B): This script include extends the SNC version and is intended for customer customizations.

If an administrator needs to add a custom pre-requisite (such as ensuring a specific field is filled or a related record is closed) before a problem can move out of the Fix in Progress state, they must modify the ProblemStateUtils script. This ensures that their changes are preserved during platform upgrades.