The statement that is not true for Modules is that every Module must be associated with a table. A Module is the functionality within an Application Menu that opens a content page in the content frame or a separate tab or window. A Module can be associated with a table, a list, a form, a report, a script, or any other type of page. For example, the Open Module under the Incident Application Menu opens a list of incident records from the Incident table, while the Overview Module under the Performance Analytics Application Menu opens a dashboard page with various charts and widgets. The other statements are true for Modules. Access to Modules is controlled with roles, as each Module can have one or more roles specified in its definition that determine who can see and access it. Modules open content pages, as they are links to different types of pages that provide information and functionality to users. Every Module must be part of an Application Menu, as they are the second-level navigation options for Applications. Reference: Modules

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.
References:
[Workflow overview]
[Workflow context]

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

In ServiceNow, Access Controls (ACLs) are used to manage permissions for various database operations on tables and their records. The primary operations that can be controlled include:
* Create:
* Description: Permission to insert new records into a table.
* Control: ACLs can be defined to allow or deny users the ability to create records based on roles, conditions, or scripts.
* Update:
* Description: Permission to modify existing records in a table.
* Control: ACLs can restrict who can update records, ensuring that only authorized users can make changes.
Other Operations:
* Read: Controls the ability to view records in a table.
* Delete: Manages the permission to remove records from a table.
Incorrect Options:
* Execute: Not a standard database operation controlled by ACLs in ServiceNow.
* Query: While querying is part of the read operation, ACLs specifically control the read access rather than the query process itself.