Oracle 1z0-771 Oracle APEX Cloud Developer Professional Exam Practice Test

Working Copies in APEX allow safe experimentation:

C. Get the latest updates from the Main application: "Refresh Working Copy" (in App Builder > Working Copies) pulls changes from the Main application into the Working Copy, ensuring it reflects the latest state (e.g., new pages, fixes) without overwriting Working Copy changes.

A. Merge with Main: Merging is a separate "Merge Working Copy" task.

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

The "Check Syntax" process in APEX, typically used in SQL Workshop or when validating code, authenticates usingDatabase schema credentials. These are the credentials of the schema associated with the APEX workspace (e.g., username/password of the schema like "HR"). This ensures the process has access to parse and validate SQL or PL/SQL against the database objects in that schema.

APEX Workspace Admin credentials: These are for managing workspaces, not executing database-level syntax checks.

The APEX_PWA package manages Push Notifications:

B. APEX_PWA.PUSH_QUEUE: This procedure forces immediate processing of the Push Notification queue, sending queued messages (added via APEX_PWA.SEND) to subscribed devices without waiting for the default scheduler (e.g., every 5 minutes). Example: APEX_PWA.PUSH_QUEUE; ensures a "Meeting now!" alert goes out instantly.

A. APEX_PWA.HAS_PUSH_SUBSCRIPTION: Checks if a user has an active subscription (returns BOOLEAN), not for sending.

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.

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

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

Faceted Search supports the ability to filter columns storing multiple values: Facets canhandle 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.

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.

Data Workshop in SQL Workshop is a powerful tool for importing/exporting table data:

B. You can load or unload a single table at a time: The wizard focuses on one table per operation. For loading, you upload a file (e.g., CSV) and map it to a single table; for unloading, you select one table to export (e.g., EMP to CSV). This granularity ensures precision and simplicity.

C. You can unload data from a new or existing table: Unloading (exporting) works on any table in the schema, whether newly created (e.g., via Quick SQL) or pre-existing (e.g., DEPT). The "Unload" option generates a file (e.g., CSV, JSON) from the table’s data.

D. You can load data into a new or existing table: Loading supports creating a new table from the uploaded file (e.g., CSV defines NEW_EMP) or appending/overwriting an existing one (e.g., EMP). The wizard prompts for table creation or selection.

In Oracle APEX, when configuring search functionality (e.g., in reports or faceted search), "Oracle Text" refers to a specific search type leveraging the Oracle Text engine. This is a powerful full-text search capability built into Oracle Database, supporting keyword-based searches, fuzzy matching, and indexing.

Standard: A basic SQL-based search (e.g., LIKE), not tied to Oracle Text.

List: Not a search type; it might refer to a UI component or LOV, not a search mechanism.

TheShow AI Assistant Dynamic Actionin 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").

The requirement is to allow users to pick a single employee (name and ID) from a list tied to the MANAGER_ID column in the EMPLOYEES table, implying a dynamic, searchable selection:

A. Popup LOV: This item type displays a popup window with a searchable list of values, sourced from a SQL query (e.g., SELECT ename, empno FROM employees WHERE empno IN (SELECT DISTINCT manager_id FROM employees)). It returns a single value (e.g., EMPNO) while displaying the name, perfectly meeting the need for a single selection from a related dataset.

B. Switch: A toggle (Yes/No), unsuitable for selecting from a list of employees.

The Universal Theme (Theme 42) provides pre-built components:

A. Calendar: A region type for date-based displays (e.g., events), styled with Universal Theme templates (e.g., FullCalendar integration).

B. Comments: A region type for user feedback or notes, with built-in styling and moderation options.

C. Badge: A UI component for displaying counts or statuses (e.g., "5 New"), often in navigation or lists, styled via CSS classes.

AnInteractive Gridis the report type that supports searchable, customizable data display withinline editingat runtime using mouse or keyboard. Interactive Reports are searchable and customizable but lack inline editing. Classic Reports are static, and Smart Filters is a component, not a report type.

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.