Courseiva

CCNA Ui Navigation Forms Questions

19 of 94 questions · Page 2/2 · Ui Navigation Forms topic · Answers revealed

Practice these questionsExam hubAll questions
76
MCQmedium

When creating a new form section, which configuration ensures the section appears on the form for all users?

A.Visibility set to 'Everyone'
B.Roles field left blank
C.Condition set to true
D.Order set to 1
AnswerB

A blank Roles field means no role restriction, so all users can see the section.

Why this answer

Leaving the Roles field blank on a form section means no role restrictions are applied, making the section visible to all users by default. In ServiceNow, form sections are controlled by the 'Roles' field; if it is empty, the section is not filtered by any role and appears for everyone. This is the standard configuration for universal visibility.

Exam trap

The trap here is that candidates may confuse the 'Roles' field behavior with other visibility mechanisms like UI policies or client scripts, or assume that leaving a field blank means the section is hidden, when in fact it means no restrictions are applied.

How to eliminate wrong answers

Option A is wrong because 'Visibility set to Everyone' is not a valid configuration in ServiceNow form sections; there is no such field or setting. Option C is wrong because 'Condition set to true' refers to a client script or UI policy condition, not a form section property; form sections do not have a 'Condition' field for visibility. Option D is wrong because 'Order set to 1' only controls the section's position on the form, not its visibility to users.

Practice this question →
77
MCQmedium

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

A.Use an ACL to restrict access
B.Set a condition on the 'Filter' property of the module
C.Create a UI policy on the table
D.Add a client script to the list
AnswerB

The filter property allows defining a condition for the module's list.

Why this answer

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

Exam trap

ServiceNow often tests the distinction between server-side record filtering (module Filter property) and client-side or security-based restrictions (ACLs, UI policies, client scripts), leading candidates to confuse access control with data scoping.

How to eliminate wrong answers

Option A is wrong because ACLs (Access Control Lists) control record-level security (create, read, write, delete) based on user roles and conditions, but they do not filter the records shown in a module's list view; a user with read access would still see all records unless a filter is applied. Option C is wrong because UI policies run on the client side to control field visibility, mandatory status, or values on a form, not to filter the list of records displayed in a module. Option D is wrong because a client script executes on the client side (e.g., onLoad, onChange) and cannot modify the server-side query that populates a module's list view; it can only affect the current form or list client-side behavior.

Practice this question →
78
MCQhard

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

A.Grants read access only to admin
B.Denies read access to everyone
C.Denies read access to non-admin users
D.Grants read access to everyone
AnswerC

Non-admin users get false, so they are denied read access.

Why this answer

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

Option C correctly describes this behavior.

Exam trap

The trap here is that candidates often misinterpret a deny rule as a grant rule, thinking the ACL 'grants read access to admin' when it actually denies access to non-admin users, with admin access being the default behavior when no deny applies.

How to eliminate wrong answers

Option A is wrong because the ACL does not 'grant' read access to admin; it denies access to non-admin users, which implicitly allows admin access, but the ACL itself is a deny rule, not a grant. Option B is wrong because the ACL does not deny read access to everyone; it only denies non-admin users, while admin users can still read. Option D is wrong because the ACL explicitly denies read access to non-admin users, so it does not grant read access to everyone.

Practice this question →
79
MCQeasy

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

A.On the 'sys_ui_section' table
B.On the 'incident' table record under 'Views'
C.In the 'sys_ui_view' table directly
D.In the 'Application Navigator' module
AnswerB

Views are created from the table record's related list 'Views'.

Why this answer

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

Exam trap

The trap here is that candidates often think views are created directly in the 'sys_ui_view' table (Option C) because that is where the records are stored, but the correct procedure is to create them from the table record's 'Views' related list to ensure proper table association and ServiceNow platform configuration.

How to eliminate wrong answers

Option A is wrong because the 'sys_ui_section' table stores individual sections of a form, not the entire view; creating a view there would only define a section, not a complete mobile-optimized layout. Option C is wrong because while views are ultimately stored in the 'sys_ui_view' table, directly creating a record there bypasses the necessary table-level association and view configuration that the platform requires for proper behavior. Option D is wrong because the 'Application Navigator' module is used to configure the left-hand navigation menu and modules, not to create form views.

Practice this question →
80
MCQeasy

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

A.Use a UI Macro to arrange report positions within the dashboard.
B.Modify the report output format to display inline.
C.Create a new dashboard using a two-column template and add the reports again.
D.Edit the dashboard's layout property and change the column count to 2.
AnswerD

This directly changes the layout to display reports side by side without recreating the dashboard.

Why this answer

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

Exam trap

The trap here is that candidates often assume they must rebuild the dashboard from scratch (Option C) or use a complex customization (Option A), when ServiceNow provides a simple built-in layout property to adjust column count on existing dashboards.

How to eliminate wrong answers

Option A is wrong because UI Macros are used for custom UI elements or reusable server-side code, not for dynamically arranging report positions within a dashboard; they cannot modify dashboard column layouts. Option B is wrong because the 'report output format' (e.g., list, pie chart) controls how data is displayed within a single report, not the spatial arrangement of multiple reports on a dashboard. Option C is wrong because while creating a new dashboard with a two-column template would work, it is unnecessary and inefficient—the administrator can simply edit the existing dashboard's layout property to change the column count, avoiding the need to recreate and re-add reports.

Practice this question →
81
MCQmedium

A manager wants to see a real-time gauge on their homepage showing the number of open incidents assigned to their team. Which widget should they add to their dashboard?

A.Mashup widget
B.Report gauge widget
C.HTML widget
D.Filter widget
AnswerB

Report gauge widget displays a report as a gauge, perfect for showing counts.

Why this answer

The Report gauge widget is specifically designed to display a single metric, such as a count of open incidents, in a real-time gauge format on a dashboard. It allows the manager to configure a report that counts incidents assigned to their team with a status of 'Open', and the gauge updates automatically as data changes. This widget is part of the standard dashboard toolkit in ServiceNow for visualizing key performance indicators.

Exam trap

The trap here is that candidates often confuse the Report gauge widget with the HTML widget, thinking they can embed a custom gauge via HTML, but the Report gauge widget is the only one that natively binds to a ServiceNow report for automatic data refresh and formatting.

How to eliminate wrong answers

Option A is wrong because the Mashup widget is used to embed external web content or applications into a dashboard, not to display a real-time gauge of ServiceNow data. Option C is wrong because the HTML widget allows custom HTML content but does not natively connect to ServiceNow reports or provide real-time data updates without additional scripting. Option D is wrong because the Filter widget is used to apply filters to other widgets on a dashboard, not to display a gauge or metric itself.

Practice this question →
82
MCQhard

An incident has state set to 'In Progress' (value 2). When the user loads the form or updates the state, what is the resulting form behavior?

A.The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden
B.The 'assigned_to' field is mandatory but the 'assignment_group' field remains visible
C.The 'assigned_to' field is not mandatory because the Client Script overrides the UI Policy
D.The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden, but the Client Script causes an error
AnswerA

UI Policy sets both actions; Client Script reinforces mandatory.

Why this answer

The UI Policy is configured to run when the state is 'In Progress' (value 2). It sets the 'assigned_to' field as mandatory and hides the 'assignment_group' field. Since UI Policies run on the client side when the form loads or the state changes, the resulting behavior is that 'assigned_to' becomes mandatory and 'assignment_group' is hidden.

The Client Script does not override the UI Policy because UI Policies have higher priority in enforcing field behavior on the form.

Exam trap

ServiceNow often tests the misconception that Client Scripts can override UI Policies, but in reality, UI Policies are applied after Client Scripts on form load and have higher precedence for mandatory and visibility settings.

How to eliminate wrong answers

Option B is wrong because the UI Policy explicitly hides the 'assignment_group' field when state is 'In Progress', so it does not remain visible. Option C is wrong because Client Scripts do not override UI Policies; UI Policies are designed to enforce field behavior (mandatory, visible) and take precedence over Client Scripts that might try to change those properties. Option D is wrong because there is no indication of an error; the UI Policy and Client Script can coexist without causing an error, and the UI Policy's mandatory and hide actions execute successfully.

Practice this question →
83
MCQhard

An administrator is troubleshooting an issue where a form section on the incident form is not visible to users with the 'itil' role, but is visible to admins. The section has no UI Policy or ACL restricting it. What is the most likely cause?

A.The section has a role requirement that the users lack
B.An ACL is blocking the fields in the section
C.The fields in the section are marked as mandatory
D.The section has 'Visible' set to false in the form layout
AnswerA

Sections can be role-restricted; if users lack the role, the section is hidden.

Why this answer

The most likely cause is that the form section has a role requirement configured in its dictionary entry or form layout. When a section is restricted to a specific role (e.g., 'admin'), users without that role (e.g., 'itil') will not see it, even if no UI Policy or ACL explicitly blocks it. This is a common visibility control in ServiceNow that overrides general role access.

Exam trap

The trap here is that candidates often assume visibility issues are always caused by ACLs or UI Policies, overlooking the role-based visibility setting on the section itself, which is a distinct configuration in the form layout or dictionary.

How to eliminate wrong answers

Option B is wrong because the question explicitly states there is no ACL restricting the section, so an ACL cannot be the cause. Option C is wrong because mandatory fields affect submission validation, not visibility; they do not hide a section from users. Option D is wrong because if 'Visible' were set to false in the form layout, the section would be hidden from all users, including admins, which contradicts the scenario where admins can see it.

Practice this question →
84
Multi-Selecthard

A user reports that a field is not visible on the form. Which three factors could cause a field to be hidden? (Choose three.)

Select 3 answers
A.The field's visibility condition in a UI Policy
B.The field is not in the current form view
C.The user does not have the required role to view the field
D.The field's 'Active' checkbox is unchecked
E.The field is configured as read-only
AnswersA, B, C

UI Policies can set the visible attribute to false based on conditions.

Why this answer

UI Policies can include visibility conditions that dynamically hide or show fields based on criteria such as the value of another field, the current state, or the user's role. When a field's visibility condition evaluates to false, the field is hidden from the form, even if it is present in the current view and the user has the appropriate role.

Exam trap

The trap here is that candidates often confuse 'read-only' with 'hidden', but read-only fields remain visible and only restrict editing, while hidden fields are completely absent from the user's view.

Practice this question →
85
MCQhard

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

A.Business rule
B.Client script with onChange event
C.UI policy
D.Data policy
AnswerC

UI policies can make fields mandatory based on conditions without scripting.

Why this answer

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

Exam trap

The trap here is that candidates often confuse UI policies with client scripts or business rules, but UI policies are the only out-of-box mechanism that can make a field mandatory based on a condition without requiring a server round-trip or custom scripting.

How to eliminate wrong answers

Option A is wrong because a business rule runs server-side and cannot dynamically change field properties like mandatory on the client form in real-time without a page refresh. Option B is wrong because a client script with onChange event can detect the field change but cannot directly make another field mandatory; it would require additional scripting to manipulate the UI, which is not the standard or recommended approach. Option D is wrong because a data policy enforces mandatory fields at the database level during record submission, not interactively on the form as the user changes fields.

Practice this question →
86
MCQmedium

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

A.Check the 'Visibility' field on the dictionary entry for 'assignment_group' and set it to 'All' if it is set to 'Admin'.
B.Create a UI Policy that sets the 'assignment_group' field visible when the form loads.
C.Add the 'itil' role to the 'Roles' field on the dictionary entry for 'assignment_group'.
D.Create a new Access Control Rule (ACL) to grant read access to the 'itil' role for the 'assignment_group' field.
AnswerA

The 'Visibility' field on the dictionary can hide fields from non-admin users.

Why this answer

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

Exam trap

The trap here is that candidates may focus on UI Policies or ACLs, overlooking the new Quebec-specific 'Visibility' dictionary field that directly controls field visibility at the metadata level.

How to eliminate wrong answers

Option B is wrong because creating a new UI Policy would be redundant and ineffective if the dictionary-level 'Visibility' field is set to 'Admin', as dictionary settings override UI Policies. Option C is wrong because adding the 'itil' role to the 'Roles' field on the dictionary entry would restrict the field to only users with that role, but the field is already missing for 'itil' users, and the current 'Roles' field is empty, so this would not solve the issue. Option D is wrong because ACLs control data access and security, not form field visibility; the field is already visible to admins, indicating no ACL issue, and the problem is a UI-level visibility setting.

Practice this question →
87
MCQmedium

A form has a UI Policy that sets a field mandatory. The mandatory is not applied. Which is a likely cause?

A.The field is already mandatory by dictionary
B.UI Policy order is too low
C.UI Policy condition returns false
D.UI Policy is set to 'Run on load' only
AnswerC

If the condition evaluates to false, the UI Policy does not apply its actions, such as setting mandatory.

Why this answer

UI Policies enforce client-side business logic. The mandatory attribute is applied only when the UI Policy's condition evaluates to true. If the condition returns false, the mandatory setting is never applied, regardless of other settings.

This is the most direct reason why a UI Policy's mandatory field would not take effect.

Exam trap

The trap here is that candidates often confuse the condition evaluation with the policy's execution order or trigger timing, assuming that a UI Policy set to 'Run on load' will always apply its actions, when in fact the condition must be true for the actions to execute.

How to eliminate wrong answers

Option A is wrong because if the field is already mandatory by dictionary, the UI Policy's mandatory setting would be redundant but not prevented; the field would still be mandatory. Option B is wrong because UI Policy order determines execution sequence among multiple policies, but a policy with a false condition will not apply its actions regardless of order. Option D is wrong because 'Run on load' only means the policy runs when the form loads, but if the condition is false at load time, the mandatory action still won't be applied; the issue is the condition, not the trigger timing.

Practice this question →
88
MCQmedium

A project manager wants all incident forms to display a static informational message at the top for all users without any conditions. Which method is most efficient and requires the least ongoing maintenance?

A.Create a CMS banner that targets the incident module.
B.Add a form annotation to the incident form view.
C.Create a UI Script that runs on load and adds a message.
D.Create a UI Policy with an 'always true' condition to show a message.
AnswerB

Form annotations are static, easy to add, and do not require conditions or code.

Why this answer

A form annotation is the most efficient method for displaying a static informational message on all incident forms without conditions. It requires no scripting, no conditions, and no ongoing maintenance, as it is a simple configuration on the form view that persists across all records.

Exam trap

The trap here is that candidates often overcomplicate the solution by choosing a UI Policy or UI Script, thinking they need a dynamic condition, when a simple form annotation is the most efficient and maintenance-free approach for a static message.

How to eliminate wrong answers

Option A is wrong because a CMS banner is designed for content management system pages, not for platform form views like the incident module, and would require additional configuration to appear on forms. Option C is wrong because a UI Script that runs on load adds unnecessary complexity and maintenance overhead for a simple static message, and it requires scripting knowledge. Option D is wrong because a UI Policy with an 'always true' condition is overkill for a static message; UI Policies are intended for dynamic field behavior and conditions, and using one for a static message introduces unnecessary processing and maintenance.

Practice this question →
89
Multi-Selectmedium

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

Select 2 answers
A.The navigator displays all tables in the instance.
B.Users can add links to the navigator as favorites.
C.The navigator can be filtered by typing in the filter field.
D.End users can add new modules to the navigator.
E.Administrators can customize the navigator by creating new modules.
AnswersC, E

The filter field allows searching modules.

Why this answer

The ServiceNow application navigator includes a built-in filter field that allows users to quickly locate modules, reports, or other navigator entries by typing keywords. This filter dynamically narrows the displayed items based on the input, improving navigation efficiency without requiring administrative changes.

Exam trap

The trap here is that candidates may confuse the navigator's filter functionality with the global search or think that end users can customize the navigator structure, when in fact only administrators can create modules and the filter is a simple client-side text match.

Practice this question →
90
Multi-Selectmedium

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

Select 3 answers
A.Form views can be imported from other instances.
B.A form view can only contain one section.
C.A form view defines which fields are displayed and their layout.
D.A form view can be assigned to a specific role.
E.If no view is assigned to a user, the default view is used.
AnswersC, D, E

Views control field placement.

Why this answer

Form views in ServiceNow are the primary mechanism for controlling which fields appear on a form and how they are arranged (e.g., order, sections, and visibility). The view definition is stored in the 'sys_ui_view' table and can be customized per table to tailor the user experience without altering the underlying data model.

Exam trap

ServiceNow often tests the misconception that form views are limited to a single section, but ServiceNow explicitly supports multiple sections within one view to group related fields.

Practice this question →
91
MCQhard

A system administrator needs to hide the 'Delete' button on the incident form for users with the 'itil' role, but allow it for administrators. What is the best approach?

A.Modify the form view to remove the button
B.UI policy with role condition
C.Business rule checking role
D.ACL with condition on role
AnswerB

UI policies can hide form buttons based on conditions like user roles.

Why this answer

A UI Policy with a role condition is the best approach because it dynamically controls the visibility of the 'Delete' button on the incident form based on the user's role. UI Policies run client-side and can hide or show fields and buttons without requiring a page refresh, making them ideal for form-level UI changes. By setting the condition to 'role=itil' and the action to 'Hide', the button will be hidden for itil users but remain visible for administrators who do not have that condition applied.

Exam trap

The trap here is that candidates often confuse ACLs (which control backend access) with UI Policies (which control frontend visibility), leading them to choose ACLs for hiding buttons instead of using the correct client-side mechanism.

How to eliminate wrong answers

Option A is wrong because modifying the form view to remove the button would permanently hide it for all users, including administrators, which does not meet the requirement of allowing it for administrators. Option C is wrong because a Business Rule runs server-side and cannot directly hide a UI element on the form; it would require additional client-side scripting or a UI Policy to achieve the visibility change. Option D is wrong because an ACL controls data access and record-level operations (like delete), not the visibility of UI elements on the form; an ACL would prevent the delete action but would not hide the button itself.

Practice this question →
92
MCQmedium

Refer to the exhibit. This script runs in a background script. Which set of records will be printed?

A.Incidents with state=3 AND assigned_to is not null
B.Incidents with state=3 AND priority<=3 AND assigned_to is not null
C.Incidents with priority<=3
D.All incidents
AnswerB

All three conditions are combined with AND.

Why this answer

The script uses a GlideRecord query on the Incident table with an encoded query string 'state=3^priority<=3^assigned_toISNOTEMPTY'. This filters for records where state equals 3 (which corresponds to 'On Hold' in the default incident state model), priority is less than or equal to 3, and the assigned_to field is not empty. The while loop iterates over the matching records and prints each one, so only incidents meeting all three conditions are output.

Exam trap

The trap here is that candidates often overlook the 'assigned_toISNOTEMPTY' condition or misinterpret the '^' as an OR operator, leading them to select an option that includes records missing one of the required filters.

How to eliminate wrong answers

Option A is wrong because it omits the priority<=3 condition; the script explicitly includes 'priority<=3' in the encoded query, so incidents with priority 4 or 5 would be excluded even if state=3 and assigned_to is not null. Option C is wrong because it ignores both the state=3 and assigned_toISNOTEMPTY conditions; the query requires all three filters, not just priority<=3. Option D is wrong because the query is not empty—it applies three specific conditions, so not all incidents are returned.

Practice this question →
93
Matchingmedium

Match each ServiceNow application scope to its description.

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

Concepts
Matches

Accessible across all applications in the instance

Isolated application with its own tables and access controls

System scope for core platform functionality

Custom applications developed by the instance owner

Pre-built applications available from ServiceNow Store

Why these pairings

Global scope means application is available to all users. User scope restricts access to a specific user or group. System scope grants system privileges.

The distractors confuse these definitions.

Practice this question →
94
MCQeasy

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

A.Check the sys_module list for role requirements on the 'My Work' module.
B.Ask the user to clear their browser cache and reload the instance.
C.Deactivate and reactivate the 'My Work' module in the application navigator.
D.Assign the user the 'admin' role to ensure full access.
AnswerA

Role requirements determine module visibility.

Why this answer

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

Exam trap

The trap here is that candidates often jump to client-side fixes like clearing cache or assume a module is broken, rather than understanding that module visibility is role-driven and must be verified in the sys_module record.

How to eliminate wrong answers

Option B is wrong because clearing the browser cache would not resolve a role-based visibility issue; it only addresses client-side caching problems. Option C is wrong because deactivating and reactivating the module does not change role assignments; it would only affect the module's active state, not its role requirements. Option D is wrong because assigning the 'admin' role is an overprivileged workaround that bypasses proper role-based access control and is not a recommended troubleshooting step.

Practice this question →
← PreviousPage 2 of 2 · 94 questions total

Ready to test yourself?

Try a timed practice session using only Ui Navigation Forms questions.

Start 20-question session