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.
Reference:
[Form sections]
[Related lists]
[Application menus and modules]
[Form buttons]

The Allow configuration Application Access option determines whether users can configure the application tables, such as adding or modifying fields, views, or indexes. The following is true for a table with the Allow configuration option selected:
Out of scope applications can create Business Rules for the table. This is true because the Allow configuration option grants access to the table configuration to any user who has the admin or personalize_dictionary role, regardless of the application scope. This means that users can create Business Rules, which are server-side scripts that run when a record is displayed, inserted, updated, or deleted, for the table from any application.
The following are not true for a table with the Allow configuration option selected:
Only the in scope application's scripts can create Business Rules for the table. This is false because the Allow configuration option does not restrict the creation of Business Rules to the in scope application, as explained above.
Any user with the application's user role can modify the application's scripts. This is false because the Allow configuration option does not grant access to the application scripts, such as client scripts or script includes, to any user who has the application's user role. To modify the application scripts, users need to have the admin role or the application's admin role.
Out of scope applications can add new tables to the scoped application. This is false because the Allow configuration option does not allow out of scope applications to add new tables to the scoped application. To add new tables to a scoped application, users need to have the admin role or the application's admin role and be in the application scope. References: Application Access, Business Rules

Explanation/Reference: https://docs.servicenow.com/bundle/orlando-application-development/page/script/client-scripts/ concept/c_CatalogClientScriptCreation.html

Explanation/Reference: https://docs.servicenow.com/bundle/orlando-platform-user-interface/page/administer/navigation- and-ui/task/t_CreateAModule.html