Free 1Z0-771 Practice Test Questions and Answers (2026)

Workflow parameters and page items in APEX support:

B . NUMBER: For numeric values (e.g., 123.45), used in calculations or IDs.

C . CLOB: For large text (e.g., descriptions), stored as character large objects.

D . VARCHAR: For variable-length strings (e.g., EMPLOYEE_NAME), capped at 4000 characters in most

cases.

A . Image: Not a supported data type for parameters or items; images are handled as BLOBs or file

uploads, not directly as a Workflow parameter type.

These types align with Oracle Database, ensuring robust data handling in workflows.

Reference: Oracle APEX 23.2 Documentation - "Workflow Parameters" under Workflow Features.

The Data Workshop utility in APEX is designed to load and unload table data only, not other schema

objects like procedures or views. Option A is false because XLSX files with multiple worksheets are

supported (each worksheet can be mapped to a table). Option B is incorrect as it’s limited to table

data. Option D is partially true but not the most precise answer, as "multiple tables at a time"

depends on the process, whereas C is universally accurate.

Reference: Oracle APEX 23.2 Documentation - "Using Data Workshop" under SQL Workshop.

Faceted search pages in APEX provide dynamic filtering. The true statements are:

Faceted Search supports the ability to filter columns storing multiple values: Facets can handle multi-

value columns (e.g., comma-separated lists or JSON arrays) using appropriate SQL (e.g., INSTR or

JSON_TABLE), enabling complex filtering scenarios like tags or categories.

Facets map to specific database columns: Each facet is tied to a column in the underlying query (e.g.,

DEPTNO or JOB), ensuring data-driven filtering.

Multiple charts are not visible in the same region: False; multiple facets can display charts within the

same region, depending on settings.

A facet’s chart can be seen only in a nonmodal dialog: False; charts can appear inline or in dialogs,

configurable via facet attributes.

This functionality makes faceted search ideal for exploratory data analysis.

Reference: Oracle APEX 23.2 Documentation - "Managing Faceted Search" under Regions.

By default, faceted search can "batch" changes, requiring an "Apply" button click to filter the report.

To enable automatic filtering:

Disable the Batch Facet Changes attribute: In Page Designer, under the Faceted Search region’s

Attributes, setting "Batch Facet Changes" to "No" ensures the report refreshes immediately when a

facet value is selected, improving responsiveness. This triggers an AJAX call to update the report

without a manual submit.

Show Facet Name: This controls facet label visibility, unrelated to filtering behavior.

Client-Side Filtering: This applies to Interactive Reports/Grids, not faceted search regions, and isn’t

the correct solution here.

This adjustment enhances the user experience by providing instant feedback.

Reference: Oracle APEX 23.2 Documentation - "Faceted Search Attributes" under Region Properties.

To use REST-enabled SQL in APEX:

Install ORDS 19.x or later: Oracle REST Data Services (ORDS) must be installed and configured on the

remote database.

REST-enable the schema: The schema on the remote database must be REST-enabled using

ORDS.ENABLE_SCHEMA to allow SQL execution via REST.

A database link is not required, and installing APEX on the remote database is unnecessary since

REST-enabled SQL connects APEX to a remote schema via ORDS.

Reference: Oracle APEX 23.2 Documentation - "Using REST-Enabled SQL" under Data Sources.

In Oracle APEX Workflow, only one instance of a workflow can exist in the "In Development" state at

a time. This ensures that developers work on a single draft version before publishing it. Multiple

instances are allowed in other states (e.g., "Published"), but not during development.

Reference: Oracle APEX 23.2 Documentation - "Managing Workflows" under Workflow Features.

Declarative options for downloading BLOB/CLOB content include:

Download Dynamic Action: A built-in action type to trigger downloads of BLOB/CLOB data.

Download Page Process: A process type that declaratively handles BLOB/CLOB downloads from a

table.

APEX_UTIL.DOWNLOAD is a PL/SQL API, not a declarative option, and Share Dynamic Action is for

sharing URLs, not downloading files.

Reference: Oracle APEX 23.2 Documentation - "Downloading Files" under Dynamic Actions and Page

Processes.

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.

Cannot be sorted/hidden/moved: False; end users can sort or move it, though hiding is restricted.

This behavior ensures consistent navigation in reports.

Reference: Oracle APEX 23.2 Documentation - "Interactive Report Link Column" under Report

Attributes.

Enabling "Used by App Builder" for a Generative AI Server allows:

Author SQL powered by Generative AI: Integrates AI-driven SQL generation in App Builder.

Build applications using natural language: Enables natural language prompts to create app

components.

Options A and B are unrelated to this setting, as it’s specific to AI integration in App Builder.

Reference: Oracle APEX 23.2 Documentation - "Configuring Generative AI Server" under AI Features.

The Show AI Assistant Dynamic Action in Oracle APEX triggers the display of the AI Assistant

interface. To customize the first message users see:

Welcome Message: This attribute in the Property Editor defines the initial text displayed when the AI

Assistant appears. Setting it to "How may I help you today?" ensures this exact phrase greets users,

enhancing user experience by setting a friendly tone. It’s a static, developer-defined string, distinct

from AI-generated responses.

Initial Prompt: This attribute defines the starting input or context sent to the AI model, not the visible

message shown to users. It’s typically hidden and used to guide the AI’s behavior (e.g., "Act as a

support agent").

AI Assistant Name: This sets the assistant’s identity (e.g., "Alex"), displayed in the UI, but it’s not the

greeting message.

This configuration is critical for branding or guiding user interaction from the outset, and it’s

adjustable per dynamic action instance, offering flexibility across pages.

Reference: Oracle APEX 23.2 Documentation - "Show AI Assistant Dynamic Action" under Dynamic

Actions.

A dynamic List of Values (LOV) in APEX populates options based on a query source. The supported

types include:

Function Returning SQL Query: A PL/SQL function that returns a SQL query string (e.g., RETURN

'SELECT ename, empno FROM emp';). This offers flexibility for dynamic conditions or complex logic.

SQL Query: A direct SQL statement (e.g., SELECT ename, empno FROM emp) executed at runtime to

fetch LOV values. It’s the simplest and most common approach.

Procedure: Procedures execute logic but don’t return query results in the format required for an LOV

(they don’t produce a result set directly).

Select List: This is a UI component, not a query source type for defining an LOV.

Dynamic LOVs enhance user interaction by providing real-time, data-driven options, critical for forms

and filters.

Reference: Oracle APEX 23.2 Documentation - "Managing Lists of Values" under Shared Components.

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

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.

D . Single Pane: Not an option; the minimum is two panes.

Developers toggle these via the Utilities menu to optimize screen real estate based on task

complexity.

Reference: Oracle APEX 23.2 Documentation - "Page Designer Layout" under Utilities.

Logging in APEX tracks runtime activity:

A . apex_automation.log_info: Correctly logs an informational message to the execution log for

automation tasks (e.g., workflows). The syntax || :ENAME || concatenates the item value (e.g.,

"JOHN") into "SAL for JOHN increased by 19." It’s stored in APEX_AUTOMATION_LOG, viewable in

Monitoring.

B . apex_debug.info: Logs to debug output, but the syntax is flawed (:ENAME || isn’t concatenated

properly; should be 'SAL for ' || :ENAME || ...). It’s valid only when debugging is enabled (e.g.,

APEX_DEBUG.ENABLE).

C . apex_error.add_error: Adds an error to the error stack for user display, not a log message.

Technical Insight: log_info is non-intrusive, unlike apex_debug, which requires debug mode, or

apex_error, which signals failure.

Use Case: Logging salary updates in a scheduled job without debug overhead.

Pitfall: Ensure :ENAME is in scope (e.g., page item).

Reference: Oracle APEX 23.2 Documentation - "APEX_AUTOMATION Package" under API Reference.

In SQL Workshop, custom stored procedures can be created using:

SQL Scripts: Allows developers to write and execute PL/SQL code directly to define stored

procedures.

Object Browser: Provides a GUI to create and edit database objects, including stored procedures, by

defining their specifications and bodies.

Quick SQL is for generating table DDL, not stored procedures, and Data Workshop is for

loading/unloading data, not creating procedures.

Reference: Oracle APEX 23.2 Documentation - "SQL Workshop Guide" under SQL Scripts and Object

Browser sections.

Validation errors in APEX default to both inline (next to the item) and notification (top of page):

C . Setting Display Location to Inline in Notification: In the validation’s properties, changing "Display

Location" to "Inline in Notification" ensures the error appears only in the notification area,

suppressing inline display. This centralizes feedback for a cleaner UI.

A . Removing Associated Item: Breaks the validation’s link to P1_SALARY, stopping it entirely.

B . Value Required: Adds a separate check, unrelated to display location.

Pitfall: Test with non-numeric input (e.g., "abc") to confirm behavior.

Reference: Oracle APEX 23.2 Documentation - "Managing Validations" under Page Processing.