SNOW-CAD Core Application Development — 20 Questions

Question 1

A developer needs to create a new application scope. Which of the following is a best practice when defining the scope?

Accepted Answer

Set the application's access level to 'Protected' to prevent other applications from modifying its records.. When defining a new application scope, setting the application's access level to 'Protected' is considered a best practice. This restricts access to the application's resources, preventing other applications from modifying its records. The scope name should be unique and not changed after creation. Using the global scope (B) should be avoided for custom applications, reusing an existing scope name (C) is not allowed, and changing the scope name after creation (D) can cause configuration issues.

Answer

Use the global scope to avoid access restrictions.

Answer

Use a scope name that is already in use to leverage existing configurations.

Answer

Create the scope and later change the name if needed.

Question 2

A developer wants to send an email notification when a new incident is created. Which component should be configured to trigger the notification?

Accepted Answer

Create a Notification record with the condition 'New' and 'Action: record inserted'.. In ServiceNow, the native Notification mechanism is specifically designed to send emails based on conditions like 'New' and 'Action: record inserted'. When a new incident is created, the system evaluates the notification's condition; if it matches, the notification triggers automatically without requiring custom scripting or flow design. This is the standard, out-of-box approach for email alerts on record creation.

Answer

Use Flow Designer to create a flow that sends an email.

Answer

Write a Business Rule that calls the email utility.

Answer

Create an ACL with email action.

Question 3

An application has a custom table 'u_project' with a field 'u_status' (choice list: Not Started, In Progress, Completed). The developer wants to prevent any update to the record if the status is 'Completed'. Which approach should be used?

Accepted Answer

Create a Business Rule with condition 'current.u_status.changesTo("Completed")' and set 'current.setAbortAction(true)' in the script.. A Business Rule with the condition `current.u_status == 'Completed'` (note: the option text mentions `changesTo('Completed')`, but the intended correct condition is equality check) and `current.setAbortAction(true)` aborts any update attempt server-side. This ensures data integrity as the restriction is enforced at the database level, regardless of how the update is initiated. Client-side options (B and D) can be bypassed, and a Database View (A) does not prevent updates to the underlying table.

Answer

Create a Database View that filters out Completed records.

Answer

Create a Client Script that sets the field to read-only when status is Completed.

Answer

Create a UI Policy to disable the entire form when status is Completed.

Question 4

A developer notices that a scheduled job runs but does not execute the script. The job is set to run every hour. The script uses the 'gs.log' function to write messages. The log shows no output. What is the most likely cause?

Accepted Answer

The job condition is set to 'false' so it never triggers.. In ServiceNow, a scheduled job runs when the scheduler triggers it, but the action script only executes if the condition script evaluates to true. If the condition is set to 'false' (e.g., the condition script returns false), the job will appear in the job history as having run, but the action script will not execute, resulting in no 'gs.log' output. Option C is incorrect because an inactive job does not run at all—it will not appear in the job history as having run.

Answer

The job's condition script has a syntax error.

Answer

The 'sys_updated_on' field is not being updated.

Answer

The job is set to 'Inactive'.

Question 5

Which TWO of the following are valid ways to create a Business Rule? (Choose two.)

Accepted Answer

Navigate to 'System Definition > Business Rules' and click 'New'.. Option B is correct because navigating to 'System Definition > Business Rules' and clicking 'New' is the standard, documented path in ServiceNow to open a new Business Rule record form. Option C is also correct because the Business Rules module itself provides a 'New' button that creates a Business Rule record directly from the list view. Option A is not a valid method since right-clicking the Business Rules list does not offer a 'New' context-menu action for creating records. Option D is invalid because 'business_rule.do' is not a navigator filter shortcut and would not create a Business Rule. Option E is incorrect because Client Scripts and Business Rules are distinct script types, and ServiceNow does not provide a convert-to-Business-Rule feature.

Answer

From the Business Rules list, right-click and select 'New'.

Answer

Type 'business_rule.do' in the navigator filter.

Answer

Create a Client Script and convert it to a Business Rule.

Question 6

The Business Rule above runs on the 'incident' table. It is set to run 'before' update. What is the most likely issue with this script?

Accepted Answer

The script will cause a recursive loop because it updates incident records within a Business Rule that runs on the same table.. Updating the same table (incident) within a 'before update' Business Rule that runs on that table creates a recursive loop. Each time the script calls gr.update() on an incident record, it triggers the same Business Rule again, leading to infinite recursion until the system enforces a governor limit or stack overflow. ServiceNow detects and prevents such loops by throwing an error, but the design is fundamentally flawed.

Answer

The script should use 'current' instead of 'gr' to update records.

Answer

The script has a syntax error: missing semicolon after the while loop.

Answer

The script does not commit the changes because it uses 'gr.update()' instead of 'current.update()'.

Question 7

The ACL above is on the 'incident' table. A user with role 'itil' tries to update an incident record. What will happen?

Accepted Answer

The user will be denied because the condition fails.. The ACL (Access Control Rule) on the 'incident' table has a condition that must evaluate to true for the user to be granted access. In this case, the condition fails for a user with role 'itil' attempting to update the record, so the script does not set answer = true, resulting in a denial of the operation. Option D is correct because the condition failing means the ACL denies the write operation.

Answer

The user will be prompted for credentials.

Answer

The user will be allowed because the condition is ignored for write operations.

Answer

The user will be allowed because the script sets answer = true.

Question 8

A company has implemented a custom application for tracking employee training. The application uses a custom table 'u_training' with fields: u_employee (reference to sys_user), u_course (string), u_completion_date (date), and u_status (choice: Not Started, In Progress, Completed). The application has a Business Rule that runs after insert and after update. The rule should send an email notification to the employee when the status changes to 'Completed'. However, the email is not being sent. The developer has verified that the notification record exists and is active. The Business Rule script uses the 'gs.eventQueue' method to trigger a custom event. The event is registered and the notification is configured to be triggered by that event. What is the most likely cause of the issue?

Accepted Answer

The Business Rule does not have a condition to check if the status changed to 'Completed'.. The Business Rule lacks a condition to verify that the status field actually changed to 'Completed'. Without a condition like `current.u_status.changesTo('Completed')`, the rule fires on every insert and update, calling `gs.eventQueue` even when the status hasn't changed. This means the event is triggered unnecessarily, but more critically, the notification may not fire because the event is not scoped to the specific state transition. The developer verified the notification record is active, so the missing condition is the most likely root cause.

Answer

The event name is misspelled in the gs.eventQueue call.

Answer

The notification is set to 'Inactive'.

Answer

The employee's email address is not set in sys_user.

Question 9

A ServiceNow instance has a custom application for managing IT assets. The application uses a custom table 'u_asset' with fields: u_asset_tag (string), u_model (string), u_assignee (reference to sys_user), u_status (choice: In Use, In Stock, Retired). The application requires that when an asset is retired, the assignee field must be cleared. The developer created a Business Rule on the 'u_asset' table that runs before update. The script checks if the status changes to 'Retired' and sets the assignee to empty. However, the assignee is not being cleared when the status is changed to 'Retired'. The Business Rule is active and runs before update. What is the most likely cause?

Accepted Answer

The script sets the field using 'current.u_assignee = null;' instead of 'current.setValue("u_assignee", "");'.. In ServiceNow Business Rules, setting a field to null using direct assignment (e.g., current.u_assignee = null) does not trigger the platform's update logic; the change is not persisted to the database. The correct method is to use current.setValue('u_assignee', '') which properly marks the field for update and clears the reference.

Answer

The Business Rule is set to run after the record is saved, so changes are overwritten.

Answer

The condition 'current.u_status.changesTo("Retired")' is incorrect.

Answer

The Business Rule runs after update instead of before update.

Question 10

Match each ServiceNow access control rule (ACL) type to its function.

Accepted Answer

Read ACL: Grants permission to view records.. ServiceNow ACL types define the operation being restricted. Read, Write, Create, Delete, and Execute are common. Correctly pair each ACL with its function: Read for viewing, Write for modifying, Create for adding, Delete for removing, Execute for running scripts. Common confusions involve swapping Delete and Execute.

Answer

Delete ACL: Grants permission to run server-side scripts.

Answer

Execute ACL: Grants permission to remove records.

Question 11

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 12

Which TWO statements about update sets are correct? (Choose two.)

Accepted Answer

Update sets must be explicitly exported and then imported into the target instance.. Option B is correct because update sets are not automatically transferred between instances; an administrator must explicitly export the update set (typically as an XML file) from the source instance and then import/retrieve it into the target instance before committing it. Option D is correct because system properties (sys_properties records) are customization records that are captured in update sets when modified in the correct scope, allowing those property values to be promoted between instances. Option A is incorrect because ACL condition scripts are stored within the ACL record itself and are captured as part of that single ACL record, not as separate records. Option C is incorrect because update sets only capture changes made in the current application scope and do not capture all changes, particularly out-of-box records that are not customized. Option E is incorrect because update sets are designed to move configuration/customization metadata, not transactional data such as user records, which are moved using other mechanisms like import sets or data replication.

Answer

Update sets capture changes to ACLs, but each condition script is captured as a separate record.

Answer

Update sets capture all changes made to an instance, including out-of-box records.

Answer

Update sets are used to move data, such as user records, between instances.

Question 13

What happens when a user changes the state from '2' to '1' on an incident record?

Accepted Answer

The record is not saved and an error message 'State change is not allowed' is displayed.. In a 'before' business rule, calling `current.setAbortAction(true)` prevents the database operation from completing and displays the error message specified in `gs.addErrorMessage()`. When the state changes from '2' to '1', the script checks for this condition and aborts the save, showing 'State change is not allowed'. This is a standard pattern for enforcing state transition restrictions in ServiceNow.

Answer

Nothing happens because the script does not have a return statement.

Answer

The record is saved without any message because setAbortAction is ignored in 'before' rules.

Answer

The record is saved and a message 'State change is not allowed' is shown.

Question 14

This ACL is configured to control read access on the 'incident' table. Under what condition will a user be allowed to read an incident record?

Accepted Answer

If the user is from the company specified and the incident is assigned to the user's manager.. The ACL condition checks that the user's company matches the company specified in the property, and the incident record's assigned_to field equals the user's manager. This is a common pattern in ServiceNow where read access is granted based on a relationship (manager) rather than direct assignment, ensuring that managers can view incidents assigned to their direct reports.

Answer

If the user is from the company specified, regardless of the assigned_to field.

Answer

If the user is from the company specified in the property and the incident is assigned to the user.

Answer

If the user's manager is from the company specified and the incident is assigned to the user.

Question 15

An application scope includes a Business Rule that runs on the 'before' operation of the Incident table. It attempts to set the 'assignment_group' based on the caller's company. However, the assignment is not being applied. Which is the most likely cause?

Accepted Answer

The field 'assignment_group' is not in the current scope's accessible table columns due to cross-scope privilege. In ServiceNow, cross-scope privilege restrictions prevent a scoped application from accessing or modifying columns in the Incident table that are not explicitly granted via the application's scope. Even though the Business Rule runs on the 'before' operation, if the 'assignment_group' field is not in the application's accessible table columns, the assignment will silently fail. This is a common issue when a scoped application attempts to interact with global table fields without proper cross-scope access.

Answer

The Business Rule is set to 'async' which delays execution

Answer

The script uses 'current.assignment_group = something' without calling setValue

Answer

The Business Rule is set to run on 'display' instead of 'update'

Question 16

An administrator sees that a client script on a catalog item is not firing. The script is defined in the catalog item's 'Variable Editor' as a 'onSubmit' script. Which is the most likely reason?

Accepted Answer

The script is written as a 'Catalog Client Script' but is defined in the 'Variable Editor' of the variable. The scenario describes a script defined in the catalog item's 'Variable Editor' as an 'onSubmit' script, which is a variable-level script. However, the question states the script is not firing. The most likely reason is that the script was written as a 'Catalog Client Script' (a global script type) but was incorrectly placed in the 'Variable Editor' of a variable. Variable-level scripts in the Variable Editor are executed only when that specific variable is present on the form; if the script is actually a Catalog Client Script (which runs on the entire catalog item), it would not execute as expected because it is scoped to the variable, not the item. This mismatch between the intended script type and its location causes the script to fail to fire.

Answer

The script is set to run on 'onLoad', but the page is being cached

Answer

The script is defined on a variable, but the variable is not on the order form

Answer

The script uses 'g_form' but the form is not loaded yet

Question 17

A developer is building a Flow in Flow Designer that needs to update an incident record when a certain event occurs. The flow uses a 'Update Record' action. However, the incident record is not being updated even though the flow runs without errors. What could be the issue?

Accepted Answer

The flow's application scope does not have write access to the Incident table. In ServiceNow, the application scope defines the permissions available to a flow. If the scope does not have write access to the Incident table, the 'Update Record' action may appear to run without throwing an error but the update is not persisted. This can occur if ACLs are configured to silently deny write operations for that scope. Other options like referencing the wrong table would typically log an error.

Answer

The flow trigger is set to 'On Created' but the incident already existed

Answer

The flow is using a 'Lookup Record' instead of 'Update Record'

Answer

The 'Update Record' action is referencing the wrong table

Question 18

A developer needs to create a UI Policy that hides a field when a checkbox is checked. The UI Policy has a condition: 'State is 2'. The field should be hidden when the checkbox is checked and state is 2. What is the correct approach?

Accepted Answer

Set condition to 'state=2' and add a script action that sets the field's visible attribute based on the checkbox value. The UI Policy condition 'State is 2' determines when the policy runs. To hide a field based on a checkbox value, you need a script action that evaluates the checkbox and sets the field's visible property accordingly. This approach allows dynamic control beyond static condition builder logic. The script action runs when the condition is true, and can check the checkbox value to decide visibility.

Answer

Add both conditions in the condition builder: checkbox=true AND state=2

Answer

Set condition to 'state=2' and add a reverse if false action with a condition on the checkbox

Answer

Use a Client Script instead of UI Policy

Question 19

A developer is configuring an approval flow for a catalog item. When a user submits a request, an approval record is created with a single approver. The approver must be the user's manager. Which is the correct way to set the approver?

Accepted Answer

In the catalog item, write an 'Approval script' that sets the approver to the submitted by user's manager using current.approver = current.caller_id.manager. It uses an approval script to dynamically set the approver to the manager of the request's caller. The script `current.approver = current.caller_id.manager` directly assigns the manager field from the user record of the caller, which is the standard way to implement a manager-based approval in ServiceNow. This approach is flexible and avoids hardcoding a specific user or group.

Answer

In the catalog item, set 'Approval type' to 'Single' and select a specific user

Answer

Use an Approval - User rule with condition that the approver is the manager

Answer

In the catalog item, set 'Approval type' to 'Group' and select the manager's group

Question 20

Which THREE are valid actions that can be performed by a Workflow Activity in Legacy Workflow Editor?

Accepted Answer

Run a script. The Legacy Workflow Editor includes a 'Run Script' activity that executes server-side JavaScript (GlideRecord, GlideSystem, etc.) within the workflow context. This allows custom logic such as data manipulation, condition checks, or API calls to be performed as part of the workflow flow.

Answer

Approve a record

Answer

Wait for condition