SNOW-CSA Practice Test 2 — 25 Questions

Question 1

An administrator notices that a flow that runs when a catalog item is submitted is failing because the flow tries to update a record that the flow's user (system) does not have permission to update. What is the best practice to address this?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Change the flow to run as the requestor. Flows can be configured to run as a specific user. Setting the flow to run as the requestor ensures permissions are based on the user who submitted the request, which typically has appropriate access. Granting additional roles to the system user is not recommended. Using a run script action or business rule does not address the permission issue directly.

Answer

Use a business rule instead

Answer

Grant the flow's user the necessary roles

Answer

Use a run script action

Question 2

Refer to the exhibit. An administrator created a catalog item using a record producer. When a user submits the request, the record producer fails to create the requested item. The log shows a missing mandatory field error. What is the most likely cause?

Accepted Answer

A mandatory field in the target table is not mapped by the record producer.. The error message 'missing mandatory field' directly indicates that a field in the target table, which is required (mandatory), has not been mapped by the record producer. In ServiceNow, when a record producer creates a record, it must map variables or fields to all mandatory fields in the target table; if any mandatory field is left unmapped, the system will fail to insert the record and log this specific error.

Answer

The record producer is not mapped to the correct table.

Answer

The 'model' variable is not mapped to a field in the target table.

Answer

The record producer is inactive.

Question 3

Which two statements about UI Policies are true? (Choose two.)

Accepted Answer

They can be used to set field values.. UI Policies can set field values on the client side using the 'Set field values' section within the UI Policy configuration. This allows administrators to automatically populate or modify field values based on conditions, such as setting a category field when a certain priority is selected, without requiring a server round trip.

Answer

They are always executed on form load.

Answer

They can be used to cancel a form submission.

Answer

They run on the server side.

Question 4

An administrator needs to create a UI action that appears on the form context menu for the Incident table, but only when the record is in 'In Progress' state. Which configuration is required?

Accepted Answer

Set the condition on the UI action to 'current.state == 2'. UI actions can have a condition field that evaluates server-side JavaScript. Setting the condition to 'current.state == 2' ensures the UI action appears only when the Incident record's state field equals the 'In Progress' value (typically 2 in the default state model). This is the standard, built-in mechanism for controlling UI action visibility based on record data.

Answer

Create a UI policy that changes the form when state is 'In Progress'

Answer

Write an ACL on the UI action table

Answer

Assign the UI action to a role that only users in this state have

Question 5

A record producer is configured to create a task when a user submits a form from the service portal. The task is created but the variables from the form are not mapped. What is the most likely cause?

Accepted Answer

The 'Variable mapping' section of the record producer is not configured. The record producer's 'Variable mapping' section is responsible for explicitly mapping form variables to fields on the target table. When this section is left unconfigured, the system creates the task record but does not transfer variable values from the service portal form, even if the form is submitted successfully. This is a common oversight because the record producer itself is triggered correctly, but the variable data is not passed without explicit mapping.

Answer

The record producer's mandatory fields are not all filled

Answer

The target table does not have the same fields as the source

Answer

The service portal is not configured to pass variables to the record producer

Question 6

During form submission, a mandatory field is not highlighted in red, and the form submits without requiring it. The field is made mandatory by a UI Policy that checks a condition set by a Client Script on form load. What is the most likely issue?

Accepted Answer

The UI Policy runs before the Client Script. The UI Policy runs before the Client Script, so when the UI Policy evaluates its condition to determine whether to make the field mandatory, the Client Script has not yet set the condition variable. As a result, the UI Policy condition fails, the mandatory attribute is not applied, and the form submits without requiring the field. The correct order of execution is UI Policy conditions first, then Client Scripts, then UI Policy actions.

Answer

A Data Policy overrides the mandatory attribute

Answer

The UI Policy is set to OnSubmit

Answer

The UI Policy runs after the Client Script

Question 7

When configuring a form, you want to add a new section. What is the correct approach?

Accepted Answer

Use the form designer. The form designer allows you to add sections directly. Options A, C, and D are not standard methods for adding sections.

Answer

Modify the default view

Answer

Create a UI action

Answer

Edit the table schema

Question 8

A form has a UI Policy that sets a field mandatory. The mandatory is not applied. Which is a likely cause?

Accepted Answer

UI Policy condition returns false. UI Policies enforce client-side business logic. The mandatory attribute is applied only when the UI Policy's condition evaluates to true. If the condition returns false, the mandatory setting is never applied, regardless of other settings. This is the most direct reason why a UI Policy's mandatory field would not take effect.

Answer

The field is already mandatory by dictionary

Answer

UI Policy order is too low

Answer

UI Policy is set to 'Run on load' only

Question 9

Refer to the exhibit. An administrator sets the system properties as shown. What is the result?

Accepted Answer

It decreases security by disabling HTML escaping in UI.. Disabling HTML escaping in UI system properties (e.g., glide.ui.escape_text) means user-supplied input is rendered as raw HTML. This directly reduces security by making the instance vulnerable to cross-site scripting (XSS) attacks, as malicious scripts in input fields will not be escaped before display.

Answer

It increases security by escaping all text in UI.

Answer

It enables cross-site scripting protection.

Answer

It has no effect on security.

Question 10

A system administrator needs to hide the 'Delete' button on the incident form for users with the 'itil' role, but allow it for administrators. What is the best approach?

Accepted Answer

UI policy with role condition. A UI Policy with a role condition is the best approach because it dynamically controls the visibility of the 'Delete' button on the incident form based on the user's role. UI Policies run client-side and can hide or show fields and buttons without requiring a page refresh, making them ideal for form-level UI changes. By setting the condition to 'role=itil' and the action to 'Hide', the button will be hidden for itil users but remain visible for administrators who do not have that condition applied.

Answer

Modify the form view to remove the button

Answer

Business rule checking role

Answer

ACL with condition on role

Question 11

Which TWO of the following are true regarding catalog item variables? (Choose two.)

Accepted Answer

Variables can be configured as 'Read only' after submission.. Catalog item variables can be configured as 'Read only' after submission. This setting is found in the variable's dictionary record under the 'Read only after submission' checkbox. When enabled, the variable's value becomes non-editable once the requested item (RITM) is submitted, which is useful for preserving audit trails or preventing changes to critical data like asset tags or approval decisions.

Answer

Variables defined on a catalog item cannot be referenced in workflows.

Answer

Variables are always displayed in the order they were created.

Answer

Variables in a variable set are independent and cannot share values across sets.

Question 12

A company has a business rule that runs on the Incident table during update. The rule checks if the state is 'In Progress' and sets a field. However, after saving, the field is not being set. Which of the following is the most likely cause?

Accepted Answer

The business rule is set to run after the record updates but another business rule with a higher order reverts the field.. If a business rule runs after the record updates (i.e., 'When to run' is set to 'After'), and another business rule with a higher order number runs later and reverts the field, the first rule's change will be overwritten. The order of execution is determined by the 'Order' field; lower numbers run first. Since the field is not being set after save, a higher-order 'After' rule is the most likely culprit, as it can undo the change made by the original rule.

Answer

The business rule is using 'setValue' instead of 'setDisplayValue'.

Answer

The business rule has the condition 'Current state changes' unchecked.

Answer

The business rule is set to run on 'display' instead of 'update'.

Question 13

A business rule is configured to run 'before' a record is updated. If the business rule sets a field value and then a subsequent 'after' business rule also updates the same field, what will be the final value stored in the database?

Accepted Answer

The value set by the 'after' business rule. In ServiceNow, business rules execute in a defined order: 'before' business rules run first, followed by 'after' business rules. When both a 'before' and an 'after' business rule update the same field, the 'after' business rule executes later in the transaction and its value overwrites the 'before' business rule's value. The final value stored in the database is therefore the one set by the 'after' business rule, because the database write occurs after all business rules have completed.

Answer

Both values are stored in a history field

Answer

The database rejects the second change

Answer

The value set by the 'before' business rule

Question 14

A catalog item uses Flow Designer to send an email notification when the state changes to 'fulfilled'. The flow uses a trigger 'State changed' on the requested item table. However, the email is not sent. The flow logs show the trigger fired. What is the most likely issue?

Accepted Answer

The flow action 'Send Email' is not configured with a valid recipient. The most common reason a flow trigger fires but the email is not sent is that the 'Send Email' action lacks a valid recipient. In Flow Designer, the 'Send Email' action requires a recipient (e.g., user, group, or email address) to be explicitly defined; if the recipient field is empty or references a non-existent variable, the action will execute without sending the email, and no error will be logged in the flow logs.

Answer

The trigger is set to 'State changed' but the state field is not properly referenced

Answer

The flow is set to 'Deactivated'

Answer

The email notification is blocked by an email property

Question 15

Which feature should be used to allow users to track the status of their service catalog requests via the self-service portal?

Accepted Answer

My Requests module. The My Requests module in ServiceNow provides users with a dedicated view to track the status, stage, and approval progress of their service catalog requests. It displays all requests submitted by the user, including those from both the service catalog and other request sources, and allows them to see real-time updates without needing ITIL roles or elevated permissions.

Answer

My Items module

Answer

Service Catalog module

Answer

Requested Items related list

Question 16

Refer to the exhibit. This ACL is applied to the Incident table for 'write' operation. A user is editing their own incident but is still denied. What is the issue?

Accepted Answer

The script returns true but another ACL denies.. When an ACL is applied to a table for 'write' operations, multiple ACLs can evaluate the same operation. Even if one ACL (the one shown) returns true, another ACL on the same table for the same operation may return false, causing the overall write to be denied. The exhibit shows a script that checks `current.caller_id == gs.getUserID()`, which should allow the user to edit their own incident, but another ACL with a higher order or a different condition is blocking the write.

Answer

The script returns false because current.caller_id is not the user's sys_id.

Answer

The ACL is set to 'read' instead of 'write'.

Answer

The user does not have the necessary role.

Question 17

A user is able to view records in the Incident table but cannot edit them. Which ACL type is preventing the edit?

Accepted Answer

write. (write). In ServiceNow, the write ACL controls the ability to update or edit existing records. Since the user can view records (read ACL allows this) but cannot edit them, the write ACL is the one blocking the operation. The write ACL is evaluated when a user attempts to modify a record after it has been created.

Answer

read

Answer

create

Answer

delete

Question 18

A catalog item has a variable 'category' (choice) and 'subcategory' (select box). When a user selects 'hardware' for category, the subcategory dropdown shows laptop and desktop. When 'software' is selected, it shows Operating System and Office Suite. However, users report that after selecting category, the subcategory dropdown does not update. What is the most likely cause?

Accepted Answer

The script incorrectly uses g_form.getControl instead of g_form.setOptions on the variable. The script must use `g_form.setOptions()` to dynamically update the choices of a select box variable (subcategory) based on the selected category. Using `g_form.getControl()` only retrieves the DOM element but does not modify the variable's options; it is typically used for UI manipulation like disabling or styling, not for updating choice lists. The failure to call `setOptions` means the subcategory dropdown never receives the new list of options, so it remains unchanged.

Answer

The 'subcategory' variable is not a select box but a reference field

Answer

The script returns on isLoading, which prevents the update

Answer

The onChange event is not triggered because the category field is a choice list

Question 19

A business rule set to run 'async' is supposed to update a large number of child records. The administrator notices that the updates are not being applied consistently. What is the most likely reason?

Accepted Answer

The async queue processes multiple instances simultaneously, causing race conditions. When a business rule is set to run 'async', it executes asynchronously via the system's queue. If the business rule updates a large number of child records, multiple instances of the same async business rule can be processed simultaneously by different queue workers. This concurrency can lead to race conditions, where one instance reads stale data or overwrites changes made by another instance, resulting in inconsistent updates.

Answer

The business rule condition is incorrect

Answer

The system property 'glide.sys.schedulers.max_threads' is set too low

Answer

The business rule is running 'before' instead of 'after'

Question 20

An ACL has a condition script that returns true if the user is a member of the 'service_desk' group and the record's 'state' is 'New'. The ACL type is 'read'. A user in the 'service_desk' group reports that they cannot see a record with state 'New'. What is the most likely cause?

Accepted Answer

The condition script does not have a default return false statement, so it returns undefined.. In ServiceNow, ACL condition scripts that lack an explicit return statement will return undefined, which is a falsy value. When the condition script returns undefined, the ACL does not grant read access, effectively denying the user from seeing the record even though they meet the intended group and state criteria. This is a common pitfall where developers forget to add a default return true or return false at the end of the script.

Answer

The ACL is defined on a different table that extends 'incident'.

Answer

The script uses gs.hasRole('service_desk') which checks role, not group membership.

Answer

Another read ACL exists that explicitly denies read access to the 'service_desk' group.