SNOW-CSA Practice Test 10 — 10 Questions

Question 1

Which THREE actions can be performed using UI policies? (Choose three.)

Accepted Answer

Make a field read-only. UI policies in ServiceNow are client-side rules that dynamically change the behavior of form fields at runtime, and option B (make a field read-only) is correct because a UI policy action can set the 'Read only' attribute to true so users cannot edit the field. Option C (make a field mandatory) is correct because UI policies can toggle the 'Mandatory' attribute, forcing the user to populate the field before saving. Option E (hide a field) is correct because UI policies can set the 'Visible' attribute to false, removing the field from the form display. Option A (set a field's default value) is not a UI policy action — default values are configured via the dictionary Default value or a before-insert business rule/script, not UI policies. Option D (create a new field on the form) is not a UI policy action — fields are created by adding columns to the table (dictionary entries) and placing them on the form via the form designer/layout, not through UI policies.

Answer

Set a field's default value

Answer

Create a new field on the form

Question 2

A user reports that the 'My Tasks' module they frequently use has disappeared from the left navigation. Other users can still see it. What is the most likely cause?

Accepted Answer

The user accidentally used 'Personalize' and hid the module from their navigation. The 'Personalize' feature in ServiceNow allows users to hide modules from their own left navigation without affecting other users. When a user right-clicks a module and selects 'Personalize', they can choose to hide it, which removes it only from their view. Since other users can still see the module, this indicates a user-specific change rather than a global or role-based one.

Answer

A system property was changed that hides the module for all users

Answer

The module was deleted from the application menu by an admin

Answer

The user's role was changed and they no longer have access to the module

Question 3

Refer to the exhibit. A catalog item has a variable 'department' (choice list with values 'IT', 'HR', 'Finance') and a variable 'cost_center' (choice list initially empty). The client script is supposed to add an option to 'cost_center' when 'department' is set to 'IT'. However, when a user selects 'IT', no new option appears. What is the most likely reason?

Accepted Answer

The variable 'cost_center' is not a 'Choice' variable type.. The `g_form.addOption()` method only works on variables of type 'Choice' (or similar select-type variables like 'Select Box'). If 'cost_center' is not a Choice variable, the client script cannot dynamically add options to it, and the method call silently fails or has no effect. In ServiceNow, only choice-based variable types support runtime option manipulation via client-side APIs.

Answer

The script is a server-side script and cannot use 'g_form'.

Answer

The script needs to call 'g_form.clearOptions()' before adding options.

Answer

The method should be 'g_form.addOption()' with different syntax.

Question 4

A user complains that when they submit a catalog item, they receive an error: 'The variable is mandatory but has no value.' However, the variable is not marked as mandatory in the item's variable definition. What could be the cause?

Accepted Answer

A Catalog Client Script of type 'onSubmit' sets the variable mandatory.. A Catalog Client Script of type 'onSubmit' can dynamically set a variable as mandatory using the `g_form.setMandatory('variable_name', true)` method. This overrides the variable's definition in the catalog item, causing the 'mandatory but has no value' error even when the variable is not marked mandatory in the item's variable definition.

Answer

A Business Rule on the request table sets the variable mandatory.

Answer

A UI Policy on the record producer makes the variable mandatory.

Answer

The variable is mandatory in the parent catalog category.

Question 5

A catalog item has a variable 'Country' and another 'State'. The State variable should be mandatory only when Country is 'USA'. What is the most efficient way to achieve this?

Accepted Answer

Catalog UI policy with condition on Country. The most efficient way is to use a Catalog UI Policy (Option A). A Catalog UI Policy can set the mandatory attribute of a variable based on a condition on another variable, such as making 'State' mandatory when 'Country' equals 'USA'. This is declarative and requires no scripting. Option B (Workflow with a 'Set Mandatory' activity) acts after submission and cannot make a field mandatory before submission. Option C (Variable set with mandatory condition) is for grouping variables and does not enforce mandatory conditions. Option D (Catalog client script on Country's onChange event) is possible but requires more coding and is less supportable than a UI Policy.

Answer

Workflow with a 'Set Mandatory' activity

Answer

Variable set with mandatory condition

Answer

Catalog client script on Country's onChange event

Question 6

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 7

A project manager wants all incident forms to display a static informational message at the top for all users without any conditions. Which method is most efficient and requires the least ongoing maintenance?

Accepted Answer

Add a form annotation to the incident form view.. A form annotation is the most efficient method for displaying a static informational message on all incident forms without conditions. It requires no scripting, no conditions, and no ongoing maintenance, as it is a simple configuration on the form view that persists across all records.

Answer

Create a CMS banner that targets the incident module.

Answer

Create a UI Script that runs on load and adds a message.

Answer

Create a UI Policy with an 'always true' condition to show a message.

Question 8

A user reports that a catalog item's 'Requested for' field is not being set correctly after submission. The catalog item uses a workflow that includes a 'Set Requested For' activity. What is the most likely cause?

Accepted Answer

The 'Set Requested For' activity is configured with a static user value. The 'Set Requested For' activity in a ServiceNow workflow explicitly overrides the 'Requested for' field on the catalog item. If it is configured with a static user value, it will always set that user regardless of who submitted the request, causing the reported issue. This is the most direct cause because the activity's configuration takes precedence over the default behavior of populating the field with the requester.

Answer

The workflow context variable for requested for is missing

Answer

The workflow is not published

Answer

The catalog item variable mapping is incorrectly configured

Question 9

An organization wants to allow managers to approve requests from their direct reports through the mobile app. Which type of approval rule should be configured?

Accepted Answer

Approval - Manager. The Approval - Manager rule is correct because it automatically routes approval requests to the manager of the requester based on the manager relationship defined in the user record. This rule is specifically designed for scenarios where managers need to approve requests from their direct reports, leveraging the built-in manager hierarchy in ServiceNow.

Answer

User approval

Answer

Role approval

Answer

Group approval

Question 10

A scheduled report is generated but not sending email notifications to recipients. What should the administrator check first?

Accepted Answer

Check the email notification configuration for the scheduled report.. The most likely cause of a scheduled report generating but not sending email notifications is a misconfiguration in the email notification settings for that specific schedule. The administrator should first verify that the 'Send email' checkbox is enabled, that valid recipients are listed, and that the notification is not being suppressed by a condition or an inactive email account. Checking the email notification configuration directly addresses the delivery mechanism, which is the immediate point of failure.

Answer

Check the report source definition.

Answer

Check the report filter to ensure data exists.

Answer

Check the report output format (e.g., PDF, CSV).