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

Question 1

A user cannot see any records in a module. What is the first thing to check?

Accepted Answer

User roles. User roles define the set of permissions and access rights a user has within ServiceNow. If a user cannot see any records in a module, the most fundamental and first check is their role assignment, because without the appropriate role (e.g., 'snc_internal' or a custom role granting read access), the user will have no visibility into any records, regardless of other settings.

Answer

User's browser cache

Answer

Module active flag

Answer

ACLs on the table

Question 2

Which THREE factors influence the order of fields on a form?

Accepted Answer

Form section order. The order of sections in a form determines the sequence in which fields are grouped and displayed. The form section order directly influences the overall layout and flow of the form, as fields are organized within sections that appear in the order defined by the section order.

Answer

Role-based field visibility

Answer

Field order in dictionary

Question 3

Which TWO are valid methods to add a new form section?

Accepted Answer

Adding a section in the sys_ui_section table. The sys_ui_section table stores the definitions of form sections in ServiceNow. Adding a record directly to this table is a valid method to create a new section on a form. Option E is correct because the Form Designer provides a graphical interface to add, remove, and rearrange sections on a form without manual table manipulation.

Answer

Creating a new UI page

Answer

Modifying the table's XML definition

Answer

Using an application file

Question 4

Refer to the exhibit. This is a script used in an ACL on the 'incident' table with 'type' set to 'record' and 'operation' set to 'read'. What is the effect of this ACL?

Accepted Answer

Denies read access to non-admin users. The ACL script uses `gs.getUser().hasRole('admin')` to check if the current user has the 'admin' role. If the user is not an admin, the script returns `false`, which denies read access. This effectively restricts read access to admin users only, denying it to all non-admin users. Option C correctly describes this behavior.

Answer

Grants read access only to admin

Answer

Denies read access to everyone

Answer

Grants read access to everyone

Question 5

A system administrator wants to ensure that a mandatory field on a form is always visible, even if the form section collapses. Which form layout option should be used?

Accepted Answer

Configure the field as 'Mandatory' and set 'Always visible' in the section. The 'Always visible' option on a form section ensures that mandatory fields remain displayed even when the section is collapsed. This is a native form layout configuration in ServiceNow that overrides the default behavior of hiding fields in collapsed sections, guaranteeing user visibility for required data entry.

Answer

Add a UI policy to show the field on load

Answer

Use 'glide.mandatory.visible' system property

Answer

Set the field to read-only

Question 6

An administrator notices that a UI policy on the Incident form is not firing for a specific user role. The UI policy is set to 'Run script' and has conditions on the 'State' field. The script uses g_form.setValue to set a field. What is the most likely reason the UI policy fails to execute for that role?

Accepted Answer

The UI policy condition uses a field that the role cannot see due to field-level security. UI policies execute client-side, and if a field used in the condition (e.g., 'State') is hidden from the user's role due to field-level security (FLS), the client-side script cannot read the field's value. This causes the condition to evaluate as false or undefined, preventing the UI policy from firing. The g_form.setValue call in the script would also fail silently if the target field is not visible or accessible to the role.

Answer

The UI policy is configured to run on the server side

Answer

The role does not have read access to the field being set

Answer

The UI policy is set to 'Run script' but the script has a syntax error

Question 7

A user reports that the 'My Tickets' module in the ITIL application does not show any records, even though the user has incidents assigned. What is the most likely cause?

Accepted Answer

The module's filter condition does not include the 'Assigned to' field for the current user. The 'My Tickets' module is a filtered list based on the Incident table, typically using a condition such as 'Assigned to = current user' to display only records assigned to the logged-in user. If this filter condition is missing or incorrectly configured, the module will show no results even when the user has assigned incidents. Option A is incorrect because 'Personalize' mode allows users to customize column layout, not hide records. Option B is incorrect because the module is a list filter, not a report; reports display aggregated data. Option D is incorrect because the module is accessible (it appears in the menu), so the user has the necessary 'incident_read' role; the issue is with the filter condition.

Answer

The module is set to 'Personalize' mode

Answer

The module is configured as a report, not a list

Answer

The user does not have the 'incident_read' role

Question 8

Which THREE factors should be considered when customizing navigation in ServiceNow? (Choose three.)

Accepted Answer

Performance impact of custom UI16 navigation. Option B is correct because customizing UI16 navigation (adding modules, changing the navigator structure) directly affects page rendering and load times, so the performance impact on the navigation must be evaluated. Option D is correct because users can personalize their own navigation, including reordering modules, and customization decisions must account for how that personalization interacts with the intended module ordering. Option E is correct because modules are gated by security roles, so any navigation customization must consider which roles are required to access each module to avoid exposing or hiding content incorrectly. Option A is not relevant because session timeout settings govern authentication session lifetime, not navigation customization. Option C is not relevant because application scope determines which application a record belongs to and its cross-scope access, not how navigation is customized for users.

Answer

Session timeout settings for inactive users

Answer

Application scope of the modules

Question 9

Refer to the exhibit. The UI Policy script above is meant to make the Short Description field mandatory when the incident state is 'In Progress'. However, it does not work. What is the most likely reason?

Accepted Answer

There is a syntax error in the function parameters: 'previous !=null' is invalid. The condition `previous != null` is invalid syntax in a UI Policy script. UI Policy scripts run on the client side and do not have access to the `previous` object, which is only available in server-side business rules. The correct approach would be to check the current state of the `state` field using `g_form.getValue('state')` or similar client-side methods.

Answer

The method 'g_form.setMandatory' is deprecated

Answer

The script is blocked by the 'glide.script.secure' property

Answer

The script uses 'current' object which is not available in client scripts

Question 10

Refer to the exhibit. An administrator imports these system properties into a ServiceNow instance. After the import, what is the expected impact on the UI?

Accepted Answer

Rich text fields will no longer have the ability to insert/edit tables. The exhibit shows system properties that disable the 'glide.ui.richtext[2].table' and 'glide.ui.richtext[3].table' properties. These properties control whether the table insert/edit button is available in rich text fields. Setting them to 'false' removes the table functionality from the rich text editor toolbar, so users can no longer insert or edit tables in rich text fields.

Answer

It will prevent users from editing list records in a UI16 form

Answer

Buttons will lose their shadow effect

Answer

No change because system properties are not used in UI

Question 11

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 12

A new ServiceNow administrator is tasked with setting up a dashboard for the IT help desk. The team wants to see a list of their assigned open incidents and a pie chart showing incident priority. The administrator creates two separate reports: a list report for open incidents and a pie chart for priority. Then, the administrator creates a new dashboard and adds both reports to it. However, the dashboard displays the reports in a single column, stacked vertically. The team wants the reports to appear side by side for a better overview. The administrator is unsure how to achieve this layout without rebuilding everything. What should the administrator do?

Accepted Answer

Edit the dashboard's layout property and change the column count to 2.. ServiceNow dashboards have a configurable layout property that allows administrators to set the number of columns (e.g., 1, 2, or 3) without needing to rebuild the dashboard. By editing the dashboard's layout and changing the column count to 2, the existing reports will automatically rearrange into a side-by-side format, preserving all report configurations and data sources.

Answer

Use a UI Macro to arrange report positions within the dashboard.

Answer

Modify the report output format to display inline.

Answer

Create a new dashboard using a two-column template and add the reports again.

Question 13

A company uses a custom application with a table named 'project_task' that contains several reference fields pointing to large tables (e.g., 'User', 'Department'). Users report that the 'project_task' form takes over 10 seconds to load, primarily due to the time required to fetch options for these reference fields. The administrator wants to improve the form loading performance without removing any fields or changing the user workflow. The instance is on a standard license and performance optimization is a priority. Which approach should the administrator take?

Accepted Answer

Enable the 'Use Ajax on Reference' option on the dictionary records for the reference fields.. Enabling 'Use Ajax on Reference' on the dictionary records causes the reference fields to load their options asynchronously via AJAX after the form renders, rather than during the initial page load. This significantly reduces the initial load time because the large reference tables (e.g., 'User', 'Department') are not queried synchronously when the form is first opened.

Answer

Convert all reference fields to choice fields with a predefined list.

Answer

Write a client script to load reference options asynchronously using GlideAjax.

Answer

Add a reference qualifier to each reference field to limit the number of options displayed.

Question 14

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.. The UI Action is active, has no conditions, and is associated with the Incident table, so it should appear. However, after an upgrade, the form layout may have been reset or the UI Action may not be placed in the desired form view. The administrator must check the form layout for the specific incident form view (e.g., 'Default view') to ensure the UI Action is added as a form button or context menu item, as UI Actions must be explicitly included in the form layout to appear on the form.

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 15

A company uses a customized service catalog form. Recently, after a patch application, several catalog variables that were configured as drop-downs (choice fields) are now displaying as plain text fields on the order form. The administrator checks the variable definitions in the catalog item and confirms that they are still set to 'Choice' type and that the choice list values are intact. The catalog form is using the default 'Order' view. No UI Policies or client scripts are modifying the variable types on the form. What is the most likely cause and resolution?

Accepted Answer

Clear the system cache (e.g., via 'Cache Flush' in System Diagnostics) and test again.. The most likely cause is that the system cache still holds the old form configuration from before the patch, causing the choice fields to render as plain text despite the correct variable definitions. Clearing the cache (via 'Cache Flush' in System Diagnostics) forces the platform to rebuild the form metadata from the current database state, resolving the display issue. This is a common post-patch symptom in ServiceNow because cached form layouts can become stale.

Answer

Check the form layout for the variable editor.

Answer

Re-import the catalog variables from a saved XML backup.

Answer

Check any UI Policies that may be converting the variable type.