CCNA UI, Navigation and Forms Questions

After patches, the system cache may hold outdated metadata causing variables to render incorrectly. Clearing the cache forces the system to reload the variable definitions from the database, which often resolves rendering issues. Re-importing variables is not needed since definitions are correct; UI Policies and form layouts do not affect the type of the variable itself.

Option B is correct because the form designer allows you to add sections directly. Options A, C, and D are not standard methods for adding sections.

Option A is correct because leaving the 'Roles' field blank makes the section visible to all users. Options B, C, and D are incorrect because they either restrict visibility or are not necessary conditions.

Option B is correct because 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.

Option D is correct because the ACL grants read access only to users with the admin role, effectively denying read access to non-admin users. Options A, B, and C misinterpret the ACL logic.

Option B is correct because 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.

Dashboards have a layout configuration that allows changing the number of columns. Editing the dashboard's properties to set a two-column layout is the simplest and most efficient way to achieve a side-by-side arrangement. Creating a new dashboard would require re-adding reports, and UI Macros or report format changes do not affect dashboard layout.

Options A, C, and D are correct: UI Policy can set visible false; field not in form view; role restriction in dictionary. Option B (active checkbox) does not hide on form; it hides from table. Option E (read-only) does not hide, just makes non-editable.

A UI Policy must be active to execute, and it only runs on forms for the table it is defined on. Inactive policies are ignored, and policies on a different table will never trigger. Script errors may cause runtime failures but the policy still attempts to run; ordering or condition being always true do not prevent execution.

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.

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.

Option B is correct because if the condition script returns false, the UI Policy actions will not execute. Options A, C, and D are less likely to cause this specific issue.

Form annotations are static text that can be added directly to the form view and appear for all users without any conditions or scripting. UI Policies and UI Scripts add unnecessary overhead, and CMS banners are designed for global headers not specific to a table.

Option C is correct because 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.

Option C is correct because 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.

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.

Option B is correct because the script queries incidents where state=3, priority<=3, and assigned_to is not null (AND logic). Options A, C, and D describe different sets.

Scopes define the boundaries and accessibility of applications.

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.