You created a LOV based upon a three-column Record Group called CUST, which was created at design time.
View the Exhibit and examine the structure of the CUST Record Group.
At run time, the user sometimes requires the LOV to be populated from the PROD Record
Group.
Which two built-ins will enable you to create the PROD Record Group and repopulate the
LOV? (Choose two.)

• A. CREATE_GROUP_FROM_QUERY ('PROD',
  'SELECT rownum as Index, P_id as ID, '||
  'Name as Desc, date_sold as Date '||
  'from products ' );
• B. CREATE_GROUP_FROM_QUERY ('PROD',
  'SELECT P_id, '||
  'date_sold as Date, Name as Desc '||
  'from products ' );
• C. CREATE_GROUP_FROM_QUERY ('PROD',
  'SELECT P_id as ID, '||
  'Name as Desc, date_sold as Date '||
  'from products ' );
• D. RETRIEVE_LIST(lov_id, 'PROD');
• E. POPULATE_LIST(lov_id, 'PROD');
• F. SET_LOV_PROPERTY(lov_id,GROUP_NAME,'PROD');

You create a text item in the Object Navigator. Which property must you change from the default value so that the text item will not be part of the SQL statement when a query is issued on the block?

• A. Column Name
• B. Validate from List
• C. Database Item
• D. Calculation Mode
• E. Conceal Data
• F. Item Type
• G. Query Allowed

The following On-Error trigger was written to give users a more meaningful message when they press the Up key when the cursor is in the first record (the FRM-40100 error) and to display default messages for all other errors:
IF message_code = 40100 THEN
MESSAGE('You are already at the first record');
ELSE
MESSAGE(message_type || '-' ||
to_char(message_code) || ': ' || message_text);
END IF;
When you test the form, you still get the FRM-40100 message when you press the Up key while the cursor is in the first record. Your custom message does not appear.
What corrections can you make so that the code functions properly?

• A. Eliminate the to_char function because message_code is a varchar2 value.
• B. Change all occurrences of message_code, message_type, and message_text to
  DBMS_error_code, DBMS_error_type, and DBMS_error_text.
• C. To keep the remaining code from executing, add after the second line:
  RAISE FORM_TRIGGER_FAILURE;
• D. Change all occurrences of message_code, message_type, and message_text to error_code, error_type, and error_text.

The validation unit for the Orders form is set to Item. This master-detail form contains an
Orders block and a multirecord Order Items block. Why might you want to create a When-
Validate-Record trigger on the Orders block in this form?

• A. to check that all items in the Order Items block whose Required property is set to Yes have values
• B. to check that the shipping date for the order is not earlier than the order date
• C. to perform some logic every time a user navigates to a different record in the queried block
• D. to check that all items in the Orders block whose Required property is set to Yes have values

To centralize some of your processing, you decide to write PL/SQL library modules that contain procedures that can be called from form triggers or menu items. You need to populate some fields based on values in other fields. Which code do you use?

• A. IF 'ORDERS.order_total' > 10000
  THEN
  'ORDERS.large_order' := 'Y';
  MESSAGE('WARNING - large order!');
  END IF;
• B. IF NAME_IN('ORDERS.order_total') > 10000
  THEN
  COPY('Y','ORDERS.large_order');
  MESSAGE('WARNING - large order!');
  END IF;
• C. IF FIND_ITEM('ORDERS.order_total') > 10000
  THEN
  FIND_ITEM('ORDERS.large_order') := 'Y';
  MESSAGE('WARNING - large order!');
  END IF;
• D. IF :ORDERS.order_total > 10000
  THEN
  COPY('ORDERS.large_order','Y');
  MESSAGE('WARNING - large order!');
  END IF;
• E. IF :ORDERS.order_total > 10000
  THEN
  :ORDERS.large_order := 'Y';
  MESSAGE('WARNING - large order!');
  END IF;