SNOW-CAD Practice Test 19 — 15 Questions

Question 1

A ServiceNow instance has a custom table 'u_staff' extended from the User table. A business rule on the 'User' table updates the 'Active' field. When updating a user record, the business rule does not fire for records in 'u_staff'. What is the most likely reason?

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

Accepted Answer

Business rules on the User table do not fire on child table records. Business rules on a parent table (User) do not automatically fire on child table records (u_staff) unless the business rule is configured to run on descendant tables. By default, business rules operate only on the table they are defined on. Option A is incorrect because permission is not the issue; the rule simply isn't triggered. Option C is incorrect because even without a specific condition, the rule won't fire on child tables. Option D is incorrect because ordering affects execution order, not whether the rule fires at all.

Answer

The user does not have permission to run business rules on the 'u_staff' table

Answer

The business rule has a condition that only allows running on User table records

Answer

The business rule ordering is set too low and is being skipped

Question 2

Refer to the exhibit. The developer expects a list of incidents in the widget, but the page renders with an error. What is the most likely cause?

Accepted Answer

getRow() is not a valid method on GlideRecord. The error occurs because getRow() is not a valid method on GlideRecord. The correct method to access field values from a GlideRecord object is getValue(). Option A is not the most likely cause because server scripts do not require an explicit return statement; the data structure is implicitly returned. Option C is a logic issue, not a syntax error. Option D is incorrect because the data.items array is correctly initialized with new Array() or [] and then pushed in the loop.

Answer

The server script is missing a return statement

Answer

The query does not filter for active incidents

Answer

The data.items array is not initialized correctly

Question 3

A developer is creating a business rule that updates a field on the incident table whenever the state changes to 'Resolved'. The business rule should only run when the incident is updated via the form, not through web services. Which condition should be used?

Accepted Answer

In the condition script, add '!gs.getUser().isWebService()'.. The condition should check if the update did not originate from a web service. The method 'gs.getUser().isWebService()' returns true if the current user is a web service user.

Answer

Set the business rule to run only on 'Submit'.

Answer

Use the 'Filter Conditions' on the table to exclude web service users.

Answer

Set the 'When to run' to 'Update' and nothing else.

Question 4

A company is redesigning a service catalog item that has multiple variables. Some variables should only appear when a specific value is selected in a previous variable, and some fields must be mandatory based on the selected options. The development team is debating whether to use UI policies or client scripts for this logic. What is the best practice for implementing such dynamic behavior in a ServiceNow catalog item?

Accepted Answer

Use UI policies for visibility and mandatory conditions, and use client scripts only for advanced logic that UI policies cannot handle.. UI policies are declarative and intended for visibility, read-only, and mandatory conditions, making them easier to maintain and debug. Option A is wrong because client scripts should be used only for complex logic that cannot be achieved with UI policies, not as a default approach. Option B is wrong because ACLs control data access, not form behavior. Option D is wrong because workflows are for backend processes, not client-side field behavior.

Answer

Always use client scripts for visibility and mandatory conditions to handle complex scenarios.

Answer

Configure Access Control Lists (ACLs) to restrict field access based on user roles and variable values.

Answer

Use a workflow to control field visibility and mandatory settings based on variable values.

Question 5

A ServiceNow administrator is building a new custom application to track employee training records. The application includes a custom table 'Training Record' with fields such as employee name, training course, completion date, and score. The administrator wants to create a user-friendly form for data entry. The form should display fields in a logical order: first employee details, then training details, then completion information. Additionally, the form should only show the 'score' field if the training type is 'Exam'. Which configuration approach best addresses these requirements?

Accepted Answer

Define multiple form sections to group related fields and use a UI policy to set the 'score' field visible only when training type is 'Exam'.. It uses form sections to logically group fields (employee details, training details, completion information) and a UI policy to conditionally show the score field only when the training type is 'Exam'. This provides a clean, user-friendly, and maintainable solution. Option A is incorrect because relying on client scripts (onLoad and onChange) to hide fields is less maintainable and more complex than using UI policies. Option B is incorrect because creating separate modules for each combination of fields is overly complex and not scalable. Option C is incorrect because instructing users to use filters does not provide a streamlined data entry experience.

Answer

Design a single form view with all fields and use two client scripts (onLoad and onChange) to hide the score field when conditions are not met.

Answer

Create separate modules for each combination of fields (e.g., one for Exam training, one for others) to simplify data entry.

Answer

Create a single form view with all fields and instruct users to use the filter function to find the fields they need.

Question 6

A developer is troubleshooting an integration where an inbound SOAP message fails to insert a record into the 'change_request' table. The SOAP message is well-formed and the user has the 'change_manager' role. The ACL for the 'change_request' table allows write to 'admin' and 'change_manager'. What is the most likely cause?

Accepted Answer

The SOAP message is missing a mandatory field.. The most likely cause is that the SOAP message is missing a mandatory field, causing the insert to fail validation. The SOAP web service processes the request and if a required field is omitted, the insert is rejected.

Answer

The 'change_request' table is locked for data imports.

Answer

The user's role is not recognized when using SOAP web services.

Answer

The SOAP message uses a different namespace.

Question 7

Which TWO of the following are valid ways to create a UI Action?

Accepted Answer

Duplicate an existing UI Action from the list view.. Options A and B are correct. UI Actions can be created by duplicating an existing UI Action from the list view (Option A) or by creating a new UI Action record directly from the UI Actions module (Option B). Option C is wrong because Script Includes are separate server-side scripts and cannot be configured directly as UI Actions (they might be used in UI Action scripts, but not a direct creation method). Option D is wrong because the Form Design interface is used for layout customization, not for creating UI Actions. Option E is wrong because the Business Rules module is for business rules, a different record type.

Answer

Write a Script Include and configure it as a UI Action.

Answer

Create a UI Action from the Form Design interface.

Answer

Create a UI Action from the Business Rules module.

Question 8

Which TWO are best practices for designing forms in ServiceNow to enhance user experience and maintainability?

Accepted Answer

Leverage related lists to display one-to-many relationships on a form.. Options A and D are correct. A: Leveraging related lists is a best practice for displaying one-to-many relationships on a form, enhancing user access to related records. D: Grouping related fields into sections improves form readability and logical organization. Option B is incorrect because always enabling the 'Use Default Form' checkbox is not a universal best practice; it depends on context. Option C is incorrect because using a single form layout for all record types may not suit varying needs and can reduce usability. Option E is incorrect because reference fields are essential for relational data and do not inherently slow down performance.

Answer

Always enable the 'Use Default Form' checkbox to ensure consistency.

Answer

Use a single form layout for all record types to reduce complexity.

Answer

Avoid using reference fields on forms as they slow down performance.

Question 9

A form has a UI Policy that conditionally makes a field mandatory. The UI Policy works on the server side but the mandatory validation is not enforced on the client side before submission. What is the most likely reason?

Accepted Answer

The UI Policy is set to run only on the server and not on the client.. UI Policies that are set to run only on the server will not enforce mandatory validation on the client. For client-side mandatory enforcement, the UI Policy must have the 'Run on client' checkbox checked or the mandatory attribute must be set via a client script. Option A is wrong because ACLs control visibility and access rights, not mandatory field validation. Option C is wrong because the ordering of UI Policies affects execution order, not whether they run on the client. Option D is wrong because while a client script could override the mandatory property, the issue here is that the UI Policy itself is not set to run on the client, not that it is being overridden.

Answer

The field's ACL does not allow the user to see it.

Answer

The form is in a different ordering of UI Policies.

Answer

A client script is overriding the mandatory property.

Question 10

A developer is writing a script to update a large number of records. To avoid hitting the execution time limit, what is the recommended approach?

Accepted Answer

Use GlideRecord with setLimit and a loop to process in batches.. Processing records in batches using setLimit and a loop prevents long-running scripts and allows the system to handle the load efficiently.

Answer

Use a single GlideRecord update with setWorkflow(false).

Answer

Use a scheduled job to run the script asynchronously.

Answer

Use a business rule to trigger the update on save.

Question 11

An organization is planning to import a large dataset into ServiceNow using import sets. According to best practices, which TWO actions should the developer take to optimize performance? (Choose two.)

Accepted Answer

Disable business rules and ACLs during import.. Scheduling imports during off-peak hours reduces load on the system. Disabling business rules and ACLs during import speeds up processing by avoiding unnecessary checks.

Answer

Increase the import set table row limit.

Answer

Enable 'Create multiple' for transform maps.

Answer

Use a single transform map for all records.

Question 12

A developer is customizing a form layout for the 'incident' table. They want to group related fields into titled sections for better usability. Which approach should they use?

Accepted Answer

Add fields to form sections via the Form Layout module. The Form Layout module in ServiceNow allows administrators to group fields into titled sections on a form, which is the standard way to organize related fields. Option A is incorrect because UI Pages are custom pages that can be embedded via HTML fields, but they are not the standard method for grouping fields. Option C is incorrect because catalog client scripts are used for service catalog forms, not standard incident form layout. Option D is incorrect because UI Policies control field visibility and behavior based on conditions, but they do not create titled sections for grouping fields.

Answer

Create a UI Page and embed it in the form via an HTML field

Answer

Use a catalog client script to rearrange fields dynamically

Answer

Use a UI Policy to show/hide groups of fields

Question 13

Which TWO client-side APIs are available in a Service Portal widget to interact with form fields?

Accepted Answer

c.data (to bind data to the template). The correct answers are B and C. In a Service Portal widget, `c.data` is the primary mechanism for data binding between the server and client. `g_form.setValue()` is available when the widget includes a form (e.g., using the Form widget or a custom form). Option A is incorrect because `spUtil.setValue()` does not exist; `spUtil` has methods like `update` and `addInfoMessage`. Option D is wrong because `g_list.setValue()` is for list views, not standard forms. Option E is incorrect because `$scope` is AngularJS's scope but the recommended pattern in Service Portal is to use `c.data` for data binding.

Answer

spUtil.setValue()

Answer

g_list.setValue() (to set a value in a list)

Answer

$scope (to set values in the controller)

Question 14

A developer needs to find the number of open incidents assigned to each assignment group. Which GlideAggregate script correctly groups by assignment group and counts?

Accepted Answer

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.addAggregate('COUNT'); ga.groupBy('assignment_group'); ga.query();. The GlideAggregate API requires addQuery() to filter open incidents, then addAggregate('COUNT') to define the aggregation, then groupBy('assignment_group') to specify the grouping field, and finally query() to execute. Option A is wrong because it uses addAggregate('COUNT', 'assignment_group'), which incorrectly passes the grouping field as a second parameter; the correct method is separate groupBy() call. Option B is wrong because getRowCount() returns the number of rows after query(), not the count per group; also missing addAggregate(). Option C is wrong because it uses get() instead of query() and the order of methods is incorrect; get() is for fetching a single record, not aggregate queries.

Answer

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.addAggregate('COUNT', 'assignment_group'); ga.query();

Answer

var ga = new GlideAggregate('incident'); ga.addQuery('active', true); ga.groupBy('assignment_group'); var count = ga.getRowCount();

Answer

var ga = new GlideAggregate('incident'); ga.get('active', true); ga.groupBy('assignment_group'); ga.addAggregate('COUNT');

Question 15

Which THREE factors contribute to poor UI performance in ServiceNow forms and portals? (Choose three.)

Accepted Answer

Large number of catalog client scripts in a variable set. Correct options B, C, and E. In ServiceNow, poor UI performance can be caused by excessive client scripts (B), multiple client scripts firing on the 'load' event (C), and unindexed GlideRecord queries in UI Macro server scripts (E). Option A is incorrect because simple conditions in UI Policies are lightweight and do not significantly impact performance. Option D is incorrect because CSS custom properties are a modern feature that can actually improve performance by reducing repeated styles.

Answer

Using simple conditions in UI Policies

Answer

Use of CSS custom properties