SNOW-CSA UI, Navigation and Forms Practice Test 8 — 15 Questions

Question 1

A system administrator has added new fields to the Incident table through the dictionary. Users report that they cannot see these fields when they open an incident record. The administrator confirms the fields exist and are correctly configured. What should the administrator check first?

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

Accepted Answer

Check the form layout for the Incident table form view.. The form layout determines which fields are visible on a given form view. Even if fields exist in the dictionary and are correctly configured, they will not appear on the form unless they have been added to the form layout for the specific view (e.g., the default form view). The administrator should check the form layout by navigating to the Incident table's form view and ensuring the new fields are placed on the form.

Answer

Inspect client scripts on the Incident table for hiding logic.

Answer

Verify the access controls (ACLs) for the new fields.

Answer

Review the data policy configuration for the table.

Question 2

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 3

An administrator notices that a UI Policy does not seem to run on the incident form. Which two of the following are likely reasons for this issue? (Choose two.)

Accepted Answer

The UI Policy is defined on a different table.. Option A is correct because a UI Policy only executes on the table it is defined for (or on tables that extend it), so if the policy is defined on a different table than incident, it will never run on the incident form. Option C is correct because an inactive UI Policy is not evaluated or applied at all, so it will appear to do nothing on the form. Option B is incorrect because ordering only affects the sequence in which multiple UI Policies execute, not whether a policy runs. Option D is incorrect because a condition of 'true' with no additional condition simply means the policy always applies, which would make it run, not prevent it. Option E is incorrect because a syntax error in a condition script would typically cause an error or the policy to fail evaluation, but it is not one of the standard reasons a UI Policy silently does not run; the primary causes are table mismatch and inactivity.

Answer

The UI Policy is ordered after all other UI Policies.

Answer

The UI Policy condition is set to 'true' without any additional condition.

Answer

The UI Policy has a syntax error in its condition script.

Question 4

A large enterprise has extensively customized the Incident table with many UI Policies and Client Scripts. After a recent upgrade, users report that the incident form takes significantly longer to load, especially on records with many fields. The administrator investigates and discovers that multiple UI Policies share the same condition but are defined separately, causing the condition to be evaluated multiple times. Additionally, there are several client scripts that also evaluate the same conditions. The administrator wants to reduce page load time without altering the functionality. The instance is running on a mid-sized deployment with no budget for hardware scaling in the near term. Which course of action will best address the performance issue?

Accepted Answer

Combine UI Policies with identical conditions into a single UI Policy with multiple actions.. Combining UI Policies with identical conditions into a single UI Policy reduces redundant condition evaluations, directly improving performance. Increasing timeouts only masks the problem, disabling client-side scripting removes functionality, and converting to client scripts may still evaluate conditions inefficiently.

Answer

Disable all client-side scripting and rely solely on server-side validation.

Answer

Increase the system's form load timeout setting to prevent errors.

Answer

Convert all UI Policies to Client Scripts to move processing to the client.

Question 5

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 6

Refer to the exhibit. A user reports that the category field is not becoming mandatory on the incident form even when priority is set to '3' and the system property 'myapp.high_priority' is set to 'true'. What is the most likely cause?

Accepted Answer

The UI Policy is set to run on load only, and the priority field change does not trigger re-evaluation.. UI Policies have a 'Run on load' and 'Run on change' setting. By default, UI Policies run only when the form loads. If the policy is set to run on load only, changing the priority field after the form has loaded will not trigger re-evaluation, so the category field will not become mandatory even when the condition is met.

Answer

The system property 'myapp.high_priority' is set to 'false'.

Answer

The condition script uses 'g_form.getValue' which is not available in a UI Policy condition.

Answer

The user must refresh the page after changing priority for the UI Policy to take effect.

Question 7

A ServiceNow administrator needs to give the Service Desk group the ability to see and edit the 'Work notes' field on the Incident form, but only when the Incident is assigned to their group. Other groups should not see the field at all. The administrator creates a UI Policy with the condition 'Assignment group is Service Desk' and sets the 'Work notes' field to Visible and Editable. However, after testing, users in other groups can still see the 'Work notes' field. What is the most likely cause?

Accepted Answer

The UI Policy action for 'Work notes' was not set to 'Reverse if false'.. UI Policy actions only apply when the condition evaluates to true. To hide a field when the condition is false, the action must have 'Reverse if false' enabled. Without it, the field remains visible for users who do not meet the condition. This is a common oversight when configuring conditional field visibility.

Answer

The 'Work notes' field has a dictionary attribute that overrides UI Policies.

Answer

The UI Policy was created on the wrong table, such as Task instead of Incident.

Answer

The UI Policy condition is using 'Assignment group' instead of 'Assigned to'.

Question 8

An administrator opens the Incident form in the ServiceNow UI and notices that a previously configured UI Policy named 'Hide Priority for Low Impact' no longer hides the Priority field. The UI Policy is active, has a condition of Impact is 3 - Low, and runs on the form. The administrator confirms the user is viewing the default view and has no conflicting client scripts. Which configuration should the administrator verify first to explain why the UI Policy is not applying?

Accepted Answer

A UI Policy action for the Priority field is missing or is configured with 'Visible' set to true instead of false.. UI Policies change field behavior only through their UI Policy Actions. If the policy condition is met but no action targets Priority, or the action sets Visible to true, the field will not be hidden. Verifying the presence and configuration of the Priority action is the correct first step before investigating views, roles, or dictionary settings.

Answer

The UI Policy's 'Run scripts' option is enabled, which bypasses the field visibility actions.

Answer

The Priority field is marked as mandatory in the dictionary, which overrides UI Policy visibility.

Answer

The UI Policy's 'Global' field is set to true, so the policy applies to all views instead of the current view.

Question 9

A ServiceNow administrator needs to change the label of the 'Short description' field on the Incident form from 'Short description' to 'Summary' for all users. The field already exists on the form. Which action should the administrator take?

Accepted Answer

Edit the dictionary entry for the 'short_description' field and change the 'Label' field.. The dictionary entry is the authoritative source for a field's label. Changing the Label field on the dictionary record updates the display name across all forms, lists, and related lists. Form Designer and UI policies do not provide a supported way to globally rename a field. Therefore, editing the dictionary is the correct and only reliable method.

Answer

Create a UI policy that sets the field label to 'Summary' when the form loads.

Answer

Open the form in Form Designer and double-click the field to rename it.

Answer

Modify the form layout record to override the label with 'Summary'.

Question 10

A ServiceNow administrator is preparing to demonstrate the Incident form to a group of new ITIL users. The users need a compact form that shows only the most relevant fields, and the administrator does not want to modify the default form layout used by everyone else. Which form configuration feature should the administrator use to create a separate, role-specific layout for the Incident table?

Accepted Answer

A form view. A named form view is the correct mechanism because it stores a distinct field and section arrangement for a table and can be restricted to specific roles. This satisfies the requirement to show a compact layout to a subset of users while preserving the default view for everyone else.

Answer

A form section

Answer

A list view

Answer

A UI policy

Question 11

A ServiceNow administrator is designing a new form view for the Problem record. Users report that the form feels cluttered and that some fields are irrelevant for the 'Network' category. The administrator wants to conditionally control field behavior without writing client scripts. Which two configuration elements should the administrator use to hide, make mandatory, or make read-only fields based on the Category value? (Choose two.)

Accepted Answer

UI Policy Action. UI Policies and UI Policy Actions together provide declarative, condition-based control of field visibility, mandatory status, and read-only state. A UI Policy defines the condition, and its actions specify the field-level changes. This combination meets the requirement on the Problem form without client scripts, making it the correct pairing.

Answer

Client Script

Answer

UI Action

Answer

Dictionary Override

Question 12

A service desk agent reports that when they open a Change Request record, the form shows fields in an unexpected order and some fields appear in different sections than their colleague sees. Both users have the same roles and are opening the same record. Which form configuration element most directly controls the arrangement of fields into sections and the order in which they appear?

Accepted Answer

The form layout configured for the view the user is accessing.. Form layouts define field placement, section grouping, and order for a specific table and view. When two users see different arrangements on the same Change Request record, the most likely cause is that they are viewing different form views, each with its own layout. The layout is therefore the configuration element that most directly controls field arrangement.

Answer

The Access Control list applied to the Change Request table.

Answer

The system property controlling default field order on all forms.

Answer

The dictionary entry for each field on the Change Request table.

Question 13

A ServiceNow administrator is asked to add a new field to the Incident form. The field should appear in the 'Details' section, below the 'Short description' field. Which two components must the administrator configure to achieve this?

Accepted Answer

Dictionary and Form Design. Adding a new field requires creating it in the Dictionary and then placing it on the form using Form Design. The Dictionary defines the field's properties, while Form Design controls its position within sections. Both steps are essential.

Answer

UI Policy and Form Layout

Answer

Form Layout and Section

Answer

Client Script and Dictionary

Question 14

A ServiceNow administrator needs to make the 'Assignment group' field on the Incident form read-only when the incident state is 'Closed'. The administrator creates a UI policy with the condition 'State is Closed' and sets the 'Assignment group' field to read-only. However, users report that they can still edit the field when the state is 'Closed'. What is the most likely cause?

Accepted Answer

The 'Read only' check box is not selected on the UI policy action.. The most likely cause is that the UI policy action did not have the 'Read only' check box selected. UI policies require both a condition and explicit actions on fields. If the action is missing, the policy has no effect. While other factors like inactive policy or view restrictions could cause issues, they are less probable in this scenario. The administrator should verify the UI policy action configuration.

Answer

A client script is overriding the UI policy.

Answer

The UI policy is not applied to the correct view.

Answer

The UI policy is not active.

Question 15

A ServiceNow administrator needs to add the 'Assigned to' field to the Incident form and have it appear immediately after the 'Assignment group' field. The administrator has the appropriate role and opens the form in the instance. Which action should the administrator take to add the field to the correct position?

Accepted Answer

Use the Configure > Form Layout option, drag the field into the desired section, and save.. Form layout configuration is the correct tool for placing fields and controlling their order within sections. Dragging 'Assigned to' next to 'Assignment group' and saving writes the necessary form element records so the field appears in the intended position for users.

Answer

Add the field to the Incident table using the table designer.

Answer

Create a new UI policy that sets the 'Assigned to' field to visible and mandatory.

Answer

Modify the 'Assignment group' dictionary entry to reference the 'Assigned to' field.