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

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]

Custom Apps are specific to your workspace and are only available if your instance administrator has enabled them. You can install Sample Apps and Starter Apps directly from the Gallery or download them from GitHub. Sample Apps and Starter Apps are available with every Oracle APEX workspace. References: Using the App Gallery and Configuring the Application Gallery

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.

An interactive grid is a customizable report that allows end users to modify the data and layout of the report. End users can change the report layout by using the Actions menu or by dragging and dropping columns. They can also create private reports that save their personal preferences for the report. These features are available for both editable and noneditable interactive grids. Verified References: Using an Interactive Grid - Oracle Help Center, Example Interactive Grid - Oracle Help Center

Theme Styles in Oracle APEX are CSS style sheets that are added to the base CSS of a theme to alter the look and feel of an application. A theme can have multiple theme styles with one style set as current. When the Is Public attribute is enabled for a theme style, end users can choose the theme style from the runtime environment by using the Theme Style Switcher component. This allows end users to customize the appearance of the application according to their preferences. Verified References: Using Themes and Theme Styles - Oracle Help Center, Theme Styles - Oracle APEX

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.

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.

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]

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.

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]

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]

Data Workshop is a feature in Oracle APEX that enables you to load and unload data to and from the database. You can use Data Workshop to copy data between Oracle databases or between an Oracle database and external files. Data copying is accomplished by exporting and importing data, and by unloading and loading data. While migrating apps, once the database objects are created in the target environment, you can load the data using Data Workshop by following these steps:

• Access Data Workshop by clicking Utilities and then Data Workshop in SQL Workshop.
• Click Load Data.
• Select a data source type, such as Text File (CSV), XML File (XML), Copy & Paste (Spreadsheet), or Object Store Reference (Autonomous Database only).
• Specify a file name or location for your data source.
• Select a table name for your data destination.
• Map your data columns to your table columns.
• Review your data load settings and click Load Data.

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. 

d event under the Drag and Drop PL/SQL Code attribute of the Calendar component. This attribute allows you to write PL/SQL code to update the event row in the database after the user drags and drops an event on the calendar. To reference the ID, the new start date, and the new end date of the dragged event, you can use these bind variables: :APEX.PK_VALUE, :APEX.NEW_START_DATE and :APEX.NEW_END_DATE. These variables are automatically populated by APEX when the user performs a drag and drop action on the calendar. For example, you can write something like this:

UPDATE events

SET start_date = :APEX.NEW_START_DATE,

end_date = :APEX.NEW_END_DATE

WHERE id = :APEX.PK_VALUE;

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]

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.

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]

Theme Styles in Oracle APEX are CSS style sheets that are added to the base CSS of a theme to alter the look and feel of an application. A theme can have multiple theme styles with one style set as current. When the Is Public attribute is enabled for a theme style, end users can choose the theme style from the runtime environment by using the Theme Style Switcher component. This allows end users to customize the appearance of the application according to their preferences. Verified References: Using Themes and Theme Styles - Oracle Help Center, Theme Styles - Oracle APEX

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.

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.

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 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 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 dynamic action, you need to specify at least three options: what action or actions are performed, when the action occurs, and what elements are affected by the action1. The action is the behavior that you want to happen when the event is triggered. You can choose from a list of predefined actions or create your own custom action using JavaScript code1. The event is the user interaction or condition that causes the dynamic action to fire. You can select an event from a list of available events based on the type of element you select1. The affected elements are the items, buttons, or regions that are affected by the action. You can select one or more elements by using jQuery selectors1. You do not need to specify why the action is performed, as this is not a required option for creating a dynamic action.

A Faceted Search and a Smart Filter are two types of pages that behave similarly in functionality. They both allow users to filter data based on multiple criteria and see the results in real time. They differ in the following aspects:

• A Faceted Search uses facets to filter data. A facet is a set of filters based on a column or expression. A facet can be displayed as a list, a range slider, a star rating, or a chart.
• A Smart Filter uses conditions to filter data. A condition is a logical expression that evaluates to true or false. A condition can be based on a column, an item, or a function.

The other options are incorrect because:

• A Map is a type of region that displays spatial data on an interactive map. It allows users to zoom, pan, and select features on the map.
• A Cards is a type of region that displays data in a grid of cards. Each card represents one row of data and can contain text, images, icons, or buttons.

Verified References: [About Faceted Search] [About Smart Filter] [About Maps] [About Cards]

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.

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

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

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

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

 Public reports are available to all users who can access the interactive grid1. However, to enable an end user to save a public interactive grid report, the user must have the required permission. By default, only developers can save public reports1. Any user may save private interactive grid reports, but only the user who creates a private report can view, save, rename, or delete it12. Verified References: 12

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.

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.

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

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

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 stacked master detail is a form type that displays two editable interactive grids based on two related tables or views on the same page. Users select a row in the master grid to update the detail grid6. In this scenario, the departments names with location on the left is the master grid and the employees details on the right is the detail grid. A cards report is not a form type, but a report type that displays data in cards with an image and text7. A side by side master detail is a form type that displays two editable interactive grids based on two related tables or views side by side on the same page. Users select multiple rows in the master grid to update multiple detail grids6. An interactive report is not a form type, but a report type that allows users to customize the report layout and filter data interactively5.

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