Explanation
App Builder is the main interface of Oracle APEX that allows developers to create and manage web applications. App Builder provides various features and tools to design, develop, test, debug, deploy, and maintain applications. Some of the tasks that you can perform using App Builder are importing previously exported apps, creating new apps from scratch or from predefined templates or blueprints, editing app properties and attributes, adding pages and regions, creating shared components, running and debugging apps, exporting apps to files or workspaces, etc. You cannot create join queries using drag and drop or generate DDL statements from the Oracle data dictionary using App Builder. Verified References: [Using App Builder
- Oracle Help Center], [App Builder Concepts - Oracle Help Center]

Explanation
You can apply an authorization scheme for the following components in APEX:
A specific control such as a region, item, or button. You can select an authorization scheme from the Authorization Scheme list on the attributes page of the control. This will control the rendering and processing of the control based on the user privileges12.
A page. You can select an authorization scheme from the Authorization Scheme list on the Security page of the page definition. This will control the access to the page based on the user privileges12.
An entire application. You can select an authorization scheme from the Authorization Scheme list on the Security Attributes page of the application definition. This will control the access to the entire application based on the user privileges12.
You cannot apply an authorization scheme for a session, as a session is not a component in APEX. A session is a stateful connection between a browser and the APEX engine that persists across multiple requests and responses3. You can control session security by using session state protection, session expiration, and session isolation4.

Explanation
Search configuration is a shared component that defines the data source to be searched and the way results should be displayed. You can create a search configuration based on a local data source (table or SQL query), an APEX list, a REST enabled SQL service, or a REST data source2. You can use one or more search configurations in a search page, depending on the search type you select. For example, you can use multiple search configurations for a standard search, but only one search configuration for an Oracle TEXT or a list search2.

Explanation
A REST Data Source with ORDS as the REST Data Source Type is based on an AutoREST-enabled table or view on a remote Oracle Database. AutoREST enables you to perform CRUD (Create, Read, Update, Delete) operations on a table or view using standard HTTP methods. When a user updates an employee record in an editable interactive grid that uses this REST Data Source as source, the PUT operation defined in the REST Data Source is utilized to update a record in the EMP table on the remote Oracle Database. The PUT operation sends an HTTP PUT request to the REST endpoint with the primary key value of the record and the updated column values in JSON format. Verified References: Creating REST Data Sources - Oracle Help Center, Oracle REST Data Services (ORDS) : AutoREST - Oracle-Base

Explanation
A stacked master detail is a type of master detail implementation that features two editable interactive grids based on two related tables or views. Users can select a row in the master grid to update the detail grid. Users can also interact with the master or the detail without leaving the page. A stacked master detail is suitable for scenarios where you want to display and edit data from a one-to-many relationship in a single page. You can create a stacked master detail using either the Create Application Wizard or the Create Page Wizard. Verified References: [Managing Master Detail Forms - Oracle Help Center], [Creating a Single Page Master Detail Using the Create Application Wizard - Oracle Help Center]