1. A
The Application Express Engine is the core component that renders pages and processes all user requests. It interprets metadata stored in the database and generates HTML output dynamically.
2. B
Page Processes are server-side operations that execute at specific points during page processing, such as after submit, after validation, or during page rendering. They handle business logic and DML operations.
3. C
Application Express Account Authentication validates users against the internal APEX workspace user repository. This is different from Database Account Authentication, which validates against Oracle database accounts.
4. A
The correct order is: Rendering (showing the page), Validations (checking user input), Processing (executing business logic), and Branching (redirecting to another page or URL).
5. B
Saved Reports allow users to save their customized Interactive Report settings including filters, columns, sorting, and highlighting. These can be saved as private or public reports.
6. B
APEX_APPLICATION_INSTALL is used to set various installation options when importing an application, such as workspace ID, schema, and application ID to use during import.
7. B
&APP_ID. returns the current application ID. &APP_USER. returns the logged-in username, &APP_SESSION. returns the session ID, and &APP_PAGE_ID. returns the current page number.
8. B
Build Options allow developers to include or exclude components from an application without deleting them. This is useful for feature toggles, A/B testing, and environment-specific configurations.
9. B
The Cards Region is specifically designed in Universal Theme to display data in a responsive card layout with built-in styling options for images, titles, descriptions, and actions.
10. B
APEX_UTIL.SET_SESSION_STATE programmatically sets the value of page items or application items. It’s commonly used in PL/SQL processes to manipulate session state values.
11. B
When ‘Fire on Initialization’ is enabled, the Dynamic Action executes automatically when the page loads, without requiring any user interaction to trigger it.
12. B
PL/SQL Function Returning Boolean authorization schemes execute a PL/SQL function that returns TRUE or FALSE to determine if the user has access to the protected component.
13. B
Page 0 (Global Page) holds components like regions, items, and buttons that appear on all pages in the application. It’s useful for global navigation elements, headers, or footers.
14. A
APEX_APPLICATION_PAGE_ITEMS is the dictionary view that contains information about all page items defined across all pages in an application, including item types, labels, and settings.
15. B
Plug-ins are developer-created extensions that add new item types, region types, dynamic actions, processes, or authentication schemes to Oracle APEX beyond the built-in components.
16. A
Email is sent using PL/SQL processes that call the APEX_MAIL package, specifically procedures like APEX_MAIL.SEND. There is no built-in ‘Email Process Type’ in APEX.
17. B
Lost Update Detection uses checksums or row versions to detect when data has been modified by another user since it was fetched, preventing the current user from unknowingly overwriting those changes.
18. B
POST is the standard HTTP method for creating new resources in REST services. GET retrieves data, PUT updates/replaces resources, and PATCH makes partial updates.
19. A
Field Size template options in Universal Theme control the width of form items. Options typically include X-Small, Small, Medium, Large, and X-Large.
20. B
APEX_JSON provides procedures and functions for generating JSON output and parsing JSON input within PL/SQL code, enabling easy JSON handling in APEX applications.
21. B
Faceted Search regions provide interactive filtering capabilities where users can filter data using multiple facets (dimensions) simultaneously, similar to e-commerce filtering.
22. B
Checksum Required – Session Level provides protection against URL tampering by requiring a valid session-level checksum for any value passed through the URL.
23. A
APEX_COLLECTION API allows developers to create, manage, and query named collections of data stored in session state. Collections are useful for temporary data storage during user sessions.
24. B
Shared Components contain reusable elements like templates, LOVs, breadcrumbs, navigation menus, authentication schemes, and other components that can be used across multiple pages.
25. B
Server-Side Conditions evaluate on the server to determine whether a component should be rendered or processed. If the condition evaluates to false, the component is skipped.
26. A
PWA settings are configured in Application Definition under the Progressive Web App section, where developers can enable PWA features and configure manifest settings.
27. A
In Interactive Grid, Save writes changes to session state (client-side model), while Submit posts the form and writes changes to the database through defined DML processes.
28. B
Globalization Support in APEX handles application translation, including translatable text, date/number formats, and language-specific messages stored in translation repositories.
29. B
APEX_WEB_SERVICE package provides procedures and functions to make HTTP requests to external REST and SOAP web services from within APEX applications.
30. C
Authorization Schemes control what users can access in an application. They can be applied to applications, pages, regions, items, buttons, and other components to restrict access.
31. B
Application Items are not associated with any specific page and are globally accessible throughout the application session. They don’t have an associated display component like page items do.
32. B
Escape Special Characters converts HTML special characters to their entity equivalents (e.g., < to <), preventing Cross-Site Scripting (XSS) attacks by ensuring HTML is not executed.
33. B
Page Groups are an organizational feature that allows developers to categorize pages for easier management in the Application Builder. They have no runtime effect on the application.
34. B
Oracle APEX applications are exported as .sql files containing the SQL and PL/SQL statements needed to recreate the application when imported into another workspace.
35. B
G_X01 through G_X10 are global variables in the APEX_APPLICATION package used to pass additional parameters during Ajax callbacks made with apex.server.process or similar methods.
36. B
APEX_DEBUG package provides procedures to log debug messages during application execution. These messages can be viewed in the Debug section of the Developer Toolbar to help troubleshoot issues.
37. B
Interactive Grid supports master-detail configurations and provides inline editing capabilities, allowing users to edit data directly within the grid without navigating to a separate form page.
38. B
Computations automatically calculate and assign values to page items or application items at specific points during page processing. They are useful for setting default values or derived values.
39. C
Maintain Session State must be set to ‘Per Session (Disk)’ or ‘Per Request (Memory)’ to allow item values to be stored and passed. Items with ‘Do Not Save Session State’ cannot receive URL values.
40. B
APEX_CUSTOM_AUTH provides utility functions for custom authentication schemes, including functions like LOGIN, POST_LOGIN, LOGOUT, GET_USERNAME, and SESSION_ID_EXISTS for session management.