Oracle 1z0-770 Oracle APEX Cloud Developer Professional Exam Practice Test

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.

To highlight certain rows in the interactive report based on a condition, you must choose a condition in Format > Highlight. This option allows you to apply a conditional formatting rule to the report, which changes the appearance of the rows that match the condition. You can specify the condition type, expression, column, operator, and value. You can also choose the highlighting style, such as background color, text color, or icon.

The other options are incorrect because:

• Provide a conditional SQL query: This option will not highlight certain rows in the interactive report based on a condition. It will filter the data in the report by applying a WHERE clause to the SQL query that defines the report source.
• Edit the rows in the report and select a color: This option will not highlight certain rows in the interactive report based on a condition. It will modify the data in the report by using inline editing or modal dialog editing. You cannot select a color for the rows in this option.
• Rows cannot be highlighted in an Interactive report: This option is false. Rows can be highlighted in an Interactive Report by using the Format > Highlight option.

Verified References: [Customizing Interactive Reports] [Highlighting Rows Based on Conditions]

The Column Heading menu of an Interactive Report provides various options to customize the report based on the selected column. The options include:

• Control Break: This option allows you to create a control break on the column, which groups the rows by the column values and inserts a header and a footer for each group. You can also apply aggregate functions, such as sum, count, or average, to the footer of each group.
• Hide: This option allows you to hide the column from the report, which reduces the clutter and improves the readability of the report. You can also show the hidden columns by using the Columns option in the Actions menu.

The other options are incorrect because:

• Group By: This option is not provided in the Column Heading menu of an Interactive Report. It is provided in the Actions menu of an Interactive Report. It allows you to group the rows by one or more columns and display the result in a chart or a pivot table.
• Delete: This option is not provided in the Column Heading menu of an Interactive Report. It is provided in the Data option in the Actions menu of an Interactive Report. It allows you to delete one or more rows from the report and the underlying table.

Verified References: [Customizing Interactive Reports] [Column Heading Menu]

Oracle APEX provides several preconfigured authentication schemes that follow a standard behavior for authentication and session management. You can select a preconfigured authentication scheme from the gallery when you create an authentication scheme for your application. The preconfigured authentication schemes are:

• Open Door Credentials: This scheme enables anyone to access your application using a built-in login page that captures a user name.
• LDAP Directory: This scheme authenticates a user and password with an authentication request to a LDAP server.
• HTTP Header Variable: This scheme authenticates users externally by storing the username in a HTTP Header variable set by the web server.
• Social Sign-In: This scheme supports authentication with Google, Facebook, and other social networks that support OpenID Connector OAuth2 standards.
• Oracle APEX Accounts: This scheme authenticates users against Oracle APEX user accounts that are created within and managed in the APEX user repository.
• Custom Authentication: This scheme allows you to create a custom authentication scheme from scratch to have complete control over your authentication interface.
• Database Accounts: This scheme authenticates users using database schema accounts.
• Oracle Application Server Single Sign-On Server: This scheme delegates authentication to the Oracle AS Single Sign-On (SSO) Server.
• SAML Sign-In: This scheme delegates authentication to the Security Assertion Markup Language (SAML) Sign In authentication scheme.

 In Oracle APEX, you can choose from different authentication methods to establish a user’s identity and control access to your application. Authentication may require a user to provide some type of credentials, such as a user name and password, or could involve the use of digital certificates or a secure key. Three of the authentication methods that you can choose in Oracle APEX are:

• Custom Authentication Scheme: This method allows you to create your own authentication logic using PL/SQL code or an external web service. You can also customize the login page and session management for your application.
• No Authentication (using DAD): This method adopts the current database user as the authenticated user. This approach can be used in combination with a mod_plsql Database Access Descriptor (DAD) configuration that uses basic authentication to set the database session user.
• Built-in Authentication Scheme: This method allows you to use one of the preconfigured authentication schemes that ship with Oracle APEX, such as Open Door Credentials, LDAP Directory, Social Sign-In, and so on.

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

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.

The navigation menu is the list of pages that displays when you click on the hamburger menu in the upper-left corner of an APEX application. The navigation menu is a shared component that can be created and edited in the Shared Components page3. Lists, breadcrumbs, and navigation bar entries are other types of navigation components in APEX, but they are not the same as the navigation menu.

An Interactive Report and an Interactive Grid are two types of regions that allow end users to customize how and what data is displayed. They have some common capabilities such as:

• End users can add, modify, and refresh data directly on the report by using the Edit option. This option enables inline editing or modal dialog editing depending on the region settings.
• End users can customize how and what data is displayed by using the Actions menu. This menu provides various options such as Filter, Highlight, Aggregate, Chart, Group By, Pivot, etc.

The other options are incorrect because:

• End users cannot rearrange the report interactively using the mouse in an Interactive Report. This capability is only available in an Interactive Grid by using the Reorder option in the Actions menu.
• End users cannot save the report in an Interactive Grid. This capability is only available in an Interactive Report by using the Save Report option in the Actions menu.

Verified References: [About Interactive Reports] [About Interactive Grids]

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]

A list of values (LOV) is a definition that provides a set of display values and return values for a page item or a report column. A LOV can be created at the application level as a shared component or at the page level as a local component. There are three types of LOVs that you can create on a page:

• Static LOV: A static LOV is based on a fixed list of display values and return values that you specify when you create the LOV. A static LOV does not change unless you edit it manually.
• Cascading LOV: A cascading LOV is based on another parent LOV that determines the values of the child LOV. A cascading LOV changes dynamically depending on the selection made in the parent LOV.
• Dynamic LOV: A dynamic LOV is based on a SQL query that returns display values and return values from the database. A dynamic LOV changes dynamically depending on the data in the database.

An interactive grid is a customizable report that allows end users to modify the data and layout of the report. To make an employee’s commission editable in the grid, you need to perform two actions:

• In the Interactive Grid attributes, turn “On” the Enabled switch, under the Edit group. This enables editing for the entire interactive grid region and allows you to specify which columns are editable and which are not.
• Ensure that the “Primary Key” switch is turned “On” for the EMPNO column. This identifies the EMPNO column as the primary key for the EMP table and allows APEX to perform DML operations on the table when end users edit the data in the grid. You do not need to set EMPNO or ENAME to “Display Only” or select COMM for “Allowed Row Operations Column” to make an employee’s commission editable in the grid. Verified References: [Managing Interactive Grids - Oracle Help Center], [Interactive Grid Attributes - Oracle Help Center]

A plugin is a component that extends the native functionality of Oracle APEX by allowing developers to create custom components using SQL, PL/SQL, HTML, CSS, and JavaScript. A plugin can be created for any of the following component types: Dynamic Action, Item, Process, Region, Report Layout, Authentication Scheme, Authorization Scheme, or Data Load Method. A process plugin is a custom process type that can be executed when a page is submitted or loaded. A region plugin is a custom region type that can display data or content on a page. Verified References: [Creating Plugins - Oracle Help Center], [Plugin Concepts - Oracle Help Center]

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.

Task definitions that exist on the application level in the Shared Components section are made up of all of the following: Participants, Task Settings, Parameters, and Actions. Task definitions are used to define approval workflows for data changes in interactive grids or forms5. Participants are the users or groups who can approve or reject tasks. Task Settings are the properties that control how tasks are created, assigned, and completed. Parameters are the variables that store information about tasks or data changes. Actions are the PL/SQL code blocks that execute when tasks are created, updated, or completed5.

An Interactive Report and an Interactive Grid are two types of regions that allow end users to customize how and what data is displayed. They have some common capabilities such as:

• End users can add, modify, and refresh data directly on the report by using the Edit option. This option enables inline editing or modal dialog editing depending on the region settings.
• End users can customize how and what data is displayed by using the Actions menu. This menu provides various options such as Filter, Highlight, Aggregate, Chart, Group By, Pivot, etc.

The other options are incorrect because:

• End users cannot rearrange the report interactively using the mouse in an Interactive Report. This capability is only available in an Interactive Grid by using the Reorder option in the Actions menu.
• End users cannot save the report in an Interactive Grid. This capability is only available in an Interactive Report by using the Save Report option in the Actions menu.

Verified References: [About Interactive Reports] [About Interactive Grids]

A page item is a component that is part of an HTML form and can accept user input or display output. There are many types of page items that can be placed on a page in APEX, such as text fields, text areas, radio groups, checkboxes, date pickers, select lists, popup LOVs, shuttles, and so on. Each type of page item has different properties and attributes that affect its appearance and functionality. Three of the types of page items that can be placed on a page are:

• Checkbox: A checkbox is a page item that displays one or more options that can be selected or deselected by the user. A checkbox can have either static values or dynamic values based on a list of values (LOV). A checkbox can also have different display styles, such as pill button or switch.
• Date Picker: A date picker is a page item that displays a text field with an icon that opens a calendar popup when clicked. A date picker allows users to enter or select a date value in a specific format. A date picker can also have different attributes, such as minimum or maximum date, display format, or time picker.
• Select List: A select list is a page item that displays a drop-down list of options that can be selected by the user. A select list can have either static values or dynamic values based on a list of values (LOV). A select list can also have different attributes, such as multiple selection, null value display text, or cascading LOV.

An authentication scheme is a rule that determines if a user is authorized to access a specific component or feature of an application, such as a page, region, button, item, etc. An authentication scheme type defines how users are authenticated when they access an application. The authentication scheme type that supports authentication with social networks and enterprise identity providers that support OpenID Connect or OAuth2 standards is Social Sign-In. Social Sign-In supports authentication with Google, Facebook, and other social networks that support these standards. The other authentication scheme types do not support authentication with social networks or enterprise identity providers. They are:

• HTTP Header Variable: Authenticate users externally by storing the username in a HTTP Header variable set by the web server.
• SAML Sign-In: Delegates authentication to the Security Assertion Markup Language (SAML) Sign In authentication scheme.
• Open Door Credentials: Enable anyone to access your application using a built-in login page that captures a user name. Verified References: [Understanding Preconfigured Authentication Schemes - Oracle Help Center], [Social Sign-In - Oracle Help Center]

Page Designer is a tool that allows developers to create and edit pages in Oracle APEX using a graphical user interface. Page Designer has three main panes: Rendering, Processing, and Property Editor. You can change the layout of Page Designer under Utilities by selecting one of the following options:

• Single Pane Mode - This option displays only one pane at a time. You can switch between the Rendering, Processing, and Property Editor panes by using the buttons on the toolbar or the keyboard shortcuts.
• Two Pane Mode - This option displays two panes side by side. You can choose which panes to display by using the buttons on the toolbar or the keyboard shortcuts. You can also resize the panes by dragging the splitter bar between them. There is no Three Pane Mode or Four Pane Mode option for Page Designer layout. Verified References: [Managing Pages in Page Designer - Oracle Help Center], [Page Designer Layout Options - Oracle Help Center]

To migrate an APEX app between environments, such as from development to production, you need to consider three components that make up an APEX app:

• Database objects: These are the tables, views, procedures, functions, packages, triggers, sequences, synonyms, and other schema objects that store or manipulate the data used by the app. You need to move these objects from the source schema to the target schema using tools such as SQL Developer, Data Pump Export/Import, or Data Workshop.
• Images: These are the static files, such as images, CSS files, JavaScript files, or PDF files, that are used by the app for display or download purposes. You need to move these files from the source web server to the target web server using tools such as FTP, SCP, or File Explorer.
• Application definition and all associated files: These are the metadata files that define the app components, such as pages, regions, items, buttons, processes, validations, computations, dynamic actions, shared components, and so on. You also need to include any supporting object definitions or data scripts that are used to create or populate database objects for the app. You need to move these files from the source APEX instance to the target APEX instance using tools such as App Builder Export/Import or One-click Remote Application Deployment.

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

 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.

The feature pages that can be created using the Create Page Wizard are About Page, Access Control, Activity Reporting, Configuration Options, Email Reporting, Feedback, Login Page, and Theme Style Selection. These pages provide application-level functionality that can be added to an existing application. Search Page and Unified Task List are not feature pages that can be created using the Create Page Wizard. Verified References: Managing Feature PagesFeature Page Types

To hide a few columns in your interactive report, you should choose Columns from the Actions menu. This option allows you to select which columns to show or hide in your report by using checkboxes. You can also reorder or resize the columns from this option.

The other options are incorrect because:

• Filter allows you to filter the data in your report by applying one or more conditions on the columns.
• Data allows you to add, modify, or delete data in your report by using inline editing or modal dialog editing.
• Format allows you to change the appearance of your report by applying conditional formatting rules or highlighting colors.

Verified References: [Customizing Interactive Reports] [Actions Menu]

There are three different ways in which you can add a checkbox to a page in APEX:

• Drag and drop the checkbox item into the Layout pane: In Page Designer, you can drag and drop items from the Gallery pane into the Layout pane to create them on your page. To create a checkbox item, expand the Items node in the Gallery pane and drag and drop Checkbox into the Layout pane.
• Right click Body in the Rendering Tree and add a New Page Item as Checkbox Type: In Page Designer, you can right click any node in the Rendering tree andselect Create to create a new component under that node. To create a checkbox item under the Body node, right click Body and select Create > New Page Item > Checkbox.
• Use the context sensitive menu in the Gallery pane: In Page Designer, you can use the context sensitive menu in the Gallery pane to create items on your page. To create a checkbox item using this method, expand the Items node in the Gallery pane and right click Checkbox. Then select Create Checkbox.

As a general rule, you cannot import an application created in a newer release of APEX into an earlier version. This is because the newer release may have features or attributes that are not supported or recognized by the older version. For example, you cannot import an application created in APEX 21.2 into APEX 19.2. However, you can import an application created in an older release into a newer one, as long as the application is compatible with the newer release. For example, you can import an application created in APEX 18.2 into APEX 21.2, but you may need to upgrade or modify some components to use the latest features.

A faceted search page is a type of page that allows end users to filter data by applying one or more facets. A facet is a set of filters based on a column or expression. By default, when end users select a facet value, they need to click on an Apply button for that facet to apply the filter to the report. To make report filtering automatically executed when any facet value changes, you need to navigate to the faceted search region Attributes, and disable the Batch Facet Changes attribute. The Batch Facet Changes attribute determines whether end users need to click on an Apply button for each facet or not. When this attribute is disabled, the report is automatically refreshed when any facet value changes. The other options are not relevant to the report filtering behavior. Verified References: [Faceted Search Attributes - Oracle Help Center], [Batch Facet Changes - Oracle APEX]

The APEX_MAIL package is an API for the APEX mail system that enables developers to send emails from PL/SQL code. Some of the statements that are true about the APEX_MAIL package are:

• You can add files as attachments to your emails using the APEX_MAIL package. You can use the APEX_MAIL.ADD_ATTACHMENT procedure to add one or more files as attachments to your emails. The files can be in various formats, such as PDF, DOCX, XLSX, etc.
• You can send emails using the APEX_MAIL package from an Oracle APEX application. You can use the APEX_MAIL.SEND procedure or function to send an outbound email message from your application. You can also specify various parameters for your email, such as sender, recipients, subject, body, priority, etc. The APEX_MAIL package does not support sending emails only to Oracle database users or receiving emails in an Oracle APEX application. You can send emails to any valid email address or use other tools or services to receive emails. Verified References: [APEX_MAIL - Oracle Help Center], [APEX_MAIL : Send Emails from PL/SQL - ORACLE-BASE]

In a faceted search page, facets can be displayed as different UI types depending on the data type and cardinality of the facet column or expression. The facet item types are the UI components that are used to render the facets in the faceted search region. The supported facet item types are Range, Checkbox Group, Radio Group, List, Star Rating, and Switch. Date Picker and Popup LOV are not valid facet item types. Verified References: [Faceted Search Attributes - Oracle Help Center], [Facet Item Types - Oracle APEX]

To create a REST Enabled SQL Reference, you need to meet the following requirements:

• Install Oracle REST Data Services (ORDS) 19.x or later. ORDS is a Java application that enables developers to create, publish, and manage RESTful web services for Oracle databases1.
• Activate REST Enabled SQL for the target schema on the remote database. REST Enabled SQL is a feature of ORDS that allows you to execute any SQL or PL/SQL through a REST endpoint. You need to enable this feature for the schema that contains the data you want to access2.
• Configure and enable the REST Enabled SQL service feature. This is a workspace-level setting that allows you to use REST Enabled SQL references in your APEX applications. You need to specify a path prefix and a secret for the REST Enabled SQL service3.

You do not need to set up any remote database, as long as it meets the ORDS and REST Enabled SQL requirements. You can use any Oracle database or MySQL database as a remote data source2.

Object Browser is a utility in SQL Workshop that enables developers to browse, create, and edit objects in a database. Some of the actions that you can perform using Object Browser are:

• Browse database objects of the current schema. You can view the details of an object by selecting it from the Object Tree and then clicking the different object detail tabs.
• Create a lookup table based on a column in the current table. You can use the Create Lookup Table option in the Column Details tab to create a new table that stores the distinct values of the selected column and a foreign key constraint to reference it. You cannot restore dropped database objects, create and run SQL scripts, or export and import SQL scripts using Object Browser. You can use other utilities in SQL Workshop to perform these actions, such as Recycle Bin,SQL Commands, and SQL Scripts. Verified References: [Managing Database Objects with Object Browser - Oracle Help Center], [Creating Lookup Tables - Oracle Help Center]

When you use the Create Page Wizard to create a faceted search page on any table or SQL query, such as EMP table, APEX generates a classic report region as default report type for this page. A classic report region displays data from a SQL query or PL/SQL function returning a SQL query in tabular format. A faceted search page also contains a region of Faceted Search type, which holds one or more facets that allow end users to filter data by applying one or more facets. Verified References: Creating Faceted Search Pages - Oracle Help Center, Creating Classic Reports - Oracle Help Center

REST Data Source Synchronization is a feature that enables developers to automatically sync the contents of a local table with the data from an external REST service. To execute REST source synchronizations on schedule, the CREATE JOB privilege must be granted to the application’s parsing schema, which allows APEX to create a DBMS_SCHEDULER job for each scheduled synchronization task. If the local table is not in sync with the Data Profile, which defines the columns and data types of the REST service response, Data Synchronization continues to work for columns present in both the table and the Data Profile (other columns are ignored). However, APEX generates SQL DDL statements to sync table columns back to the Data Profile, which can be added to the application as supporting objects. Verified References: Managing Data Synchronization - Oracle Help Center, Synchronize Data from REST Services to Local Table - Oracle Blogs

You can create a chart in an interactive grid by selecting Chart in the Actions menu. You can only create one chart at a time in an interactive grid. To create a second chart, you have to reconfigure or delete the existing chart1. To remove a chart, you can click the Remove Chart icon (X) adjacent to the chart filter12. Once a chart is created, you can switch the view between Grid and Chart by clicking the toggle that appears at the top of the interactive grid

Universal Theme has many features that make it an ideal user interface for Oracle APEX applications. Three of the key features of Universal Theme are:

• Versatile UI Components: Universal Theme provides a rich set of UI components that can be used to create interactive and engaging applications. Some of the UI components include cards, lists, charts, calendars, maps, timelines, accordions, tabs, modals, alerts, and more.
• Responsive Design: Universal Theme adapts to different screen sizes and devices using CSS media queries and grid layout. It ensures that the applications look good and work well on any device, from desktops to tablets to smartphones.
• Easy Customization: Universal Theme allows developers to customize the appearance and behavior of their applications using template options and theme styles. Template options enable developers to apply different styles to components on a page without writing custom code. Theme styles enable developers to change the overall look and feel of the application by choosing from a variety of pre-built styles or creating their own.

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]

Universal Theme is a responsive, versatile, and customizable user interface for your APEX apps. It is designed uniquely for Oracle APEX to make it easy for developers to build beautiful, modern applications, at any scale, for any purpose, that work on any device. All of the statements given are true about Universal Theme:

• Features a responsive design and enables developers to create web applications without extensive knowledge of HTML, CSS, or JavaScript. Universal Theme adapts to different screen sizes and devices using CSS media queries and grid layout. It also provides a rich set of UI components, template options, and theme styles that can be used declaratively without writing custom code.
• Universal theme is the default theme that is shipped with Oracle APEX. Universal Theme is the default theme for new applications created in APEX 5.0 or later. It is also the recommended theme for upgrading existing applications to the latest version of APEX.
• Uses a 12-column grid layout system for arranging components on a page. Ships with a variety of pre-built theme styles. Universal Theme uses a 12-column grid layout system based on Flexbox to arrange components on a page. It also ships with a variety of pre-built theme styles that can be applied to change the look and feel of the application.

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]

In a Classic Report, an end user can perform the following actions:

• Filter values of a column in the report by using the Search Bar. This bar allows the user to enter a search string and apply it to one or more columns in the report.
• Sort the columns of the report by clicking on the column headers. This action toggles the sort order between ascending and descending for the selected column.

The other options are incorrect because:

• Create Control Breaks in the report is not an action that an end user can perform in a Classic Report. This action is only available in an Interactive Report by using the Control Break option in the Actions menu.
• Rearrange the columns in the report is not an action that an end user can perform in a Classic Report. This action is only available in an Interactive Grid by using the Reorder option in the Actions menu.

Verified References: [About Classic Reports] [Searching Classic Reports] [Sorting Classic Reports]

A Progressive Web Application (PWA) is a web application that uses modern web technologies and best practices to provide a native app-like experience to users. Enabling the PWA functionality in your APEX app has the following benefits:

• It optimizes page loading speed on a mobile device by caching static resources and using service workers to handle network requests.
• It adds a new navigation bar entry named Install App to your app, which allows users to install the app on their device’s home screen and access it offline.
• It enhances the app’s appearance and behavior by using a manifest file to specify the app’s name, icon, theme color, orientation, and display mode.

The other options are incorrect because:

• To use the PWA feature, the Friendly URLS attribute in the Application Definition, Properties section must be turned On. This attribute enables user-friendly URLs that are required for PWA functionality.
• PWA features will not be rendered if the application is served in an unsecured environment. The application must use HTTPS protocol to enable PWA functionality.
• You can create a PWA from an existing application or a new application with the Create Application Wizard. You just need to enable the PWA functionality in the User Interface section of the Application Definition.

Verified References: Progressive Web ApplicationsEnabling Progressive Web Application Functionality