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.
References:
Application Access
Web service access to scoped applications

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.

In ServiceNow, the GlideSystem (gs) object provides several methods for logging messages in server-side scripts. In a privately-scoped application, the following methods are commonly used:
A . gs.log(): This method logs a message to the system log (syslog table). It is a general-purpose logging method that allows developers to record informational messages.
E . gs.info(): This method logs informational messages to the system log. It is functionally similar to gs.log() but is specifically intended for informational messages.
The other options are not standard methods provided by the GlideSystem object:
B . gs.error(): This method does not exist in the GlideSystem API.
C . gs.debug(): This method does not exist in the GlideSystem API.
D . gs.logError(): This method does not exist in the GlideSystem API.
For more detailed information, refer to the official ServiceNow documentation on the GlideSystem API.

Flow Designer is a no-code platform capability that lets you automate business processes in a single drag-and-drop design environment. Some of the features of Flow Designer are:
Add stages to a flow: You can define the stages of a flow to track its progress and status. Stages can be used to group actions, subflows, and conditions into logical units.
Call a flow from another flow or subflow: You can reuse existing flows or subflows by calling them from another flow or subflow. This allows you to modularize your automation and avoid duplication of logic.
Test a flow using the "Run as" feature: You can test a flow using the "Run as" feature to specify the user context and input parameters for the flow execution. This helps you to verify the functionality and performance of your flow before publishing it.
Reference:
Flow Designer - No-Code Workflows - ServiceNow
Flow Designer - ServiceNow
Flow Designer Data Sheet - ServiceNow