1Z0-141 試験問題を無料オンラインアクセス

You are developing a Human Resources application, and you create an Employees button in the Departments form. The When-Button-Pressed trigger calls the Employees form to display the employees in the current department. You have set the Employees button properties so that navigation to the button does not occur. The Validation Unit property of the Departments form is set to Item.
You want to ensure that the Department ID is valid prior to calling the Employees form, even if the user has updated the Department ID and has not navigated out of that item. The
Department_Id item has a When-Validate-Item trigger that performs some complex validation logic.
What code in the When-Button-Pressed trigger would force the When-Validate-Item trigger to fire for the Department_Id item without navigating from the item?

• A.ENTER;
• B.SET_ITEM_PROPERTY(:SYSTEM.CURSOR_ITEM,ITEM_IS_VALID,
  PROPERTY_TRUE);
• C.SET_FORM_PROPERTY('departments',VALIDATION,
  PROPERTY_TRUE);
• D.REDISPLAY;
• E.You cannot programmatically cause validation without navigation.
• F.SYNCHRONIZE;

The Orders table in the database contains several thousand records. There is a block in the Orders form that is based on the ORDERS table and displays one record. The block is ordered by the Order_Date in descending order, because order entry clerks usually must access only the most recent orders.
Which one of the following combinations of property settings for the Orders block will provide the fastest response time before a record appears in the block upon executing a query?

• A.Query Array Size: 0
  Number of Records Buffered: 1000
  Query All Records: No
• B.Query Array Size: 1000
  Number of Records Buffered: 0
  Query All Records: Yes
• C.Query Array Size: 0
  Number of Records Buffered: 0
  Query All Records: Yes
• D.Query Array Size: 1000
  Number of Records Buffered: 0
  Query All Records: No
• E.Query Array Size: 0
  Number of Records Buffered: 1000
  Query All Records: Yes

View the Exhibit.
You are attempting to drag the Control and CV_Order objects to an object group as shown in the exhibit, but you are unable to release them in the Object Group Children node of the object group.
What is the reason for this?

• A.You should drag them to the ObjectGroup96 node, not to its Object Group Children node.
• B.You need separate object groups for different types of objects.
• C.You cannot drag a block to an object group.
• D.You cannot drag multiple types of objects to an object group at the same time.
• E.You cannot drag a canvas to an object group.

View the Exhibit and examine the PL/SQL code. The code uses the valmess package, which should print out the employee's salary if it exceeds 2345.
To resolve compiler or run-time errors and ensure that the code works as intended, what changes should you make to the trigger code?

• A.Define an EXCEPTION section to handle exceptions.
• B.Delete the BEGIN and END keywords.
• C.No changes are required.
• D.Define a DECLARE section to declare PL/SQL variables.
• E.Pass the Forms variable to the package function with the format
  :block_name.item_name.

View the Exhibit.
You are developing an Order Entry form. The When-New-Form-Instance trigger executes a query on the only block in the form. Instead of the alert shown in the exhibit, when the query cannot be performed you want to display to the user a message with the actual database error that is received.
What can you do to implement this?

• A.Place this code in a form-level On-Error trigger:
  IF ERROR_CODE = 40505 THEN
  message(DBMS_ERROR_TEXT);
  END IF;
• B.In the When-New-Form-Instance trigger, insert this code after the EXECUTE_QUERY built-in:
  IF NOT FORM_SUCCESS THEN
  message(SQLERRM);
  END IF;
• C.Add this exception handler to the When-New-Form-Instance trigger:
  EXCEPTION
  WHEN ERROR_CODE = 40505 THEN
  MESSAGE(DBMS_ERROR_TEXT);
• D.Place this code in a form-level On-Error trigger:
  IF ERROR_CODE = 40505 THEN
  message(SQLERRM);
  END IF;
• E.In the When-New-Form-Instance trigger, insert this code after the EXECUTE_QUERY built-in:
  IF NOT FORM_SUCCESS THEN
  message(DBMS_ERROR_TEXT);
  END IF;
• F.Add this exception handler to the When-New-Form-Instance trigger:
  EXCEPTION
  WHEN ERROR_CODE = 40505 THEN
  MESSAGE(SQLERRM);