SNOW-CAD Practice Test 33 — 15 Questions

Question 1

The UI Policy has a 'Reverse if false' checkbox unchecked. When will the UI Policy's actions (such as setting a field mandatory) be applied?

Accepted Answer

When any user accesses a record interactively.. A UI Policy with the 'Reverse if false' checkbox unchecked means that its actions (such as making a field mandatory) are applied only when the UI Policy's condition evaluates to true. UI Policies run on interactive form loads (i.e., when a user accesses a record via the browser). Therefore, when any user interacts with the record and the condition is true, the actions are applied. Options B and C are incorrect because UI Policies do not run for web services or background operations. Option D is incorrect because it unnecessarily restricts the policy to admin users; UI Policies apply to all users based on conditions, not roles.

Answer

When any user accesses a record via any method.

Answer

When a user with the 'admin' role accesses a record via web services.

Answer

When a user with the 'admin' role accesses a record interactively (e.g., via the browser).

Question 2

Drag and drop the steps to create a new Scheduled Job in ServiceNow into the correct order.

Accepted Answer

Navigate to Scheduled Jobs, Create new, Set name and type, Define schedule, Write script/select report, Submit. The correct order: navigate to Scheduled Jobs, create new, set name and type, define schedule, write script/select report, and submit.

Answer

Navigate to Scheduled Jobs, Create new, Define schedule, Set name and type, Write script/select report, Submit

Answer

Navigate to Scheduled Jobs, Create new, Set name and type, Write script/select report, Define schedule, Submit

Answer

Create new, Navigate to Scheduled Jobs, Set name and type, Define schedule, Write script/select report, Submit

Question 3

Drag and drop the steps to create a new Catalog Item in ServiceNow into the correct order.

Accepted Answer

Navigate to Maintain Items, then Create New, then Set Category and Details, then Add Variables, then Submit. The correct order: navigate to Maintain Items, create new, set category and details, add variables, and submit.

Answer

Navigate to Maintain Items, then Create New, then Add Variables, then Set Category and Details, then Submit

Answer

Set Category and Details, then Navigate to Maintain Items, then Create New, then Add Variables, then Submit

Answer

Navigate to Maintain Items, then Add Variables, then Create New, then Set Category and Details, then Submit

Question 4

A mid-sized company heavily relies on ServiceNow for incident management. They have a business rule that runs before insert on the Incident table. The rule dynamically sets the assignment group based on the category of the incident and the location of the caller. To determine the correct group, the script performs a GlideRecord query against a custom table called "u_group_mapping", which contains approximately 5000 records mapping category-location pairs to groups. During peak business hours, when many incidents are created simultaneously, the business rule causes significant delays and occasional timeouts, impacting user experience. The development team has been tasked with optimizing this business rule without changing its functionality. The current script structure is roughly:
(function executeRule(current, previous) {
    var gr = new GlideRecord('u_group_mapping');
    gr.addQuery('category', current.category);
    gr.addQuery('location', current.caller_id.location);
    gr.query();
    if (gr.next()) {
        current.assignment_group = gr.assignment_group;
    }
})(current, previous);
The team wants to reduce the database access overhead. Which optimization technique should the developer implement?

Accepted Answer

Create a script include with a static variable to cache the mapping for the duration of the current transaction. Caching the mapping data in a static variable within a script include ensures that the GlideRecord query against the 5000-record custom table is executed only once per transaction, rather than on every incident creation. This drastically reduces database access overhead during peak hours, as subsequent invocations of the business rule within the same transaction reuse the cached results, eliminating redundant queries and preventing timeouts.

Answer

Use GlideAggregate to retrieve the count of matching groups

Answer

Store the mapping in a global script include variable that persists across sessions

Answer

Move the business rule to run after insert so it does not block the insert

Question 5

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 6

A ServiceNow instance has a business rule named 'Update CI Status' that runs on the 'Change Request' table after insert. The rule is intended to update the 'Configuration Item' record's 'Operational Status' to 'Under Maintenance' when a change request is created. The business rule uses the following script:

(function executeRule(current, previous != null)) {
    var gr = new GlideRecord('cmdb_ci');
    gr.get(current.cmdb_ci);
    gr.operational_status = 'Under Maintenance';
    gr.update();
})(current, previous);

After a recent upgrade to the Vancouver release, the business rule stopped working. The change request is created successfully, but the CI's operational status remains unchanged. The system logs show no errors. What is the most likely cause and the correct fix?

A. The business rule is running asynchronously; change it to synchronous.
B. The condition field is empty; add 'gs.action() === 'insert'' as the condition.
C. The 'current.cmdb_ci' field is not populated; check that the field is required on the form.
D. The script uses 'previous' incorrectly; remove 'previous != null' from the function signature.

Accepted Answer

The script uses 'previous' incorrectly; remove 'previous != null' from the function signature.. The business rule contains a syntax error in the function signature. The correct format for a business rule script is `(function executeRule(current, previous))`. The script uses `(function executeRule(current, previous != null))` which is invalid JavaScript and prevents the script from executing. Since the script never runs, no error appears in the logs, and the CI is not updated. Option A is incorrect because changing to synchronous does not fix a syntax error. Option B is incorrect because the condition field being empty means the rule runs, but the script still fails to execute. Option C addresses a possible data issue, but the primary cause is the syntax error; even if `cmdb_ci` is populated, the script would still not run.

Answer

The condition field is empty; add 'gs.action() === 'insert'' as the condition.

Answer

The business rule is running asynchronously; change it to synchronous.

Answer

The 'current.cmdb_ci' field is not populated; check that the field is required on the form.

Question 7

A ServiceNow administrator notices that a business rule designed to update the 'short_description' field on the 'incident' table is not executing when a user changes the field via a custom UI page that uses GlideRecord. The script in the business rule uses current.setValue() and current.update(). What is the most likely cause?

Accepted Answer

The business rule is set to run on the server, but the custom UI page uses client-side GlideRecord which does not trigger server-side business rules.. Client-side GlideRecord (g_form.getReference or direct GlideRecord in a UI page) runs entirely in the browser and does not trigger server-side business rules. Business rules execute only when a record is saved via server-side operations (e.g., form submit, web service, or server-side script). Since the custom UI page uses client-side GlideRecord, the update bypasses the business rule engine entirely.

Answer

The 'short_description' field is read-only on the form.

Answer

The business rule is updating itself recursively and has been disabled.

Answer

The 'short_description' field is not in the business rule's 'Fields to update' list.

Question 8

In ServiceNow Studio, which file type is automatically generated when creating a new application?

Accepted Answer

manifest.xml. ServiceNow Studio automatically generates a manifest.xml file for each new application. This file contains metadata about the application. Option A is incorrect because update.xml files are used for update sets, not automatically generated for applications. Option B is incorrect; readme.md is an optional file that can be added manually. Option D is incorrect; app.xml is not a standard file generated by Studio.

Answer

update.xml

Answer

readme.md

Answer

app.xml

Question 9

What is the effect of this business rule?

Accepted Answer

It sets assignment_group to 'IT Support' every time the caller or short description changes.. The business rule is configured to trigger 'on change' for both the 'caller' and 'short description' fields. When either field changes, the rule sets the 'assignment_group' field to 'IT Support'. This is a typical use of a business rule to automatically assign incidents based on field updates.

Answer

It will cause an error because assignment_group is a reference field.

Answer

It only runs when both caller and short description change.

Answer

It only sets assignment_group when the incident is first created.

Question 10

A company has a Service Portal that includes a custom widget for submitting hardware requests. The widget has a client controller that calls a server script to create a new record in the 'hardware_request' table. Recently, users have reported that when they click the 'Submit' button, the widget sometimes does not show a success message, and the record is not created. The developer reviews the server script, which uses gs.log to log errors, and sees no errors in the logs. The client controller uses $scope.server.get() to call the server. The widget template uses ng-show='data.success' to display a success message. Based on this scenario, what is the most likely cause of the intermittent issue?

Accepted Answer

The client controller does not handle the asynchronous response properly; the success message depends on the promise resolving before the user might navigate away or click again.. The client controller uses $scope.server.get() to make an asynchronous call to the server script. If the user clicks 'Submit' and then navigates away or clicks again before the promise resolves, the success message (ng-show='data.success') may never display because the $scope.data object is not updated in time. The server script logs no errors because it executes correctly, but the client-side asynchronous handling fails to capture the response, leading to the intermittent issue.

Answer

The server script fails due to a mandatory field not being provided, but the error is not logged.

Answer

The server script uses data.success = true; but the client controller does not read it.

Answer

The widget has a Client Script that conflicts with the server script.

Question 11

A developer is working on a catalog client script that references the 'caller_id' field on the 'sc_req_item' table. The caller_id field references the 'sys_user' table. To get the caller's email, which dot-walking syntax is correct?

Accepted Answer

current.caller_id.email. Dot-walking uses the reference field name followed by a dot and the target field. 'caller_id' references the sys_user table, so current.caller_id.email retrieves the caller's email. Option B is wrong because 'caller' is not a field on sc_req_item. Option C is wrong because parentheses are not used in dot-walking. Option D is wrong because you do not need to specify the table name; the reference is automatically followed.

Answer

current.caller.email

Answer

current.caller_id(email)

Answer

current.caller_id.sys_user.email

Question 12

In ServiceNow Studio, which TWO elements can be created directly from the 'Create Application File' wizard? (Choose two.)

Accepted Answer

Table. The correct answers are D (Table) and E (Business Rule). In ServiceNow Studio, the 'Create Application File' wizard allows creation of various application files such as Tables, Business Rules, Client Scripts, etc. Update Sets (C) are not created as application files; they are containers for changes. System Properties (B) are created via the sys_properties module. Flows (A) are created in Flow Designer, not directly from the 'Create Application File' wizard. Therefore, only Tables and Business Rules are among the options that can be created directly via that wizard.

Answer

Flow

Answer

System Property

Answer

Update Set

Question 13

A developer creates a Scheduled Job that runs daily and sends an email notification to a list of users. The job uses a Script Action to query the 'incident' table and sends an email if the count exceeds a threshold. However, the email is not being sent. What is the most likely cause?

Accepted Answer

There is a script error in the Script Action that prevents the email from being sent.. The most likely cause of the email not being sent is a script error in the Script Action. If the script encounters an error (e.g., a syntax error, a null reference, or a failed query), it will stop execution before reaching the email-sending logic, and the email will not be sent. Scheduled Jobs in ServiceNow execute scripts in a headless environment, and any unhandled exception will silently fail without sending the email.

Answer

The email notification is set to 'Inactive'.

Answer

The Scheduled Job is configured to run on a different schedule than expected.

Answer

The user who created the job does not have the 'email_send' role.

Question 14

A developer is debugging a Business Rule that runs on 'before' but not showing expected behavior. In Studio, which tool can show the execution order and triggered scripts?

Accepted Answer

Debugger. The Debugger in Studio allows stepping through scripts and viewing execution order, making it ideal for debugging a Business Rule that runs on 'before' but is not showing expected behavior. Option A is wrong; Scripts Background is for running ad-hoc server-side scripts, not for debugging execution order. Option B is wrong; Update Set tracks changes to configuration items, not script execution. Option D is wrong; Flow Designer is for creating and managing flows, not for debugging script execution order.

Answer

Scripts Background

Answer

Update Set

Answer

Flow Designer

Question 15

A company is using ServiceNow for incident management. They have a business rule on the 'before update' of the incident table that automatically assigns the incident to the first available member of the 'Support' group when the state changes to 'New'. The business rule works correctly when an incident is first created with state 'New', but when an existing incident's state is changed to 'New' from another state, the assignment does not happen. The business rule script checks if current.state.changesTo('New') and then queries the group members. The group has multiple members. Other business rules that run on state changes work fine. What is the most likely cause?

Accepted Answer

A subsequent business rule that runs after this one in the same order is clearing the assignment field.. The business rule runs on 'before update', and if a subsequent business rule in the same execution order clears the assignment field after this rule sets it, the assignment will be lost. This is a common issue when multiple business rules interact on the same table and order of execution matters. The fact that other state-change business rules work fine indicates the logic itself is sound, but a later rule is overriding the assignment.

Answer

The condition current.state.changesTo('New') only works on insert, not on update.

Answer

The business rule should be set to run on 'after' update instead of 'before' to ensure the state is committed.

Answer

The script uses current.assignment_group which is not available on update because the group might be different.