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

Question 1

Refer to the exhibit. What security risk is present in this implementation?

Accepted Answer

The data is not subject to the same ACLs as server-side calls. Using client-side $http calls bypasses the server-side ACL evaluation that occurs when using spUtil or server scripts. Client-side REST API calls still respect ACLs based on the user's session, but they may expose sensitive data that goes through different security checks. However, a more critical risk is that the endpoint might be susceptible to CSRF if not protected. In the context of Service Portal, the recommended approach is to use spUtil.get or a server script to ensure proper data access control. Option D highlights the risk of inconsistent ACL enforcement.

Answer

The request exposes internal API credentials

Answer

The endpoint does not require authentication

Answer

The client exposes the widget to XSS attacks

Question 2

A company needs to allow employees to request a new laptop through a catalog item. The form should only show a 'Configuration' section if the user selects 'Yes' for 'Custom Configuration?'. Which design approach best accomplishes this?

Accepted Answer

Use a UI Policy to show/hide the section based on the field value.. A UI Policy is the correct approach because it is specifically designed to dynamically show/hide form sections, fields, or make them mandatory/read-only based on the value of another field. In ServiceNow, UI Policies run on the client side and can be configured declaratively without writing code, making them ideal for conditional section visibility on catalog items. The condition 'Custom Configuration? = Yes' triggers the UI Policy to show the 'Configuration' section only when that condition is met, and hide it otherwise.

Answer

Use a client script to hide the section when the field changes.

Answer

Use an ACL to restrict access to the section.

Answer

Use a catalog client script to set the visibility.

Question 3

A flow designer wants to send an email notification with a custom logo. They need to ensure the email template references the correct image. What is the best practice?

Accepted Answer

Attach the image to the sys_attachment table and use the sys_id in the template.. The best practice is to attach the image to the sys_attachment table and reference its sys_id in the email template. This ensures the image is stored within the instance, is available to all users, and avoids external dependencies. The email template can then use the attachment sys_id to embed the image via a URL like /sys_attachment.do?sys_id=...

Answer

Reference the image from an external CDN using a URL.

Answer

Upload the image directly into the email template using base64 encoding.

Answer

Store the image in the 'images' table and use the image name.

Question 4

A developer is creating a service portal widget that shows a list of active incidents. The data should be refreshed every 30 seconds. What is the recommended design pattern?

Accepted Answer

Use a widget option to set the refresh rate and a server-side script to fetch data.. Service Portal widgets support a built-in 'refresh' option that can be set to a number of seconds, causing the widget to automatically re-render and re-fetch data via its server-side script. Combining this widget option with a server-side script that queries incidents is the recommended, platform-native pattern, avoiding custom client-side timers or third-party libraries.

Answer

Use a server-side script with a polling model to return data on a timer.

Answer

Use a third-party library for WebSocket connections.

Answer

Use a client-side JavaScript interval to reload the page.

Question 5

A form has a field 'Department' that, when changed, should make 'Manager' mandatory. The current implementation uses a client script that updates the field attribute on change. However, the mandatory behavior only works when the user first loads the form, but not when changing the field. What is the most likely cause?

Accepted Answer

A UI Policy with same condition is overriding the client script.. The script should use a UI Policy instead, as client scripts for such actions require proper event bindings and are less reliable.

Answer

The client script is not triggered because the field change event is not handled.

Answer

The script uses g_form.setMandatory() which only works on initial load, not on change.

Answer

The field is referenced by the wrong name.

Question 6

A company wants to customize the theme of their ServiceNow instance to match corporate branding, including colors and fonts. Which method is the most maintainable and upgrade-safe?

Accepted Answer

Use the 'Application' > 'Global CSS and Theme' module to define overrides.. Using the Global CSS and Theme system allows customizations in a dedicated module that survives upgrades, unlike direct modifications of system CSS.

Answer

Modify the system CSS files directly via the UI.

Answer

Override CSS in a custom stylesheet and include it in the page using a UI Macro.

Answer

Inject custom CSS using a UI Script.

Question 7

A knowledge base article template needs a new custom field for 'Article Version'. The administrator wants to add this field to the template so it appears on all articles using that template. What is the correct approach?

Accepted Answer

Modify the existing template to include the new field.. In ServiceNow, a knowledge base article template defines the set of fields that appear on articles using that template. To add a new custom field to a template, the administrator modifies the existing template record to include the new field, which then makes it available on all articles that use that template. This is the standard, supported approach and does not require re-assigning articles or creating new templates.

Answer

Create a new template with the field and re-assign all articles.

Answer

Use a UI Policy to show the field on articles using that template.

Answer

Add the field globally to the Knowledge base application file.

Question 8

Which TWO conditions can be used as triggers for a UI Policy to set a field as mandatory? (Choose two.)

Accepted Answer

A specific field value changes. In ServiceNow, UI Policies run client-side and can be triggered by two conditions: 'onLoad' (when the form is loaded) and 'onChange' (when a specified field value changes). Option C is correct because a UI Policy with the 'onLoad' trigger executes when the form is loaded, allowing it to set a field as mandatory based on the record's current values. Option B is correct because a UI Policy with the 'onChange' trigger executes when a specific field's value changes, enabling dynamic mandatory settings as the user edits the form. Option A is incorrect because 'record is submitted' is a server-side event handled by Business Rules or Data Policies, not a UI Policy trigger. Option D is incorrect because ACLs control access (read/write/create/delete) and are not UI Policy triggers. Option E is incorrect because user role is not a UI Policy trigger condition; role-based logic would be implemented via conditions or ACLs, not the trigger itself.

Answer

A record is submitted

Answer

An ACL evaluates to false

Answer

The user has a specific role

Question 9

Refer to the exhibit. A UI Policy is configured to run 'On Condition' with the condition 'Urgent is true'. Users report that when they check the 'Urgent' checkbox, the 'Reason' field does not become mandatory. What is the most likely cause?

Accepted Answer

The script uses getValue('urgent') but the field name is 'u_urgent'.. The script uses getValue('urgent') but the actual field name is 'u_urgent' as per the condition (UI Policy condition uses 'Urgent' which maps to 'u_urgent' in the database). The mismatch causes the script to not trigger properly.

Answer

The UI Policy should be set to 'On Load' only.

Answer

The condition should be set to 'Urgent is false'.

Answer

The script should use g_form.setValue instead of setMandatory.

Question 10

Refer to the exhibit. A dashboard filter configuration contains the above JSON. When the dashboard runs, it shows an 'Invalid filter condition' error. What is the issue?

Accepted Answer

The JSON has a trailing comma after the 'operator' line.. The JSON has a trailing comma after the 'operator' value, which is invalid JSON syntax. This causes the parser to fail.

Answer

The condition string is missing a closing parenthesis.

Answer

The operator should be 'OR' instead of 'AND'.

Answer

The assignment group name is misspelled.

Question 11

A ServiceNow developer is building a custom service portal widget that displays a list of open incidents for the current user. The widget includes a button to reassign an incident to a selected group. The developer writes a client controller function that calls $http.post to a scripted REST API endpoint. However, when the button is clicked in production, the console shows 'unexpected token <'. The developer confirms the endpoint does not exist. What is the best course of action?

Accepted Answer

Create a script include with the reassign logic, and call it from the widget server-side script using a client callable action.. The error 'unexpected token <' indicates the client received HTML (likely a 404 page) instead of JSON, because the scripted REST API endpoint does not exist. The best fix is to implement the reassign logic server-side in a Script Include and invoke it from the widget's server script via a client-callable action, avoiding the missing endpoint entirely. This keeps the logic secure and maintainable within the platform.

Answer

Change the button to a direct link to a different page.

Answer

Move the entire reassign logic to a client-side script using GlideRecord via Ajax.

Answer

Use a custom UI macro instead of a widget.

Question 12

A multinational corporation uses a single ServiceNow instance for IT service management. The ServiceNow portal serves thousands of users across multiple departments (HR, Finance, IT, Legal). Each department requires a customized portal experience: specific branding, tailored service catalog, and unique knowledge bases. The current implementation uses a single portal with multiple widgets that conditionally display content based on user group membership. Users have reported slow page loads and inconsistent styling across departments. The ServiceNow administrator must redesign the portal architecture to improve performance and maintainability while accommodating each department's requirements. Which approach should the administrator take?

Accepted Answer

Maintain a single portal but leverage ServiceNow's branding records and theme variants to apply department-specific styling; optimize widgets with client-side caching and lazy loading.. Maintaining a single portal with branding records and theme variants allows department-specific styling without duplicating the entire portal. Optimizing widgets with client-side caching and lazy loading improves performance. This approach balances customization with maintainability and performance, as ServiceNow supports multiple themes and branding within a single portal, and widget optimization reduces load times.

Answer

Create a separate portal for each department, each with its own theme and set of widgets to fully isolate customizations.

Answer

Standardize all departments onto a single, simple portal with no customizations to reduce complexity and improve load times.

Answer

Keep one portal with a single theme and use extensive client scripts to alter styling and content based on the user's department.

Question 13

Which TWO are benefits of using a Service Portal widget over a UI Page?

Accepted Answer

Widgets can be easily reused across multiple portals.. Service Portal widgets are designed as reusable components that can be shared across multiple portals without duplication. Unlike UI Pages, which are page-specific and must be copied or recreated for each portal, widgets can be configured with options and instances, making them modular and maintainable. Option E is correct because Service Portal widgets natively support AngularJS, enabling two-way data binding between the client-side controller and the HTML template, which simplifies dynamic UI updates without manual DOM manipulation.

Answer

Widgets automatically handle user authentication.

Answer

Widgets provide built-in accessibility features.

Answer

Widgets are faster because they use synchronous server calls.

Question 14

A company uses Service Portal for employee self-service. One widget displays a list of open requests from the sc_request table. The widget uses a server script that queries all records without a filter. As the request table grows, users experience slow loading times. The widget configuration allows client-side filtering but not server-side pagination. The developer must improve performance without changing the user experience. What should the developer do?

Accepted Answer

Implement pagination in the server script and modify the widget to load data in chunks.. Implementing server-side pagination reduces the amount of data retrieved from the database in a single query, which directly addresses the performance bottleneck caused by loading all records from the sc_request table. By modifying the server script to return only a subset of records (e.g., 25 per page) and updating the widget to request subsequent pages as the user scrolls or clicks, the developer improves load times without altering the user experience. This approach leverages ServiceNow's GlideRecord query efficiency and avoids the overhead of transferring and rendering large datasets on the client.

Answer

Increase the server timeout value to allow more time for the query to complete.

Answer

Add a client-side filter to the widget to display only a subset of records.

Answer

Use a UI Policy to hide the widget for users with many requests.

Question 15

A developer is building a Service Portal page for a facilities team. The page must display a list of open facility requests from the custom table u_facility_request, and the list must be limited to records the logged-in user opened. The developer wants to reuse an existing out-of-box widget rather than build a custom one. Which approach should the developer take?

Accepted Answer

Add the My Requests widget to the page, then in its instance options set the Table to u_facility_request and the Filter to opened_by=javascript:gs.getUserID().. The My Requests widget is purpose-built for showing a configurable table's records scoped to the logged-in user, and its instance options accept both a table name and a filter. Setting the table to the custom facility request table and the filter to the current user's sys_id satisfies the requirement while reusing an out-of-box widget, avoiding custom development and preserving standard behavior.

Answer

Add the Data Table widget from the Service Portal widget library to the page and set its table to u_facility_request with a filter of opened_by=javascript:gs.getUserID().

Answer

Add the Simple List widget to the page and configure its Table field to u_facility_request, then set the filter to opened_by=javascript:gs.getUserID().

Answer

Add the Form widget to the page and configure it to display u_facility_request records, then set the form's view to a custom view that hides records not opened by the current user.