When creating a table, the Create module field allows you to automatically create a module for the table in the application menu. The default behavior of the new module is to display a list of all records from the table. This can be changed later by editing the module properties and specifying a different link type, such as form, URL, or script.
Reference:
Create a table
Module properties

This class allows you to create and manipulate dialog windows on the user interface. You can use this class to display messages, forms, or custom HTML content in a modal window.
GuideAjex: This class allows you to make asynchronous calls to the server and process the response. You can use this class to retrieve data, execute scripts, or perform actions on the server without reloading the page.
GuideForm: This class allows you to access and manipulate the fields and values on a form. You can use this class to get or set field values, show or hide fields, add or remove options, or validate field inputs.
The class GuideRecord is not part of the Client side scoped APIs. GuideRecord is part of the Server side scoped APIs, which are a set of classes and methods that allow you to interact with the database and perform server-side logic on the ServiceNow platform. GuideRecord is a class that represents a record in a table and allows you to query, insert, update, or delete records on the server.
Reference:
[Client side scoped APIs]
[Server side scoped APIs]

The ServiceNow Store is a marketplace for free and paid certified ServiceNow applications and integrations. The ServiceNow Store provides customers with access to Now Certified enterprise workflow apps from partners that complement and extend ServiceNow products and solutions. Customers can browse, try, buy, and deploy apps and integrations that suit their needs and enhance their ServiceNow experience. The ServiceNow Store is not the source for ServiceNow Community created developer content, as that is available on the Developer Portal or the Share site. The ServiceNow Store is not a downloadable content ServiceNow script archive, as that is available on the Script Library or the Script Repository. The ServiceNow Store is not an alternate name for the ServiceNow Developer Share site, as that is a separate site where developers can share applications, code snippets, UI pages, etc. Reference: ServiceNow Store

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/form-administration/concept/c_FormDesign.html The Form Designer is a graphical interface for creating and customizing forms. The following statements are true for the Form Designer:
To add a field to the form layout, drag the field from the Fields tab to the desired destination on the form. This will add the field to the form view without changing the table definition.
To create a new field on a form's table, drag the appropriate data type from the Field Types tab to the form and then configure the new field. This will create a new column on the table and add the field to the form view.
To remove a field from the form layout, hover over the field to enable the Action buttons, and select the Delete (X) button. This will remove the field from the form view but not from the table definition.
The following statement is false for the Form Designer:
To add a section to the form layout, drag it from the Field Types tab to the desired destination on the form. This is incorrect because sections are not available in the Field Types tab. To add a section, click the Add Section button on the toolbar or right-click on the form and select Add Section. Reference: Introduction to App Engine Studio for Developers, ServiceNow Studio Overview, Form Designer

Table Extension in ServiceNow:
Extending a table in ServiceNow means creating a child table based on a parent table. The child table inherits the fields, configurations, and functionality of the parent table.
What is Inherited:
Fields: All fields from the parent table are available in the child table.
Functionality: The child table benefits from any business logic or workflows defined for the parent table.
Access Controls: The child table respects the Access Control rules defined for the parent table unless explicitly overridden.
Why Other Options Are Incorrect:
Option B: This is incorrect because the new table does inherit fields from the parent table.
Option C: This is incorrect because you do not need to script or configure behaviors from scratch; they are inherited.
Option D: This is incorrect because Access Controls are not ignored; they still apply and can be extended or modified for the child table.
Reference:
ServiceNow Developer Documentation on Table Inheritance​.