SNOW-CSA Practice Test 25 — 15 Questions

Question 1

An administrator notices that a scheduled job that creates Catalog Tasks from a report runs successfully but produces duplicate tasks for the same request. What is the most likely cause?

Accepted Answer

The report does not filter out tasks that have already been created. The most likely cause of duplicate Catalog Tasks is that the report driving the scheduled job does not include a filter to exclude records for which a task has already been created. Without this filter, each time the job runs, it re-evaluates the same source records and creates a new task for each, leading to duplicates.

Answer

The scheduled job uses the 'Run once' option

Answer

The report condition uses '=' instead of 'starts with'

Answer

The scheduled job runs too frequently

Question 2

A catalog item uses a 'Catalog Client Script' to hide a variable when another variable is set to 'No'. However, the script is not working. The script is of type 'onChange' and the variable to hide is a 'Single Line Text'. What is the most likely cause?

Accepted Answer

The variable's 'Display' property is set to 'Static' or 'Read only'.. When a variable's 'Display' property is set to 'Static' or 'Read only', the client-side script cannot override that setting via `g_form.setDisplay()`. The catalog client script runs on the client, but the variable's display behavior is enforced by the platform's UI policy layer, which takes precedence over client script calls. This is a common misconfiguration where the variable's display property is locked, preventing the onChange script from hiding it.

Answer

The variable type 'Single Line Text' does not support hiding.

Answer

The script is missing a 'g_form.setDisplay()' call.

Answer

The script should be of type 'onSubmit' instead of 'onChange'.

Question 3

Which TWO are valid options when configuring a module in the application navigator? (Choose two.)

Accepted Answer

Link type. The 'Link type' is a required configuration when adding a module to the application navigator. It determines how the module behaves when clicked, such as opening a new window, displaying in the same window, or using a specific UI action. Without setting the link type, the module cannot properly navigate the user to the intended target.

Answer

Table name (optional)

Answer

Role (optional)

Answer

Module name (optional)

Question 4

An administrator wants to add a new section to the incident form to group related fields. Which tool should they use?

Accepted Answer

Form Designer. The Form Designer is the correct tool because it allows administrators to add new sections to an incident form by dragging and dropping fields into a new section container. This is the dedicated interface for modifying form layouts, including creating sections to group related fields, without needing to write code or use other configuration tools.

Answer

Dictionary Override

Answer

Application Navigator

Answer

UI Policy

Question 5

Which three of the following are valid methods to control field visibility on a form based on user input? (Choose three.)

Accepted Answer

Dynamic Form Configuration.. Dynamic Form Configuration (B) is correct because it allows form fields to be shown, hidden, or made mandatory based on conditions evaluated against user input or other field values, directly controlling field visibility on a form without requiring server-side processing. Client scripts that set field attributes (C) are correct because they can manipulate field visibility by setting the 'visible' attribute dynamically in response to user input. UI Policies with visibility actions (E) are correct because they are client-side scripts that can show or hide fields based on conditions evaluated on the browser. Data Policies (A) are incorrect because they are server-side enforcement rules that control data integrity and do not directly control form field visibility. Role-based ACLs on the field (D) are incorrect because they control access to the field based on user roles, not visibility based on user input.

Answer

Data Policies with conditions.

Answer

Role-based ACLs on the field.

Question 6

A transform map for importing incidents uses a co-paste field mapping for 'short_description' that references the source field 'caller_id'. The import fails with the error shown. What is the most likely cause?

Accepted Answer

The import set does not contain a column named 'caller_id'. The error indicates that the transform map is trying to reference a source field named 'caller_id' via a co-paste field mapping, but the import set table does not contain a column with that name. Co-paste mappings combine source fields from the import set row, so if 'caller_id' is missing from the import set columns, the transform engine cannot find the data and fails. Option B correctly identifies that the import set lacks the required column.

Answer

The 'caller_id' field in the target table is read-only

Answer

The target table 'incident' does not have a 'caller_id' field

Answer

The co-paste function cannot combine more than two fields

Question 7

A company has an SLA definition that starts when the state is 'New' and pauses when the state is 'On Hold'. A task is created with state 'New' at 10:00 AM. At 10:30 AM, the state is changed to 'In Progress'. At 11:00 AM, the state is changed to 'On Hold' for 30 minutes, then back to 'In Progress' at 11:30 AM. The task is resolved at 12:00 PM. The SLA has a 2-hour duration. What is the elapsed time used for SLA compliance?

Accepted Answer

1 hour 30 minutes. The SLA definition starts when the state is 'New' and pauses when the state is 'On Hold'. The task was in 'New' from 10:00 to 10:30 (30 minutes), then 'In Progress' from 10:30 to 11:00 (30 minutes), then 'On Hold' from 11:00 to 11:30 (30 minutes, paused), then 'In Progress' from 11:30 to 12:00 (30 minutes). The total elapsed time for SLA compliance is the sum of non-paused time: 30 + 30 + 30 = 1 hour 30 minutes, which is within the 2-hour SLA duration.

Answer

2 hours

Answer

1 hour 30 minutes from state change to resolve

Answer

1 hour

Question 8

Refer to the exhibit. An incident is assigned to a group, but no email notification is sent. Which is the most likely cause?

Accepted Answer

The assigned_to field did not change because only the group was updated.. The default 'Assignment' notification in ServiceNow triggers on a change to the `assigned_to` field, not the assignment group field. When only the group is updated, the `assigned_to` field remains unchanged, so the notification condition is not met. Option D is incorrect because the question does not indicate the incident is closed, and even if it were, state 6 (Closed) does not inherently suppress notifications unless explicitly configured; the most likely cause is the group update not triggering the notification.

Answer

The email template is missing.

Answer

The assignment group has no members.

Answer

The incident state is 6 (Closed).

Answer

The assigned_to field did not change because only the group was updated.

Question 9

A system administrator has created a UI Policy to make several fields mandatory on the incident form when the 'Category' field equals 'Software'. The policy works correctly when creating a new incident: if the user selects 'Software', the fields become mandatory. However, when viewing an existing incident and changing the category to 'Software', the fields do not become mandatory. The administrator verifies that the condition is correctly set to 'Category equals Software' and the action sets mandatory true on the target fields. The UI Policy is active and the order is not relevant. What is the most likely reason for this behavior?

Accepted Answer

The UI Policy is set to 'Run on Load' only, not 'Run on Change'.. UI Policies have two execution triggers: 'Run on Load' (fires when the form loads) and 'Run on Change' (fires when a specified field changes). When creating a new incident, the form loads with the condition already evaluated, so 'Run on Load' makes the fields mandatory. However, when editing an existing incident and changing the Category to 'Software', the change event does not re-trigger the policy unless 'Run on Change' is enabled. Without this setting, the policy only applies on initial form load, not on subsequent field modifications.

Answer

The UI Policy condition is checking the wrong field.

Answer

The UI Policy order is too low compared to other policies.

Answer

The UI Policy is inactive.

Question 10

A company wants to block all update operations on the 'problem' table for users with only the 'itil' role, except for the user who created the record. Which ACL configuration should be used?

Accepted Answer

Create an ACL with type 'record', operation 'write', role 'itil', condition script 'current.created_by != gs.getUserID()', and set 'Requires role' true.. It uses a condition script that denies write access to users with the 'itil' role when the current record's creator is not the logged-in user. The ACL type 'record' with operation 'write' and 'Requires role' checked ensures that only users with the 'itil' role are evaluated, and the condition script 'current.created_by != gs.getUserID()' returns true for users who did not create the record, thus blocking their update operations. This matches the requirement to block all updates except for the record creator.

Answer

Create an ACL with type 'record', operation 'write', role 'itil', condition script 'current.assignment_group == gs.getUser().getMyGroups()', and set 'Requires role' true.

Answer

Create an ACL with type 'record', operation 'write', role 'itil', condition script empty, and uncheck 'Requires role'.

Answer

Create an ACL with type 'record', operation 'write', role 'itil', condition script 'current.created_by == gs.getUserID()', and set 'Requires role' true.

Question 11

Refer to the exhibit. A ServiceNow administrator created a catalog item that allows users to select a CI via a reference variable named 'ci'. The business rule shown is supposed to update the CI's operational status to 'In Production' when the requested item is closed complete. However, the CI status is not being updated. What is the most likely cause?

Accepted Answer

The script does not properly retrieve the CI record because current.variables.ci returns the sys_id but may not be accessible directly in an after business rule without using the sc_item_option table.. In an 'after' business rule on the Requested Item (sc_req_item) table, the variable values from the catalog item are not directly accessible via current.variables.ci. Instead, they are stored in the sc_item_option table and must be retrieved using a GlideRecord query on sc_item_option joined to the requested item's sys_id. The script attempts to use current.variables.ci, which does not resolve to the CI's sys_id in this context, causing the update to fail.

Answer

The condition 'current.state.changesTo(3)' is incorrect; it should check if the state is already 3.

Answer

The reference variable 'ci' is not storing the sys_id of the CI; it stores the display value.

Answer

The business rule runs 'Before' instead of 'After', so the state hasn't changed yet.

Question 12

A catalog item uses a variable substitution in the short description like: 'Request for ${variable_name}'. The variable is a reference field to the 'Configuration Item' table. When a user submits the request, the short description displays 'Request for sys_id' instead of the display value. What could be the cause?

Accepted Answer

The display field of the Configuration Item table is not set correctly. The variable substitution in the short description uses the display value of the reference field. If the display field of the Configuration Item table is not set correctly (e.g., it is set to 'sys_id' instead of a meaningful field like 'name'), the substitution will output the sys_id instead of the intended display value. This is a common configuration issue in ServiceNow where the display field determines which column value is shown in reference fields and variable substitutions.

Answer

The reference qualifier on the variable is restricting allowed values

Answer

The variable type is not a reference field

Answer

The variable substitution uses the field name instead of the variable name

Question 13

A business rule is set to run on 'before update' on the 'incident' table. The script updates 'current.description' and then calls 'current.update()'. What is the likely outcome?

Accepted Answer

The script causes a recursion error or multiple updates.. In ServiceNow, calling `current.update()` inside a 'before update' business rule triggers a recursive loop because the update operation re-invokes the same business rule. The platform detects this recursion and typically throws an error or causes multiple updates, leading to the described outcome. Option B is correct because the script explicitly calls `current.update()`, which is prohibited in before business rules to prevent infinite loops.

Answer

The description is updated and no error occurs.

Answer

The script fails silently because current.update() is not allowed in before business rules.

Answer

The script runs but the description is not updated.

Question 14

Based on the exhibit, why did the transform create or update zero records?

Accepted Answer

The script on the category field has an error. The script on the category field contains an error that causes the transform to fail silently, resulting in zero records being created or updated. In ServiceNow, a transform script that throws an unhandled exception or returns an unexpected value (e.g., 'false' or 'skip') will abort the mapping for that row, and if it affects all rows, no records are processed. The exhibit likely shows a script that either has a syntax error or logic that prevents any row from passing through the transform map.

Answer

The assigned_to field mapping is missing a coalesce

Answer

The staging table does not match the target table

Answer

The coalesce field is set incorrectly

Question 15

A user needs to access the 'Update Sets' module directly from the application navigator. Which filter path should they use?

Accepted Answer

sys_update_set.list. The 'Update Sets' module in ServiceNow is stored in the 'sys_update_set' table. To access it directly from the application navigator, you must use the table name followed by '.list', which renders the list view of that table. Therefore, 'sys_update_set.list' is the correct filter path.

Answer

update_set.list

Answer

sys_update.set.list

Answer

update_sets