CAD Certified Application Developer - ServiceNow Questions and Answers

The elements of an Access Control are evaluated in the following order: Conditions, Roles, Script. The Conditions are a set of criteria that must be met for the Access Control to apply. The Roles are a list of user roles that are required to access the object. The Script is an optional script that can further restrict or allow access based on custom logic. If any of these elements return false, the Access Control denies access and stops evaluating the remaining elements. Reference: Access control rules

"There are two possible ways to respond to events:

- Email Notification

- Script Action" - see this quote in link below:

https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/new_to_servicenow/app_store_learnv2_automatingapps_tokyo_responding_to_events

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]

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 ServiceNow, when importing data from external sources, the data is first loaded into an Import Set table, which acts as a staging area. To move this data into an existing ServiceNow table (known as the target table), a Transform Map is used. A Transform Map is a set of field mappings that define the relationships between fields in the Import Set table and fields in the target table. This mapping ensures that data is accurately transformed and transferred to the correct fields in the target table during the import process. Therefore, the correct answer is C. Transform Map.

The other options are not related to this specific function:

A. Business Service Management Map: This is not a standard term used in the context of data import and transformation in ServiceNow.

B. Data Sources: These define the origin of the data being imported but do not handle the field mapping between Import Set tables and target tables.

D. Schema Map Relationship Builder: This tool visualizes the relationships between tables in the database schema but is not used for mapping fields during data transformation.

For more detailed information, refer to the official ServiceNow documentation on Transform Maps.

there are only two types of UX options: Mobile and Classic. Classic is defined as "manage records via lists and form"

In ServiceNow, a Record Producer is a specific type of catalog item that enables users to create task-based records through a simplified interface.

servicenow.com

To create a module that directs users to a Record Producer UI:

Link Type Selection: Choose "URL (from Arguments:)" as the Link Type. This option allows you to specify a direct URL, enabling the module to open the desired Record Producer interface.

URL Configuration: In the "Arguments" field, input the URL that points directly to the Record Producer. This URL typically follows the format:

/record_producer.do?sys_id=

Replace with the actual sys_id of the Record Producer you intend to open.

By configuring the module this way, users accessing it will be presented with the Record Producer's user-friendly interface, facilitating the creation of new records without navigating through the standard form UI.

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.

 The correct combination of statements is a, b, and d. These are possible reasons to build custom applications on ServiceNow:

To replace outdated, inadequate, custom business applications and processes. Building custom applications on ServiceNow can help digitize and automate manual or legacy processes that are not covered by existing ServiceNow solutions. This can improve efficiency, data quality, user experience, and innovation.

To extend service delivery and management to all enterprise departments. Building custom applications on ServiceNow can help provide consistent and scalable services across different functions and teams in the organization. This can enhance collaboration, visibility, productivity, and customer satisfaction.

To extend the value of ServiceNow. Building custom applications on ServiceNow can help leverage the capabilities and benefits of the Now Platform®, such as low-code development tools, workflow automation engine, AI-powered insights, security operations, etc. This can increase agility, resilience, performance, and value.

The statement c is not a valid reason to build custom applications on ServiceNow:

To allow users full access to all ServiceNow tables, records, and fields. Building custom applications on ServiceNow does not imply granting users full access to all data and objects in ServiceNow. Access control rules still apply to custom applications and their components to ensure security and compliance. Reference: Build Custom Apps in ServiceNow – eBook

A workflow is a tool that allows you to automate processes on the ServiceNow platform. A workflow consists of activities and transitions that define the logic and flow of the process. A workflow context is an instance of a workflow that is generated from a workflow version, executes activities, and follows transitions. A workflow context is associated with a specific record on a table and tracks the state and progress of the workflow. You can view and manage the workflow contexts from the Workflow Contexts module or the Workflow Contexts related list on a record.

The other options are not valid definitions of a workflow context. A checked out workflow is a workflow that is being edited by a user and has not been published yet. The table and conditions for a workflow are the criteria that determine when a workflow should run on a record. The business reason or process for a workflow is the purpose and function of the workflow.

The step that does not belong when creating a Utils Script Include is identifying the table. A Script Include is a server-side script that can contain one or more classes or functions that can be reused by other scripts. It does not depend on a specific table, but can access any table through GlideRecord or other APIs. The other steps are part of creating a Script Include class and its prototype object. References: [ServiceNow Docs - Script Includes], [ServiceNow Docs - GlideRecord API]

https://developer.servicenow.com/dev.do#!/learn/courses/sandiego/app_store_learnv2_learnmore_sandiego_learn_more/app_store_learnv2_learnmore_sandiego_form_and_list_layouts/app_store_learnv2_learnmore_sandiego_what_is_form_designer

The Form Designer is a tool that allows you to create and customize forms on the ServiceNow platform. The Form Designer has four main components:

Form layout: The form layout shows the preview of the form and allows you to drag and drop fields, sections, and related lists onto the form. You can also resize, reorder, and delete the elements on the form layout.

Page header: The page header shows the name of the table and the form that you are editing. You can also access the form properties, save the form, and switch to the form view from the page header.

Field navigator: The field navigator shows the list of available fields for the table and allows you to search, filter, and add fields to the form. You can also create new fields and edit existing fields from the field navigator.

Schema map: The schema map is not part of the Form Designer. The schema map is a separate tool that shows the relationships between tables and fields on the platform. You can access the schema map from the System Definition > Tables module or from the context menu of a table.

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]

One of the uses of the ServiceNow REST API Explorer is to create sample code for sending REST requests to ServiceNow. The REST API Explorer is a tool that allows you to discover and test the ServiceNow REST APIs. You can select an API endpoint, set the HTTP method, parameters, headers, and body, and then execute the request. The REST API Explorer will show you the response status, headers, and body, as well as generate sample code for various languages and frameworks, such as cURL, Java, JavaScript, Node.js, Python, Ruby, and more. References: [Use the REST API Explorer - Product Documentation: Tokyo - ServiceNow], [Introduction to Scripted REST APIs - ServiceNow Developers]

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

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]

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

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.

The Create Branch operation is available from both Studio and the Git Repository. This operation allows you to create a new branch from an existing branch in your Git repository. You can use branches to work on different features or versions of your application without affecting the main branch. Reference: [Create a branch]

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/applications/task/set-RCA-level.html

In ServiceNow, the Application Picker is a user interface element that allows developers to select the active application they are working on. The selected application determines the Application Scope, which defines the boundaries within which application artifacts (like tables, scripts, and UI components) reside and operate.

A. Selecting Global in the Application Picker sets the Application Scope to Incident: This is incorrect. Selecting "Global" sets the scope to the global application, not specifically to the Incident application.

B. Global is a reserved application that does not appear in the Application Picker: This is incorrect. The "Global" application is available in the Application Picker and represents the global scope.

C. Selecting an application from the Application Picker sets the Application Scope: This is correct. Choosing an application from the Application Picker establishes that application's scope as the current context for development and configuration.

D. Selecting an application from the Application Picker does not set the Application Scope: This is incorrect. The Application Picker directly influences the current Application Scope.

For more information, refer to the official ServiceNow documentation on Application Scope.

For a visual demonstration of restricting access to your ServiceNow application, you may find the following video helpful:

Restricting Access to your ServiceNow App

When creating a table in a privately-scoped application, four Access Controls are automatically created for the table. These Access Controls define the permissions for the four basic operations on the table: Create, Delete, Read, and Write. The Create operation allows the user to create new records on the table. The Delete operation allows the user to delete existing records on the table. The Read operation allows the user to view the records on the table. The Write operation allows the user to modify the records on the table. By default, these Access Controls grant access to the admin role and the application scope. You can modify or delete these Access Controls as needed.

The other options are not valid Access Controls for a table. Insert, Query, and Update are not operations, but methods of the GlideRecord class that are used to manipulate records on the server-side. They are not part of the Access Control rules.

Web services are software systems that use standardized protocols and formats, such as XML and HTTP, to exchange data and messages between different applications or systems over the Internet or other networks12. Web services enable interoperability and integration among diverse software components, regardless of their programming languages, platforms, or architectures34.

References = 1: What are Web Services? - GeeksforGeeks 2: Web service - Wikipedia 3: What are Web Services? - Online Tutorials Library 4: What is a Web Service? | Webopedia

Search branch and merge branches are available features in Studio. Search branch allows you to search for a specific branch name or ID in your Git repository. Merge branches allows you to merge changes from one branch to another, resolving any conflicts that may arise. Push to external source control and push to update set are not available features in Studio. Push to external source control is a feature of Source Control Integration, which is a separate application from Studio. Push to update set is a feature of Update Set Previewer, which is also a separate application from Studio. Reference: Studio, Source Control Integration, Update Set Previewer

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

To include specific records from a table (often referred to as seed data) when distributing an application in ServiceNow, developers must add these records to the application as application files. This ensures that when the application is installed on another instance, the specified records are included.

Option C is correct because using the "Create Application Files" feature allows developers to select specific records to include in the application package. This process creates application files for the selected records, ensuring they are installed along with the application on other instances.

Options A, B, and D are incorrect:

A: The activation status of Table A and whether it extends the Task table do not determine whether its records are included during installation.

B: Having an automatic number counter and setting a table property do not control the inclusion of records in the application package.

D: The System Clone > Exclude Tables list pertains to cloning operations and does not affect application installation.

For detailed guidance on including table records in application deployments, refer to the official ServiceNow documentation:

SERVICENOW.COM

The Event Registry is a table that stores the definitions of all the Events that can be triggered or processed by the ServiceNow system1. The Event Registry allows ServiceNow to react when Events are generated by executing actions such as sending notifications, running scripts, or starting workflows2. The Event Registry also provides information about the Event parameters, description, and source3.

References = 1: Event Registry - ServiceNow Docs 2: Event Management - ServiceNow Docs 3: Event Registry form - ServiceNow Docs

https://developer.servicenow.com/dev.do#!/learn/learning-plans/tokyo/new_to_servicenow/app_store_learnv2_automatingapps_tokyo_use_application_properties

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

To allow a module to open a form for new record insertion, the Link type should be set to “Create new record” or similar.

From Platform App Design Docs:

“Modules control navigation behavior via the Link type setting. To insert records, use the 'Create record' or 'New record' link type.”

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

Application Access settings in ServiceNow control which operations are permitted on a table by other applications. The following operations can be restricted:

Query (A) - Valid: Controls whether other applications can read (query) records from the table.

Create (B) - Valid: Determines whether other applications can add new records to the table.

Execute (C) - Incorrect: No such operation exists for Application Access.

Update (D) - Incorrect: "Update" permissions are controlled through Access Control Lists (ACLs), not Application Access settings.

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

Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table. References: [ServiceNow Docs - Table extension], [ServiceNow Community - How to change field label in child table]

There is no "copy" button on the application record (at least I couldn't see one). Also, see here: https://docs.servicenow.com/bundle/sandiego-application-development/page/build/applications/reference/r_ManagingApplications.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.

Scheduled Script Executions (formerly known as Scheduled Jobs) are used to run server-side logic at specific intervals, such as querying or updating records automatically. Option B describes a valid server-side scheduled use case.

From ServiceNow Docs (https://developer.servicenow.com/ ):

“Scheduled Script Executions allow you to define JavaScript logic that runs on a schedule to automate tasks such as checking data integrity, generating reports, or reassigning records.”

Client-side logic like in options A, C, and D must use Client Scripts or UI Policies, not Scheduled Jobs.

In ServiceNow, the Caller Access field is used to define the level of access that external scripts or applications have to a particular script include or application resource. The valid options for the Caller Access field are:

None: No special restrictions are applied; the resource is accessible as defined by other security settings.

Caller Restriction: Limits access to the resource, allowing only specified callers or applications to invoke it.

Caller Tracking: Enables tracking of which callers are accessing the resource, providing an audit trail for monitoring purposes.

Options such as "Accessible from," "Allow Configuration," and "Caller Permission" are not valid selections for the Caller Access field.

For more detailed information, refer to the official ServiceNow documentation on Restricted Caller Access Privileges.

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.

 When configuring a REST Message, the Endpoint is:

The URI of the data to be accessed, queried, or modified. This is the correct answer because the Endpoint is the part of the REST Message that specifies the location and the resource of the REST provider. The Endpoint is composed of the base URL and the resource path, which can include query parameters or variables. For example, the Endpoint for a REST Message that retrieves the weather information for a city from a web service could be https://api.openweathermap.org/data/2.5/weather?q=London.

The following are not correct definitions of the Endpoint when configuring a REST Message:

The commands to the REST script to stop execution. This is not correct because the commands to the REST script to stop execution are not part of the REST Message, but of the Scripted REST API, which is a feature that allows users to create custom REST endpoints on the ServiceNow platform. The commands to the REST script to stop execution are methods of the RESTAPIResponse object, such as setStatusCode, setError, or complete.

Information about the format of the returned data. This is not correct because the information about the format of the returned data is not part of the Endpoint, but of the HTTP headers or the Accept field of the REST Message. The HTTP headers or the Accept field can be used to specify the content type of the response, such as JSON, XML, or HTML.

The response from the provider indicating there is no data to send back. This is not correct because the response from the provider indicating there is no data to send back is not part of the Endpoint, but of the HTTP status code or the response body of the REST Message. The HTTP status code or the response body can be used to indicate the result of the REST request, such as 200 OK, 404 Not Found, or 500 Internal Server Error. References: REST Messages, Scripted REST APIs

"If there are no spreadsheets or existing tables to use for your application, you can create and customize a new table." see this quote in link below:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/app-engine-studio/task/create-table.html

Also see:

https://docs.servicenow.com/bundle/tokyo-application-development/page/build/guided-app-creator/task/gac-create-table-from-scratch.html

Also, no search results if search on "Now Experience Table Creator".

https://docs.servicenow.com/bundle/paris-servicenow-platform/page/administer/flow-designer/concept/spokes.html

A spoke is a scoped application containing Flow Designer content dedicated to a particular application or record type. Flow Designer provides a set of core actions to automate Now Platform® processes. You can add application-specific core actions by activating the associated spoke.

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.

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()]

The Automated Test Framework (ATF) is a tool that allows you to create and run automated tests on the ServiceNow platform. The ATF uses test steps to define the actions and validations for each test. The test step that allows you to create a user with specified roles and groups for the test is the Create a user test step. This test step creates a temporary user record that is deleted at the end of the test. You can specify the user name, password, roles, and groups for the user. You can also use the Impersonate a user test step to switch to the created user and perform actions as that user.

The other options are not valid test steps for creating a user. The Create a role and Create a group test steps do not exist in the ATF. To create a role or a group, you need to use the Create a record test step and specify the sys_user_role or sys_user_group table. The Impersonation test step does not create a user, but switches to an existing user.

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/platform-events/reference/r_ScriptActions.html

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

ServiceNow provides several methods for developers to publish and share applications once they are ready for distribution. The supported methods include:

Publish to an application repository: This method allows developers to publish their applications to a centralized repository, enabling easy distribution and installation across multiple ServiceNow instances. The application repository serves as a hub where applications can be stored and accessed by other instances.

snowunderground.com

Publish to the ServiceNow Store: Developers can submit their applications to the ServiceNow Store, a marketplace where applications are reviewed, certified, and made available to all ServiceNow customers. Publishing to the Store involves a certification process to ensure the application meets ServiceNow's standards.

support.servicenow.com

Publish to an update set: An update set is a container for capturing configuration changes in ServiceNow. Developers can publish applications to an update set, which can then be moved between instances, allowing for the transfer of application configurations and customizations.

servicenow.com

Options A (Publish to a spreadsheet), D (Publish to a local USB device), and F (Publish to a local drive) are not supported methods for publishing applications in ServiceNow. These options do not align with the platform's mechanisms for application distribution and deployment.

https://docs.servicenow.com/bundle/tokyo-application-development/page/script/server-scripting/concept/c_ServerScripting.html

In ServiceNow, Modules are navigation elements that provide access to various parts of the platform, such as forms, lists, reports, or other application components. They are organized within Application Menus to create a structured and intuitive navigation hierarchy.

Key characteristics of Modules:

Part of Application Menus: Every module is contained within an application menu. This organization helps users navigate to different areas of the platform efficiently. For instance, the "Incident" application menu may contain modules like "Create New" or "All Incidents."

Functionality: Modules can open various elements, including forms, lists, reports, or URLs. This flexibility allows modules to direct users to specific records, filtered lists, or external resources.

Association with Tables: While many modules are associated with specific tables (e.g., a module that displays a list of incidents is associated with the "Incident" table), it's not a strict requirement. Some modules may link to external URLs or perform actions not directly tied to a table.

Access Control: Access to modules is controlled through roles. Administrators can define which user roles have visibility and access to specific modules, ensuring that users only see modules relevant to their responsibilities.

For example, a module named "Active Incidents" under the "Incident" application menu might display a list of all active incident records. Access to this module can be restricted to users with the "itil" role, ensuring that only authorized personnel can view active incidents.

A Module in ServiceNow is a navigational element within an Application Menu that directs users to specific records, lists, forms, or reports.

Option A (Correct): Modules always belong to an Application Menu, providing structured navigation.

Option B (Incorrect): Modules can link to pages, reports, and URLs, not just tables.

Option C (Incorrect): Modules can open forms, lists, dashboards, and external URLs.

Option D (Incorrect): Modules can be restricted by roles, limiting visibility and access.

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

The baseline behavior of a table in a privately-scoped application is that all application scopes can read from the table. A privately-scoped application is an application that restricts write access to its tables and resources to scripts within the same scope. However, read access is allowed by default for all scopes, unless the administrator explicitly denies it using an Access Control rule. This allows for data sharing between different applications while maintaining data integrity and security. References: [Product Documentation | ServiceNow], [Advantages of Scoped Applications in ServiceNow]