SNOW-CAD Designing interfaces and user experiences Practice Test 3 — 15 Questions

Question 1

A developer is creating a UI Page in ServiceNow that must display a list of active incidents. The page should render a table with columns for number, short description, and priority. The developer wants to minimize server-side JavaScript and leverage the platform's built-in rendering. Which approach should the developer use to display the incident data?

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

Accepted Answer

Embed a tag with a data source that queries the incident table for active records, and specify columns.. The Jelly tag is designed to render tabular data from a specified data source, such as a GlideRecord, directly in a UI Page. This approach uses server-side rendering, reduces the need for custom client scripts, and is a standard practice for displaying lists. The other options either use non-existent tags or require excessive custom JavaScript, making them less efficient and not aligned with the requirement.

Answer

Use a <g:ui_list> tag to embed a standard list view of incidents filtered by active=true.

Answer

Create a client script that uses GlideAjax to fetch incident records and dynamically build an HTML table.

Answer

Use a <g:list> tag with the table attribute set to incident and a condition to filter active incidents.

Question 2

A developer is building a Service Portal page that must show a compact, at-a-glance view of the current user's open incidents, grouped by state, with a clickable number in each group that opens a filtered list. The counts must reflect live data and update whenever the page loads, and no custom server-side code should be needed. Which approach should the developer use?

Accepted Answer

Use the Count widget, point it at the Incident table, and configure a filter and grouping so each state renders as a clickable count that links to a filtered list.. The requirement is interactive, live, grouped counts that each link to a filtered list, achieved with the out-of-the-box Count widget. It queries a table using a filter, groups rows, and renders each group as a clickable numeric tile without custom server-side code. Report charts, Data Table grouping, and Performance Analytics indicators each fail to deliver clickable per-group counts on page load.

Answer

Add a Data Table widget, set the table to Incident, and group rows by the State column so users can read the counts.

Answer

Create a Performance Analytics indicator for open incidents by state and surface it through the KPI Details widget on the page.

Answer

Configure a Report with a Bar Chart grouped by State on the Incident table, then embed that report on the portal page using the Report widget.

Question 3

A developer needs to create a Service Portal widget that displays a chart of incident counts by priority. The chart must update automatically every 30 seconds without a full page reload. The developer wants to minimize server load and avoid unnecessary data retrieval when the widget is not visible. Which approach should be used?

Accepted Answer

Use the $interval service in the widget's client controller to poll the server every 30 seconds, and cancel the interval when the widget is destroyed.. Using the $interval service in the client controller allows the widget to poll the server at a defined interval and automatically cancel the polling when the widget is destroyed, which prevents unnecessary server calls and respects the widget lifecycle. This is the recommended approach for periodic updates without a full page reload.

Answer

Use the spUtil.recordWatch method to watch the incident table and refresh the chart when records change.

Answer

Use a client script with setInterval to call the server and refresh the chart data every 30 seconds.

Answer

Use a scheduled job that runs every 30 seconds to update a custom table, and have the widget read from that table.

Question 4

A developer is designing a new Service Portal widget that will display a complex form with multiple input fields. The developer wants to ensure the widget is user-friendly and follows ServiceNow best practices. Which TWO practices should the developer follow? (Choose two.)

Accepted Answer

Use the widget's HTML template to include AngularJS directives for form validation.. Best practices for Service Portal widget development include fetching data server-side with spUtil.get to populate the model, and using AngularJS directives for client-side form validation. These approaches ensure efficient data handling, security, and a responsive user interface, while avoiding unsupported or discouraged techniques.

Answer

Use a scheduled job to pre-populate the form fields with default values.

Answer

Embed a UI Page within the widget using an iframe to reuse existing form logic.

Answer

Use client-side GlideRecord to query data directly in the widget's client script.

Question 5

A developer is creating a new Service Portal widget that will display a list of available catalog items. The widget must allow users to filter the list by category and search by name. The developer wants to use AngularJS directives and services provided by Service Portal to implement the filtering and searching. Which two approaches are valid for implementing this functionality? (Choose two.)

Accepted Answer

Use the $http service to call a Scripted REST API that returns filtered catalog items based on query parameters.. Filtering and searching in a Service Portal widget can be implemented either by retrieving data and filtering on the client side using AngularJS filters, or by calling a Scripted REST API that performs the filtering server-side. Both are valid and commonly used patterns, depending on the size of the dataset and performance considerations.

Answer

Use the spModal service to open a modal dialog where users can select a category and enter a search term.

Answer

Use the $rootScope to broadcast an event when the filter changes, and have the widget listen for that event to refresh the list.

Answer

Use the sn_record_watch directive to watch the catalog item table and update the list when changes occur.

Question 6

A developer is creating a Service Portal widget that displays a list of records from a custom table. The widget must allow users to filter the list by a category field and sort by a date field. The developer wants to implement this using widget options so that the behavior can be configured per instance. Which two actions should the developer take? (Choose two.)

Accepted Answer

Define widget options in the widget's option schema to allow configuration of the category filter and sort field.. To make a widget configurable with filter and sort options, the developer should define widget options in the option schema, allowing per-instance configuration. Additionally, the client script can use the $http service to send dynamic filter and sort parameters to the server script, which then queries the database. This combination provides both static configuration via options and dynamic interaction via client-server communication.

Answer

In the server script, use the gs.getParameter() method to retrieve the filter and sort parameters from the URL.

Answer

Use the c.data object in the server script to pass the filter and sort parameters from the client script.

Answer

Add the filter and sort parameters to the widget's HTML template as data attributes.

Question 7

A developer is designing a Service Portal page that includes a widget for displaying a user's approvals. The widget must show a list of approvals and allow the user to approve or reject each item directly from the list. The developer wants to implement this using standard Service Portal widgets and services. Which approach should the developer take?

Accepted Answer

Use the 'Approvals' widget and customize its client controller to include approve/reject buttons that call the ApprovalAction API.. The 'Approvals' widget is a standard Service Portal widget that lists approvals. To allow inline approve/reject actions, the developer can customize the widget's client controller to add buttons that call the ApprovalAction API, which is the standard way to process approval actions. This approach uses existing widgets and services, avoiding the need to build a completely custom solution. Other options either reference non-existent features or require unnecessary complexity.

Answer

Create a custom widget that uses the spModal service to open a confirmation dialog for each approval action.

Answer

Use the 'Approvals' widget from the Service Portal widget library and configure it to allow actions.

Answer

Use the 'Approval List' widget and enable the 'Show Actions' option in its instance configuration.

Question 8

A developer is creating a custom Service Portal widget that displays a list of records from a custom table. The widget must allow users to filter the list by multiple criteria and sort the results. The developer wants to implement this using standard Service Portal features. Which two approaches are valid for enabling filtering and sorting in the widget? (Choose two.)

Accepted Answer

Use the 'spList' directive to render the list, and configure it with a filter and sort options.. The 'spList' directive is the standard Service Portal component for rendering lists with filtering and sorting. It can be configured with filter and sort options directly, and its attributes can be bound to scope variables that users can change, enabling dynamic interaction. The other options either require custom development, use directives for different purposes, or add unnecessary complexity. Thus, the two valid approaches are using spList with configured options and binding its filter/sort attributes to user-modifiable variables.

Answer

Use the 'spModal' service to open a modal with filter options, and then refresh the list based on the selected filters.

Answer

Implement a custom client-side filter using AngularJS and call the server to retrieve filtered data via GlideAjax.

Answer

Use the 'spWidget' directive to embed a list widget that includes filtering and sorting controls.

Question 9

A ServiceNow developer is designing a portal for end users to submit requests. The requirements state that users should be able to track the status of their requests and receive notifications when the status changes. Which combination of ServiceNow features best meets these requirements?

Accepted Answer

Service Portal and Notifications. Service Portal provides the user interface for request submission and tracking, while Notifications (via the Notification and Event Management framework) automatically send email or in-app alerts when a record's status changes. This combination directly fulfills both the tracking and notification requirements without adding unnecessary complexity.

Answer

Service Portal and Access Controls (ACLs)

Answer

Service Portal and Catalog Client Scripts

Answer

Service Portal and UI Policies

Question 10

A developer is troubleshooting a Service Portal widget that loads slowly. The widget uses a server script that queries a large table without any filters. Which design change would most improve performance?

Accepted Answer

Add a filter condition in the GlideRecord query. Adding a filter condition to the GlideRecord query reduces the dataset retrieved from the database, minimizing network transfer and server-side processing time. Without filters, the query returns all rows from a large table, causing excessive load on the instance and slow widget rendering. Filtering at the database level is the most efficient way to improve performance in Service Portal widgets.

Answer

Add client-side caching using $scope

Answer

Load the widget using ng-if instead of ng-show

Answer

Create a custom table with only required fields

Question 11

A developer is designing a custom application with a table that stores sensitive employee data. The requirement is that only managers can view records where they are the manager of the employee. Which two configurations are needed to implement this requirement?

Accepted Answer

Create an ACL with a condition script that checks if the logged-in user is the manager of the record's employee. A record-level ACL with a condition script can check whether the logged-in user matches the manager field on the employee record, enforcing that only managers can view those records. Option A is not correct because a UI Policy only changes how fields appear on the form; it does not restrict record access via lists, web services, or direct database queries and therefore cannot satisfy the requirement that only managers can view records. Option C is not correct because a view only changes form layout and does not enforce security. Option D is not correct because deleting records is destructive and does not implement a view restriction. Option E is not correct because a Client Script is client-side and can be bypassed. Only B is a valid configuration; no second option meets the record-level security requirement.

Answer

Use a UI Policy to set fields to read-only or invisible for non-managers

Answer

Create a new view that excludes sensitive fields

Answer

Create a Business Rule that deletes records if the user is not the manager

Answer

Use a Client Script to hide fields if the user is not the manager

Question 12

A developer created a UI Script and a Client Script as shown. Both scripts set urgency and impact to '1' when priority is '1'. However, when the priority is changed to '1' on an existing record, the urgency and impact fields do not update. What is the most likely cause?

Accepted Answer

The UI Script is not being called because it is not associated with any form or event. A UI Script is a reusable client-side script that must be explicitly called from a Client Script, UI Policy, or form event to execute. In this scenario, the UI Script is not associated with any form or event, so it never runs when the priority field changes. The Client Script alone cannot invoke the UI Script without a direct call, leaving the urgency and impact fields unupdated.

Answer

The priority field is not a choice field, so onChange does not fire

Answer

The Client Script function name is incorrect; it should be 'onChangePriority'

Answer

The g_form API is deprecated and no longer works

Question 13

Drag and drop the steps to create a new Update Set in ServiceNow into the correct order.

Accepted Answer

Navigate to Local Update Sets, then Click New, then Provide name and description, then Set state to In Progress, then Submit. The sequence: navigate to Local Update Sets, create new, provide details, set state to In Progress, and submit.

Answer

Navigate to Local Update Sets, then Click New, then Set state to In Progress, then Provide name and description, then Submit

Answer

Click New, then Navigate to Local Update Sets, then Provide name and description, then Set state to In Progress, then Submit

Answer

Navigate to Local Update Sets, then Click New, then Provide name and description, then Submit, then Set state to In Progress

Question 14

When designing a custom portal page, the developer notices that the page layout breaks on mobile devices. What is the most efficient approach to ensure responsiveness?

Accepted Answer

Implement Bootstrap grid classes. Implementing Bootstrap grid classes is the most efficient approach to ensure responsiveness on a custom portal page. ServiceNow's UI is built on Bootstrap, and using its grid system (e.g., col-md-6, col-xs-12) automatically adjusts layout based on screen size. This avoids the need for custom media queries for each device and ensures consistency with the platform's responsive design.

Answer

Add a media query for each device

Answer

Use fixed pixel widths

Answer

Use a single-column layout

Question 15

A company wants to create a custom homepage for their service portal that displays three different data sources in a single view. The design must ensure that if one data source fails to load, the other two continue to function. Which implementation approach aligns best with this requirement?

Accepted Answer

Use three separate widgets each fetching their own data. Using three separate widgets, each fetching its own data, provides fault isolation: if one widget's data source fails, the other two widgets continue to render independently because they have no shared dependency. This is the standard Service Portal design pattern for resilience, since each widget has its own server script, client script, and data binding. The requirement for independent operation under partial failure is satisfied by this decoupled architecture.

Answer

Use a parent widget that calls three child widgets

Answer

Use a widget that loads data in parallel with error handling

Answer

Use a single widget that fetches all data sequentially