SNOW-CSA Practice Test 4 — 10 Questions

Question 1

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?

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

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 2

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 3

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 4

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 5

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 6

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 7

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 8

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 9

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 10

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