Oracle 1z0-770 Dumps

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]

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]

You can access the Shared Components page from two places in App Builder: the Page Designer and the Application home page. In Page Designer, you can click on the Shared Components icon at the top of the page to open the Shared Components page in a new tab5. In the Application home page, you can click on the Shared Components link in the center of the page to navigate to the Shared Components page6. Gallery, SQL Workshop, and other pages do not have direct links to the Shared Components page.

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]

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.

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]

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.

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

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.

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]

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 friendly URL syntax 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]

The Column Heading menu of an Interactive Report provides various options to customize the report based on the selected column. The options include:

• Control Break: This option allows you to create a control break on the column, which groups the rows by the column values and inserts a header and a footer for each group. You can also apply aggregate functions, such as sum, count, or average, to the footer of each group.
• Hide: This option allows you to hide the column from the report, which reduces the clutter and improves the readability of the report. You can also show the hidden columns by using the Columns option in the Actions menu.

The other options are incorrect because:

• Group By: This option is not provided in the Column Heading menu of an Interactive Report. It is provided in the Actions menu of an Interactive Report. It allows you to group the rows by one or more columns and display the result in a chart or a pivot table.
• Delete: This option is not provided in the Column Heading menu of an Interactive Report. It is provided in the Data option in the Actions menu of an Interactive Report. It allows you to delete one or more rows from the report and the underlying table.

Verified References: [Customizing Interactive Reports] [Column Heading Menu]

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

The Approvals component in Oracle APEX is a feature that allows developers to create approval workflows for business processes that require human intervention or decision making. The Approvals component consists of three main elements: Tasks, Task List Page, and Task Details Page. The Unified Task List is a page type in the Create Page Wizard that is used to create a summary of tasks that functions like an inbox for end users. The Unified Task List displays all tasks assigned to or created by an end user along with their status, priority, due date, etc. End users can filter, sort, search, view details, and perform actions on tasks from this page. Verified References: [Using Approvals - Oracle Help Center], [Creating a Unified Task List Page - Oracle Help Center]

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]

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 Page Designer Toolbar allows you to perform various actions related to the development of an APEX page. Two of the actions that you can perform are:

• Navigate to Shared Components: This option lets you access the shared components of your application, such as lists, breadcrumbs, navigation menus, and so on. You can edit, create, or delete shared components from this option. To access this option, click the icon that resembles a puzzle piece on the Page Designer Toolbar.
• Create a new page: This option lets you create a new page for your application using the Create Page Wizard. You can choose from different page types, such as blank page, form, report, chart, calendar, and so on. To access this option, click the icon that resembles a plus sign (+) on the Page Designer Toolbar.

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.

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.

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.

The Access Control feature pages are a set of pages that allow developers to implement role-based access control for an application. The Access Control feature pages consist of four pages: Administration, Users, Roles, and Role Assignments. The Administration page allows administrators to perform various tasks related to managing users and roles, such as:

• Add Users: Administrators can add new users to the application by entering their username, email address, password, status, etc.
• Assign roles to users: Administrators can assign one or more roles to users by selecting them from a list of available roles.
• Edit Users: Administrators can edit user details such as username, email address, password, status, etc.
• Delete Users: Administrators can delete users from the application by selecting them from a list of existing users.
• Lock/Unlock Users: Administrators can lock or unlock users by changing their status from active to locked or vice versa. You cannot create authorization schemes or create new application roles using the Administration page. You can create authorization schemes by using Shared Components > Security > Authorization Schemes. You can create new application roles by using Shared Components > Security > Access Control > Roles. Verified References: [Using Access Control - Oracle Help Center], [Creating an Administration Page - Oracle Help Center]

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

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.

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;

To hide a few columns in your interactive report, you should choose Columns from the Actions menu. This option allows you to select which columns to show or hide in your report by using checkboxes. You can also reorder or resize the columns from this option.

The other options are incorrect because:

• Filter allows you to filter the data in your report by applying one or more conditions on the columns.
• Data allows you to add, modify, or delete data in your report by using inline editing or modal dialog editing.
• Format allows you to change the appearance of your report by applying conditional formatting rules or highlighting colors.

Verified References: [Customizing Interactive Reports] [Actions Menu]

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.

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

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.

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.

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. 

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]

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]

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.

Query Builder is a component in SQL Workshop that allows you to build queries graphically without manual SQL coding. You can use Query Builder to select tables and views from your schema, join them using drag-and-drop operations, add filters andgroupings, and view the results in a grid or chart format. You can also switch to the SQL mode to view or edit the generated SQL statement.

The other options are incorrect because:

• Quick SQL is a component in SQL Workshop that allows you to generate SQL scripts for creating tables and other database objects using shorthand syntax. You cannot use Quick SQL to build queries graphically.
• SQL Commands is a component in SQL Workshop that allows you to run individual SQL statements or PL/SQL blocks interactively. You cannot use SQL Commands to build queries graphically.
• Data Workshop is a component in SQL Workshop that allows you to load or unload data from the database using various file formats. You cannot use Data Workshop to build queries graphically.

Verified References: [About Query Builder] [Using Query Builder]

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]

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 feature pages that can be created using the Create Page Wizard are About Page, Access Control, Activity Reporting, Configuration Options, Email Reporting, Feedback, Login Page, and Theme Style Selection. These pages provide application-level functionality that can be added to an existing application. Search Page and Unified Task List are not feature pages that can be created using the Create Page Wizard. Verified References: Managing Feature PagesFeature Page Types

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]