Courseiva

CCNA UI, Navigation and Forms Questions

75 of 94 questions · Page 1/2 · UI, Navigation and Forms · Answers revealed

Practice these questionsDomain overviewAll questions
1
Multi-Selectmedium

Which TWO of the following are valid ways to modify the layout of a form in ServiceNow?

Select 2 answers
A.Using the Form Designer
B.Creating an Access Control Rule (ACL)
C.Creating a UI Policy that hides or shows fields
D.Modifying the Dictionary Override
E.Creating a report on the table
AnswersA, C

Form Designer is the primary tool for layout changes.

Why this answer

The Form Designer is the dedicated tool in ServiceNow for modifying form layouts, including rearranging fields, adding sections, and configuring field properties. It provides a drag-and-drop interface to control the position and visibility of fields on a form, making it a primary method for layout changes.

Exam trap

The trap here is that candidates may confuse UI Policies (which dynamically modify form behavior) with Access Control Rules (which manage security), leading them to incorrectly select ACLs as a layout tool instead of recognizing UI Policies as a valid method for modifying form visibility.

Practice this question →
2
MCQmedium

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?

A.Request an upgrade to the latest ServiceNow release which includes performance improvements
B.Set the system property 'glide.ui.form.load.max_sections' to 5 to limit sections
C.Convert client scripts to UI policies to leverage server-side execution
D.Review and disable unnecessary UI policies that are set to run on form load
AnswerD

UI policies execute on load and can be heavy; disabling unneeded ones improves performance.

Why this answer

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.

Exam trap

The trap here is that candidates may confuse UI policies (server-side, run on form load) with client scripts (client-side, run after form load) and incorrectly assume that moving logic to UI policies (Option C) would improve performance, when in fact it would increase server load during the 'getFormMeta' call.

How to eliminate wrong answers

Option A is wrong because upgrading to a newer release may include general performance improvements, but it does not address the specific issue of excessive UI policies causing slow 'getFormMeta' calls; the problem is configuration-based, not version-based. Option B is wrong because the system property 'glide.ui.form.load.max_sections' limits the number of visible sections on a form, but the Incident form's load time issue is due to UI policies, not the number of sections; this property would not reduce the metadata processing overhead. Option C is wrong because converting client scripts to UI policies would actually increase server-side processing during form load, as UI policies execute on the server when the form is loaded, whereas client scripts run client-side after the form loads; this change would worsen, not improve, load times.

Practice this question →
3
MCQmedium

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?

A.sys_app
B.sys_app_application
C.sys_ui_module
D.sys_app_module
AnswerD

sys_app_module stores both application menu and module definitions for the navigator, making it the correct answer.

Why this answer

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.

Exam trap

Candidates often confuse `sys_app_application` (which is not the correct table for navigator definitions) with `sys_app_module` (which stores both application menus and modules).

How to eliminate wrong answers

Option A is wrong because `sys_app` stores the application record itself (e.g., name, vendor, version), not the menu or module definitions. Option C is wrong because `sys_ui_module` is a legacy table for UI modules in the old UI16 navigator, not the current standard for application menu/module definitions. Option D is wrong because `sys_app_module` does not exist as a standard table in ServiceNow; the correct table for modules within an application is `sys_app_application`.

Practice this question →
4
Drag & Dropmedium

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

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.

Practice this question →
5
MCQhard

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?

A.Create a new view with only essential fields and assign it to users via a UI policy based on role.
B.Enable Form Layout Personalization so users can hide fields they don't need.
C.Remove fields from the default view to reduce the number of fields loaded.
D.Use Form Sections to collapse fields into tabs.
AnswerA

A lean view reduces the number of fields loaded, improving performance. UI policy can assign the view to appropriate roles.

Why this answer

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.

Exam trap

The trap here is that candidates confuse visual hiding (via personalization or sections) with actual removal of fields from the server-side load, but only reducing the fields in the view definition eliminates the performance overhead.

How to eliminate wrong answers

Option B is wrong because enabling Form Layout Personalization allows users to hide fields client-side, but the fields are still loaded in the DOM and their reference data is still fetched, so it does not improve form load performance. Option C is wrong because removing fields from the default view affects all users and can break workflows or hide required fields, reducing usability without a targeted approach. Option D is wrong because using Form Sections to collapse fields into tabs only hides them visually; all fields and their reference lookups are still loaded when the form opens, so performance remains unchanged.

Practice this question →
6
Multi-Selecteasy

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

Select 2 answers
A.Table name (optional)
B.Link type
C.Role (optional)
D.Condition filter
E.Module name (optional)
AnswersB, D

Link type defines what the module opens (list, form, etc.).

Why this answer

The 'Link type' is a required configuration when adding a module to the application navigator. It determines how the module behaves when clicked, such as opening a new window, displaying in the same window, or using a specific UI action. Without setting the link type, the module cannot properly navigate the user to the intended target.

Exam trap

ServiceNow often tests the misconception that 'Table name' and 'Role' are optional fields, when in fact they are required for module configuration, while 'Condition filter' is an optional but valid advanced setting.

Practice this question →
7
MCQeasy

An administrator wants to add a new section to the incident form to group related fields. Which tool should they use?

A.Dictionary Override
B.Application Navigator
C.UI Policy
D.Form Designer
AnswerD

Form Designer allows adding sections, fields, and configuring the form layout.

Why this answer

The Form Designer is the correct tool because it allows administrators to add new sections to an incident form by dragging and dropping fields into a new section container. This is the dedicated interface for modifying form layouts, including creating sections to group related fields, without needing to write code or use other configuration tools.

Exam trap

The trap here is that candidates often confuse UI Policy (which controls field visibility) with form layout changes, but UI Policy cannot create new sections or rearrange field groupings—it only modifies existing field states.

How to eliminate wrong answers

Option A is wrong because Dictionary Override is used to modify field-level properties (e.g., label, default value, reference qualifier) for a specific table or view, not to add sections to a form. Option B is wrong because Application Navigator is used to configure the left-hand navigation menu (modules and applications) in the platform, not to edit form layouts. Option C is wrong because UI Policy is used to dynamically show/hide fields or make them mandatory based on conditions, not to add structural sections to a form.

Practice this question →
8
MCQeasy

Refer to the exhibit. This JSON represents a table schema. What is the data type of the 'short_description' field?

A.Integer
B.String
C.Reference
D.Date
AnswerB

The type attribute is set to 'string'.

Why this answer

The 'short_description' field in a ServiceNow table schema is defined as a string data type because it stores alphanumeric text values, such as brief summaries or titles. In ServiceNow, string fields are used for textual data that does not require numeric operations, and they are typically mapped to the 'varchar' database column type.

Exam trap

The trap here is that candidates may confuse 'short_description' with a reference field because it often appears in forms with a magnifying glass icon for lookup, but it is actually a plain string field without a foreign key relationship.

How to eliminate wrong answers

Option A is wrong because 'Integer' is used for numeric values that support arithmetic operations, not for descriptive text like 'short_description'. Option C is wrong because 'Reference' is a data type that links to a record in another table via a sys_id, not for storing free-text descriptions. Option D is wrong because 'Date' is used for calendar dates without time components, whereas 'short_description' holds arbitrary text strings.

Practice this question →
9
MCQeasy

A form has a reference field that should display the ticket number. Which dictionary attribute controls the displayed value?

A.Reference qualifier
B.Choice field
C.Default value
D.Display value
AnswerD

The Display value attribute specifies the column to show when referencing a record.

Why this answer

The 'Display value' attribute on a reference field determines which field from the referenced table is shown to the user in the form. By default, this is often set to the 'Number' field (e.g., INC0010001), but it can be changed to any other field on the target table, such as 'Short description' or 'Name'. This attribute controls the displayed value without affecting the underlying sys_id reference.

Exam trap

The trap here is that candidates confuse 'Display value' with 'Reference qualifier', thinking that filtering the list also controls what is shown, but they are separate attributes with distinct purposes.

How to eliminate wrong answers

Option A is wrong because 'Reference qualifier' is used to filter which records from the referenced table are available for selection, not to control the displayed value. Option B is wrong because 'Choice field' is a separate field type that presents a predefined list of options, not a property of a reference field. Option C is wrong because 'Default value' sets the initial value of the field when the form loads, not the display format of the referenced record.

Practice this question →
10
MCQeasy

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?

A.List
B.Form
C.URL
D.Report
AnswerA

A list module shows a list of records from a table.

Why this answer

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.

Exam trap

The trap here is that candidates may confuse a List module with a Report module, thinking a Report can display a list of users, but Reports are for aggregated or charted data, not a native record list view.

How to eliminate wrong answers

Option B is wrong because a Form module type is used to display a single record form for creating or editing a record, not a list of multiple users. Option C is wrong because a URL module type is used to link to an external or internal URL, such as a webpage or a report, not to display a native list of records from a table. Option D is wrong because a Report module type is used to display a report (e.g., chart, pivot table) based on a data source, not a standard list view of records.

Practice this question →
11
MCQhard

A ServiceNow administrator at a large enterprise is troubleshooting an issue with the incident form. A custom form section titled 'Sensitive Data' should only be visible to users with the 'security_admin' role. The administrator created a UI Policy with the condition g_user.hasRole('security_admin') and an action that sets the 'Sensitive Data' section's visible attribute to true. The UI Policy is active and set to run on load. However, users with the 'security_admin' role report that they do not see the section. The administrator verified that the section is configured with a 'Visible' condition that is blank, and the section's 'Roles' field is empty. What is the most likely reason the section is not showing?

A.The UI Policy condition should use 'g_user.hasRoleExactly' instead of 'g_user.hasRole'.
B.The section has a 'Visible' condition script that returns false, overriding the UI Policy.
C.A table-level ACL is blocking visibility of the section for all users.
D.The section's 'Roles' field is empty and must be set to 'security_admin'.
AnswerB

A section's own 'Visible' condition, if it returns false, will hide the section regardless of UI Policy.

Why this answer

The UI Policy is correctly configured to set the section's visible attribute to true when the condition is met. However, the section itself has a 'Visible' condition script that returns false, which overrides the UI Policy because the section's visibility condition is evaluated after the UI Policy runs. The UI Policy sets the visible attribute on the form, but the section's own condition script can independently control visibility, and if it returns false, the section remains hidden regardless of the UI Policy.

Exam trap

The trap here is that candidates often assume UI Policies always control form element visibility, but they forget that a section's own 'Visible' condition script can override UI Policy actions, leading them to incorrectly blame the UI Policy condition syntax or the Roles field.

How to eliminate wrong answers

Option A is wrong because 'g_user.hasRole' is the correct method to check for role membership; 'g_user.hasRoleExactly' is not a valid method in ServiceNow and would cause a script error. Option C is wrong because table-level ACLs control record-level access (read, write, etc.), not form section visibility; they do not affect whether a section is shown or hidden on a form. Option D is wrong because the 'Roles' field on a section controls visibility based on role membership, but it is empty, meaning no role restriction is applied; setting it to 'security_admin' would actually be an alternative way to restrict visibility, but the issue is that the section is not showing despite the UI Policy, so the empty Roles field is not the cause.

Practice this question →
12
MCQeasy

A user needs to access the 'Update Sets' module directly from the application navigator. Which filter path should they use?

A.update_set.list
B.sys_update_set.list
C.sys_update.set.list
D.update_sets
AnswerB

Correct table path for Update Sets.

Why this answer

The 'Update Sets' module in ServiceNow is stored in the 'sys_update_set' table. To access it directly from the application navigator, you must use the table name followed by '.list', which renders the list view of that table. Therefore, 'sys_update_set.list' is the correct filter path.

Exam trap

The trap in ServiceNow is that candidates often confuse the table name with the module label (e.g., 'Update Sets') and forget that the filter path must use the exact system table name, which is 'sys_update_set', not a human-readable variant.

How to eliminate wrong answers

Option A is wrong because 'update_set.list' uses an incorrect table name; the actual table is 'sys_update_set', not 'update_set'. Option C is wrong because 'sys_update.set.list' incorrectly places a dot between 'update' and 'set', which does not match the table name 'sys_update_set'. Option D is wrong because 'update_sets' is not a valid filter path; it lacks the '.list' suffix and does not reference the correct table name.

Practice this question →
13
MCQmedium

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?

A.Delete the user's personalization from sys_user_preference
B.Set the form's 'Reset' attribute to true
C.Run a scheduled job to clear all user preferences
D.Use the 'Restore Default' button on the form
AnswerA

This directly removes the personalization, reverting to the default layout.

Why this answer

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.

Exam trap

The trap here is that candidates confuse the 'Restore Default' button (which only resets the current session's view for the logged-in user) with the ability to permanently clear another user's personalization, leading them to choose option D.

How to eliminate wrong answers

Option B is wrong because there is no 'Reset' attribute on a form; the form's 'Reset' attribute is not a valid mechanism in ServiceNow for clearing user personalizations. Option C is wrong because running a scheduled job to clear all user preferences would remove all preferences for all users, which is overly broad and not targeted to resetting a single user's form layout. Option D is wrong because the 'Restore Default' button on the form resets the current session's view for the administrator, not the user's personalization; it does not clear the user's saved preference.

Practice this question →
14
Multi-Selecteasy

Which two statements about UI Policies are true? (Choose two.)

Select 2 answers
A.They are always executed on form load.
B.They can be used to cancel a form submission.
C.They can be used to set field values.
D.They run on the client side.
E.They run on the server side.
AnswersC, D

UI Policies can set the value of fields using the 'Set value' action.

Why this answer

UI Policies can set field values on the client side using the 'Set field values' section within the UI Policy configuration. This allows administrators to automatically populate or modify field values based on conditions, such as setting a category field when a certain priority is selected, without requiring a server round trip.

Exam trap

The trap here is that candidates often confuse UI Policies with Client Scripts or Business Rules, mistakenly thinking UI Policies can cancel submissions (which is a Client Script function) or run server-side (which is a Business Rule function), leading them to select options B or E.

Practice this question →
15
MCQmedium

A system administrator wants to add a choice list to a field that shows options depending on the value of another field. Which feature should be used?

A.Reference field with cascading
B.Dependent choices
C.Client Script with GlideAjax
D.UI Policy with onChange
AnswerB

Dependent choices allow a choice field to change its options based on another field's value, configured declaratively.

Why this answer

Dependent choices is a built-in feature that dynamically filters a choice list based on the value of a parent field. Option A (Reference field with cascading) is not a standard ServiceNow feature for choice lists. Option C (Client Script with GlideAjax) could be used but is not the built-in best practice for simple dependencies.

Option D (UI Policy with onChange) can show or hide fields but cannot dynamically populate choice lists.

Practice this question →
16
Drag & Dropmedium

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

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.

Practice this question →
17
MCQhard

A UI Policy is intended to make a field mandatory when another field equals 'Yes', but the mandatory condition is not working. What is a common cause?

A.UI Policy order is too high
B.Field type is not string
C.UI Policy is set to 'Run script' only
D.Condition script has syntax error
AnswerD

A syntax error will break the condition evaluation, preventing the UI Policy from applying its actions.

Why this answer

A syntax error in the condition script will cause the UI Policy to fail silently. When the script encounters an error (e.g., a missing semicolon, undefined variable, or incorrect operator), the entire condition evaluates to false, so the mandatory field action never triggers. UI Policies execute client-side in the browser, and syntax errors prevent the script from running at all, making the mandatory condition appear non-functional.

Exam trap

The trap here is that candidates often assume a UI Policy with a syntax error will show an error message or that the 'Run script' option (Option C) is the culprit, but in reality, the condition script executes first and a syntax error prevents the entire policy from applying, including mandatory actions.

How to eliminate wrong answers

Option A is wrong because UI Policy order determines the sequence of execution when multiple policies apply to the same field, but a high order does not prevent a policy from running; it only affects priority. Option B is wrong because field type does not affect whether a UI Policy can make it mandatory; UI Policies can set mandatory on any field type (string, choice, reference, etc.) as long as the condition is met. Option C is wrong because 'Run script' only means the policy runs its script but does not apply the 'Mandatory' or 'Visible' actions; however, the condition itself still executes, so a syntax error in the condition script would still break it, and the 'Run script' setting does not cause the mandatory condition to fail.

Practice this question →
18
MCQmedium

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?

A.The system property 'myapp.high_priority' is set to 'false'.
B.The condition script uses 'g_form.getValue' which is not available in a UI Policy condition.
C.The UI Policy is set to run on load only, and the priority field change does not trigger re-evaluation.
D.The user must refresh the page after changing priority for the UI Policy to take effect.
AnswerC

Correct: Without the priority field in the UI Policy's 'Fields' list, changing priority does not re-trigger the condition.

Why this answer

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.

Exam trap

The trap here is that candidates often assume UI Policies automatically re-evaluate on any field change, but ServiceNow tests the distinction between 'Run on load' and 'Run on change' settings, which is a key nuance in UI Policy behavior.

How to eliminate wrong answers

Option A is wrong because the question states the system property 'myapp.high_priority' is set to 'true', so it is not false. Option B is wrong because 'g_form.getValue' is actually available in UI Policy condition scripts; it is a client-side API that works in UI Policies. Option D is wrong because refreshing the page would reload the form and trigger the UI Policy on load, but the issue is that the policy does not re-evaluate on priority change, not that the user needs to manually refresh.

Practice this question →
19
Multi-Selectmedium

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

Select 2 answers
A.Change the order of modules within a menu.
B.Create a UI Policy that shows or hides the module.
C.Define a filter condition for the module's menu.
D.Define a link to a specific URL or report.
E.Set the default view for a form.
AnswersA, D

Order can be set via the 'Order' field.

Why this answer

The 'Application Navigator' module (sys_app_module) allows administrators to reorder modules within a menu by adjusting the 'Order' field. This directly controls the sequence in which modules appear in the application navigator, enabling customization of the user interface hierarchy.

Exam trap

The trap here is that candidates confuse the Application Navigator module (sys_app_module) with other navigational or form configuration tools, such as UI Policies or table-level settings, leading them to select options that are technically valid for other areas but not for sys_app_module.

Practice this question →
20
MCQeasy

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

A.User roles
B.User's browser cache
C.Module active flag
D.ACLs on the table
AnswerA

If the user lacks the role that grants access to the module, they will not see any records.

Why this answer

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.

Exam trap

The trap here is that candidates often jump to ACLs as the first check, forgetting that roles are the gatekeeper for module access and record visibility in ServiceNow.

How to eliminate wrong answers

Option B is wrong because browser cache issues typically affect UI rendering or form behavior, not the complete absence of records in a module; clearing cache might resolve display glitches but not permission-based invisibility. Option C is wrong because the module active flag controls whether the module appears in the application navigator, not whether records within that module are visible; a deactivated module simply hides the menu entry. Option D is wrong because ACLs (Access Control Lists) on the table control record-level read permissions, but they are evaluated after role-based access; if the user lacks the required role, ACLs are never checked, making role verification the logical first step.

Practice this question →
21
Multi-Selecteasy

A ServiceNow administrator needs to create a form section that is only visible to users with the 'itil' role. Which TWO configuration options can achieve this? (Choose two.)

Select 2 answers
A.Configure a client script to hide the section on load based on the user's role.
B.Set the 'Role' field on the form section to 'itil'.
C.Use a role-based ACL on the table to restrict access to the fields in that section.
D.Apply a UI Policy that sets the section's visible attribute to false for non-itil users.
E.Set the 'Visible' condition on the form section using `g_user.hasRole('itil')`.
AnswersD, E

Correct: A UI Policy can dynamically set a section's visible attribute based on conditions.

Why this answer

A UI Policy can conditionally set the 'visible' attribute of a form section to false based on a condition like `g_user.hasRole('itil')`, effectively hiding the section from non-itil users. Option E is correct because the 'Visible' condition on a form section directly accepts a script expression, and `g_user.hasRole('itil')` evaluates to true for itil users, making the section visible only to them. Both approaches leverage client-side role checking to control section visibility without requiring server-side ACLs or client scripts.

Exam trap

The trap here is that candidates often confuse the 'Role' field on a form section (which does not exist) with the role field on a field or table ACL, or they mistakenly think a client script is a proper configuration for role-based section visibility when UI Policies or the Visible condition are the intended methods.

Practice this question →
22
Multi-Selectmedium

Which three of the following are valid methods to control field visibility on a form based on user input? (Choose three.)

Select 3 answers
A.Data Policies with conditions.
B.Dynamic Form Configuration.
C.Client scripts that set field attributes.
D.Role-based ACLs on the field.
E.UI Policies with visibility actions.
AnswersB, C, E

Dynamic Form Configuration allows conditionally showing or hiding fields in form views.

Why this answer

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.

Exam trap

The trap here is confusing Data Policies (server-side data enforcement) with UI Policies (client-side visibility control), leading candidates to incorrectly select Data Policies as a method for form field visibility.

Practice this question →
23
MCQhard

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?

A.The condition uses the wrong operator
B.The UI Policy is set to run on submit only
C.The UI Policy is inactive
D.The warning message is not enabled on the UI Policy
AnswerC

An inactive UI Policy will not execute, so no message appears regardless of settings.

Why this answer

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.

Exam trap

The trap here is that candidates often overlook the 'Active' checkbox on the UI Policy form, assuming that if the policy is configured to run on load and submit, it will automatically execute, but ServiceNow requires the policy to be explicitly set to active.

How to eliminate wrong answers

Option A is wrong because an incorrect operator in the condition would cause the condition to evaluate to false, but the warning message would still appear if the condition were true; the issue here is that the message does not appear at all, indicating the policy is not running. Option B is wrong because the question states the UI Policy is set to run on both load and submit, so it cannot be set to run on submit only; this would contradict the given configuration. Option D is wrong because UI Policies do not have a separate 'enable warning message' toggle; the warning message is defined as an action within the UI Policy, and if the policy is active and conditions are met, the message will display.

Practice this question →
24
MCQeasy

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

A.Client Script
B.UI Policy
C.Data Policy
D.Business Rule
AnswerB

UI Policies are designed for client-side form behavior, including conditional mandatory fields.

Why this answer

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.

Exam trap

The trap here is that candidates confuse Data Policy (server-side) with UI Policy (client-side), assuming any mandatory rule must be enforced on the server, when in fact the requirement for immediate client feedback dictates a client-side solution.

How to eliminate wrong answers

Option A is wrong because a Client Script runs JavaScript on the client but cannot directly set a field's mandatory attribute; it would require additional code to manipulate the g_form object, which is less efficient and not the intended use for simple mandatory conditions. Option C is wrong because Data Policy enforces mandatory fields on the server side during database operations, which does not provide immediate client-side feedback and requires a server round-trip to evaluate. Option D is wrong because a Business Rule runs server-side after a record is saved, so it cannot make a field mandatory before submission, and it would not provide the real-time client-side behavior needed for a checkbox-driven mandatory field.

Practice this question →
25
MCQmedium

A company wants to display a custom field on the incident form only when the incident state is 'In Progress'. Which configuration should be used?

A.Modify the Dictionary Override to set a default visibility condition
B.Configure an Access Control Rule (ACL) on the field
C.Create a UI Policy with a condition on state and set field visibility
D.Write a Business Rule that updates the field visibility attribute
AnswerC

UI Policies allow conditional client-side actions like hiding/showing fields.

Why this answer

UI Policies allow you to define a condition (e.g., incident.state == 'In Progress') and then set field-level actions such as making a field visible or mandatory. This is the intended declarative mechanism for controlling field visibility based on form state without writing code.

Exam trap

The trap here is confusing server-side controls (ACLs, Business Rules) with client-side form behavior, leading candidates to select an option that controls data access or server logic instead of UI visibility.

How to eliminate wrong answers

Option A is wrong because Dictionary Overrides are used to modify field-level properties like label or type for a specific table, not to set dynamic visibility conditions based on record state. Option B is wrong because Access Control Rules (ACLs) control data access (read/write permissions), not UI visibility on a form. Option D is wrong because Business Rules run server-side and cannot directly update a field's visibility attribute on the client-side form; visibility is a client-side concern.

Practice this question →
26
MCQeasy

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?

A.Inspect client scripts on the Incident table for hiding logic.
B.Verify the access controls (ACLs) for the new fields.
C.Check the form layout for the Incident table form view.
D.Review the data policy configuration for the table.
AnswerC

Fields must be added to the form layout to appear on the form. This is the most direct and common cause.

Why this answer

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.

Exam trap

The trap here is that candidates often jump to ACLs or client scripts as the cause of missing fields, but the most fundamental check is the form layout, which directly controls field visibility on the form.

How to eliminate wrong answers

Option A is wrong because client scripts can hide or show fields dynamically, but the first step should be to verify the form layout, as client scripts are typically used for conditional logic and not for initial field visibility. Option B is wrong because access controls (ACLs) control read/write permissions, not field visibility on the form; users would see the fields but may be unable to interact with them if ACLs restrict access. Option D is wrong because data policies enforce data consistency and validation rules, not field visibility; they would not prevent fields from appearing on the form.

Practice this question →
27
MCQmedium

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?

A.Create a new form section
B.Configure a UI policy
C.Set an ACL to allow field addition
D.Enable personalization on the form
AnswerD

Personalization allows users to customize their own form view by adding or removing fields.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse ACLs (which control data access) with form layout customization, or assume UI policies can add fields, when in fact UI policies only modify existing field properties like visibility or mandatory status.

How to eliminate wrong answers

Option A is wrong because creating a new form section modifies the form layout for all users globally, not just for individual end users. Option B is wrong because a UI policy controls field visibility, mandatory status, or read-only behavior based on conditions, but it does not allow users to add new fields to the form. Option C is wrong because ACLs control access to records and fields (read/write permissions), but they do not provide a mechanism for users to add fields to the form layout.

Practice this question →
28
MCQeasy

Refer to the exhibit. A UI Policy is configured with the above condition to make the 'resolution_notes' field mandatory when the variable 'state' is 2. When state is set to 2, the field is still not mandatory. What is the most likely issue?

A.The field is not in the form layout
B.The condition uses 'state' instead of 'variables.state'
C.The UI Policy is inactive
D.The UI Policy is set to run on submit only
AnswerB

In a catalog UI Policy, variables are accessed using the 'variables' prefix; 'state' is not a valid variable reference.

Why this answer

In ServiceNow UI Policies, when referencing a variable on a catalog item or record producer, you must prefix the variable name with 'variables.' (e.g., 'variables.state') because the condition is evaluated against the variable map, not the field directly. Using 'state' alone refers to the field on the current table (e.g., the task table), which is not the same as the catalog variable 'state'. Therefore, the condition never matches when the variable is set to 2, so the UI Policy does not fire.

Exam trap

ServiceNow often tests the distinction between table fields and catalog variables, and the trap here is that candidates assume 'state' refers to the variable because it is displayed on the form, but without the 'variables.' prefix, the condition references the underlying table field instead.

How to eliminate wrong answers

Option A is wrong because if the field were not in the form layout, it would not appear at all, but the question states the field is present yet not mandatory. Option C is wrong because an inactive UI Policy would never run, but the question implies the policy is configured and expected to work; the issue is a condition mismatch, not inactivity. Option D is wrong because a UI Policy set to 'run on submit only' would still enforce mandatory on submit, but the field is not mandatory at any point when state is 2, indicating the condition never evaluates to true.

Practice this question →
29
Multi-Selectmedium

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

Select 2 answers
A.Use a consistent order of fields across similar tables
B.Group related fields into sections with clear headings
C.Hide mandatory fields using UI policies to reduce clutter
D.Use many-to-many fields instead of reference fields for better relationships
E.Include as many fields as possible on one form to minimize navigation
AnswersA, B

Consistency reduces cognitive load.

Why this answer

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.

Practice this question →
30
MCQhard

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?

A.The condition uses '&&' instead of '||'
B.There is a syntax error in the script
C.The isValid() method is not available in UI Policy context
D.The caller_id field is empty
AnswerC

UI Policy scripts run client-side and cannot use server-side methods like isValid().

Why this answer

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.

Exam trap

ServiceNow exams often test the distinction between client-side and server-side scripting contexts in ServiceNow, and the trap here is that candidates assume `isValid()` is a generic JavaScript method available everywhere, when in fact it is a GlideRecord method restricted to server-side execution.

How to eliminate wrong answers

Option A is wrong because using '&&' (AND) is correct for requiring both conditions (state is 1 AND caller_id is valid) to be true; using '||' (OR) would incorrectly apply the mandatory attribute if either condition is true, which is not the intended logic. Option B is wrong because there is no syntax error in the script; the issue is a runtime error due to an undefined method, not a syntax issue. Option D is wrong because the caller_id field being empty is the scenario described in the question, not the cause of the failure; the cause is that the script cannot evaluate the condition correctly when caller_id is empty due to the missing method.

Practice this question →
31
Multi-Selecthard

Which TWO of the following are true about the Application Navigator in the UI16 interface?

Select 2 answers
A.Module visibility is controlled by roles via the 'Requires role' field
B.Modules are grouped under 'modules' in the navigator
C.Personalizing a module removes it from the navigator for all users
D.The navigator can be customized by any user to reorganize modules
E.Users can add a module to their 'Favorites' by right-clicking the module
AnswersA, E

Modules can be restricted to specific roles.

Why this answer

In the UI16 interface, module visibility is controlled by roles through the 'Requires role' field on the module record. When a user does not have the specified role, the module is hidden from their Application Navigator. This is a core access control mechanism in ServiceNow.

Exam trap

The trap here is confusing personalization (which only affects the current user) with global configuration (which affects all users), leading candidates to incorrectly select option C or D.

Practice this question →
32
MCQmedium

The section 'Assignment Information' currently displays two fields in one row. An administrator wants to add a new field 'due_date' to this section, placing it in a new row below the existing fields. What should the administrator do?

A.Set the order of 'due_date' to 3 in the Dictionary Override
B.Change the number of columns in the section to 1
C.Create a new section named 'Due Date' and place the field there
D.Use Form Designer to drag the 'due_date' field into the section and drop it below the current fields
AnswerD

Form Designer allows precise placement of fields in rows and columns.

Why this answer

The Form Designer allows administrators to visually rearrange fields within a section, including moving a field to a new row below existing fields. By dragging the 'due_date' field into the 'Assignment Information' section and dropping it below the current fields, the field will automatically be placed in a new row, as the section's column layout (default 2 columns) will wrap fields into rows based on their order. This is the standard method for adding fields to existing sections without altering the section's column configuration.

Exam trap

The trap here is that candidates often confuse the 'order' property in the Dictionary Override (which controls field sequence across the entire form) with the visual row placement within a section, leading them to incorrectly believe that setting order to 3 will automatically place the field in a new row, when in fact the section's column count and the Form Designer's drag-and-drop are the correct mechanisms for controlling row placement.

How to eliminate wrong answers

Option A is wrong because setting the order of 'due_date' to 3 in the Dictionary Override only controls the field's position within the form's field order, but does not guarantee it will appear in a new row below existing fields; the section's column layout determines row wrapping, and simply changing the order may cause the field to appear in the same row as other fields if the column count allows. Option B is wrong because changing the number of columns in the section to 1 would force all fields into a single column, which would place 'due_date' in a new row but would also restructure the entire section, potentially breaking the existing two-field-per-row layout and causing unintended layout changes for other fields. Option C is wrong because creating a new section named 'Due Date' would separate the field from the 'Assignment Information' section, which is not what the administrator wants; the requirement is to add the field to the existing section, not to create a separate section.

Practice this question →
33
MCQhard

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?

A.Create a UI policy that changes the form when state is 'In Progress'
B.Write an ACL on the UI action table
C.Set the condition on the UI action to 'current.state == 2'
D.Assign the UI action to a role that only users in this state have
AnswerC

Condition script on UI action shows/hides it based on state.

Why this answer

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.

Exam trap

The trap here is confusing UI actions with UI policies or ACLs, leading candidates to select options that control field behavior or security instead of the direct condition field on the UI action itself.

How to eliminate wrong answers

Option A is wrong because UI policies control field visibility, mandatory status, and read-only behavior on forms; they do not control the appearance of UI actions in the context menu. Option B is wrong because ACLs (Access Control Lists) control data access and security permissions, not the conditional display of UI actions on a form context menu. Option D is wrong because roles control which users can see or use a UI action, not the state of the current record; a user with the role would see the action regardless of the record's state.

Practice this question →
34
MCQeasy

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

A.Dictionary
B.Table
C.UI Page
D.Form Layout
AnswerD

Form Layout allows adding, removing, and ordering sections on a form.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse the Dictionary (which defines field metadata in ServiceNow) with the Form Layout (which controls visual arrangement), leading them to incorrectly select Dictionary when the question is about adding a section to a ServiceNow form.

How to eliminate wrong answers

Option A is wrong because the Dictionary defines the properties of individual fields (e.g., type, length, reference) but does not control the layout or sections on a form. Option B is wrong because a Table is a database object that stores records; editing the table schema does not affect the visual form layout or add sections. Option C is wrong because UI Pages are used to create custom standalone pages or widgets, not to modify the standard form layout or add sections to an existing form.

Practice this question →
35
MCQeasy

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?

A.Use only one UI Policy per form
B.Set the UI Policy and Client Script to run only when needed using conditions
C.Disable all client-side scripts
D.Convert all UI Policies to Business Rules
AnswerB

Conditional execution reduces unnecessary client scripts, speeding up form loading.

Why this answer

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.

Exam trap

The trap here is that candidates assume 'fewer scripts' always means better performance, but ServiceNow tests the understanding that conditional execution (not just reducing count) is the correct optimization strategy.

How to eliminate wrong answers

Option A is wrong because there is no platform limit of one UI Policy per form; you can have multiple UI Policies, and the issue is not the count but the conditions under which they execute. Option C is wrong because disabling all client-side scripts would break essential form functionality like validation, dynamic visibility, and field behavior; the goal is to optimize, not eliminate, client-side logic. Option D is wrong because converting UI Policies to Business Rules moves logic server-side, which does not improve form load performance (client-side rendering) and can introduce latency for real-time user interactions; Business Rules are for server-side operations, not for optimizing client-side form performance.

Practice this question →
36
Multi-Selectmedium

Which TWO conditions must be met for a UI Policy to run on a form?

Select 2 answers
A.The form must be in edit mode
B.The user must have the admin role
C.The condition script must return true
D.The UI Policy must be active
E.The UI Policy must be set to 'Run on load'
AnswersC, D

If the condition returns false, the UI Policy does not execute its actions.

Why this answer

A UI Policy's condition script must evaluate to true for the policy to execute its actions on the form. The condition script is a server-side script that returns a boolean value; if it returns true, the UI Policy's actions (such as setting fields mandatory, visible, or read-only) are applied. Without a true condition, the UI Policy will not run, regardless of other settings.

Exam trap

The trap here is that candidates often confuse the 'Run on load' property as a mandatory condition for execution, when in fact it is just one of several trigger options, and the core requirement is that the condition script must return true and the UI Policy must be active.

Practice this question →
37
MCQeasy

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?

A.Configure the field as 'Mandatory' and set 'Always visible' in the section
B.Add a UI policy to show the field on load
C.Use 'glide.mandatory.visible' system property
D.Set the field to read-only
AnswerA

This ensures visibility even when section collapses.

Why this answer

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.

Exam trap

The trap here is that candidates confuse the 'Always visible' section property with UI policies or system properties that control field highlighting or read-only behavior, rather than recognizing it as a distinct form layout option for collapsed sections.

How to eliminate wrong answers

Option B is wrong because a UI policy can show or hide fields based on conditions, but it does not inherently keep a field visible when its parent section collapses; the 'Always visible' setting is a section-level property, not a UI policy action. Option C is wrong because the 'glide.mandatory.visible' system property controls whether mandatory fields are highlighted with a red asterisk, not whether they remain visible in collapsed sections. Option D is wrong because setting a field to read-only prevents editing but does not affect its visibility when the section collapses; the field could still be hidden.

Practice this question →
38
MCQeasy

A user wants to quickly filter the incident list to show only high-priority incidents. What is the fastest way to apply this filter?

A.Use the filter condition builder above the list
B.Modify the query business rule for the incident table
C.Create a new report with a filter condition
D.Personalize the list view to add a filter condition
AnswerA

The filter condition builder provides immediate filtering.

Why this answer

The filter condition builder above the list provides a quick, ad-hoc way to apply a filter directly to the current list view without any configuration changes. In ServiceNow, this builder allows users to add conditions like 'Priority is High' in seconds, making it the fastest method for a one-time filter.

Exam trap

The trap here is that candidates may confuse the quick ad-hoc filter with more permanent configuration options like personalizing the list view or modifying business rules, thinking they need to 'set up' a filter rather than just applying it on the fly.

How to eliminate wrong answers

Option B is wrong because modifying a query business rule would permanently alter the underlying query for all users and all views of the incident table, which is not a quick filter and would affect system-wide behavior. Option C is wrong because creating a new report is a separate module designed for data visualization and analysis, not for filtering the list view in place; it requires extra steps and does not apply the filter to the list. Option D is wrong because personalizing the list view to add a filter condition involves configuring a saved filter for that specific view, which is a more permanent setup and not the fastest way to apply a temporary filter.

Practice this question →
39
Multi-Selecthard

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

Select 3 answers
A.Form section order
B.Role-based field visibility
C.User preference for field order
D.Field order in form layout
E.Field order in dictionary
AnswersA, C, D

Sections are ordered, and fields are placed within sections.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse the dictionary field order with the form layout field order, assuming that changing the dictionary order will automatically reorder fields on the form, when in fact the form layout order is independent and must be modified separately.

Practice this question →
40
MCQeasy

Which of the following is NOT a valid type of UI action?

A.tab
B.context_menu
C.button
D.link
AnswerA

Tab is not a UI action type; it's a form element.

Why this answer

In ServiceNow, UI actions are defined as scripts that execute when a user interacts with a UI element such as a button, link, or context menu item. The 'tab' type is not a valid UI action type; UI actions can be of type 'button', 'context_menu', or 'link', but not 'tab'. Tabs are separate UI elements managed through form layouts or UI policies, not through the UI Actions table.

Exam trap

The trap here is that candidates may confuse UI actions with other UI elements like tabs or UI policies, assuming 'tab' is a valid UI action type because tabs are common in ServiceNow forms, but ServiceNow explicitly restricts UI action types to button, context_menu, and link.

How to eliminate wrong answers

Option B is wrong because 'context_menu' is a valid UI action type that adds an option to the context menu (right-click menu) on a form or list. Option C is wrong because 'button' is a valid UI action type that creates a button on a form or list. Option D is wrong because 'link' is a valid UI action type that creates a clickable link on a form or list.

The only invalid type among the options is 'tab', which is not a UI action type in ServiceNow.

Practice this question →
41
MCQhard

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?

A.A Data Policy overrides the mandatory attribute
B.The UI Policy is set to OnSubmit
C.The UI Policy runs after the Client Script
D.The UI Policy runs before the Client Script
AnswerD

UI Policies execute earlier in the form load sequence; if the condition depends on a client script value, it may be missed.

Why this answer

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.

Exam trap

The trap here is that candidates often assume UI Policies and Client Scripts run in the order they appear in the application navigator, but ServiceNow explicitly evaluates UI Policy conditions before Client Scripts, regardless of the order they are created.

How to eliminate wrong answers

Option A is wrong because a Data Policy cannot override the mandatory attribute set by a UI Policy; Data Policies enforce data integrity on the server side and do not interact with UI Policy mandatory attributes in this way. Option B is wrong because a UI Policy set to OnSubmit would only apply its actions at form submission, but the issue occurs during form load and submission without the field being required, indicating the condition never set the mandatory attribute. Option C is wrong because if the UI Policy ran after the Client Script, the condition would see the variable set by the Client Script and correctly apply the mandatory attribute, which contradicts the described behavior.

Practice this question →
42
MCQmedium

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?

A.Create an Access Control Rule (ACL) on the form section.
B.Create a Business Rule that sets the section visibility.
C.Create a UI Action with a condition on the 'State' field.
D.Create a UI Policy with a condition on the 'State' field.
AnswerD

UI Policies control form visibility and field states.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse UI Policies with Business Rules or ACLs, mistakenly thinking server-side logic or access controls can manage client-side form visibility, when in fact UI Policies are the dedicated feature for conditional UI rendering based on field values.

How to eliminate wrong answers

Option A is wrong because Access Control Rules (ACLs) control data access and record-level permissions, not UI element visibility; they cannot show or hide form sections based on field values. Option B is wrong because Business Rules run server-side and cannot directly control client-side form section visibility; they would require additional client-side scripting or a UI Policy to achieve the same effect. Option C is wrong because UI Actions are buttons or links that execute actions (e.g., scripts, redirects) and are not designed to conditionally show or hide form sections based on field state.

Practice this question →
43
MCQhard

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?

A.The UI policy is configured to run on the server side
B.The role does not have read access to the field being set
C.The UI policy is set to 'Run script' but the script has a syntax error
D.The UI policy condition uses a field that the role cannot see due to field-level security
AnswerD

If the condition depends on a hidden field, the policy may not evaluate correctly.

Why this answer

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.

Exam trap

The trap here is that candidates confuse field-level security with ACLs or assume that g_form.setValue requires read access, when in fact the issue is that the condition field is invisible to the role, causing the UI policy to never trigger.

How to eliminate wrong answers

Option A is wrong because UI policies are inherently client-side scripts that run in the browser; there is no 'server side' execution mode for UI policies. Option B is wrong because g_form.setValue does not require read access to the field being set—it only requires write access, and the question states the script uses setValue, not getValue. Option C is wrong because a syntax error would cause the script to fail for all roles, not just a specific role, and the question specifies the failure is role-specific.

Practice this question →
44
MCQeasy

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?

A.The module is set to 'Personalize' mode
B.The module is configured as a report, not a list
C.The module's filter condition does not include the 'Assigned to' field for the current user
D.The user does not have the 'incident_read' role
AnswerC

Without proper condition, records may not appear.

Why this answer

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.

Practice this question →
45
MCQmedium

An administrator is asked to make the 'State' field read-only on the incident form after the record is saved. Which configuration should be used?

A.Create a UI Policy with condition 'always true' and set 'Read only' action, with 'On load' and 'After update' options
B.Write a Business Rule that sets the field read-only after update
C.Create an ACL that denies write access to the field
D.Use a Client Script that runs on load and makes the field read-only if the record has a sys_id
AnswerA

UI Policies can set read-only and apply after update, making the field read-only after save.

Why this answer

A UI Policy with the condition 'always true' and the 'Read only' action, with both 'On load' and 'After update' options selected, ensures the 'State' field becomes read-only immediately after the record is saved. The 'After update' option triggers the UI Policy to re-evaluate and apply the read-only state after the record is committed, while 'On load' ensures it is also read-only when the form is first opened. This is the only declarative client-side configuration that enforces the field state both on initial load and after every save.

Exam trap

The trap here is that candidates often confuse UI Policies (which can run after update) with Client Scripts (which cannot), leading them to choose option D, not realizing that a Client Script's 'onLoad' event does not reapply after a save.

How to eliminate wrong answers

Option B is wrong because a Business Rule runs server-side and cannot directly set a field as read-only on the client form; it can only modify field values or perform server-side logic, not control client-side UI behavior. Option C is wrong because an ACL that denies write access prevents the field from being updated via any channel (including REST, SOAP, or direct database writes), which is too broad and would block legitimate updates from other processes or integrations, not just the form. Option D is wrong because a Client Script that runs on load and checks for a sys_id only makes the field read-only when the form is first loaded, but it does not reapply the read-only state after the record is saved (since the 'After update' option is not available in Client Scripts), so the field would become editable again after a save.

Practice this question →
46
MCQmedium

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?

A.The menu's condition fails for those users
B.The module is inactive
C.The application menu is not active
D.The module's roles are empty
AnswerA

A condition on the menu can restrict visibility based on user attributes; if it fails, modules in that menu are hidden.

Why this answer

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.

Practice this question →
47
MCQmedium

A company needs to add a reference field on the Incident form that points to the Service Catalog item requested. However, the reference field must only allow selection of Catalog Items that are in the 'Software' category. Which configuration should be used?

A.Create a UI policy to show/hide the field
B.Set a default value on the reference field
C.Add a reference qualifier to the field with condition 'Category = Software'
D.Use an Access Control Rule to limit visibility
AnswerC

Reference qualifier filters the list to matching records.

Why this answer

A reference qualifier is the standard mechanism in ServiceNow to filter the records that appear in a reference field's lookup. By adding a condition such as 'Category = Software' to the reference qualifier on the field pointing to the Service Catalog item table (sc_cat_item), only catalog items in the 'Software' category will be selectable, meeting the requirement precisely.

Exam trap

The trap here is that candidates often confuse UI policies (which control field behavior) with reference qualifiers (which control lookup data), leading them to choose option A instead of the correct filtering mechanism.

How to eliminate wrong answers

Option A is wrong because UI policies control the visibility, mandatory status, or read-only state of fields based on conditions, but they cannot filter the selectable records in a reference field's lookup list. Option B is wrong because setting a default value only pre-populates the field with a specific record; it does not restrict the user from selecting other records that do not meet the category condition. Option D is wrong because Access Control Rules (ACLs) govern record-level security (who can read, write, etc.) and do not filter the options presented in a reference field's lookup; they would either block access entirely or allow it, not provide a filtered list.

Practice this question →
48
MCQmedium

An administrator wants to create a homepage that displays a filtered list of high-priority incidents assigned to the current user. Which widget should be used?

A.Dashboard widget with a list report
B.Content Selector widget
C.HTML widget with embedded Jelly script
D.Metric tag widget
AnswerA

List report widget can filter incidents and display them.

Why this answer

The Dashboard widget with a list report is correct because it allows an administrator to embed a filtered list report directly on a homepage. By configuring the report to filter for 'high-priority incidents' and setting the condition 'Assigned to is current user', the widget dynamically displays only the relevant records for the logged-in user, meeting the requirement without custom scripting.

Exam trap

The trap here is that candidates may confuse the Content Selector widget (which also displays lists) with the Dashboard widget, not realizing that the Content Selector is specifically for knowledge articles and CMS content, not for ad-hoc filtered table reports.

How to eliminate wrong answers

Option B is wrong because the Content Selector widget is used to display content from a knowledge base or CMS, not to show filtered list reports from tables like Incident. Option C is wrong because while an HTML widget with embedded Jelly script could technically achieve this, it is not the standard or recommended approach; ServiceNow provides the Dashboard widget with list reports as a no-code solution, and using Jelly would be unnecessarily complex and harder to maintain. Option D is wrong because the Metric tag widget is designed to display metric scores or indicators (e.g., SLAs) on a form or dashboard, not to show a filtered list of records from a table.

Practice this question →
49
Multi-Selecthard

Which THREE actions can be performed using UI policies? (Choose three.)

Select 3 answers
A.Set a field's default value
B.Make a field read-only
C.Make a field mandatory
D.Create a new field on the form
E.Hide a field
AnswersB, C, E

UI policies can set read-only.

Why this answer

UI policies can set the 'read-only' attribute on a field, preventing users from modifying its value based on conditions. This is a core function of UI policies, which control field behavior on a form without requiring server-side scripting.

Exam trap

The trap here is that candidates often confuse UI policies with Data Policies or client scripts, assuming UI policies can set default values or create fields, but UI policies only modify existing field attributes on the client side.

Practice this question →
50
MCQmedium

After applying a new theme, some modules are missing from the application navigator. What is the most likely cause?

A.Modules are inactive
B.Theme overrides the navigation
C.User roles changed
D.Cache needs refresh
AnswerA

Inactive modules are hidden from navigation. The theme change may have triggered a review, but inactivation is the direct cause.

Why this answer

When a new theme is applied in ServiceNow, the theme controls the visual styling but does not control which modules appear in the application navigator. Modules are missing because they are set to inactive, which hides them from the navigator regardless of the active theme. The most likely cause is that the modules themselves have been deactivated, often due to a system property or upgrade that changed their active state.

Exam trap

The trap here is that candidates confuse the visual impact of a theme (which changes colors and layout) with the functional visibility of modules, assuming a theme can hide or show modules, when in fact only module activation status or role-based ACLs control that.

How to eliminate wrong answers

Option B is wrong because themes in ServiceOnly affect the look and feel (colors, fonts, logos) and do not override the navigation structure or module visibility. Option C is wrong because user roles control access to modules via ACLs, but if a module is inactive, it is hidden from all users regardless of their roles. Option D is wrong because a cache refresh (e.g., clearing the browser cache or running a system cache flush) would not restore inactive modules; cache issues typically cause display glitches or outdated styling, not missing modules.

Practice this question →
51
MCQhard

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?

A.Add a group by condition on the list view
B.Set the list control to 'Auto' to reduce data threshold
C.Increase the 'glide.ui.list.threshold' system property to 10000
D.Create a new list view that includes only essential columns
AnswerD

Fewer columns reduces data load and improves performance.

Why this answer

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.

Exam trap

The trap here is that candidates often assume increasing the list threshold or using aggregation will solve performance issues, but they fail to recognize that calculated fields are the primary performance drain and that reducing columns is the simplest and most effective first step.

How to eliminate wrong answers

Option A is wrong because adding a group by condition does not reduce the number of records or columns; it only aggregates data, which can actually increase processing overhead on a list view with calculated fields. Option B is wrong because setting the list control to 'Auto' adjusts the pagination behavior but does not reduce the number of records loaded or the evaluation of calculated fields; it merely changes how the list is displayed. Option C is wrong because increasing 'glide.ui.list.threshold' to 10000 would allow more records to load at once, worsening performance by forcing the system to evaluate calculated fields for even more rows.

Practice this question →
52
MCQeasy

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

A.Access Control Rule
B.Form Layout configuration
C.UI Policy
D.Dictionary Entry
AnswerB

Form Layout lets you add sections and arrange fields.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse the Form Layout configuration with Dictionary Entries, thinking field properties control layout, or with UI Policies, assuming client-side rules can restructure forms, when in fact only the Form Layout directly manages sections and field placement.

How to eliminate wrong answers

Option A is wrong because Access Control Rules (ACLs) control user permissions to read, write, create, or delete records, not the layout or addition of sections to forms. Option C is wrong because UI Policies define client-side behavior (like making fields mandatory or visible) based on conditions, but they do not add sections or fields to a form's layout. Option D is wrong because Dictionary Entries define the properties of individual fields (such as type, length, and reference), but they do not manage the structural layout of sections on a form.

Practice this question →
53
MCQeasy

A form has a field with a default value that is automatically populated when a new record is created. The administrator wants to change this default value. Where should the administrator set the new default?

A.Business Rule
B.Dictionary entry for the field
C.UI Policy
D.Client Script
AnswerB

The dictionary entry has a 'Default value' field that populates automatically on new records.

Why this answer

The default value for a field is stored in the dictionary entry for that field. Changing the default value in the dictionary entry ensures that all new records created after the change will use the new default. This is the correct and intended method for setting field defaults in ServiceNow.

Exam trap

The trap here is that candidates often confuse the purpose of UI Policies or Client Scripts with setting default values, but the dictionary entry is the only place where a true field-level default is stored and applied at record creation.

How to eliminate wrong answers

Option A is wrong because Business Rules run on the server side after a record is saved or queried, and they are not designed to set default values for new records before the form loads. Option C is wrong because UI Policies control field visibility, mandatory status, and read-only state based on conditions, but they do not set default values for fields. Option D is wrong because Client Scripts run in the browser and can set field values on the client side, but they are not the standard or recommended way to set a default value that should be applied automatically when a new record is created; the dictionary entry is the authoritative source for defaults.

Practice this question →
54
MCQmedium

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?

A.The UI Policy condition is checking the wrong field.
B.The UI Policy is set to 'Run on Load' only, not 'Run on Change'.
C.The UI Policy order is too low compared to other policies.
D.The UI Policy is inactive.
AnswerB

UI Policies must have 'Run on Change' checked to execute when a field value changes on an existing record.

Why this answer

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.

Exam trap

The trap here is that candidates assume a UI Policy with a condition will automatically re-evaluate when the condition field changes, but they overlook the separate 'Run on Change' checkbox required for that behavior.

How to eliminate wrong answers

Option A is wrong because the administrator verified the condition is correctly set to 'Category equals Software', so the field reference is not the issue. Option C is wrong because the order of UI Policies only affects the sequence of execution when multiple policies apply to the same fields; the problem here is a missing trigger, not a conflict in order. Option D is wrong because the administrator explicitly states the UI Policy is active and works on new records, so inactivity is not the cause.

Practice this question →
55
MCQhard

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?

A.Disable all client-side scripting and rely solely on server-side validation.
B.Increase the system's form load timeout setting to prevent errors.
C.Convert all UI Policies to Client Scripts to move processing to the client.
D.Combine UI Policies with identical conditions into a single UI Policy with multiple actions.
AnswerD

This reduces the number of condition evaluations, decreasing server load and improving load time.

Why this answer

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.

Practice this question →
56
MCQhard

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?

A.Convert all reference fields to choice fields with a predefined list.
B.Write a client script to load reference options asynchronously using GlideAjax.
C.Add a reference qualifier to each reference field to limit the number of options displayed.
D.Enable the 'Use Ajax on Reference' option on the dictionary records for the reference fields.
AnswerD

This loads reference options asynchronously, allowing the form to render quickly while options populate in the background.

Why this answer

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.

Exam trap

The trap here is that candidates often think a reference qualifier (Option C) will improve performance by reducing the dataset, but they overlook that the query still executes synchronously during page load, whereas 'Use Ajax on Reference' changes the loading mechanism itself to be asynchronous.

How to eliminate wrong answers

Option A is wrong because converting reference fields to choice fields with a predefined list would require manual maintenance of static lists, which is impractical for large, dynamic tables like 'User' and 'Department', and would break referential integrity. Option B is wrong because writing a client script with GlideAjax to load reference options asynchronously is a custom approach that duplicates built-in functionality, adds unnecessary complexity, and is not the standard or recommended optimization for this scenario. Option C is wrong because adding a reference qualifier limits which records are displayed but does not change the synchronous loading behavior; the query still runs during page load, so it would not address the 10-second delay caused by fetching all options.

Practice this question →
57
Multi-Selecteasy

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

Select 2 answers
A.Configure the form layout to hide the field
B.Create an ACL that denies write access
C.Create a UI policy that sets the field to read-only when a condition is true
D.Set the field attribute to 'Read only' in dictionary entry
E.Add the field to a related list
AnswersC, D

UI policy can change state dynamically.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse ACLs (which control write access at the data layer) with UI policies (which control field editability at the presentation layer), leading them to incorrectly select option B as a method to make a field read-only on a form.

Practice this question →
58
MCQhard

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?

A.The field is hidden by a UI policy
B.The field is not in the default form view
C.The user has a personal form layout that removed the field
D.The user's role does not have read access to the field
AnswerC

Personalization can cause a field to be missing for an individual user.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse personal form layouts with UI policies or role-based access, assuming that a missing field for one user must be due to a system-wide rule rather than a user-specific customization.

How to eliminate wrong answers

Option A is wrong because a UI policy that hides the 'Category' field would apply to all users with the same conditions, not just one user. Option B is wrong because if the field were not in the default form view, it would be missing for all users, not just one. Option D is wrong because if the user's role did not have read access to the field, the field would typically be hidden or grayed out for all users with that role, not just a single user.

Practice this question →
59
Multi-Selecteasy

Which THREE of the following are features available in the UI16 interface?

Select 3 answers
A.Favorites list pinned at the top of the navigator
B.Ability to switch between Classic UI and UI16 via a button
C.Application tree view in the navigator
D.High-contrast themes for accessibility
E.Configurable Workspace for agents
AnswersA, C, D

UI16 includes a favorites section at the top.

Why this answer

The UI16 interface includes a Favorites list that can be pinned at the top of the navigator, allowing users to quickly access frequently used modules. This feature is part of the enhanced navigator in UI16, which replaces the classic application tree with a more streamlined, role-based menu.

Exam trap

The trap here is that candidates may confuse the Configurable Workspace (a separate agent interface) with a UI16 navigator feature, or assume a direct UI toggle exists for switching between Classic UI and UI16, when in fact the switch is handled through user preferences or system properties.

Practice this question →
60
Multi-Selecthard

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

Select 3 answers
A.Using the 'Form Layout' option from the table's context menu to add/remove fields.
B.Using the 'Personalize Form' option to reorder fields for all users.
C.Creating a UI Policy that reorders fields using the 'Reorder' action.
D.Writing a Client Script that sets the visibility of fields.
E.Modifying the 'Form Sections' related list on the table's dictionary entry.
AnswersA, C, E

This updates the sys_ui_form_section table.

Why this answer

The 'Form Layout' option, accessible from the table's context menu (or via the 'Configure' > 'Form Layout' menu), allows administrators to add, remove, and reorder fields on a form. This directly modifies the underlying form XML configuration for the table, making it a standard and valid method for customizing form layout.

Exam trap

The trap here is that candidates often confuse user-level personalization ('Personalize Form') with global configuration ('Form Layout'), or assume that Client Scripts can permanently alter form layout when they only affect runtime behavior.

Practice this question →
61
Matchingmedium

Match each ServiceNow report type to its visual representation.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Displays data as vertical bars

Shows proportions of a whole

Trends over time with connected points

Tabular view of data

Compares performance against targets

Why these pairings

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.

Practice this question →
62
MCQeasy

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?

A.Check the form layout for the incident form view to ensure the UI Action is included.
B.Check if there is a condition on the UI Action that evaluates to false.
C.Check the application scope to ensure the UI Action is in the correct scope.
D.Check the access controls (ACLs) for the UI Action.
AnswerA

UI Actions must be placed in the form layout to appear; after upgrades, layout assignments can sometimes be lost.

Why this answer

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.

Exam trap

The trap here is that candidates often assume a UI Action will automatically appear on the form if it is active and has no conditions, but they overlook the requirement that UI Actions must be explicitly added to the form layout for the specific form view.

How to eliminate wrong answers

Option B is wrong because the administrator already confirmed that no conditions are defined on the UI Action, so checking for a condition that evaluates to false is irrelevant. Option C is wrong because the UI Action is associated with the Incident table and is active, and scope issues would typically prevent the UI Action from being visible or functional, but the administrator has not indicated any scope-related symptoms; moreover, UI Actions are not scoped to applications in the same way as other records, and the upgrade would not change the scope of an existing UI Action. Option D is wrong because access controls (ACLs) control who can see or use a UI Action based on roles, but the administrator has not mentioned any role-based restrictions, and the UI Action is active and has no conditions; ACLs would not cause a UI Action to disappear from the form unless the user lacks the required role, but the question states the user reports it disappeared after an upgrade, implying a configuration change rather than a permission issue.

Practice this question →
63
Multi-Selectmedium

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

Select 2 answers
A.Creating a new UI page
B.Modifying the table's XML definition
C.Adding a section in the sys_ui_section table
D.Using an application file
E.Using form designer
AnswersC, E

Directly inserting a record in the sys_ui_section table creates a section.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse modifying a table's XML definition (Option B) with adding a form section, but XML changes affect the form's structure at a lower level and are not the standard method for section creation.

Practice this question →
64
Multi-Selectmedium

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.)

Select 2 answers
A.Business Rule (before query)
B.Data Policy (update)
C.Client Script (onSubmit)
D.UI Policy (on load)
E.Dictionary (read only)
AnswersB, E

A Data Policy can enforce read-only on update, preventing changes after initial save.

Why this answer

(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.

Exam trap

The trap here is that candidates often confuse client-side controls (Client Scripts and UI Policies) with server-side enforcement in ServiceNow, mistakenly believing that a client-side onSubmit script or UI Policy can reliably prevent field changes, when in fact only server-side mechanisms like Data Policies and Dictionary read-only settings provide true enforcement.

Practice this question →
65
MCQmedium

Refer to the exhibit. A business rule has this script and is set to run on 'before insert' and 'before query'. When a user creates a new incident and sets the assignment_group to 'Network', after saving the assignment_group displays 'Help Desk'. What is the most likely cause?

A.The script runs on 'before query' and overwrites the value when the record is retrieved
B.The script should use setValue instead of setDisplayValue
C.The setDisplayValue method is incorrect for this field
D.The script runs on 'before insert' and overwrites the user's selection
AnswerA

The 'before query' action runs every time the record is loaded, setting the assignment_group to 'Help Desk' regardless of saved value.

Why this answer

The script runs on 'before query', which executes when the record is retrieved from the database. Since the business rule is set to run on both 'before insert' and 'before query', the 'before query' phase overwrites the assignment_group value to 'Help Desk' after the user saves the record and it is retrieved for display. This explains why the user sees 'Help Desk' instead of 'Network' after saving.

Exam trap

The trap here is that candidates assume the 'before insert' phase is the only one affecting the saved value, overlooking that 'before query' runs on retrieval and can change what the user sees after saving.

How to eliminate wrong answers

Option B is wrong because setDisplayValue is the correct method for setting a display value on a reference field like assignment_group; setValue would set the sys_id, not the display name. Option C is wrong because setDisplayValue is valid for reference fields and is not inherently incorrect; the issue is the script's execution phase, not the method itself. Option D is wrong because if the script ran only on 'before insert', it would overwrite the user's selection before the record is saved, but the user would see 'Help Desk' immediately upon saving, not after saving; the fact that the value changes after saving points to the 'before query' phase.

Practice this question →
66
MCQmedium

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?

A.Dictionary entry with a default value calculated from the reference field
B.Access Control Rule on the email field
C.UI Policy with an 'onChange' condition
D.Data lookup field configuration
AnswerC

Correct. A UI Policy with an 'onChange' condition on the reference field can automatically populate the email field when a user is selected, using the reference field's dot-walked value.

Why this answer

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.

Exam trap

Candidates often think that a dictionary default value with dot-walking will populate the email when the reference field changes, but dictionary defaults only set values on record creation. The correct reactive mechanism is a UI Policy with an onChange condition.

How to eliminate wrong answers

Option B is wrong because Access Control Rules (ACLs) control read/write permissions on fields, not automatic data population; they cannot set a field's value based on another field. Option C is wrong because a UI Policy with an 'onChange' condition can populate fields client-side, but it is less reliable for this use case as it depends on client-side execution and may not trigger correctly in all scenarios (e.g., when the record is created via web services or import sets). Option D is wrong because a Data Lookup field configuration is used to display related data from another table in a read-only manner, not to automatically populate a separate field with a value from a reference field.

Practice this question →
67
MCQeasy

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

A.Navigator filter
B.Favorites
C.History
D.Global search
AnswerA

Typing the incident number in the navigator filter directly opens the record.

Why this answer

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.

Exam trap

ServiceNow often tests the distinction between the Navigator filter (for quick record lookup by number) and Global search (for broader text searches), leading candidates to mistakenly choose Global search because they think it is the default search tool for all purposes.

How to eliminate wrong answers

Option B is wrong because Favorites are user-defined shortcuts to frequently accessed modules or reports, not a feature for searching by record number. Option C is wrong because History shows recently viewed records and modules, but it does not allow direct searching by a specific incident number. Option D is wrong because Global search performs a broader text-based search across multiple tables and fields, which is less efficient for quickly locating a record by its exact number compared to the Navigator filter.

Practice this question →
68
MCQmedium

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?

A.The method 'g_form.setMandatory' is deprecated
B.The script is blocked by the 'glide.script.secure' property
C.There is a syntax error in the function parameters: 'previous !=null' is invalid
D.The script uses 'current' object which is not available in client scripts
AnswerC

The correct is 'previous' without the comparison.

Why this answer

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.

Exam trap

ServiceNow often tests the distinction between client-side and server-side objects, and the trap here is that candidates mistakenly think `previous` is available in UI Policy scripts because it is commonly used in business rules, leading them to overlook the syntax error.

How to eliminate wrong answers

Option A is wrong because `g_form.setMandatory` is not deprecated; it is a standard client-side API used to make fields mandatory. Option B is wrong because the `glide.script.secure` property affects server-side script execution, not client-side UI Policy scripts. Option D is wrong because `current` is indeed available in UI Policy scripts as a client-side object representing the current record, but the issue is with `previous`, not `current`.

Practice this question →
69
MCQeasy

A user wants to add a shortcut to an often-used module on their application navigator. Which feature should they use?

A.Add the module to the 'Configurable Workspace'
B.Right-click the module and select 'Create Favorites'
C.Right-click the module and select 'Personalize'
D.Use the 'Personalize Form' option from the hamburger menu
AnswerB

Favorites provide easy access to frequently used modules.

Why this answer

To add a shortcut to a frequently used module on the application navigator, users can right-click the module and select 'Create Favorites'. This adds the module to their favorites list, which appears at the top of the navigator for quick access. Option A is incorrect because 'Configurable Workspace' is a different interface and not used for adding navigator shortcuts.

Option C is incorrect because 'Personalize' allows users to hide modules but does not create shortcuts. Option D is incorrect because 'Personalize Form' is used to customize form layouts, not the navigator.

Practice this question →
70
MCQhard

A user reports that the 'My Tasks' module they frequently use has disappeared from the left navigation. Other users can still see it. What is the most likely cause?

A.The user accidentally used 'Personalize' and hid the module from their navigation
B.A system property was changed that hides the module for all users
C.The module was deleted from the application menu by an admin
D.The user's role was changed and they no longer have access to the module
AnswerA

Users can right-click on a module and choose 'Personalize' to hide it, which only affects their own view.

Why this answer

The 'Personalize' feature in ServiceNow allows users to hide modules from their own left navigation without affecting other users. When a user right-clicks a module and selects 'Personalize', they can choose to hide it, which removes it only from their view. Since other users can still see the module, this indicates a user-specific change rather than a global or role-based one.

Exam trap

ServiceNow often tests the distinction between user-specific personalization and global or role-based changes, and the trap here is that candidates may assume a role change or admin action is the cause when the symptom is isolated to a single user.

How to eliminate wrong answers

Option B is wrong because a system property change would affect all users, not just one, and the question states other users can still see the module. Option C is wrong because deleting the module from the application menu by an admin would remove it for all users, not just one. Option D is wrong because if the user's role was changed and they lost access, the module would be hidden for them, but other users with the same role would also be affected unless the role change was unique to that user; however, the most likely cause given the user-specific nature is the Personalize feature, not a role change.

Practice this question →
71
Multi-Selecthard

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

Select 3 answers
A.Session timeout settings for inactive users
B.Performance impact of custom UI16 navigation
C.Application scope of the modules
D.How personalization affects module ordering
E.Security roles required to access modules
AnswersB, D, E

Heavy navigation can slow down the system.

Why this answer

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.

Exam trap

The trap here is that candidates confuse system-level settings (like session timeout) with navigation customization factors, or assume application scope directly controls navigation ordering, when in fact scope only affects module ownership and update set isolation.

Practice this question →
72
MCQhard

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?

A.Create a UI Policy that hides the 'Description' field and reorders fields for the specific group.
B.Use the 'Personalize Form' option to rearrange fields and share the view with the group.
C.Create a new view for the Incident table and assign it to a user criteria that includes the group.
D.Write a Business Rule that updates the form configuration when the group members open a record.
AnswerC

Views can be scoped to user criteria.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse UI Policies (which can hide fields) with views (which control the entire form layout including field order and visibility), leading them to select option A despite UI Policies being unable to reorder fields.

How to eliminate wrong answers

Option A is wrong because UI Policies are designed to dynamically show/hide fields or make them mandatory based on conditions, but they cannot reorder fields on a form; field reordering is a layout function that requires a view or form section configuration. Option B is wrong because 'Personalize Form' allows an individual user to rearrange fields for their own session, but sharing a personalized view with a group is not a supported feature; it does not create a persistent, group-specific view accessible from the context menu. Option D is wrong because Business Rules run server-side and cannot directly modify the client-side form layout (field order or visibility) for a specific group; they are used for data manipulation and validation, not for UI configuration.

Practice this question →
73
MCQhard

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?

A.Rich text fields will no longer have the ability to insert/edit tables
B.It will prevent users from editing list records in a UI16 form
C.Buttons will lose their shadow effect
D.No change because system properties are not used in UI
AnswerA

List editor refers to table insertion.

Why this answer

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.

Exam trap

The trap here is that candidates may think system properties have no UI impact or confuse rich text toolbar properties with other UI settings like list editing or button styling, but the question specifically tests knowledge of how rich text editor features are toggled via system properties.

How to eliminate wrong answers

Option B is wrong because UI16 forms and list editing are controlled by different system properties (e.g., 'glide.ui.list_edit' or 'glide.ui.form_edit') and not by rich text table properties. Option C is wrong because button shadow effects are controlled by CSS or theme properties, not by rich text configuration system properties. Option D is wrong because system properties directly affect UI behavior; in this case, the rich text editor reads these properties to determine which toolbar buttons to display.

Practice this question →
74
MCQmedium

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?

A.Check the form layout for the variable editor.
B.Re-import the catalog variables from a saved XML backup.
C.Check any UI Policies that may be converting the variable type.
D.Clear the system cache (e.g., via 'Cache Flush' in System Diagnostics) and test again.
AnswerD

Clearing cache removes stale data and forces reload of variable definitions, often fixing rendering issues after patches.

Why this answer

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.

Exam trap

The trap here is that candidates assume the problem is with the variable definition or a UI Policy, when in fact the patch likely introduced a new form layout version that the cache is ignoring, making cache flush the correct first diagnostic step.

How to eliminate wrong answers

Option A is wrong because the variable editor is used to configure variable definitions and choice lists, but the question states those definitions are intact; the issue is with the form's runtime rendering, not the variable's stored configuration. Option B is wrong because re-importing from XML would overwrite the current (correct) variable definitions with potentially outdated data, and the problem is not data corruption but a cached form layout. Option C is wrong because the question explicitly states that no UI Policies or client scripts are modifying the variable types, and UI Policies cannot change a field's type from 'Choice' to 'Plain text'—they can only hide, show, or make fields mandatory.

Practice this question →
75
MCQmedium

When configuring a form, you want to add a new section. What is the correct approach?

A.Modify the default view
B.Use the form designer
C.Create a UI action
D.Edit the table schema
AnswerB

Form designer provides a drag-and-drop interface to add and arrange sections.

Why this answer

The form designer allows you to add sections directly. Options A, C, and D are not standard methods for adding sections.

Practice this question →
Page 1 of 2 · 94 questions totalNext →

Ready to test yourself?

Try a timed practice session using only UI, Navigation and Forms questions.

Start 20-question session