SNOW-CSA Practice Test 35 — 15 Questions

Question 1

A large organization with 15,000 active users recently migrated from UI15 to UI16. Users are now reporting that form load times have increased significantly, especially on the Incident form, which has many sections and fields. The system administrator notices that the form is taking over 8 seconds to load. The administrator has checked the server logs and found that the majority of time is spent on 'getFormMeta' calls. The Incident form uses several UI policies, client scripts, and catalog client scripts. There are no business rules with heavy scripts on the table. Which course of action should the administrator take to improve form load performance?

Accepted Answer

Review and disable unnecessary UI policies that are set to run on form load. Option C is correct because disabling UI policies that run on form load can significantly reduce client-side processing. Option A is wrong because reducing system properties may affect other tables. Option B is wrong because client scripts can be optimized, but UI policies are often heavier. Option D is wrong because upgrading is not a quick fix and may not address the root cause.

Answer

Request an upgrade to the latest ServiceNow release which includes performance improvements

Answer

Set the system property 'glide.ui.form.load.max_sections' to 5 to limit sections

Answer

Convert client scripts to UI policies to leverage server-side execution

Question 2

A user reports that a custom UI Action button labeled 'Escalate' has disappeared from the incident form after a recent upgrade. The administrator checks the UI Action record and confirms that it is active, has no conditions defined, and is associated with the Incident table. The UI Action is set to appear in the context menu and form button. The administrator also confirms that no UI Policies or client scripts are hiding it. What should the administrator check next to resolve the issue?

Accepted Answer

Check the form layout for the incident form view to ensure the UI Action is included.. Even if the UI Action record is correct, it may not be placed in the default form view. The form layout determines which UI Actions are available on a given form view. If the UI Action is assigned to a different form view than the one users are using, it will not appear. Checking the form layout is the logical next step after verifying the UI Action configuration.

Answer

Check if there is a condition on the UI Action that evaluates to false.

Answer

Check the application scope to ensure the UI Action is in the correct scope.

Answer

Check the access controls (ACLs) for the UI Action.

Question 3

Refer to the exhibit. A user with username 'john.doe' tries to view an incident record. What is the outcome?

Accepted Answer

The user cannot view the incident because the ACL condition evaluates to false.. The ACL requires snc_internal role or username 'admin'. John has neither, so read is denied.

Answer

The user can view the incident because no ACLs apply to incident table.

Answer

The user can view the incident because they have the itil role.

Answer

The user cannot view the incident because the ACL is missing a condition for itil role.

Question 4

Refer to the exhibit. An incident is created with state 'New' (1). The user creating the incident has the role 'itil', not 'admin'. After the business rule runs, what is the value of the priority field?

Accepted Answer

The priority is set to 1 because business rules run with system user privileges.. The business rule runs before insert and sets priority to 1. However, the ACL for writing to priority requires admin role. The business rule runs with system user privileges, so it bypasses ACLs. Therefore, the priority is set to 1.

Answer

The priority remains null because the ACL denies write for non-admin users.

Answer

The priority is set to 1 because the business rule runs before the ACL check.

Answer

The priority is set to 1 but the update fails due to ACL.

Question 5

Refer to the exhibit. An incident is updated and state changes from 'New' to 'In Progress'. Active is true. The notification is not sent. Which is the most likely cause?

Accepted Answer

The assigned user field is empty, so there is no recipient for the notification.. The condition requires state changes AND active is true. Both are true. However, the notification might be missing a condition that the assigned user is not empty. Or the email template might be missing. But the most typical reason is that the 'Who will receive' is 'Assigned user', but the incident's assigned_to field is empty. The exhibit does not show the assigned user, but the condition doesn't check assigned_to. However, if assigned_to is empty, the notification will not send because there is no recipient. The log does not indicate an error, just that notification was not sent.

Answer

The condition 'state changes' is not satisfied because the state changed from 'New' to 'In Progress', which is a change.

Answer

The email template 'incident_update' is missing or invalid.

Answer

The notification is configured to send only on insert, not on update.

Question 6

Refer to the exhibit. A user submits a Laptop Request but receives the error shown. The user's session does not have a location set. What is the most likely cause?

Accepted Answer

The catalog item is configured to use a mandatory variable without a default value.

Answer

The user's role does not have access to u_location variable.

Answer

The flow is incorrectly configured to require u_location before submission.

Answer

The variable u_location is missing from the catalog item form.

Question 7

Refer to the exhibit. When a user submits a request for a laptop, the approval is granted by admin even though admin is not the manager. Which configuration allows this?

Accepted Answer

The catalog item's approval rule is set to 'Use approval group' and admin is a member of that group.

Answer

Admin has the 'approval_admin' role that overrides normal approval constraints.

Answer

The workflow has an approval activity with 'Delegate to group' and admin is the group manager.

Answer

The approval group 'IT Hardware' has admin as a member and approval delegation is enabled.

Question 8

Refer to the exhibit. A server provisioning request is in progress. The network configuration task is waiting for the VM creation task to provide an IP address, but no IP is passed. What is the most likely cause?

Accepted Answer

The flow did not capture the output variable from the VM creation task and pass it to the network task.

Answer

The IP address is manually entered by the VM team and they forgot to update it.

Answer

The network team does not have access to the VM task output.

Answer

The VM creation task did not run successfully despite being closed complete.

Question 9

Refer to the exhibit. A user without the admin role attempts to update an incident record where the caller's department is 'Finance'. The user's department is 'IT'. What will happen?

Accepted Answer

The update is denied because the condition evaluates to false.. The condition checks if user has admin role (false) or user's department equals caller's department (IT != Finance). Both false, so ACL denies write.

Answer

The update is allowed because the user has the admin role.

Answer

The update is allowed because the user's department matches the caller's department.

Answer

The update is denied because the ACL is misconfigured.

Question 10

Refer to the exhibit. A user selects 'Full Tunnel' and sees the info message, but the request is auto-approved. What is the most likely cause?

Answer

The client script runs on load and overrides the workflow condition.

Answer

The workflow condition is evaluated before the user selects the variable value.

Answer

The workflow condition is based on the variable 'u_vpn_type' but the condition is incorrectly configured to use '==' instead of '==='.

Answer

The workflow condition uses the variable value from the request, which may be set to 'Split Tunnel' due to a default.

Question 11

Refer to the exhibit. An incident is created with state 'New' and assigned_to is empty. Later, the state is changed to 'In Progress' and assigned_to is set to 'user1'. The notification does not fire. Which is the most likely reason?

Accepted Answer

The notification's condition includes 'state changes' which is evaluated at the time the trigger runs, not at the time of the update. The trigger may be waiting for a future time, but the condition is re-evaluated then. If the state hasn't changed since the update, it might not fire.. The condition requires state changes AND assigned_to is not empty. On update, both conditions are met, but the trigger may still be waiting. However, the condition is checked at the time of the update; it should fire. The issue might be that the notification is configured to send only on insert or update, but the trigger shows a future next_action, indicating it's scheduled. Possibly the notification is set to send after a delay or the condition uses 'state changes' which is a field change condition that might not be met if the state changed from null to 'In Progress'? Actually, state changes is a condition that checks if the field changed. The correct answer is that the condition 'state changes' is not satisfied because the previous state was empty? But incident state is always set. Another possibility: the notification is set to 'Record inserted or updated' but the trigger is still waiting; maybe the notification is timed and the condition is evaluated at the time of the trigger, not at the time of the update. The most likely reason is that the condition 'state changes' requires the previous value to be different, which it is. However, the exhibit shows a sys_trigger with state 'waiting' and a future next_action, indicating the notification is scheduled for a later time and hasn't run yet. So the notification will fire later.

Answer

The notification's 'Who will receive' is set to assignment group, but the assignment group is empty.

Answer

The notification condition requires the state field to change, but the state changed from 'New' to 'In Progress', so it should fire. The trigger is scheduled for later, so it will fire at that time.

Answer

The notification is configured to send only on insert, not on update.

Question 12

Your organization has implemented a notification on the 'incident' table to send an email when an incident's priority is changed. The notification is configured with a condition: 'Priority changes to 1 - Critical' and uses the 'Send email' action. Recently, administrators noticed that for a single incident that was updated multiple times, duplicate emails were sent. The incident record's audit history shows that the priority was only changed once. What is the most likely cause?

Accepted Answer

The notification condition has a script that incorrectly evaluates to true multiple times.. Option D is correct because the notification condition uses a script that evaluates to true multiple times during a single update, causing the 'Send email' action to fire repeatedly. Even though the audit history shows the priority changed only once, a flawed script can return true for other field changes or on subsequent database operations, leading to duplicate emails. This is a common issue when conditions are not properly scoped to detect only the specific field change.

Answer

The email notification is configured with 'Send when record is updated' and the update triggers multiple business rules that each fire the notification.

Answer

The 'Send email' action is set to 'Send to all users in the role' and multiple users have the same role.

Answer

The notification is also triggered by the 'cmdb_ci' field update.

Question 13

You are responsible for the CMDB at a large enterprise. The CMDB is used for change management and incident management. Recently, during a major incident, it was found that several critical CIs were missing from the CMDB, causing delays in troubleshooting. Further analysis reveals that the Discovery probes were not running on those devices due to schedule conflicts. You need to ensure that all critical devices are discovered regularly. What is the most effective solution?

Accepted Answer

Create a dedicated Discovery schedule for critical devices with a higher frequency.. Option C is correct because creating a dedicated Discovery schedule for critical devices ensures they are discovered at a higher frequency without being affected by schedule conflicts that impact the general discovery schedule. This approach guarantees that critical CIs are consistently updated in the CMDB, which is essential for effective change and incident management. By isolating critical devices into their own schedule, you avoid the overhead of increasing frequency for all devices while meeting the specific requirement for regular discovery of critical assets.

Answer

Manually add the missing CIs and set a reminder to check every week.

Answer

Use horizontal discovery to prioritize critical devices.

Answer

Increase the frequency of Discovery schedules for all devices.

Question 14

A company imports employee data from an HR system weekly. The import set table always retains the data from previous imports, causing storage issues. The administrator wants to automatically delete the import set rows after a successful transform to free up space. Which configuration should be made?

Accepted Answer

Select the 'Cleanup after transform' checkbox on the transform map.. Option A is correct because selecting the 'Cleanup after transform' checkbox on the transform map instructs the platform to automatically delete the import set rows from the staging table once the transform has completed successfully. This directly addresses the storage issue caused by retaining all historical import data, without requiring manual or scheduled cleanup.

Answer

Create a scheduled job to delete old import set rows.

Answer

Set a retention policy on the import set table.

Answer

Use a business rule to delete the import set row after transform.

Question 15

An SLA is defined for incident resolution with a 4-hour breach timer. The SLA should not count time when the incident is in 'Awaiting Customer' status. The administrator has configured a pause condition on the SLA definition. However, when the state changes to 'Awaiting Customer', the SLA timer continues to run. The administrator wants to troubleshoot the issue. What should the administrator check first?

Accepted Answer

Verify the SLA pause condition script or condition.. Option C is correct because the pause condition on the SLA definition is the primary mechanism that stops the breach timer when the incident enters a specific state, such as 'Awaiting Customer'. If the timer continues to run despite the state change, the most likely cause is that the pause condition script or condition is incorrectly configured, not evaluating to true, or missing entirely. The administrator should first verify this condition before investigating other potential issues.

Answer

Ensure the business rule that triggers SLA recalculation is active.

Answer

Check the SLA metric timeline.

Answer

Check the SLA schedule for the 'Pause' field.