CAD ServiceNow Certified Application Developer - ServiceNow Free Practice Exam Questions (2026 Updated)

Recurring checks, like finding task records that are unassigned, are implemented using platform automation that runs on a schedule. ServiceNow provides two common development-aligned places for this type of logic. Scheduled Script Execution is a scheduled job mechanism that runs server-side scripts at defined intervals. Developers use it to query tables (such as Task) and take actions like updating fields, creating follow-up records, or sending notifications when conditions are met. This matches option C. For low-code automation, Flow Designer also supports scheduled triggers, allowing developers to run a flow at specific times or on a repeating schedule to perform checks and actions. This matches option A (Scheduled Flows). Discovery Schedules are specific to the Discovery feature set for scanning infrastructure and are not used for general task management checks. “System Schedules” is not the standard construct where custom recurring business logic is authored for application development; the platform’s scheduled logic is typically implemented through scheduled jobs (including script executions) and scheduled flow triggers.

In ServiceNow, when a new field is added to an existing table, it is not automatically included in any existing List views. List views are predefined configurations that determine which fields are displayed when viewing records in a list format. To display the new field in a List view, you must manually modify the List layout to include the field.

Steps to Add a New Field to a List View:

Navigate to the List Layout Configuration:

Go to the table ' s list view.

Right-click on the header row (where the column titles are displayed).

Select " Configure " and then " List Layout. "

Add the New Field:

In the List Layout configuration, you ' ll see two columns: " Available " and " Selected. "

Locate your new field in the " Available " column.

Use the arrow buttons to move the new field to the " Selected " column, placing it in the desired order.

Save the Configuration:

Click " Save " or " OK " to apply the changes.

The new field will now appear in the List view as configured.

An example of when an application might not use a Scheduled Script Execution (Scheduled Job) is when the application needs to run a client-side script at the same time every day. A Scheduled Script Execution is a server-side script that runs on a specified schedule and performs some action on the server or database. A client-side script runs on the user’s browser and cannot be scheduled by ServiceNow. The other options are examples of when an application might use a Scheduled Script Execution, such as sending email reminders, running a clean up script, or querying the database for unassigned records. Reference: Scheduled Script Execution, Client scripts

https://docs.servicenow.com/bundle/rome-application-development/page/build/applications/concept/c_ScriptProtectionPolicy.html

The following is true for a Script Include with a Protection Policy value of Protected:

The Protection Policy is applied only if the application is downloaded from the ServiceNow App Store. This is true because the Protection Policy is a feature that allows developers to protect their Script Includes from being viewed or modified by other users when they distribute their applications through the ServiceNow App Store. The Protection Policy is only enforced when the application is installed from the App Store, not when it is developed or tested on the instance.

The following are not true for a Script Include with a Protection Policy value of Protected:

Any user with the protected_edit role can see and edit the Script Include. This is false because the protected_edit role is not related to the Protection Policy, but to the Access Control (ACL) rules. The protected_edit role allows users to edit protected fields on a table, such as the script field on the sys_script table, which stores the Business Rules. The Protection Policy does not use roles to control access to the Script Includes, but a cryptographic key that is generated when the application is published to the App Store.

The Protection policy option can only be enabled by a user with the admin role. This is false because the Protection policy option can be enabled by any user who has the application_admin role for the scoped application that contains the Script Include. The application_admin role grants full access to the application development and administration within the scope of the application.

The Protection Policy is applied only if the glide.app.apply_protection system property value is true. This is false because the glide.app.apply_protection system property is not related to the Protection Policy, but to the Application Restricted Caller Access (ARCA) feature. The ARCA feature allows developers to restrict the access to the Script Includes from other applications based on the caller’s scope. The glide.app.apply_protection system property determines whether the ARCA feature is enabled or disabled on the instance. References: Script Includes, Protect Script Includes, Application Restricted Caller Access

From: https://docs.servicenow.com/bundle/paris-application-development/page/script/general-scripting/reference/r_ScriptingAlertInfoAndErrorMsgs.html

g_form.showFieldMsg( " field_name " , " Hello World " , " error " ); Puts " Hello World " in an error message **below the specified field**. g_form.addInfoMessage() or g_form.addErrorMessage() place a blue box message at the top of the screen. Pg 126 of the CAD handbook

The method that prints a message on a blue background to the top of the current form by default is g_form.addInfoMessage(). The g_form object is a global object that provides access to form fields and UI elements on a form. The addInfoMessage() method is a method of the g_form object that displays an informational message next to the form header. The message has a blue background color by default, unless it is overridden by a CSS style. The addInfoMessage() method takes one argument, which is the message text to display. References: [ServiceNow Docs - GlideForm (g_form) API], [ServiceNow Docs - g_form.addInfoMessage()]

A benefit of creating an Application Properties page for each application you develop is that Application Properties allow a developer or admin to make changes to an application’s behavior without modifying application artifacts. Application Properties are system properties that store configuration information for a specific application. They can be used to control various aspects of the application, such as feature flags, default values, thresholds, or URLs. By creating an Application Properties page, you can group and display all the properties related to your application in one place and make them easy to access and update. This way, you can avoid hard-coding static data in your application code and make your application more flexible and maintainable. Reference: Working with System Properties, Organizing your ServiceNow System Properties

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/form-administration/concept/c_FormDesign.html

From the list below, the following is a reason an application might not be a good fit with ServiceNow:

Requires “as-is” use of low-level programming libraries. This is the correct answer because ServiceNow is a high-level platform that abstracts away the low-level details of the underlying infrastructure and technology stack. ServiceNow provides a rich set of APIs, tools, and features that allow users to develop applications without coding or with minimal coding. However, ServiceNow does not support the direct

ServiceNow provides multiple ways to show messages to users in the UI, and the correct method depends on whether the message is meant for the top of the form or next to a specific field. In the GlideForm client API, ServiceNow documents g_form.addInfoMessage(String message) as the method that adds an informational message to the top of the form. This is the standard client-side approach for showing an info banner at the top area of the current form and is commonly used in Client Scripts and UI Policies to inform users about guidance, rules, or results of client-side logic. ServiceNow’s GlideForm documentation specifically names this method and provides examples of its usage via g_form. By contrast, g_form.showFieldMsg() (and similarly named field-message functions) are used to display messages associated with a particular field location, not as a general blue banner at the top of the form. The option g_form.addInfoMsg() is not the documented default method name. Therefore, the correct answer is g_form.addInfoMessage().

Application Access on a table defines cross-scope behavior at the table boundary. To ensure that no other application scope can create records on the application’s data tables, the table must be restricted so that only the owning scope can access it. Setting Accessible from to This application scope only enforces that boundary by preventing other scoped applications from accessing the table, including record creation. This is exactly what the requirement describes: blocking other private scopes from creating records on the table. The “All application scopes” option is the opposite of what you want because it opens cross-scope access, and then trying to selectively block “Can create” still leaves broader exposure and is not aligned with the stated goal. Creating ACLs to block other scopes is also not the correct approach for cross-scope isolation because ACLs primarily control user and role access, while cross-scope access is governed by Application Access and cross-scope rules. Disabling “Allow access to this table via web services” is about API/web service exposure, not about other application scopes creating records through normal platform access.

Enabling “Allow access to this table via web services” allows authenticated users with proper roles to access this table via REST/SOAP APIs.

From Development Handbook 4.0.4, p. 191:

" This setting allows web service access to a table, but still requires that users have appropriate roles and permissions through ACLs. "

Thus, access isn’t automatic — proper access controls still apply.

In ServiceNow, a workflow context refers to a specific instance of a workflow execution. When a workflow is initiated—whether by inserting or updating a record, triggering an event, or through scripts—the system creates a workflow context. This context is derived from a particular version of the workflow and is responsible for executing the defined activities and following the specified transitions within that workflow.

Key points about workflow context:

Instance of Execution: Each time a workflow runs, a new context is created to manage that specific execution instance. This allows multiple instances of the same workflow to operate independently and simultaneously.

Execution of Activities: The context manages the progression through the workflow ' s activities, ensuring that each step is executed in the defined order and under the specified conditions.

Tracking and Management: Workflow contexts enable administrators to monitor the state and progress of workflow executions. They provide visibility into which activities have been completed, which are pending, and any transitions that have occurred.

For example, if a workflow is designed to handle approval processes, each time an approval is initiated, a new workflow context is created to manage that particular approval instance. This context will track the approval ' s progress, manage notifications, and handle any branching logic defined in the workflow.

In ServiceNow, when developing within a privately-scoped application, certain logging methods are recommended for use in server-side scripts to ensure proper logging and debugging. The GlideSystem (gs) object provides several methods for this purpose:

gs.debug():

Description: Logs messages at the " Debug " level.

Usage: gs.debug( ' Debug message here ' );

Purpose: Useful for logging detailed information during development and troubleshooting. These messages are typically only visible when the system ' s logging level is set to " Debug. "

gs.error():

Description: Logs messages at the " Error " level.

Usage: gs.error( ' Error message here ' );

Purpose: Used to log error messages that indicate a problem that might still allow the application to continue running.

gs.warn():

Description: Logs messages at the " Warning " level.

Usage: gs.warn( ' Warning message here ' );

Purpose: Used to log potentially harmful situations that are not necessarily errors but may require attention.

gs.info():

Description: Logs messages at the " Information " level.

Usage: gs.info( ' Information message here ' );

Purpose: Used to log informational messages that highlight the progress of the application at a coarse-grained level.

Deprecated or Unsupported Methods in Scoped Applications:

gs.log():

Description: This method is not supported in scoped applications. It is restricted to the global scope and is not accessible from a private scope. Therefore, it should be avoided in privately-scoped applications.

Definition of a Spoke:A " spoke " is a scoped application or component of an application that contains Flow Designer actions and integrations. Spokes provide reusable functionality and are typically used to extend the capabilities of Flow Designer.

Why It’s Called a Spoke:

Spokes are part of the ServiceNow Flow Designer framework.

They contain predefined actions that are reusable across multiple flows. For example, an " Email Spoke " might include actions for sending emails or managing email configurations.

Why Other Options Are Incorrect:

Option B (Flow): This refers to an individual flow, not the application containing reusable actions.

Option C (Bundle): There is no such term as " Bundle " specific to Flow Designer in ServiceNow.

Option D (Action): While flows contain actions, the scoped application that houses these actions is referred to as a spoke.

ServiceNow Developer Documentation on Flow Designer Spokes​.

Catalog Client Scripts and Catalog UI Policies are the client-side scripts that apply to Record Producers. Catalog Client Scripts allow you to add or modify functionality on a catalog item or record producer form. Catalog UI Policies dynamically change information on a catalog item or record producer form. UI Scripts, UI Actions, Client Scripts, and UI Policies do not apply to Record Producers. Reference: Catalog client scripts, Catalog UI policies

A transform map determines the relationships between fields in an import set table and fields in an existing ServiceNow table. It also specifies how to transform the imported data before mapping it to the target table.

1. What Exactly is an Import Set? - ServiceNow Developers

Import set table - ServiceNow Application Development [Book]