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.
Reference:
[Access Control rules]
Create a table in a scoped application
[GlideRecord methods]

Explanation/Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/ t_LinkAnApplicationToSourceControl.html

Ensuring that users receive email notifications in ServiceNow requires verifying specific attributes on the user record:
* A. The Email field must have a valid value: This is correct. The Email field should contain a valid email address, as notifications are sent to the address specified in this field.
* B. The user must not be locked out: While it's important for user access, being locked out does not directly impact the sending of email notifications.
* C. The First name and Last name fields must have values: These fields are for identification purposes and do not affect email notification delivery.
* D. Active must be true: This is correct. Only active users are eligible to receive email notifications. If a user is marked as inactive, notifications will not be sent to them.
* E. Delegation must be enabled: Delegation pertains to assigning responsibilities to another user and does not influence the receipt of email notifications.
For effective email notification delivery, always ensure that the user's Email field contains a valid address and that the Active field is set to true.

Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/ concept/c_DelegatedDevelopment.html The incorrect statement about Delegated Development in ServiceNow is that administrators can grant non- admin users the ability to develop global applications. Delegated Development allows administrators to grant non-admin users the ability to develop scoped applications, not global applications. Global applications are accessible by all other applications and do not have a namespace prefix. Scoped applications are isolated from other applications and have a unique namespace identifier. Delegated Development provides more granular control over the developer permissions, application resources, and data access. References: [Advantages of Scoped Applications in ServiceNow], [Product Documentation | ServiceNow]