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

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.

Application Access is a feature that allows you to control the access level of other application scopes to your application’s data tables. By selecting the Allow access to this table via web services option, you can enable other application scopes to access your data tables using web services, such as SOAP or REST. However, the user performing the query via web services must have the correct permissions to access the table’s records. The user must have the appropriate roles and access controls to perform the operations on the table, such as create, read, write, or delete.

The other statements are not true when this option is selected. This option does not restrict the ability to delete records via web services, nor does it allow records to be always read. The access to the records depends on the user’s permissions and the web service method. This option also does not restrict access only to SOAP web services, but applies to both SOAP and REST web services. Finally, this option is not the only way to enable web service access to the table’s records. Even when this option is not selected, users with the correct permissions can use web services to access the table’s records, as long as they specify the application scope in the web service request.

https://docs.servicenow.com/bundle/tokyo-platform-security/page/administer/contextual-security/concept/access-control-rules.html

"Use an existing MID Server to connect to a Source Control repository. Linking or importing an application through a MID Server enables access to repositories behind a firewall." https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/c_SourceControlIntegration.html

When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.

The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.

The application name is not required to link a ServiceNow application to a Git repository. You only need to provide the URL, user name, and password of the Git repository, as well as the branch name and the authentication type. The application name is automatically generated based on the scope name of your application. Reference: [Link an application to a Git repository]

In ServiceNow, a Record Producer allows users to create records in a specific table through the Service Catalog. After a user submits a Record Producer, developers may want to redirect the user to a specific page. This can be achieved by setting the producer.redirect property within the Script field of the Record Producer.

For example:

javascript

CopyEdit

producer.redirect = 'incident.do?sys_id=' + current.sys_id;

This script redirects the user to the newly created incident record after submission.

Option A is incorrect because configuring the module that opens the Record Producer does not control the post-submission behavior.

Option C is unnecessary for simple redirection purposes; creating an application property to store the URL adds unnecessary complexity.

Option D is incorrect because using window.redirect in a Business Rule is not appropriate; Business Rules run on the server side and do not have access to the client-side

You must script and configure all required behaviors Provided link has this statement: Extending an existing ServiceNow table means the new table inherits the parent table's columns as well as its business logic.

The following statements apply when extending an existing table:

The parent table’s Access Controls are evaluated when determining access to the new table’s records and fields. This is true because Access Control (ACL) rules are inherited from the parent table to the child table, unless the child table has its own ACL rules that override the parent table’s rules. ACL rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions.

The new table inherits the functionality built into the parent table. This is true because the new table inherits the business logic and the relationships from the parent table, such as Business Rules, Script Includes, UI Actions, UI Policies, and Reference Fields. Business logic and relationships are used to define the behavior and the structure of the data on the ServiceNow platform.

The new table inherits all of the fields from the parent table. This is true because the new table inherits the columns and the attributes from the parent table, such as Field Name, Data Type, Default Value, and Mandatory. Columns and attributes are used to define the properties and the characteristics of the data on the ServiceNow platform.

The following statement does not apply when extending an existing table:

You must script and configure all required behaviors. This is false because you do not have to script and configure all required behaviors when extending an existing table, as some of the behaviors are already inherited from the parent table, as explained above. However, you can script and configure additional or customized behaviors for the new table, such as adding new fields, creating new Business Rules, or modifying existing UI Actions. References: Table Extension, Access Control Rules

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

The correct statement regarding Application Scope is that applications downloaded from 3rd party ServiceNow application developers cannot have naming conflicts. Application Scope is a feature that identifies and isolates applications and their related artifacts from other applications. Each scoped application has a unique namespace identifier that consists of a prefix and a scope name. This prevents cross-application name collisions and ensures that only authorized scripts can access or modify data in a scoped application. References: [Product Documentation | ServiceNow], [How To Create a Scoped App in ServiceNow - YouTube]

Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only

"The sequence is ROLES first, then condition, then script." - Chuck Tomasi says so at this link: https://www.servicenow.com/community/grc-forum/order-of-execution-of-an-acl/m-p/1311962/highlight/true#M6538

Create table from template is not an option for creating a table through the Guided Application Creator. The other options are available for creating a table in the app. Upload spreadsheet allows you to import data from an Excel file and create a table based on the spreadsheet columns and rows. Extend a table allows you to create a child table that inherits fields and behaviors from a parent table. Create table from scratch allows you to define your own fields and data types for a new table. Reference: Create tables

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/concept/gac-tables.html

https://developer.servicenow.com/dev.do#!/learn/courses/tokyo/app_store_learnv2_scripting_tokyo_scripting_in_servicenow/app_store_learnv2_scripting_tokyo_server_side_scripting/app_store_learnv2_scripting_tokyo_script_includes

In the Automated Test Framework (ATF) of ServiceNow, the "Impersonate" test step is used to simulate actions as a specific user. This is crucial for testing functionalities that depend on user roles, permissions, or specific user contexts.

Key Points:

Purpose: The "Impersonate" step allows the test to execute subsequent steps as if performed by the specified user, ensuring that role-based permissions and access controls are accurately tested.

Usage: To add an "Impersonate" step:

Open your test in ATF.

Click on "Add Test Step."

Select "Impersonate User."

Choose the user you want to impersonate for the test.

Considerations: Ensure that the user being impersonated has the necessary roles and permissions for the actions being tested. Additionally, be aware that impersonation affects both server-side and client-side operations during the test.

The fastest way to create and configure a Record Producer is to open the table in the Table records and select the Add to Service Catalog Related Link. This will automatically create a Record Producer with the same fields as the table and add it to the Service Catalog. You can then modify the Record Producer as needed. The other options require more steps and manual configuration. Reference: Create a record producer

In ServiceNow, Business Rules are server-side scripts that execute whenever a record is inserted, updated, deleted, or queried. However, certain actions can be configured without writing any script, using the Business Rule's user interface options.

The primary actions that can be configured without scripting are:

Set field values: This allows administrators to specify new values for fields when the Business Rule conditions are met. This is configured in the "Actions" tab of the Business Rule form, where specific fields and their desired values can be set without any scripting.

Add message: Administrators can configure a message to be displayed to the user when the Business Rule executes. This is done by selecting the "Add message" checkbox and providing the desired message text.

Options C (Set field values and write to the system log) and D (Set field values and generate an event) would require scripting. Writing to the system log involves using server-side APIs like gs.log(), and generating an event requires calling event generation methods—both necessitate scripting.

For more detailed information, refer to the official ServiceNow documentation on Business Rules:

servicenow.com

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