Free Oracle 1z0-771 Practice Exam with Questions & Answers

Authorization Schemes in APEX can be evaluated at:

Once per page view: Checks authorization each time a page is rendered.

Master-detail pages in APEX link a master dataset (e.g., list of orders) to its details (e.g., order items). The requirements demand:

C. Side by Side: This layout places the master region (e.g., an Interactive Report) and detail region (e.g., a Form or Grid) horizontally on the same page. Selecting a master row updates the detail region via AJAX, allowing interaction with both regions without navigation. It’s ideal for workflows needing simultaneous visibility (e.g., editing details while browsing masters).

A. Drill Down: Master links to a separate detail page, requiring navigation, which violates the "without leaving the page" condition.

The Link Column in an Interactive Report adds a clickable link to each row. The true statement is:

It is not possible to exclude Link Column: Once defined in the report attributes, the Link Column is mandatory and cannot be hidden or excluded via end-user controls (e.g., Column Management). It’s always rendered unless removed by the developer.

Custom target: False; custom targets (e.g., URLs, pages) can be defined.

Always last column: False; its position is configurable.

Push Notifications in Oracle APEX enable real-time messaging to users’ devices via Progressive Web App (PWA) capabilities. The component responsible for storing messages is:

A. Queue: ThePush Notification Queue(managed internally by APEX and accessible via APIs like APEX_PWA.PUSH_QUEUE) temporarily holds messages scheduled for delivery. When a notification is created (e.g., via APEX_PWA.SEND), it’s added to this queue, awaiting processing by the APEX mail system or an external push service. The queue ensures reliable delivery, even if the user is offline temporarily, as messages are dispatched once connectivity is restored.

B. Application: The application defines the PWA settings and logic but doesn’t store messages; it’s the container, not the storage mechanism.

Page Designer’s layout modes under Utilities adjust the workspace:

A. Two Pane: Splits into two vertical sections (e.g., tree and properties), ideal for focusedediting.

B. Three Pane: Adds a third section (e.g., tree, grid, properties), offering a balanced view for complex pages.

C. Four Pane: Not available; APEX limits to three for usability.

Push notifications in Oracle APEX are enabled at theapplication level. This allows the application to register with the Progressive Web App (PWA) framework and manage subscriptions for all end users. Once enabled in the Application Definition under "Progressive Web App" settings, APEX handles the subscription process, and developers can use APIs like APEX_PWA.SEND to send notifications. Enabling at the region, page, or instance level is not supported for this feature.

Key truths about Oracle APEX:

APEX eliminates middle tier application logic: APEX runs entirely within the Oracle Database, using PL/SQL and SQL for logic, bypassing traditional middle-tier servers (e.g., Java EE). This simplifies architecture and boosts performance.

You can build interactive reporting apps based on data from disparate systems: Via REST Data Sources, database links, or ORDS, APEX integrates data from external systems, enabling unified reporting (e.g., combining on-premises and cloud data).

Needs client software: False; APEX is web-based, requiring only a browser.

Importing an APEX application involves transferring its definition (exported as a .sql file):

C. You cannot import an APEX application exported from the latest APEX version to an old APEX version: APEX enforces backward compatibility limits. An app exported from 23.2 (latest features like AI Assistants) can’t import into 19.2, as older versions lack support for newer metadata (e.g., APEX_AI tables). The import wizard checks the version and rejects incompatible files.

A. You cannot change the application ID: False; the import wizard prompts for a new ID if there’s a conflict or if you choose to override.

Object Browser in SQL Workshop is a GUI for managing schema objects:

B. Browse database objects of the current schema: Displays tables, views, procedures, etc., in a tree view, allowing inspection of definitions (e.g., columns, constraints) and data previews.

D. Create a lookup table based on a column in the current table: From a table’s column (e.g., DEPTNO), you can generate a lookup table (e.g., DEPT_LOOKUP) with unique values, automating reference table creation.

A. Restore dropped objects: Not supported; this requires DBA tools (e.g., FLASHBACK TABLE).

Regenerating Push Notification credentials updates the VAPID keys (public/private pair) in the PWA settings:

A. Existing Push Subscriptions invalidated: Subscriptions (in APEX_APPL_PUSH_SUBSCRIPTIONS) are tied to the old keys. New keys break this link, requiring users to re-subscribe (e.g., via browser prompts), as the push service (e.g., Firebase) can’t authenticate old subscriptions.

B. New notification server: False; the server configuration remains; only credentials change.