SNOW-CSA UI, Navigation and Forms — 30 Questions

Question 1

A system administrator needs to allow end users to add a 'Mobile Phone' field to the incident form without modifying the form layout for all users. Which feature should be used?

Accepted Answer

Enable personalization on the form. Personalization allows individual users to add fields to a form without affecting the form layout for all users. By enabling personalization on the incident form, the system administrator grants end users the ability to add the 'Mobile Phone' field to their own view of the form, which is stored per user in the sys_user_preference table.

Answer

Create a new form section

Answer

Configure a UI policy

Answer

Set an ACL to allow field addition

Question 2

A user reports that after clicking 'New' on the incident module, the form loads but the 'Category' field is missing. Other users see the field. What is the most likely cause?

Accepted Answer

The user has a personal form layout that removed the field. The user's personal form layout can override the default form view, removing fields like 'Category' for that specific user while others see the field. This is a common scenario where a user has customized their own form layout, either intentionally or accidentally, by dragging the field off the form or using the personalization options.

Answer

The field is hidden by a UI policy

Answer

The field is not in the default form view

Answer

The user's role does not have read access to the field

Question 3

An administrator needs to ensure that when a user changes the 'State' field to 'Resolved' on an incident form, the 'Resolution Notes' field becomes mandatory. What should be configured?

Accepted Answer

UI policy. A UI policy is the correct choice because it allows you to make a field mandatory based on a condition on the same form without requiring a server round-trip. When the 'State' field changes to 'Resolved', the UI policy can set the 'Resolution Notes' field to mandatory, and it runs client-side in real-time as the user interacts with the form.

Answer

Business rule

Answer

Client script with onChange event

Answer

Data policy

Question 4

A user wants to quickly find an incident by its number without navigating through menus. Which feature should they use?

Accepted Answer

Navigator filter. The Navigator filter allows users to quickly locate any record, including incidents, by typing its number directly into the filter field at the top of the left-hand navigation pane. This bypasses the need to navigate through menus or modules, providing instant access to the specific record. It is the fastest method for finding a record by its unique identifier without leaving the current view.

Answer

Favorites

Answer

History

Answer

Global search

Question 5

An administrator wants to add a new application 'HR Service' to the application navigator with a custom icon. Which table stores the application menu and module definitions?

Accepted Answer

sys_app_module. The `sys_app_module` table stores both application menu and module definitions. When adding a new application like 'HR Service' to the navigator, a record is created in `sys_app_module` with a type of 'Application'. This record defines the application's name, icon, and other properties. Modules (sub-entries) are also stored in this table with a type of 'Module'. In contrast, `sys_app_application` is not a standard ServiceNow table for navigator definitions, and it only relates to application menu definitions, not module definitions.

Answer

sys_app

Answer

sys_app_application

Answer

sys_ui_module

Question 6

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 7

An administrator wants to create a new view called 'Mobile View' for the incident form to optimize it for mobile devices. Where should this view be created?

Accepted Answer

On the 'incident' table record under 'Views'. Views for specific tables, such as the 'incident' table, are created directly on the table record under the 'Views' related list. This allows the administrator to define a custom layout optimized for mobile devices, which is then stored as a 'sys_ui_view' record associated with the table. The platform uses this view when the 'Mobile View' is selected or when the form is accessed from a mobile device.

Answer

On the 'sys_ui_section' table

Answer

In the 'sys_ui_view' table directly

Answer

In the 'Application Navigator' module

Question 8

Which TWO statements about the ServiceNow application navigator are true? (Choose two.)

Accepted Answer

The navigator can be filtered by typing in the filter field.. Option C is correct because the application navigator includes a filter field that lets users type text to narrow the displayed applications and modules in real time, making navigation faster. Option E is correct because administrators can customize the navigator by creating new modules (and applications/categories) through the Application Menus and Modules configuration, controlling what appears for users. Option A is not correct because the navigator shows applications and modules, not a listing of all tables in the instance. Option B is not correct because favorites are managed through the Favorites/Bookmarks feature, not by adding links directly into the navigator structure. Option D is not correct because adding modules to the navigator is an administrative customization task, not something standard end users can do.

Answer

The navigator displays all tables in the instance.

Answer

Users can add links to the navigator as favorites.

Answer

End users can add new modules to the navigator.

Question 9

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

Accepted Answer

Link type. In the ServiceNow application navigator, a module's configuration requires specifying a Link type (Option B), which determines what the module opens — for example a list, a record, a URL, or a separator — and this drives the fields shown in the module form, making it a valid option. Option D, Condition filter, is also valid because it lets you define the filter conditions applied to the list or records the module displays, controlling which records appear when the module is selected. Option A is not correct because the table name is a required field (not optional) when the module type references a table. Option C is not correct because Role is not a module configuration field in the application navigator; access is governed by roles assigned to the module via related lists or menu configuration, not as a direct optional setting here. Option E is not correct because the module name is a required field, not an optional one.

Answer

Table name (optional)

Answer

Role (optional)

Answer

Module name (optional)

Question 10

A large enterprise with over 10,000 users and 50,000 active incidents has been using ServiceNow for two years. Recently, the IT managers have noticed that the incident form loads very slowly for end users, especially when opening existing records. The form contains over 40 fields including several reference fields like 'Configuration Item', 'Assignment group', and 'Assigned to'. The system administrator suspects that the form is slow due to the number of fields and the way they are loaded. Additionally, the admin wants to improve the user experience by reducing clutter. The admin is considering several approaches: (A) removing fields from the default view to reduce the number of fields loaded, (B) enabling 'Form Layout Personalization' so users can hide fields they don't need, (C) creating a new view with fewer fields and assigning it to all users via a UI policy based on role, (D) using 'Form Sections' to collapse fields into tabs. Which approach is the most effective for improving form load performance while maintaining usability?

Accepted Answer

Create a new view with only essential fields and assign it to users via a UI policy based on role.. Creating a new view with only essential fields and assigning it via a UI policy based on role directly reduces the number of fields loaded on the form, which minimizes database queries and client-side rendering overhead. This approach improves performance because ServiceNow loads all fields in a view, including reference fields that trigger additional lookups, so fewer fields mean faster load times. It also maintains usability by tailoring the form to specific roles, ensuring users see only relevant data without manual customization.

Answer

Enable Form Layout Personalization so users can hide fields they don't need.

Answer

Remove fields from the default view to reduce the number of fields loaded.

Answer

Use Form Sections to collapse fields into tabs.

Question 11

An administrator notices that a custom module added to the application navigator is not visible to users with the 'itil' role. The module's 'Application' field is set to 'Global' and 'Roles' is empty. What is the most likely cause?

Accepted Answer

The module's 'Active' flag is set to false.. The most likely cause is that the module's 'Active' flag is set to false. In ServiceNow, module visibility is controlled by the 'Active' flag and the 'Roles' field. An empty 'Roles' field means the module is visible to all users, but if the module is inactive, it will not appear in the navigator for anyone.

Answer

The module's 'Application' field is set to 'Global', which restricts visibility to admin users only.

Answer

The module was added using the 'Personalize Module' option, which is user-specific.

Answer

The 'Roles' field is empty, so the module is not visible to any user.

Question 12

Which THREE of the following are valid ways to customize the form layout for a table in ServiceNow? (Choose three.)

Accepted Answer

Using the 'Form Layout' option from the table's context menu to add/remove fields.. Option A is correct because the 'Form Layout' option (Configure > Form Layout) from a table's context menu or the form's hamburger menu opens the slushbucket designer that lets an admin add, remove, and order fields on the form. Option C is correct because UI Policies include a 'Reorder' action that can move fields to a specified position on the form at runtime, making it a valid layout-customization mechanism. Option E is correct because form sections are stored in the sys_ui_section table, accessible via the 'Form Sections' related list on the table's dictionary entry, where admins can add, rename, and arrange sections and their fields. Option B is not correct because 'Personalize Form' only changes the layout for the individual user, not for all users. Option D is not correct because a Client Script can hide or show fields but does not reorder or restructure the form layout itself.

Answer

Using the 'Personalize Form' option to reorder fields for all users.

Answer

Writing a Client Script that sets the visibility of fields.

Question 13

A company recently upgraded their ServiceNow instance from Paris to Quebec. After the upgrade, several users report that the 'Assignment Group' field on the Incident form is missing for users with the 'itil' role. The field is still visible for administrators. The administrator checks the dictionary entry for the 'assignment_group' field and finds that it has no roles set. The form layout for the 'Default view' includes the field. The UI Policy that previously controlled visibility of this field has been deactivated. An audit of the upgrade logs shows no errors related to this field. The administrator suspects that a new feature introduced in Quebec might have affected the field visibility. Which action should the administrator take to restore the field visibility for 'itil' users?

Accepted Answer

Check the 'Visibility' field on the dictionary entry for 'assignment_group' and set it to 'All' if it is set to 'Admin'.. In Quebec, a new 'Visibility' field was added to dictionary entries. When set to 'Admin', the field is hidden from non-admin users regardless of form layout or UI Policies. Since the dictionary entry for 'assignment_group' has no roles set but the field is missing for 'itil' users, the administrator should check and set the 'Visibility' field to 'All' to restore visibility.

Answer

Create a UI Policy that sets the 'assignment_group' field visible when the form loads.

Answer

Add the 'itil' role to the 'Roles' field on the dictionary entry for 'assignment_group'.

Answer

Create a new Access Control Rule (ACL) to grant read access to the 'itil' role for the 'assignment_group' field.

Question 14

Match each ServiceNow application scope to its description.

Accepted Answer

Global scope: Available to all users across the instance.. Global scope means application is available to all users. User scope restricts access to a specific user or group. System scope grants system privileges. The distractors confuse these definitions.

Answer

Global scope: Runs with system privileges.

Answer

User scope: Available to all users.

Question 15

Match each ServiceNow report type to its visual representation.

Accepted Answer

Bar chart: Uses vertical or horizontal bars to compare quantities across categories.. Bar charts compare categories using bars, pie charts show proportions as slices, and line charts display trends over time. Common confusions involve swapping bar and pie chart definitions.

Answer

Bar chart: Represents data as slices of a circle, showing proportions of a whole.

Answer

Pie chart: Uses vertical or horizontal bars to compare quantities across categories.

Question 16

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?

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 17

A system administrator wants to add a new section to a form. Which component should they edit?

Accepted Answer

Form Layout. The Form Layout component is the correct choice because it directly controls the arrangement and visibility of fields, sections, and related lists on a ServiceNow form. Editing the Form Layout allows the administrator to add a new section by dragging and dropping a section placeholder or by configuring the form's structure through the Form Layout UI.

Answer

Dictionary

Answer

Table

Answer

UI Page

Question 18

An administrator configures a UI Policy to display a warning message when a reference field is empty. The warning message does not appear. The UI Policy is set to run on both load and submit. What is the most likely cause?

Accepted Answer

The UI Policy is inactive. An inactive UI Policy will not execute any of its actions, including displaying warning messages, regardless of its configuration to run on load and submit. The UI Policy must be set to active in its property to be evaluated by the platform.

Answer

The condition uses the wrong operator

Answer

The UI Policy is set to run on submit only

Answer

The warning message is not enabled on the UI Policy

Question 19

A system administrator wants to prevent users from changing the value of a field after the record is saved. Which two features can be used to enforce this? (Choose two.)

Accepted Answer

Data Policy (update). (Data Policy (update)) is correct because a Data Policy with an 'update' condition can enforce that a field's value cannot be changed once the record is saved. It runs server-side during the update operation and can prevent the update from completing if the field value differs from the stored value. Option E (Dictionary (read only)) is correct because setting the 'Read only' attribute on a dictionary entry makes the field non-editable on forms and also prevents updates via web services or other server-side operations, effectively locking the value after the record is saved.

Answer

Business Rule (before query)

Answer

Client Script (onSubmit)

Answer

UI Policy (on load)

Question 20

Refer to the exhibit. A UI Policy is configured with the above condition script to make the 'work_notes' field mandatory when state is 1 and caller_id is valid. When the state is 1 and caller_id is empty, the mandatory attribute is not applied. What is the cause?

Accepted Answer

The isValid() method is not available in UI Policy context. The `isValid()` method is a GlideRecord method that operates on the server side, not a client-side method available in UI Policy scripts. UI Policies run on the client side (in the browser), so `isValid()` is not defined in that context, causing the condition to fail silently or not behave as expected. This is why the mandatory attribute is not applied when `caller_id` is empty, even though the script intends to check for a valid record.

Answer

The condition uses '&&' instead of '||'

Answer

There is a syntax error in the script

Answer

The caller_id field is empty