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

In ServiceNow, extending a table means creating a new table (child class) that inherits properties from an existing table (parent class). This inheritance includes fields, business logic, and other configurations, allowing for efficient reuse and customization.
Key Points:
* Field Inheritance: The child table inherits all fields from the parent table. For example, if you extend the Task table, your new table will include fields like "short_description" and "priority."
* Business Logic Inheritance: The child table also inherits business rules, client scripts, and other logic defined on the parent table, ensuring consistent behavior across related tables.
* Access Controls: Access controls are not ignored; instead, the child table inherits the parent table's access controls. However, you can define additional access controls specific to the child table as needed.
* Customization: While the child table inherits many properties, you can add new fields, scripts, and behaviors to tailor it to specific requirements without affecting the parent table.
Reference: For more detailed information, please refer to the official ServiceNow documentation on Table Extension and Classes.

In ServiceNow, UI Actions are elements such as buttons, links, and context menu items that allow users to perform actions on records or lists. The three valid UI Action types are:
1. List Banner Button (Option A)
* Description: A button that appears in the list view header, allowing users to trigger an action affecting multiple records at once.
* Example: A "Bulk Approve" button that processes selected records.
2. Form Button (Option B)
* Description: A button that appears on a form, allowing users to trigger actions related to the current record.
* Example: A "Submit for Approval" button on an incident form.
3. Record Navigation Button (Option D)
* Description: A button that helps users navigate between related records.
* Example: A "Go to Parent Record" button that redirects users to a linked record.
Incorrect Options:
* Form Choice (Option C):
* Not a UI Action type. Choices are typically used in choice fields (dropdowns) rather than UI actions.
* List Choice (Option E):
* Not a valid UI Action type. Similar to "Form Choice," it pertains to field options rather than UI elements.
* Workflow Action (Option F):
* Workflows are process automation tools, not UI Actions. They are not directly related to buttons or links that users interact with.
Reference:For more details, see the official ServiceNow documentation on UI Actions.