Explanation
A stacked master detail is a form type that displays two editable interactive grids based on two related tables or views on the same page. Users select a row in the master grid to update the detail grid6. In this scenario, the departments names with location on the left is the master grid and the employees details on the right is the detail grid. A cards report is not a form type, but a report type that displays data in cards with an image and text7. A side by side master detail is a form type that displays two editable interactive grids based on two related tables or views side by side on the same page. Users select multiple rows in the master grid to update multiple detail grids6. An interactive report is not a form type, but a report type that allows users to customize the report layout and filter data interactively5.

Explanation
An interactive grid is a customizable report that allows end users to modify the data and layout of the report.
End users can change the report layout by using the Actions menu or by dragging and dropping columns. They can also create private reports that save their personal preferences for the report. These features are available for both editable and noneditable interactive grids. Verified References: Using an Interactive Grid - Oracle Help Center, Example Interactive Grid - Oracle Help Center

Explanation
Collections are temporary tables that store session-specific data in memory. They can be used for various purposes in APEX applications. Some uses of collections are:
You insert, update, and delete collection information using PL/SQL API APEX_COLLECTION. This API provides several procedures and functions to manipulate collections and their members.
Use collections to temporarily capture one or more nonscalar values. For example, you can use collections to store the results of a query, the values of page items, or the selections of a report.
Collections can be accessed, manipulated, or processed during a user's specific session. For example, you can use collections to pass data between pages, perform calculations on collection members, or create reports based on collections.
Collections do not enable you to store rows and columns in the current session into database tables.
Collections are stored in memory and are not persistent across sessions.

Explanation
A button is a component that performs an action when clicked by the user. A button can have different types, styles, icons, and labels. A button can also have different behaviors, such as submitting the page, redirecting to another page or URL, or doing nothing. A button can perform any of the following actions when clicked:
Redirect to a page in the same application: This action redirects the user to another page within the same APEX application. You can specify the target page number and optionally set some attributes, such as clear cache, request, and item values.
Redirect to a page in a different application: This action redirects the user to another page in a different APEX application. You can specify the target application ID and page number and optionally set some attributes, such as clear cache, request, and item values.
Redirect
to a URL: This action redirects the user to a custom URL that you specify. You can use any valid URL format, such as http://, https://, mailto:, or javascript:.
Submit Page: This action submits the current page to the server and performs any validations, computations, processes, or branches that are defined for the page. You can also specify a request value for the button that can be used to conditionally execute some components.
Defined by Dynamic Action: This action does not submit the page or redirect to another page. Instead, the button's behavior is defined by a dynamic action thatis associated with the button. A dynamic action is a declarative way of defining client-side behavior based on user actions or events.