Understanding Application Scope and Picker:
The Application Picker in ServiceNow allows developers to switch between different applications (scopes).
When you select an application from the Application Picker, the Application Scope is set to that application, enabling you to develop or configure within that scope.
Why Other Options Are Incorrect:
Option A: The Global application does appear in the Application Picker.
Option B: Selecting Global does not set the scope to Incident; it sets the scope to the Global application, which is not restricted by scoped boundaries.
Option D: Selecting an application does indeed set the Application Scope.
Reference:
ServiceNow Developer Documentation on Application Scope​.

A UI Action is a button, link, or choice that can be clicked by a user to perform an action, such as submitting a form or running a script. The following are UI Action types:
List choice. This is a UI Action that appears as a choice list on a list of records. It can be used to perform an action on multiple records at once, such as deleting or updating them.
Form button. This is a UI Action that appears as a button on a form. It can be used to perform an action on the current record, such as saving or approving it.
List banner button. This is a UI Action that appears as a button on the banner of a list of records. It can be used to perform an action on the entire list, such as exporting or printing it.
The following is not a UI Action type:
Form choice. This is not a UI Action type, but a field type. A form choice is a field that displays a choice list on a form. It can be used to select a value from a predefined set of options, such as priority or state. Reference: UI Actions, Field Types

https://developer.servicenow.com/dev.do#!/learn/learning-plans/quebec/servicenow_administrator/app_store_learnv2_automatingapps_quebec_scheduled_script_execution_scripts The objects that you can use in a Scheduled Script Execution (Scheduled Job) script are GlideSystem and GlideRecord. GlideSystem provides methods for performing system operations, such as logging, running background scripts, or getting system information. GlideRecord provides methods for working with records in the database, such as querying, updating, inserting, or deleting records. The current object is not available in Scheduled Script Execution scripts, as it refers to the current record on a form or list. The GlideUser object is also not available, as it refers to the current user session. Reference: Scheduled Script Execution, GlideSystem, GlideRecord

In ServiceNow, when a new field is added to an existing table, it is not automatically included in any existing List views. List views are predefined configurations that determine which fields are displayed when viewing records in a list format. To display the new field in a List view, you must manually modify the List layout to include the field.
Steps to Add a New Field to a List View:
Navigate to the List Layout Configuration:
Go to the table's list view.
Right-click on the header row (where the column titles are displayed).
Select "Configure" and then "List Layout."
Add the New Field:
In the List Layout configuration, you'll see two columns: "Available" and "Selected." Locate your new field in the "Available" column.
Use the arrow buttons to move the new field to the "Selected" column, placing it in the desired order.
Save the Configuration:
Click "Save" or "OK" to apply the changes.
The new field will now appear in the List view as configured.

In ServiceNow, when a table is extended from a parent table, it inherits all fields from the parent. These inherited fields are integral to the structure of the child table and maintain the relationship between the parent and child tables. As a result, inherited fields cannot be deleted from the child table.
Key Points:
* Inheritance Structure: The child table's structure is designed to include all fields from the parent table to preserve data integrity and ensure consistent behavior across the hierarchy.
* System Constraints: ServiceNow does not provide an option to remove inherited fields from the child table. Attempting to delete such fields would disrupt the inheritance model and potentially cause system inconsistencies.
* Alternative Approaches: While you cannot delete inherited fields, you can manage their visibility:
* Form Layout: Adjust the form layout to hide inherited fields that are not relevant to users interacting with the child table.
* Access Controls: Implement access controls to restrict visibility or edit permissions for specific fields based on user roles.