Explanation
You can access the Shared Components page from two places in App Builder: the Page Designer and the Application home page. In Page Designer, you can click on the Shared Components icon at the top of the page to open the Shared Components page in a new tab5. In the Application home page, you can click on the Shared Components link in the center of the page to navigate to the Shared Components page6. Gallery, SQL Workshop, and other pages do not have direct links to the Shared Components page.

Explanation
Commands allow you to execute SQL statements or PL/SQL blocks to create, edit, view, run, and delete database objects. One of the features of SQL Commands is the ability to unload data from the database to a CSV file. You can do this by clicking the Download button after running a query that returns data. Verified References: 34

Explanation
When a table or a SQL query returns many rows, an interactive grid is best displayed to the user with pagination. Pagination enables users to navigate through large data sets by displaying a subset of data at a time3. The two types of pagination available for interactive grids are Page and Scroll3. Page pagination displays a fixed number of rows per page and provides controls to navigate between pages. Scroll pagination displays rows as the user scrolls down the grid and fetches more data as needed

Explanation
d event under the Drag and Drop PL/SQL Code attribute of the Calendar component. This attribute allows you to write PL/SQL code to update the event row in the database after the user drags and drops an event on the calendar. To reference the ID, the new start date, and the new end date of the dragged event, you can use these bind variables: :APEX.PK_VALUE, :APEX.NEW_START_DATE and :APEX.NEW_END_DATE. These variables are automatically populated by APEX when the user performs a drag and drop action on the calendar. For example, you can write something like this:
UPDATE events
SET start_date = :APEX.NEW_START_DATE,
end_date = :APEX.NEW_END_DATE
WHERE id = :APEX.PK_VALUE;

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.