1z0-770 Sample Questions Answers

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]

APEX automation is a feature that allows you to automate tasks such as data loading, data synchronization, application export and import, and REST API calls by using declarative actions or PL/SQL code blocks. You can create automation tasks by using the Database Actions interface or by using the APEX_AUTOMATION package. To log messages to the execution log in APEX automation, you can use the APEX_DEBUG package with any of its logging levels (info, warning, error, etc.). The other options are not valid methods of logging messages in APEX automation. Verified References: [Using APEX Automation - Oracle Help Center], [APEX_DEBUG - 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 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]

You can apply an authorization scheme for the following components in APEX:

• A specific control such as a region, item, or button. You can select an authorization scheme from the Authorization Scheme list on the attributes page of the control. This will control the rendering and processing of the control based on the user privileges12.
• A page. You can select an authorization scheme from the Authorization Scheme list on the Security page of the page definition. This will control the access to the page based on the user privileges12.
• An entire application. You can select an authorization scheme from the Authorization Scheme list on the Security Attributes page of the application definition. This will control the access to the entire application based on the user privileges12.

You cannot apply an authorization scheme for a session, as a session is not a component in APEX. A session is a stateful connection between a browser and the APEX engine that persists across multiple requests and responses3. You can control session security by using session state protection, session expiration, and session isolation4.

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

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

The other options are incorrect because:

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

Verified References: Progressive Web ApplicationsEnabling Progressive Web Application Functionality

A bar chart is a type of chart that displays data as horizontal or vertical bars with lengths proportional to the values they represent. A bar chart can have one or more data series, which are groups of data points that share the same color and legend item. To enable “hide and show” behavior of a data series in a bar chart when its corresponding legend item is clicked, you need to set the Hide and Show Behavior attribute value to either Rescale or No Rescaling. The Hide and Show Behavior attribute determines how the chart behaves when a data series is hidden or shown by clicking on its legend item. The possible values are:

• None: The chart does not support hiding or showing data series by clicking on legend items.
• Rescale: The chart supports hiding or showing data series by clicking on legend items, and rescales the axes accordingly.
• No Rescaling: The chart supports hiding or showing data series by clicking on legend items, but does not rescale the axes. Setting the on Data Change attribute value to slide to Left will not affect the “hide and show” behavior of a data series in a bar chart. This attribute determines how the chart behaves when new data is loaded, such as when using dynamic actions or refresh actions. The possible values are:
• None: The chart does not animate when new data is loaded.
• Slide to Left: The chart slides to the left when new data is loaded.
• Slide to Right: The chart slides to the right when new data is loaded. Verified References: [Creating Bar Charts - Oracle Help Center], [Bar Chart Attributes - Oracle Help Center]

A drill down master detail form allows you to create a master detail form that contains two pages based on two related tables or views. The first page contains an interactive report for the master table. The second page features a standard form for the master and interactive grids for the detail. You can use the Create Page wizard to create a drill down master detail form. References: Creating Master Detail Forms and [Creating a Drill Down Master Detail Form]

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]

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;

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

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

A 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

The main components of an APEX workspace homepage are:

• Gallery: This component displays various sample applications, blueprints, plug-ins, themes, and learning resources that you can use to get started with Oracle APEX.
• SQL Workshop: This component allows you to view and manage the database objects in your schema, such as tables, views, indexes, etc. You can also use this component to run SQL queries or scripts, load or unload data from the database, generate DDL statements, view object reports, and restore dropped objects.
• App Builder: This component allows you to create and edit your applications using the Create Application Wizard or the Page Designer. You can also use this component to import or export applications from files or URLs, run or debug applications, manage application settings, and access various utilities.

The other option is incorrect because:

• RESTful Services: This component is not part of the APEX workspace homepage. It is part of the SQL Workshop component. It allows you to create and manage RESTful web services based on your database objects or SQL queries.

Verified References: [About the Workspace Home Page] [About SQL Workshop] [About App Builder]

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.

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]

When a table or a SQL query returns many rows, an interactive grid is best displayed to the user with pagination. Pagination enables users to navigate through large data sets by displaying a subset of data at a time3. The two types of pagination available for interactive grids are Page and Scroll3. Page pagination displays a fixed number of rows per page and provides controls to navigate between pages. Scroll pagination displays rows as the user scrolls down the grid and fetches more data as needed

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

The other options are incorrect because:

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

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

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]

Commands allow you to execute SQL statements or PL/SQL blocks to create, edit, view, run, and delete database objects. One of the features of SQL Commands is the ability to unload data from the database to a CSV file. You can do this by clicking the Download button after running a query that returns data. Verified References: 34

A theme is a collection of templates and stylesheets that define the layout and appearance of an application. You can create a custom theme for an application by using the Create Theme Wizard or by copying an existing theme. If you want to use a custom theme for anotherapplication in the same workspace, you can copy the theme to that application by using the Copy Theme option in Shared Components. However, if the master theme (the original theme) may still require changes, you need to subscribe the copied theme to the master theme and refresh the theme whenever there are changes in the master theme. This solution guarantees that any changes to the master theme are reflected in the copied theme by using a synchronization process that updates templates and stylesheets based on their subscription status. Verified References: [Creating Themes - Oracle Help Center], [Managing Theme Subscriptions - 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.

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]

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.

All of the options listed are different kinds of page components that you can create in APEX. A page component is an area of a page that serves as a container for content. Each page component contains a different type of content, such as HTML, a report, a form, a chart, a list, a breadcrumb, PL/SQL, a tree, a URL, or a calendar. You can create page components by using the Create Page Wizard, dragging and dropping from the Gallery pane in Page Designer, or using the context-sensitive menu in the Rendering tree in Page Designer.

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]

The commission yn column will restrict acceptable values to TRUE or FALSE because of the /check modifier in the column name. This modifier adds a check constraint to the column based on the values specified after it. The yn suffix indicates that the column is of type VARCHAR2(1). The other options are incorrect because they do not reflect the effect of the /check modifier or the yn suffix. Verified References: Using Quick SQLAbout Quick SQL Shorthand Syntax

When you create an Access Control Page using the Create Page Wizard, three of the following Access Roles get created: Reader, Administrator, and Contributor. These roles are predefined by APEX and correspond to the authorization schemes that control the access to the application, pages, or page components1. Reader role grants read-only access to the application. Administrator role grants full access to the application, including administrative and edit privileges. Contributor role grants edit privileges to the application, but not administrative privileges2. Developer role is not a default Access Role created by the wizard, but you can create your own custom roles and assign them to users on the Application Access Control page.

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.

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.

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.

The Approvals Component is a feature in Oracle APEX that enables you to create and manage tasks for user approval. The Approvals Component deals with all aspects of human approval in Oracle APEX, allowing you to put approval functionality into your applications. The Approvals Component creates one or more tasks for items that require approval based on a pre-configured template, known as the Task Definition. The Task Definition specifies the data source, display attributes, potential owners, business administrators, and available actions for the tasks. You can set up task approvers and administrators at design time or determine them dynamically at runtime based on data related to the task. For example, you can use a SQL query or a PL/SQL function to return the list of potential owners or business administrators for each task based on some criteria, such as department, role, or location.

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.

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.

When the customer name is clicked in the report, the Customer Details form dialog page is displayed. This is a page rendering event, which means the page is generated and sent to the browser. When the items in the form dialog are updated and the user clicks Apply Changes, the page process is executed and the items from the page are used to update and commit the underlying table in the Oracle Database. This is a page processing event, which means the page is submitted to the server and processed by APEX. Page validation is also a part of page processing, but it is not a separate event. Page refresh is not an event, but an action that can be triggered by a dynamic action or a process

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]

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