https://docs.servicenow.com/bundle/tokyo-platform-security/page/administer/contextual-security/concept
/access-control-rules.html

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.

When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.
The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.
References:
[Form sections]
[Related lists]
[Application menus and modules]
[Form buttons]

In ServiceNow, tables can extend other tables, inheriting all fields and functionalities from the parent table.
These inherited fields are integral to the structure and behavior of the child table.
* A. No, inherited fields cannot be deleted from a child table: This is correct. Inherited fields are part of the child table's schema due to its extension of the parent table. Removing these fields would disrupt the inherent structure and relationships defined by the table hierarchy.
* B. Yes, but only if they are text fields: This is incorrect. The data type of the field does not permit the deletion of inherited fields.
* C. Yes, select the red X in the left-most column in the table definition: This is incorrect. Inherited fields do not have a delete (red X) option in the table definition, as they are not directly created on the child table.
* D. Yes, but only if there has never been any saved field data: This is incorrect. The presence or absence of data does not affect the ability to delete inherited fields.
To modify the structure of inherited fields, consider the following approaches:
* Field Visibility: Use client scripts or UI policies to hide the inherited fields on forms where they are not needed. This approach maintains data integrity while tailoring the user interface to specific requirements.
* Form Layout Configuration: Adjust the form layout to remove inherited fields from specific views, ensuring they are not displayed to users in contexts where they are irrelevant.
These methods allow customization of the user experience without altering the underlying table schema or violating the inheritance principles established in the data model.