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.
Reference:
[Form Designer]
[Schema map]

Inbound email matching uses Watermarks and Subject lines (with record numbers like INC0010001) to associate emails with existing records.
From Email Handling Docs:
"ServiceNow uses Watermark IDs and subject lines containing record numbers to find the corresponding task or record when processing inbound email."

Comprehensive and Detailed In-Depth Explanation:
In ServiceNow, the Application Picker is a tool that allows developers to select the active application scope.
When an application is selected from the Application Picker, it sets the Application Scope to that application.
This means that any configurations, scripts, or customizations made will be associated with the selected application's scope. Therefore, the correct answer is D.
The other options are incorrect:
* A. Selecting Global in the Application Picker sets the Application Scope to Incident: Selecting
"Global" sets the scope to the global application, not specifically to Incident.
* B. Global is a reserved application which does not appear in the Application Picker: The Global application does appear in the Application Picker and can be selected.
* C. Selecting an application from the Application Picker does not set the Application Scope:
Selecting an application does set the Application Scope.
For more detailed information, refer to the official ServiceNow documentation on Application Scope.

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

The following roles grant access to source control repository operations such as importing applications from source control, or linking an application to source control:
* source_control. This is a role that allows users to perform basic source control operations, such as importing an application from a source control repository, updating an application from a source control repository, or committing changes to a source control repository.
* admin. This is a role that grants full access to all the features and functions of the ServiceNow platform, including source control operations. Users with this role can also perform advanced source control operations, such as creating or deleting source control repositories, configuring source control properties, or resolving conflicts.
The following roles do not grant access to source control repository operations:
* source_control_admin. This is not a valid role in ServiceNow. There is no separate role for source control administration, as this function is included in the admin role.
* git_admin. This is not a valid role in ServiceNow. Git is a specific type of source control system that ServiceNow supports, but there is no role dedicated to Git administration. References: Source Control, Source Control Roles Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications
/task/ t_LinkAnApplicationToSourceControl.html