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

Checkbox tooltip: "Show this module when the user has the specified roles. Otherwise the user must have the roles specified by both the application menu and the module."

The following is true for the Override application menu roles configuration option when configuring a module:

Users with the module role but without access to the application menu access the module. This is true because the Override application menu roles option allows users to bypass the application menu role requirement and access the module directly if they have the module role. For example, if a module has the itil role and the Override application menu roles option enabled, and the application menu has the admin role, then a user who has the itil role but not the admin role can still access the module.

The following are not true for the Override application menu roles configuration option when configuring a module:

Self-Service users can access the module even though they do not have roles. This is false because the Override application menu roles option does not grant access to the module to users who do not have any roles. Self-Service users are users who do not have any roles assigned to them and can only access the Self-Service portal and the Knowledge Base. To access the module, users need to have at least the module role.

Admin is given access to the module even if Access Controls would ordinarily prevent access. This is false because the Override application menu roles option does not override the Access Control (ACL) rules that apply to the module. Access Control rules are used to restrict the access to the data and functionality of the ServiceNow platform based on the user’s roles and conditions. Admin is a role

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

"Restricted caller access [sys_restricted_caller_access] records track cross-scope applications or scripts that request access to an application, application resource, or event in the Now Platform." <<== this is the third sentence down in the following link: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/concept/restricted-caller-access-privilege.html

https://developer.servicenow.com/dev.do#!/reference/api/paris/server_legacy/c_GlideSystemAPI#r_GS-nowNoTZ

https://www.servicenow.com/community/it-service-management-forum/email-notification/m-p/695221

Application Properties let developers expose configurable values (via system properties), so behavior can be changed without altering code.

From Development Handbook 4.0.4, p. 167:

“Use application properties to enable or disable features or change behavior without modifying scripts directly. This promotes modularity and flexibility.”

Creating applications in ServiceNow can help businesses replace outdated, inadequate, custom business applications and processes, extend service delivery and management to all enterprise departments, and extend the value of ServiceNow by leveraging its platform capabilities and integrations1234.

References = 1: What are Application Services? - ServiceNow 2: What is Application Development? - ServiceNow 3: Custom Applications in ServiceNow - The Cloud People 4: Build Custom Apps in ServiceNow – eBook – ServiceNow

Application Access is a feature that allows you to control the access level of other application scopes to your application’s data tables. You can use Application Access to control the following database operations:

Create: This operation allows the user to create new records on the table. You can enable or disable this operation by selecting or clearing the Can create option.

Delete: This operation allows the user to delete existing records on the table. You can enable or disable this operation by selecting or clearing the Can delete option.

Read: This operation allows the user to view the records on the table. You can enable or disable this operation by selecting or clearing the Can read option.

Write: This operation allows the user to modify the records on the table. You can enable or disable this operation by selecting or clearing the Can write option.

The one database operation that cannot be controlled with Application Access is Query. Query is not an operation, but a method of the GlideRecord class that is used to retrieve records from the database on the server-side. Query is not part of the Application Access rules, but it is affected by the Access Controls and the user’s roles.

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

The Form Designer is a graphical interface for creating and customizing forms. The following statements are true for the Form Designer:

To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form. This will add the field to the form view without changing the table definition.

To create a new field on a form’s table, drag the appropriate data type from the Field Types tab to the form and then configure the new field. This will create a new column on the table and add the field to the form view.

To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button. This will remove the field from the form view but not from the table definition.

The following statement is false for the Form Designer:

To add a section to the form layout, drag it from the Field Types tab to the desired destination on the form. This is incorrect because sections are not available in the Field Types tab. To add a section, click the Add Section button on the toolbar or right-click on the form and select Add Section. References: Introduction to App Engine Studio for Developers, ServiceNow Studio Overview, Form Designer

ServiceNow is optimized for building applications that manage structured data in tables and provide consistent user experiences through lists and forms. A core reason to develop on the platform is when the solution naturally fits the record-based model: users create, review, and update records through forms, and those records drive reporting, auditing, and process automation. That makes option C a direct match to how ServiceNow applications are designed and delivered. Another primary platform strength is workflow automation, including Flow Designer, approvals, task orchestration, notifications, and integration actions that coordinate work across teams and systems. If the solution requires repeatable, governed process automation, option D aligns with the platform’s purpose and capabilities. In contrast, “multimedia features” is not a platform driver for application development; while media can be displayed, it is not the typical reason to choose ServiceNow. Similarly, requiring low-level programming libraries is generally a mismatch, since ServiceNow development focuses on platform APIs and configuration patterns rather than direct access to low-level system libraries.

ServiceNow tables commonly use table extension, where a child table inherits fields from a parent table. When a field is defined on a parent table, that field is automatically available on all extended child tables. Because of this inheritance model, deleting a field that originates from the parent table effectively removes it from every table that inherits it, which can appear as “the field was removed from multiple tables.” That behavior is characteristic of an inherited field: it is not independently defined on each child table, so it does not exist as separate copies to delete individually. A reference field is simply a field type that points to another table and would not inherently remove itself from multiple tables when deleted. A custom field is typically created on a specific table; deleting it would usually impact only that table (unless that table is a parent and the field is inherited, which is precisely the inherited-field scenario). “Base system field” is not the right explanation for multi-table removal; the key cause is inheritance through table extension.

g_user is a global object available only in the client-side environment (Client Scripts, UI Policies, UI Actions).

From Development Handbook 4.0.4, p. 204:

“g_user is only available client-side. It returns session-specific info like roles and user ID. Not usable in Business Rules or Script Includes.”

The statement that is true for this script fragment is that the method returns true if the currently logged in user has the x_my_app_user role or the admin role. The g_user.hasRole() method is a client-side method that checks whether the current user has a specified role or set of roles. If no role is specified, it returns true if the user has any role. If one or more roles are specified, it returns true if the user has any one of the specified roles. However, this method always returns true if the user has the admin role, regardless of the role parameter. Therefore, in this case, the method returns true if the user has either the x_my_app_user role or the admin role. Reference: User Object Cheat Sheet, Checking user permissions

The ServiceNow App Repository is a central repository for all scoped applications that are published by all ServiceNow customers. It enables ServiceNow customers to upload and distribute applications between their instances. It also provides entitlements and version control for the applications.

ServiceNow application repository

Application Development Platform – ServiceNow

App Repo - ServiceNow Developer Blog

The "Enforcing" mode ensures all cross-scope access is explicitly approved, logging and requiring manual approval if missing.

From ServiceNow Docs – Cross-Scope Access Controls:

“Enforcing mode logs cross-scope access attempts and blocks access unless explicit permission is granted.”

https://developer.servicenow.com/dev.do#!/reference/api/rome/client

The GlideUser object (g_user) is part of the client-side scripting API that provides information about the current user and the user’s preferences. It can be used in Client Scripts and UI Policies to customize the user interface based on the user’s role, language, time zone, etc. The workflow.scratchpad object is only available in Workflow scripts, which are used to automate processes on the platform. The current and previous objects are only available in server-side scripts, such as Business Rules and Script Includes. The GlideSystem object (gs) is also a server-side object that provides methods for logging, debugging, date and time calculations, etc.

The steps to import new data into ServiceNow from a spreadsheet are: Load Data, Create Transform Map, Run Transform. Load Data is the process of uploading the spreadsheet file and creating an Import Set table that contains the data to be imported. Create Transform Map is the process of defining how the fields from the Import Set table map to the fields of the target table in ServiceNow. Run Transform is the process of executing the Transform Map and copying the data from the Import Set table to the target table. Reference: Import sets, Transform maps