View the Exhibit.

The Departments form has form level triggers defined as shown in the Exhibit. You have enabled array DML for the Departments block by setting its DML array size to 5 and setting the Primary Key property of Department id to Yes. You set runtime preferences for Forms Builder to use array processing.
You want to test that array processing is actually occurring, so, as shown in the Exhibit, the On-Update, On-Delete, and on insert triggers have code that:
1. Displays a message to indicate which trigger is firing for which record?
2. Does the thing (either updates, deletes, or inserts)
The other triggers simply display a message, indicating the trigger that is firing.
You run the form from Forms Builder, but from the messages, you can tell that array processing is not occurring. What should you change so that array DML gets implemented?

• A. Set the Enforce Primary Key property of the Department block to Yes; it is not enough to just set the Department_Id to be the primary key.
• B. Set the DML array size to a value of 10 or greater; for array sizes loss than 10, array processing Is inefficient, and so is not performed.
• C. Use the SYNCHRONIZE built-in after the MESSAGE built-in; otherwise, the message are not displayed until the processing is finished, giving the appearance that array processing is not taking place.
• D. Delete the "On-" triggers; these triggers remove default processing, including array processing.

Users do not want to see the "Working" message while a long query completes.
You are designing a form with a query that takes o long time to execute. What can you do to stop the "Working" message from appearing?

• A. You do not need to do anything, the default behavior of Forms is to display the
  "Working" message only if you add code to do so.
• B. Before the line of code that executes the query, add the line:
  :SYSTEM.SUPPRESS_WORKING : = 'TRUE';
• C. Use the SET_APPLICATION_PROPERTY built-in to set the message level in a When- New-Form-instance trigger.
• D. Before the line of code that executes the query, add the line:
  :SYSTEM.MESSAGE_LEVEL := '10';

You want to display employee records in tabular format, but the form is not wide enough to display all the items in the Employees block. The employee IDs and names of displayed records should always be visible, but you want to scroll the additional information as users tab through the Items, the form should look like a spreadsheet with the first two columns frozen.
Which canvas types would be most appropriate in this scenario?

• A. content canvas and a stacked canvas with a horizontal scroll bar
• B. multiple content canvases
• C. content canvas and a tab canvas with multiple tab pages
• D. content canvas in a window with a horizontal scroll bar
• E. content canvas and multiple tab canvases

You have installed WebLogic and Forms with a default configuration, which has been tested and determined to be correct.
After creating a basic form in the Forms Builder, you click Run Form to test it. Forms Builder displays an error dialog box with the following message:
FRM-10142: The HTTP Listener is not running on <host> at port 9001.
Please start the listener or check your runtime preferences.
What is one action that you can take to resolve this error?

• A. Start the Oracle HTTP server.
• B. Start WebCache.
• C. Start the WLS_FORMS managed server.
• D. Start the Web Logic Administration server.
• E. Change the serverURL parameter in formsweb.cfg