[Nov-2023] Latest Oracle 1z1-770 exam dumps and online Test Engine [Q20-Q34]

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

Explanation
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

Explanation
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

Explanation
A map is a type of component that enables users 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. Three of the supported spatial geometry objects in Oracle APEX are:
Polygons: A polygon is a closed shape that consists of three or more vertices connected by straight line segments. A polygon can represent an area on a map, such as a country, a state, a city, or a building. A polygon can have different colors, patterns, or borders to indicate different attributes or categories of the data.
Heat map: A heat map is a type of visualization that uses color gradients to show the density or intensity of data values in a geographic area. A heat map can represent the distribution or variation of a numeric variable on a map, such as population, income, crime rate, or temperature.
Points: A point is a zero-dimensional shape that represents a single location on a map. A point can have different symbols, sizes, or colors to indicate different attributes or categories of the data. A point can also have a label or a tooltip to display additional information about the data.

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

Explanation
Oracle APEX is a low-code application development platform that enables developers to build scalable, secure, and data-driven web and mobile apps. Some of the statements that are true about Oracle APEX are:
APEX eliminates middle-tier application logic. APEX runs entirely within Oracle Database and does not require any additional middleware or application server to function. This simplifies the architecture and reduces the complexity, cost, and security risks of deploying applications.
You can build interactive reporting apps based on data from disparate systems. APEX supports various data sources, such as local database, REST Enabled SQL Service, REST Data Source, Web Source Module, etc. You can use these data sources to create interactive reports that allow end users to filter, sort, search, aggregate, and visualize data from different sources.
The other statements are false because:
Application definition is stored in the database. APEX stores the metadata of the application components, such as pages, regions, items, buttons, etc., in the database tables.
Processing and data manipulation is executed in the database. APEX leverages the power and performance of Oracle Database to process and manipulate data using SQL and PL/SQL.
Running an APEX app does not need client software. APEX apps are web-based and can be accessed from any browser on any device without installing any client software. Verified References: [Oracle Application Express (APEX) – Oracle Help Center], [Platform – Oracle APEX]

Explanation
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

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

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

Explanation
A validation is a rule that checks the data entered by end users before processing it. A validation of type Item is numeric checks if a page item value is a valid number. When the page is submitted, if the validation fails, an error message is displayed both in the notification area (atthe top of the page) and below the item (next to the item label). To cause the validation error to appear only in the notification area, you need to remove P1_SALARY from the validation Associated Item attribute. The Associated Item attribute specifies which page item is associated with the validation and where to display the error message if the validation fails.
Setting the value Required to Yes on P1_SALARY or setting Display Location to Inline in Notification will not affect the validation error display. Verified References: [Creating Validations – Oracle Help Center],
[Validation Attributes – Oracle Help Center]

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

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

Explanation
A button is a component that performs an action when clicked by the user. A button can have different types, styles, icons, and labels. A button can also have different behaviors, such as submitting the page, redirecting to another page or URL, or doing nothing. A button can perform any of the following actions when clicked:
Redirect to a page in the same application: This action redirects the user to another page within the same APEX application. You can specify the target page number and optionally set some attributes, such as clear cache, request, and item values.
Redirect to a page in a different application: This action redirects the user to another page in a different APEX application. You can specify the target application ID and page number and optionally set some attributes, such as clear cache, request, and item values.
Redirect
to a URL: This action redirects the user to a custom URL that you specify. You can use any valid URL format, such as http://, https://, mailto:, or javascript:.
Submit Page: This action submits the current page to the server and performs any validations, computations, processes, or branches that are defined for the page. You can also specify a request value for the button that can be used to conditionally execute some components.
Defined by Dynamic Action: This action does not submit the page or redirect to another page. Instead, the button’s behavior is defined by a dynamic action thatis associated with the button. A dynamic action is a declarative way of defining client-side behavior based on user actions or events.