1z0-770 Oracle APEX Cloud Developer Professional Question and Answers

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.

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.

An authorization 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 authorization scheme can be evaluated at different points in time depending on its evaluation point attribute. The valid evaluation points for authorization schemes are:

• Never: The authorization scheme is never evaluated and always returns false.
• Once per session: The authorization scheme is evaluated only once per user session and caches the result for subsequent requests.
• Once per page view: The authorization scheme is evaluated once per page view and caches the result for subsequent requests within the same page view.
• On each new page view or partial page refresh: The authorization scheme is evaluated on each new page view or partial page refresh (for example, when using dynamic actions) and caches the result until the next page view or partial page refresh.
• On each request (not cached): The authorization scheme is evaluated on each request and does not cache the result. Once per user and Once per page load are not valid evaluation points for authorization schemes. Verified References: [Creating Authorization Schemes - Oracle Help Center], [Authorization Scheme Attributes - Oracle Help Center]

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]

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.

When you click a Customer Name in the Customers report, the Customer Details form dialog page is displayed. This involves two events: page rendering and page processing. Page rendering is the event that occurs when APEX generates and sends the page to the browser. Page processing is the event that occurs when APEX receives and processes the page from the browser. In this scenario, both events happen because the Customer Details form dialog page is a modal dialog that uses AJAX to communicate with the server without reloading the entire page. Page compilation is not an event, but an action that occurs when APEX compiles an application or a page before running it. 

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

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.

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]

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]

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]

Faceted Search is a feature 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. Faceted Search supports the ability to filter columns storing multiple values as one string, such as comma-separated values or JSON arrays, by using the Split Values attribute. Facets map to specific database columns or expressions that are defined in the Data Source attribute of the faceted search region. The other statements are false because Faceted Search supports displaying multiple charts in the same region by using the Chart View attribute, and a facet’s chart can be seen either in a nonmodal dialog or inline by using the Chart Display Mode attribute. Verified References: [Creating Faceted Search Pages - Oracle Help Center], [Facet Attributes - Oracle APEX]

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]

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.

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]

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

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.

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.

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]

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

You can create two types of card layout in APEX: Float and Grid. Float layout displays cards in a single row that wraps to the next row when the available space is filled. Grid layout displays cards in a fixed number of columns that can be responsive to the screen size1. Vertical and Horizontal are not valid card layout types in APEX.

The Universal Theme is a responsive user interface design for Oracle APEX applications. It has the following features:

• Responsive UI: The Universal Theme uses responsive design techniques to adapt to different screen sizes and orientations. It ensures that your applications look great and work well on any device, such as desktops, laptops, tablets, or smartphones.
• Easy customization: The Universal Theme allows you to customize the appearance and behavior of your applications using various tools and options. You can use Theme Roller to change the colors, fonts, icons, and styles of your applications. You can also use Template Options to modify the layout and functionality of your components.

The other options are incorrect because:

• Not designed to work on tablets: The Universal Theme is designed to work on tablets as well as other devices. It uses responsive design techniques to adapt to different screen sizes and orientations.
• The developers must have extensive knowledge about Javascript, CSS and HTML in order to use the Universal Theme: The developers do not need to have extensive knowledge about Javascript, CSS and HTML in order to use the Universal Theme. They can use declarative tools such as Theme Roller and Template Options to customize their applications without coding.

Verified References: [About Universal Theme] [Using Theme Roller] [Using Template Options]

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]

Faceted Search is a feature 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. Faceted Search supports the ability to filter columns storing multiple values as one string, such as comma-separated values or JSON arrays, by using the Split Values attribute. Facets map to specific database columns or expressions that are defined in the Data Source attribute of the faceted search region. The other statements are false because Faceted Search supports displaying multiple charts in the same region by using the Chart View attribute, and a facet’s chart can be seen either in a nonmodal dialog or inline by using the Chart Display Mode attribute. Verified References: [Creating Faceted Search Pages - Oracle Help Center], [Facet Attributes - Oracle APEX]

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]

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.

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]

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

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.

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

The valid Geometry Column Data Types for maps region are Latitude/Longitude, GeoJSON, and SDO_GEOMETRY. These types represent different ways of storing spatial data in Oracle Database. Latitude/Longitude uses two numeric columns for longitude and latitude values. GeoJSON uses a VARCHAR2 or CLOB column that contains geometry information in GeoJSON format. SDO_GEOMETRY uses an object type that stores spatial data using Oracle Spatial features. JSON_OBJECT is not a valid Geometry Column Data Type for maps region. Verified References: About Supported MapsEditing Maps

 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.

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

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.

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.