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

A form is a type of component that is part of an HTML form and can accept user input or display output. There are many types of forms that can be created in APEX, such as forms on tables, forms on procedures, forms on web sources, and so on. Each type of form has different properties and attributes that affect its appearance and functionality. Three of the ways in which you can create a form in APEX are:

• Using the Create Page wizard: This method allows you to create a new page with a form component using a guided wizard. You can choose from different types of forms, such as report with form, editable interactive grid, single page master detail, two page master detail, form on table, form on procedure, and so on. You can also specify various options for your form, such as data source, display style, validations, processes, and branches.
• Create a Form region in Page Designer: This method allows you to create a complex form region that includes multiple form items and processes on an existing page. You can use the Create Form Region wizard in Page Designer to create a form region based on a table, view, procedure, web source module, or SQL query. You can also customize your form region by adding or modifying items, buttons, validations, computations, processes, and dynamic actions.
• Using the Create Application Wizard: This method allows you to create a new application that contains one or more forms using a guided wizard. You can choose from different types of applications, such as database application, web source application, blueprint application, or from scratch application. You can also specify various options for your application and forms, such as name, icon, theme style, features, data source, navigation menu entry, and so on.

The events that cause the dynamic action to fire are classified into five categories: Browser Events, Component Events, Custom Events, Framework Events, and jQuery Events1. Browser events are triggered by user interactions with the browser window, such as resize, scroll, or unload. Component events are triggered by user interactions with specific APEX components, such as interactive grids, interactive reports, or trees. Custom events are user-defined events that can be triggered by other dynamic actions or JavaScript code. Framework events are triggered by APEX framework actions, such as page load, page submit, or dialog close. jQuery events are triggered by user interactions with jQuery UI widgets, such as accordion, tabs, or date picker1.

The Create Application Wizard is a tool that allows developers to create a new application by following a series of steps. Some of the actions that you can perform using the Create Application Wizard are:

• Reorder application pages. You can use the Reorder Pages option in the Pages step to change the order of the pages in your application by dragging and dropping them.
• Add or delete application pages. You can use the Add Page or Delete Page options in the Pages step to add new pages or delete existing pages from your application. You can also use the Create Page Wizard to create additional pages after creating the application. You cannot upload JavaScript or CSS files required for an application or change the application authorization using the Create Application Wizard. You can use other features in App Builder to perform these actions, such as Shared Components > User Interface > Files and Shared Components > Security > Authentication Schemes. Verified References: [Creating an Application Using the Create Application Wizard - Oracle Help Center], [Create Application Wizard - Oracle APEX]

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.

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

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.

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 REST-enabled SQL feature in Oracle APEX allows developers to execute SQL statements and PL/SQL blocks on a remote Oracle Database by using REST services. The prerequisites to use this feature are:

• On the remote Oracle Database, install ORDS 19.x or later.
• REST enable the schema in the remote Oracle Database using ORDS.ENABLE_SCHEMA.
• Create a REST Data Source with REST Enabled SQL as the REST Data Source Type in Oracle APEX.
• Create an Authorization Scheme based on the REST Data Source in Oracle APEX. You do not need to create a database link to the remote Oracle Database or install Oracle APEX in the remote Oracle Database to use this feature. Verified References: [Using REST Enabled SQL - Oracle Help Center], [REST Enabled SQL Service - Oracle Help Center]

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.

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]

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]

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.

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.

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.

 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.

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.

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 workspace is a logical work area that enables multiple users to work within the same Oracle APEX installation while keeping their objects, data, and applications private. Creating and managing an APEX workspace involves the following statements:

• During workspace creation, you can associate the workspace with an existing database schema or create a new schema for the workspace. A schema is a collection of database objects such as tables, views, indexes, etc. that belong to a user.
• A workspace enables multiple users to work within the same Oracle APEX installation. Each user can have a different role and privilege in the workspace, such as workspace administrator, developer, or end user.
• A workspace can be associated with one or more schemas. You can add or remove schemas from a workspace after it is created.
• You can create as many workspaces as you need in an APEX Service (APEX Application Development) instance. There is no limit on the number of workspaces per instance.

Verified References: Managing WorkspacesAbout Workspaces

You can create a report with form in Oracle APEX by using either the Create Application Wizard or the Create Page Wizard. The report can be either an interactive report or a classic report, and the form can be either a single row form or a multi row form. The report with form combination enables you to view and edit data from a table or a query in a single page. You can also customize the report and form attributes, such as the columns, regions, buttons, validations, processes, and so on. Verified References: [Creating a Report Using the Create Page Wizard - Oracle], [Creating a Report with Form on Table - Oracle]

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]

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]

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]

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]

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

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.

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.

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.

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 extend the functionality of the form as required, you need to create a dynamic action on P2_JOB that shows or hides P2_HIREDATE and P2_COMM based on its value. The steps are as follows:

• Create a dynamic action on P2_JOB by right-clicking it in Page Designer and selecting Create Dynamic Action.
• Set Name to Show/Hide Hire Date and Commission.
• Set Event to Change.
• Set Selection Type to Item(s).
• Set Item(s) to P2_JOB.
• Set Condition Type to Equal To.
• Set Value to SALESMAN.
• Add two true actions by clicking the Add True Action button twice.
• For the first true action, set Action to Show.
• Set Affected Elements > Selection Type to Item(s).
• Set Affected Elements > Item(s) to P2_HIREDATE,P2_COMM.
• For the second true action, set Action to Show.
• Set Fire On Initialization to Yes.
• Set Affected Elements > Selection Type to jQuery Selector.
• Set Affected Elements > jQuery Selector to label[for=“P2_HIREDATE”],label[for=“P2_COMM”].
• Add two false actions by clicking the Add False Action button twice.
• For the first false action, set Action to Hide.
• Set Affected Elements > Selection Type to Item(s).
• Set Affected Elements > Item(s) to P2_HIREDATE,P2_COMM.
• For the second false action, set Action to Hide.
• Set Fire On Initialization to Yes.
• Set Affected Elements > Selection Type to jQuery Selector.
• Set Affected Elements > jQuery Selector to label[for=“P2_HIREDATE”],label[for=“P2_COMM”].

This dynamic action will show or hide both the page items and their labels depending on whether P2_JOB is equal to SALESMAN or not. Verified References: [Creating a Dynamic Action in Oracle Apex - OrclQA.Com], [Managing Dynamic Actions - Oracle Help Center]

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]

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.

A workspace is a logical work area that enables multiple users to work within the same Oracle APEX installation while keeping their objects, data, and applications private. Creating and managing an APEX workspace involves the following statements:

• During workspace creation, you can associate the workspace with an existing database schema or create a new schema for the workspace. A schema is a collection of database objects such as tables, views, indexes, etc. that belong to a user.
• A workspace enables multiple users to work within the same Oracle APEX installation. Each user can have a different role and privilege in the workspace, such as workspace administrator, developer, or end user.
• A workspace can be associated with one or more schemas. You can add or remove schemas from a workspace after it is created.
• You can create as many workspaces as you need in an APEX Service (APEX Application Development) instance. There is no limit on the number of workspaces per instance.

Verified References: Managing WorkspacesAbout Workspaces

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.

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]

You can create a report in any of these three methods:

• Create a report as a new page in an application by using the Create Page Wizard. This wizard guides you through the steps of selecting a page type, defining attributes, selecting a source (such as SQL query or table), and adding items or buttons.
• Create a report when you create a new database application by using the Create Application Wizard. This wizard allows you to generate one or more reports based on existing tables or views in your schema. You can also create a report and form on the same table or view.
• Create a report region on a page in an application by using the Page Designer. This tool allows you to drag and drop a region type (such as Classic Report, Interactive Report, or Interactive Grid) onto the page and define its attributes and source.

The other option is incorrect because:

• You cannot create a report from Object Browser. Object Browser is a tool that allows you to view and manage the database objects in your schema, such as tables, views, indexes, etc. You can only run SQL queries or scripts from this tool, not create reports.

Verified References: [Creating Database Applications] [Creating Pages] [Creating Regions] [Using Object Browser]

APP_USER is a built-in substitution string in Oracle APEX that stores the user name of the current user session. The APEX engine uses APP_USER as one component of a key for tracking each user’s session state. As a user navigates from page to page, the APEX engine sets the value of APP_USER to identify the user. The APEX engine also uses APP_USER to perform security checks and conditional processing. You can reference APP_USER using different syntax depending on the context, such as SQL, PL/SQL, or static text.

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.

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]