Free Practice Questions for ServiceNow CAD Exam

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.

The ServiceNow REST API is a web service that allows you to interact with the ServiceNow platform using HTTP requests and responses. The ServiceNow REST API supports the following methods:

POST: This method allows you to create a new record or execute an action on the ServiceNow platform. For example, you can use the POST method to create an incident or run a script.

GET: This method allows you to retrieve information from the ServiceNow platform. For example, you can use the GET method to get the details of a user or a table.

DELETE: This method allows you to delete a record or a resource from the ServiceNow platform. For example, you can use the DELETE method to delete an attachment or a workflow context.

PUT: This method allows you to update a record or a resource on the ServiceNow platform. For example, you can use the PUT method to update the state of a task or the value of a system property.

PATCH: This method allows you to update a record or a resource on the ServiceNow platform by sending only the changes. For example, you can use the PATCH method to update the short description of an incident or the order of a module.

The method COPY is not part of the ServiceNow REST API. There is no COPY method in the HTTP protocol. To copy a record or a resource on the ServiceNow platform, you need to use the POST method with the clone action.

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.”

When a ServiceNow instance requests information from a web service, ServiceNow is the web service consumer. A web service consumer is an application that sends requests to a web service provider and receives responses from it. A web service provider is an application that exposes its functionality as web services. A web service publisher is a person or organization that publishes web services for others to use. A web service specialist is a person who has expertise in developing or using web services. Reference: Web services

" Schema map: Provides a graphical representation of the relationships between tables. "

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

" You must first select read access to grant any other API record operation. " https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/reference/r_TableApplicationAccessFields.html

The Application Access configuration fields control the access level for an application and its tables. The following Application Access configuration fields are not available if the Can read configuration field is not selected:

Can create. This field determines whether users can create records on the application tables.

Can update. This field determines whether users can update records on the application tables.

Can delete. This field determines whether users can delete records on the application tables.

These fields are not available because they depend on the Can read field, which determines whether users can view records on the application tables. If users cannot read records, they cannot create, update, or delete them either.

The following Application Access configuration fields are available regardless of the Can read configuration field:

All access to this table via web services. This field determines whether users can access the application tables using web services, such as REST or SOAP.

Allow configuration. This field determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. References: Application Access, Certified Application Developer (CAD) Learning Path

In ServiceNow, GlideForm is the client-side API used to interact with and manipulate a record form, including reading and writing field values, controlling visibility/mandatory/read-only behavior, and displaying messages to the user. The platform exposes GlideForm methods through a single global client-side object named g_form. ServiceNow documentation explicitly states that there is no constructor for the GlideForm class and that developers access GlideForm methods using the g_form global object available in client-side contexts such as Client Scripts and UI Policies. This makes g_form the correct and standard way to call GlideForm functions (for example, g_form.getValue(), g_form.setValue(), g_form.setDisplay(), etc.). The other options listed are not the documented GlideForm global object for standard client scripting in ServiceNow.

Global applications can use Automated Test Framework and Flow Designer features, but not Source Control and Delegated Development features. Source Control and Delegated Development features are only available to scoped applications . References: [Global vs Scoped Applications], [Delegated Development]

When a new application table is created and the option to create a module is used, ServiceNow creates a list module for that table in the application menu. The default module name is based on the plural form of the application or table label, so users see a natural list-style module name in the Application Navigator. The “U_” or “X_” style prefixes relate to technical table names and scoped naming, not to the user-facing module title. The same name as the application is normally used for the application menu, not the list module. This is why option B is the correct CAD answer.

================

Creating an Application Properties page in ServiceNow provides a centralized location where developers or administrators can configure settings that influence the behavior of an application. This approach offers several benefits:

Dynamic Configuration: By exposing certain parameters through an Application Properties page, administrators can adjust the application ' s behavior in response to changing requirements or environments without altering the underlying code or application artifacts.

Simplified Maintenance: Having a dedicated properties page reduces the need for direct modifications to scripts or configurations, thereby minimizing the risk of introducing errors. It also streamlines the process of updating settings, as changes can be made through the user interface.

Enhanced Flexibility: Developers can design applications with configurable options, allowing for greater adaptability across different