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

Question 1

A performance issue is reported on the Change Request list view: it takes several seconds to load. The list has 5000 records and uses several calculated fields. Which optimization should be applied first?

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

Accepted Answer

Create a new list view that includes only essential columns. Reducing the number of columns in a list view minimizes the data retrieved per row, directly addressing the performance bottleneck caused by calculated fields. Calculated fields are evaluated for every row on every load, so removing unnecessary columns reduces server-side computation and database query overhead. This is the most effective first optimization as it targets the root cause without increasing data volume or altering system thresholds.

Answer

Add a group by condition on the list view

Answer

Set the list control to 'Auto' to reduce data threshold

Answer

Increase the 'glide.ui.list.threshold' system property to 10000

Question 2

Which UI element allows an administrator to add a new section to an existing form and populate it with fields?

Accepted Answer

Form Layout configuration. The Form Layout configuration is the correct UI element because it allows administrators to define the layout of fields on a form, including adding new sections and populating them with fields. This is done by dragging and dropping fields into the desired section within the Form Layout configuration page, which directly controls the form's structure.

Answer

Access Control Rule

Answer

UI Policy

Answer

Dictionary Entry

Question 3

A form has a reference field to the 'User' table. The administrator wants to ensure that when a user is selected, the user's email is automatically populated in another field. Which mechanism should be used?

Accepted Answer

UI Policy with an 'onChange' condition. A UI Policy with an 'onChange' condition is the correct mechanism because it triggers client-side when the reference field changes, allowing the system to populate the email field based on the selected user. In ServiceNow, UI Policies can set field values dynamically when a field changes, using dot-walking to retrieve related field values like email from the User table. This approach works reactively on user interaction, unlike dictionary defaults which only apply on record creation.

Answer

Dictionary entry with a default value calculated from the reference field

Answer

Access Control Rule on the email field

Answer

Data lookup field configuration

Question 4

An administrator needs to create a UI action that appears on the form context menu for the Incident table, but only when the record is in 'In Progress' state. Which configuration is required?

Accepted Answer

Set the condition on the UI action to 'current.state == 2'. UI actions can have a condition field that evaluates server-side JavaScript. Setting the condition to 'current.state == 2' ensures the UI action appears only when the Incident record's state field equals the 'In Progress' value (typically 2 in the default state model). This is the standard, built-in mechanism for controlling UI action visibility based on record data.

Answer

Create a UI policy that changes the form when state is 'In Progress'

Answer

Write an ACL on the UI action table

Answer

Assign the UI action to a role that only users in this state have

Question 5

Which TWO best practices should be followed when designing forms in ServiceNow? (Choose two.)

Accepted Answer

Use a consistent order of fields across similar tables. Options A and B are correct. A: Using a consistent field order across similar tables improves user experience and makes forms predictable. B: Grouping related fields into sections with clear headings enhances form readability and helps users find information quickly. C is incorrect because mandatory fields should always be visible, not hidden via UI policies, as hiding them can cause submission errors. D is incorrect because many-to-many fields are not inherently better than reference fields; the choice depends on the relationship requirements, and using many-to-many fields incorrectly can complicate data model. E is incorrect because including too many fields on one form can overwhelm users and degrade performance.

Answer

Hide mandatory fields using UI policies to reduce clutter

Answer

Use many-to-many fields instead of reference fields for better relationships

Answer

Include as many fields as possible on one form to minimize navigation

Question 6

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

Accepted Answer

Performance impact of custom UI16 navigation. Custom UI16 navigation items, such as custom modules or menus, can introduce performance overhead due to additional server-side processing, ACL evaluations, and UI rendering. ServiceNow recommends evaluating the number and complexity of custom navigation elements to avoid degrading page load times and user experience.

Answer

Session timeout settings for inactive users

Answer

Application scope of the modules

Question 7

Which TWO methods allow an administrator to make a field read-only on a form? (Choose two.)

Accepted Answer

Create a UI policy that sets the field to read-only when a condition is true. A UI policy can dynamically set a field to read-only based on a specified condition, such as a particular state or value. This allows administrators to control field editability at runtime without permanently altering the field's definition. Option D is correct because setting the 'Read only' attribute in the dictionary entry makes the field read-only globally across all forms and views, providing a static, system-wide restriction.

Answer

Configure the form layout to hide the field

Answer

Create an ACL that denies write access

Answer

Add the field to a related list

Question 8

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 9

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 10

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. The 'getFormMeta' call retrieves the form's structure, including all UI policies, client scripts, and related metadata. UI policies that run on form load are executed server-side during this call, and excessive or unnecessary UI policies can significantly increase load time. Disabling UI policies that are not needed on form load directly reduces the metadata payload and processing time, improving performance.

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 11

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?

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 12

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 13

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 14

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 15

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.