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

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]

A REST Data Source is a logical representation of an external web service in Oracle APEX. It can contain one or many Operations, which are the references to a concrete external web service endpoint. Oracle APEX supports three types of REST Data Sources: REST Enabled SQL Query, Web Source Module, and Generic REST Data Source. Oracle APEX provides direct integration of REST Data Sources in interactive reports and grids, as well as other components. REST Data Sources can support various authentication methods, such as Basic, OAuth2, or Custom. References: [Understanding REST Data Sources] and [Creating a REST Data Source]

A map is a type of component that enables you 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. Two of the statements that are true about maps in Oracle APEX are:

• Background maps do not require any API keys. This statement is true because Oracle APEX provides several background map options that do not require any API keys or registration to use. These options include OpenStreetMap, Stamen Maps, CartoDB Maps, and Esri Maps.
• Maps support REST Enabled SQL. This statement is true because Oracle APEX allows you to use REST Enabled SQL as a data source for your map regions. REST Enabled SQL is a feature of Oracle REST Data Services (ORDS) that enables you to execute SQL statements and PL/SQL blocks over HTTPS using REST endpoints.

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]

Automations are a sequential set of PL/SQL actions that are triggered by query results. They are used to monitor data and then perform the appropriate action2. Some use cases of automations are:

• Monitoring log tables and raising an alert when there is an issue. For example, an automation can query a log table for any errors and send an email notification to the administrator if any errors are found2.
• Approving specific requests. For example, an automation can query a table for any pending requests and approve them automatically based on some criteria2.
• Sending email alerts at a particular time of the week. For example, an automation can query a table for any overdue tasks and send a reminder email to the assignees every Monday2.

Deleting a database record based on an end user’s request is not a use case of automations, as it does not involve querying data and triggering actions based on the query results. This can be achieved by using a PL/SQL process or a dynamic action on the page where the user requests the deletion34.

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]

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

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]

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]

A facet is a type of component that provides a set of display values and return values for a faceted search region or a smart filters region. A facet can be based on either static values or dynamic values from a list of values (LOV). A facet can also have different display styles depending on its type and settings. Three of the types of facets that you can create in APEX are:

• Range: A range facet displays numeric values in either buckets or sliders that users can select or adjust to filter the search results. A range facet can have either static values or dynamic values based on an LOV or SQL query.
• Checkbox Group: A checkbox group facet displays multiple options that users can select or deselect to filter the search results. A checkbox group facet can have either static values or dynamic values based on an LOV or SQL query.
• Input Field: An input field facet displays a text field that users can enter text to filter the search results. An input field facet does not have any values but uses an operator to compare the user input with the data.

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]

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.

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]

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.

One-click remote application deployment is a feature in Oracle APEX that simplifies the process of deploying an application from one APEX instance to another using REST Enabled SQL references. REST Enabled SQL references are shared components that work with an Oracle REST Data Services (ORDS) REST Enabled SQL Service. One-click remote application deployment can authenticate through first party authentication (Basic Authentication), Schema Authentication (database username and password), or OAuth 2 Client Credentials. Two of the advantages of using one-click remote application deployment are:

• Deploy the app, and explicitly install the supporting objects in one-click. This advantage allows you to package the app definition along with the database objects, images, and seed data necessary for your application to run correctly using the Supporting Objects functionality in APEX. You can then export and deploy this app and install the supporting objects in one-click without having to manually create or copy the database objects in the target system.
• Directly deploy your app definition along with the objects from the source system to the target system. This advantage allows you to avoid the intermediate step of exporting the app and its objects from the source system into files and then importing them into the target system. You can directly deploy your app and its objects from within your development environment to the remote production environment without having to access your production environment.

Query Builder is a component in SQL Workshop that allows you to build queries graphically without manual SQL coding. You can use Query Builder to select tables and views from your schema, join them using drag-and-drop operations, add filters andgroupings, and view the results in a grid or chart format. You can also switch to the SQL mode to view or edit the generated SQL statement.

The other options are incorrect because:

• Quick SQL is a component in SQL Workshop that allows you to generate SQL scripts for creating tables and other database objects using shorthand syntax. You cannot use Quick SQL to build queries graphically.
• SQL Commands is a component in SQL Workshop that allows you to run individual SQL statements or PL/SQL blocks interactively. You cannot use SQL Commands to build queries graphically.
• Data Workshop is a component in SQL Workshop that allows you to load or unload data from the database using various file formats. You cannot use Data Workshop to build queries graphically.

Verified References: [About Query Builder] [Using Query Builder]

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]

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

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.

The Approvals Component is Oracle APEX’s new offering as part of the 22.1 Release. It allows seamless management of approvals across APEX Applications. Approvals are commonly used in business situations involving Expense Reimbursements, Leave Requests, Purchase Requisitions, On-boarding of Employees to name a few. The Approvals Component provides the following building blocks for the approvals functionality:

• Task Definition: A shared component for configuring task parameters, participants, and actions. A task definition defines the template for creating tasks based on a specific type of approval request, such as Leave Approval or Purchase Requisition. A task definition specifies the data source, display attributes, potential owners, business administrators, and available actions for the tasks.
• Task Details Page: A page that shows task details, which can include metadata, history, comments, and actions. A task details page allows users to view and take action on a specific task, such as approve, reject, reassign, or escalate. A task details page can be created using the Create Page Wizard or the Quick SQL tool in APEX.
• Unified Task List: A page type in the Create Page Wizard, used to create a summary of a user’s tasks that functions like an inbox. A unified task list allows users to see and manage all their tasks in one place. Users can filter, sort, search, claim, release, or open tasks from the unified task list.

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.

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]

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 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]

In an Employee form, the ‘Commission’ and ‘Hire Date’ fields are enabled only if the Job is ‘Salesman’. This can be achieved by using Dynamic Actions in APEX. Dynamic Actions are declarative components that define client-side behavior without writing JavaScript code. You can create Dynamic Actions on items, buttons, or regions of a page by specifying an event, a condition, an action, and other properties. In this scenario, you can create a Dynamic Action on Job item with Change as event, Execute JavaScript Code as action, and use jQuery to enable or disable Commission and Hire Date fields based on Job value. Processing, Conditional SQL, and PL/SQL procedure are not features of APEX that can achieve this requirement without writing JavaScript code.

Shared components are common elements that can be displayed or applied on any page within an application. Once you create a shared component, you can add them to any page within your APEX application. However, shared components are specific to each application and workspace, so you cannot add them to any page in any workspace4. Breadcrumbs, lists, and navigation bar entries are examples of shared components that can be used for navigation purposes4.

Dynamic actions provide a way to define complex client-side behavior declaratively without the need for JavaScript. You can create dynamic actions on items, buttons, or regions of a page by specifying an event, a condition, an action, and other properties1. However, more dynamic actions you add to a page, the greater your overall page size. This can affect the performance and user experience of your application2. It is possible to debug dynamic actions from the Developer Toolbar by using the Debug option3. Dynamic actions do not require complex client-side JavaScript code, but they can optionally include custom JavaScript code as an action or a condition1.

A smart filters page is a type of component that features a single search field at the top of the page and a search results report (classic report, cards, map, or calendar) at the bottom. A smart filters page behaves similarly to faceted search, but it features a more space efficient layout. Two of the features of a smart filters page are:

• Consists of a single search field with filters at the top of the page and a report at the bottom. This feature provides a simple and compact user interface that allows users to enter text in the search field and see suggested filters based on their input. Users can also see and modify applied filters at any time.
• Each filter displays as a suggestion chip with a single count of how often the specific suggestion value occurs. This feature provides useful information to users about how many records match each filter value. Users can also choose between different types of suggestions, such as dynamic, static, or SQL query.

A Link Column is a special column type that you can define for an interactive report to create a link to another page, URL, or custom target. A Link Column is always displayed as the first column in the report, regardless of the order of the columns in the query. A Link Column cannot be sorted, hidden, or moved by an end user using the Actions menu or the column header. However, a developer can change the position and visibility of a Link Column by editing the report attributes in Page Designer. 

Using Data Workshop, you can perform the following tasks:

• Load vast amount of data into the database: You can use the Data Load option to load data from various file formats such as XLSX, CSV, XML, and JSON into a table or a collection in your database. You can also use the Data Load Wizard to guide you through the steps of loading data.
• Export vast amount of data from the database into a file: You can use the Data Unload option to export data from a table or a collection in your database into a file in CSV or JSON format. You can also use the Data Unload Wizard to guide you through the steps of exporting data.
• Load data using various file formats such as XLSX, CSV, XML, and JSON: You can use the Data Load option to load data from different file formats into your database. You can choose the file format from a list of supported formats or let Oracle APEX detect it automatically.

The other option is incorrect because:

• Delete data from the database: You cannot use Data Workshop to delete data from the database. You can use SQL Commands or SQL Scripts in SQL Workshop to run DELETE statements to delete data from the database.

Verified References: [About Data Workshop] [Loading Data] [Unloading Data]

 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 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]

Low Code Apps are applications that are developed using a low-code development platform such as Oracle APEX. Low Code Apps have the following characteristics:

• Scalable: Low Code Apps can handle large volumes of data and users without compromising performance or reliability. They can also leverage the scalability features of the underlying database or cloud platform.
• Provide Rich Functionality with Less Code: Low Code Apps can provide complex business logic, user interface, security, and integration features with minimal or no coding. They use declarative tools, visual editors, drag-and-drop components, and pre-built templates to speed up the development process.

The other options are incorrect because:

• Not Mobile Friendly: Low Code Apps are mobile friendly by default. They use responsive design techniques to adapt to different screen sizes and orientations. They also support touch gestures, device features, and offline capabilities.
• Expensive: Low Code Apps are not expensive to develop or maintain. They reduce the cost of development by requiring less time, resources, and skills. They also reduce the cost of maintenance by simplifying the deployment, testing, and debugging processes.

Verified References: [What is Low Code?] [Why Choose Oracle APEX?]

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]

The friendly URL syntax 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]

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

A page process type defines what action the page process performs when it is executed. There are many page process types available in Oracle APEX, such as Execute PL/SQL Code, Data Loading, Branch, etc. One of the valid page process types is Set Value. The Set Value page process type sets session state for an item or items on a page using a computation or PL/SQL expression. You can use this page process type to assign values to items based on logic or conditions. The other options are not valid page process types. Execute JavaScript Code is a dynamic action type, not a page process type. Send E-Mail is an application process type, not a page process type. Verified References: [Understanding Page Processes - Oracle Help Center], [Set Value Process Type - Oracle Help Center]

Template options provide developers with a declarative approach to applying different styles to components on an Oracle APEX page. Developers can use template options to declaratively apply CSS modifiers to the templates they have chosen for pages, regions, reports, lists, breadcrumbs, items and buttons. Developers can use template options in all of the following ways:

• Applying different colors or accents. Developers can use template options to change the color scheme or accent color of components, such as buttons, lists, or regions.
• Rendering buttons in different styles, with and without icons. Developers can use template options to change the shape, size, style, and icon of buttons on a page.
• Applying different spacing and padding. Developers can use template options to adjust the spacing and padding of components, such as regions, items, or reports.
• Displaying form fields with different alignments. Developers can use template options to change the alignment of form fields and labels, such as left-aligned, right-aligned, or top-aligned.

Dynamic actions are a declarative way to define client-side behavior without writing JavaScript code. You can create dynamic actions on an item, button, or region of a page by specifying the event, condition, affected elements, action, and other properties. Some of the statements that are true about creating and using dynamic actions are:

• You can execute JavaScript code by creating a dynamic action. One of the supported action types is Execute JavaScript Code, which allows you to enter custom JavaScript code to run when the dynamic action fires.
• If a client-side condition is defined, the true action will fire when the condition is met, and the false action will fire when it is not. You can define a client-side condition for a dynamic action to control when it should fire based on an expression or value. You can also define different actions for the true and false branches of the condition. You can add additional true actions to a dynamic action by clicking the Add True Action button in the Property Editor. If no client-side condition is defined, true actions will fire when the event occurs. Verified References: [Oracle Application Express 18: Creating Dynamic Actions], [Dynamic Action Enhancements in APEX 21.1 - Oracle Blogs]

The friendly URL syntax 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]

The Access Control feature pages are a set of pages that allow developers to implement role-based access control for an application. The Access Control feature pages consist of four pages: Administration, Users, Roles, and Role Assignments. The Administration page allows administrators to perform various tasks related to managing users and roles, such as:

• Add Users: Administrators can add new users to the application by entering their username, email address, password, status, etc.
• Assign roles to users: Administrators can assign one or more roles to users by selecting them from a list of available roles.
• Edit Users: Administrators can edit user details such as username, email address, password, status, etc.
• Delete Users: Administrators can delete users from the application by selecting them from a list of existing users.
• Lock/Unlock Users: Administrators can lock or unlock users by changing their status from active to locked or vice versa. You cannot create authorization schemes or create new application roles using the Administration page. You can create authorization schemes by using Shared Components > Security > Authorization Schemes. You can create new application roles by using Shared Components > Security > Access Control > Roles. Verified References: [Using Access Control - Oracle Help Center], [Creating an Administration Page - Oracle Help Center]