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

Question 1

An administrator notices that a field named 'Customer Account' is not appearing on the Incident form even though it exists in the dictionary and is not hidden by any UI policy. The administrator checks the form layout and sees the field listed. What is the most likely reason the field is not visible?

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

Accepted Answer

The field is not included in the current view's form layout.. Form layouts are tied to specific views. If a field is present in the dictionary and not hidden by UI policies, the next likely cause is that the field is not added to the form layout for the view the user is accessing. The administrator should verify which view is being used and ensure the field is included in that view's layout. Other options like read-only, inactive dictionary, or client scripts are less likely given the scenario details.

Answer

The field's dictionary entry has the 'Active' flag set to false.

Answer

The field is set to read-only in the dictionary.

Answer

A client script is hiding the field onLoad.

Question 2

An administrator wants to create a new module under the 'User Administration' application menu. Which module type should be used to display a list of users?

Accepted Answer

List. A List module type is specifically designed to display a table of records from a specified table, such as the sys_user table for users. When creating a module under the 'User Administration' application menu, selecting List allows the administrator to configure the module to show a list view of user records, including columns, filters, and sorting options.

Answer

Form

Answer

URL

Answer

Report

Question 3

A company has a custom table 'u_asset' and wants the 'Asset' module in the application navigator to show only records where 'active=true'. How can this be achieved?

Accepted Answer

Set a condition on the 'Filter' property of the module. The 'Filter' property on a module in the application navigator allows you to define a condition (e.g., 'active=true') that restricts which records from the underlying table are displayed when the module is clicked. This is the standard method for scoping module results without altering security or user interface behavior globally.

Answer

Use an ACL to restrict access

Answer

Create a UI policy on the table

Answer

Add a client script to the list

Question 4

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 5

Which THREE are correct about form views? (Choose three.)

Accepted Answer

A form view defines which fields are displayed and their layout.. Option C is correct because a form view's core purpose is to specify which fields appear on a record form and how those fields are arranged (layout, sections, columns), so it directly defines displayed fields and their layout. Option D is correct because form views can be assigned to specific roles, allowing different user groups to see tailored form layouts based on their role. Option E is correct because when no form view is explicitly assigned to a user, the system falls back to the default view, ensuring users always have a usable form. Option A is not correct because form views are configuration records created within an instance and are not imported from other instances as a standard capability. Option B is not correct because a form view can contain multiple sections, not just one, so limiting it to a single section is false.

Answer

Form views can be imported from other instances.

Answer

A form view can only contain one section.

Question 6

A user reports that the 'My Work' module is missing from the application navigator. The administrator has assigned the user the 'sn_hr_core.hr_case_agent' role. Which step should the administrator take to troubleshoot this issue?

Accepted Answer

Check the sys_module list for role requirements on the 'My Work' module.. The 'My Work' module is a standard application module that may have role-based visibility restrictions defined in the sys_module record. By checking the sys_module list, the administrator can verify if the 'sn_hr_core.hr_case_agent' role is included in the required roles for the module. If the role is missing, the module will not appear in the application navigator for that user.

Answer

Ask the user to clear their browser cache and reload the instance.

Answer

Deactivate and reactivate the 'My Work' module in the application navigator.

Answer

Assign the user the 'admin' role to ensure full access.

Question 7

A ServiceNow administrator wants to create a new form section that appears only when the 'State' field is set to 'In Progress'. Which configuration should be used?

Accepted Answer

Create a UI Policy with a condition on the 'State' field.. A UI Policy is the correct configuration because it allows an administrator to define conditions (e.g., 'State' is 'In Progress') that dynamically show or hide form sections, fields, or make fields mandatory/read-only on the client side without requiring a server round trip. This is the standard mechanism for controlling form section visibility based on field values in ServiceNow.

Answer

Create an Access Control Rule (ACL) on the form section.

Answer

Create a Business Rule that sets the section visibility.

Answer

Create a UI Action with a condition on the 'State' field.

Question 8

An administrator needs to provide a custom view for the Incident table that hides the 'Description' field and reorders fields for a specific group of users. The view should be accessible from the form context menu. Which approach should the administrator take?

Accepted Answer

Create a new view for the Incident table and assign it to a user criteria that includes the group.. Creating a new view for the Incident table and assigning it to a user criteria that includes the group allows the administrator to define a custom form layout (hiding the 'Description' field and reordering fields) that is automatically applied to all members of that group. Views are the native mechanism in ServiceNow for providing different form configurations to different users based on user criteria, and they are accessible from the form context menu via the 'View' option.

Answer

Create a UI Policy that hides the 'Description' field and reorders fields for the specific group.

Answer

Use the 'Personalize Form' option to rearrange fields and share the view with the group.

Answer

Write a Business Rule that updates the form configuration when the group members open a record.

Question 9

Which TWO actions can an administrator perform using the 'Application Navigator' module (sys_app_module)? (Choose two.)

Accepted Answer

Change the order of modules within a menu.. Option A is correct because the Application Navigator module record (sys_app_module) includes an Order field that controls the sequence in which modules appear within their parent menu, so an administrator can change the order of modules within a menu. Option D is correct because a sys_app_module record can be configured as a Link type, where the Link type field lets you point the module to a specific URL or to a report, rather than to a table list or a record. Options B, C, and E are not actions performed through the Application Navigator module: UI Policies are separate records (sys_ui_policy) that control form field visibility and behavior, filter conditions for a module are set on the module's associated list/filter, not as a UI Policy, and the default form view is configured through form view and sys_user_preference settings, not the sys_app_module record.

Answer

Create a UI Policy that shows or hides the module.

Answer

Define a filter condition for the module's menu.

Answer

Set the default view for a form.

Question 10

Drag and drop the steps to activate a plugin in ServiceNow into the correct order.

Accepted Answer

Navigate to System Applications > All, find the plugin, click the plugin name, click Activate.. Activating a plugin in ServiceNow requires following the correct sequence: first navigate to the plugin list via System Applications > All, then locate the desired plugin, select it, and finally click the Activate button. Any deviation from this order will result in an error or missing functionality.

Answer

Navigate to System Applications > All, click Activate, find the plugin, click the plugin name.

Answer

Find the plugin, navigate to System Applications > All, click the plugin name, click Activate.

Answer

Click the plugin name, navigate to System Applications > All, find the plugin, click Activate.

Question 11

Drag and drop the steps to create a new UI Policy in ServiceNow into the correct order.

Accepted Answer

Step 1: Navigate to System Definition > UI Policies. Step 2: Click 'New'. Step 3: Define the condition (table, conditions, etc.). Step 4: Add UI Policy Actions (set visible, mandatory, etc.). Step 5: Save the UI Policy.. Creating a UI Policy in ServiceNow requires a logical sequence: first navigate to the correct module (System Definition > UI Policies), then create a new record, define the triggering condition, add actions to control form behavior, and finally save. Common mistakes include defining conditions before creating the record or adding actions before conditions, which are invalid because they depend on prior steps.

Answer

Step 1: Navigate to System Definition > UI Policies. Step 2: Click 'New'. Step 3: Add UI Policy Actions. Step 4: Define the condition. Step 5: Save the UI Policy.

Answer

Step 1: Navigate to System Definition > UI Policies. Step 2: Define the condition. Step 3: Click 'New'. Step 4: Add UI Policy Actions. Step 5: Save the UI Policy.

Answer

Step 1: Click 'New'. Step 2: Navigate to System Definition > UI Policies. Step 3: Define the condition. Step 4: Add UI Policy Actions. Step 5: Save the UI Policy.

Question 12

A company needs to make a field mandatory only when a checkbox is checked. Which feature should the administrator use?

Accepted Answer

UI Policy. UI Policy is the correct choice because it allows an administrator to make a field mandatory, visible, or read-only based on a condition evaluated on the client side without a server round-trip. When the checkbox is checked, the UI Policy condition triggers the mandatory attribute on the target field, providing immediate user feedback. This is the standard approach for client-side conditional mandatory fields in ServiceNow.

Answer

Client Script

Answer

Data Policy

Answer

Business Rule

Question 13

A user reports that a form loads slowly. The administrator notices several UI Policies and Client Scripts are running on the form. What is the best practice to improve form performance?

Accepted Answer

Set the UI Policy and Client Script to run only when needed using conditions. UI Policies and Client Scripts execute client-side in the browser, and their conditions determine whether they run on a given form. By setting them to run only when needed (e.g., based on a specific field value or form load event), you reduce unnecessary JavaScript execution, which directly improves form load and interaction performance. This is a best practice in ServiceNow to avoid processing scripts that are irrelevant to the current context.

Answer

Use only one UI Policy per form

Answer

Disable all client-side scripts

Answer

Convert all UI Policies to Business Rules

Question 14

An administrator creates an Application Menu with a condition and adds a module to it. Users with the correct role cannot see the module. The module has no roles restriction. What could be the issue?

Accepted Answer

The menu's condition fails for those users. The menu's condition may fail for those users, hiding the module. Option B would hide the module for all users if it were inactive. Option C would hide the entire menu for all users if it were inactive. Option D means no role restriction, so it should be visible, but the menu condition overrides.

Answer

The module is inactive

Answer

The application menu is not active

Answer

The module's roles are empty

Question 15

A user has personalized their form by rearranging fields. The administrator wants to reset the form layout to the default for that user. What should the administrator do?

Accepted Answer

Delete the user's personalization from sys_user_preference. User-specific form layout customizations are stored in the sys_user_preference table. Deleting the relevant preference record for that user resets the form to the default layout without affecting other users or system-wide settings.

Answer

Set the form's 'Reset' attribute to true

Answer

Run a scheduled job to clear all user preferences

Answer

Use the 'Restore Default' button on the form