Explanation
A faceted search is a type of component that enables users to filter information easily and intuitively by selecting the options in each facet. A faceted search consists of a faceted search region and a search results region. The faceted search region displays on the left and upper part of the screen and shows possible values and occurrence counts for each facet. The search results region displays on the right side of the screen and shows the data that matches the selected facet values. The search results region can display as either a classic report or a cards report. Three of the statements that are true about faceted search are:
After the end user changes a facet, the results, dependent facets, and occurrence counts refresh immediately. This feature provides instant feedback to the user and allows them to refine their search criteria without reloading the page.
The right side of the page features a Search Results region, which can display as a classic report or a cards report. A classic report displays data in a tabular format with columns and rows. A cards report displays data in a grid of cards with images and text.
The facets are displayed on the left and upper part of the screen. This layout provides a clear separation between the facets and the results and allows users to see and access all the facets without scrolling.

Explanation
Smart Filters is a component that allows end users to filter data by typing keywords in a single search field.
Some of the statements that are true about creating and customizing Smart Filters pages are:
If you create a Smart Filters page based on a table, the filters are auto discovered using the Data Dictionary Cache. You can also manually add or remove filters as needed.
The suggestion chip count is only displayed for filters that support counts, such as LOV-based filter types. For other filter types, such as Input or Range, the count is not displayed. The search results report cannot be displayed as an interactive report or an interactive grid. The supported report types are Classic Report, Cards, Map, or Calendar. Verified References: [Managing Smart Filters - Oracle Help Center],
[Creating Smart Filters Using the Create Page Wizard - Oracle Help Center]

Explanation
A modal dialog is a type of page mode that displays an overlay window within the viewport when a button is pressed. A modal dialog is a stand-alone page that does not interact with the base page where it was launched.
A modal dialog blocks access to the base page until it is closed by the user. A modal dialog can be used for various purposes, such as displaying additional information, confirming an action, or collecting user input.

Explanation
A map is a type of component that enables users to view and manage data based on geographic locations. A map consists of a background map and spatial geometry objects that are sourced from data in a table or from a REST data source. Spatial geometry objects are shapes that represent real-world features on a map, such as points, lines, polygons, or heat maps. Three of the supported spatial geometry objects in Oracle APEX are:
Polygons: A polygon is a closed shape that consists of three or more vertices connected by straight line segments. A polygon can represent an area on a map, such as a country, a state, a city, or a building. A polygon can have different colors, patterns, or borders to indicate different attributes or categories of the data.
Heat map: A heat map is a type of visualization that uses color gradients to show the density or intensity of data values in a geographic area. A heat map can represent the distribution or variation of a numeric variable on a map, such as population, income, crime rate, or temperature.
Points: A point is a zero-dimensional shape that represents a single location on a map. A point can have different symbols, sizes, or colors to indicate different attributes or categories of the data. A point can also have a label or a tooltip to display additional information about the data.

Explanation
The friendly URL syntax
https://example.com:5500/ords/r/mycompany/hr-app/updateemployees?session=13766599855150 has the following components:
session=13766599855150 is the session ID. A new ID is generated for each session. This parameter identifies which session is associated with the request.
hr-app is the application alias. This parameter identifies which application is being requested. An application alias is a user-friendly name that can be used instead of an application ID.
mycompany is the path-prefix which is by default the workspace name. This parameter identifies which workspace is being requested. A path-prefix is a URL segment that can be used instead of a workspace ID.
updateemployees is the page alias. This parameter identifies which page is being requested. A page alias is a user-friendly name that can be used instead of a page number.
The other option is incorrect because:
update-employees is not the PL/SQL procedure to update the employee details. It is the page alias that identifies which page is being requested.
Verified References: [About Friendly URLs] [Understanding URL Syntax]