Oracle 1z0-144 Oracle Database 11g: Program with PL/SQL Exam Practice Test

Both blocks compile and execute successfully when called.

Both blocks compile successfully but the CALC_SAL procedure gives an error on execution.

The CALC_SAL procedure gives an error on compilation because the amt variable should be declared in the RAISE_SALARY procedure.

The CALC_SAL procedure gives an error on compilation because the RAISE_SALARY procedure cannot call the stand-alone increase function.

It displays

Output buffer not long enough.

This is my test string.-.

It displays only

Output buffer not long enough, and exits the anonymous block.

It displays only

This is my test string. - Because EXCEPTION should have been defined in the anonymous block to get the error message.

It does not display any of the MEMS_PUTPUT messages and gives an error because a transaction control statement cannot be used in the exception section of a procedure.

It goes into an infinite loop.

It executes successfully and displays only the list of faculty names.

It does not execute and displays an error message because the end-of-file condition is not taken care of.

It executes successfully and displays the list of faculty names followed by a "no data found” error message.

It issues a warning whenever ERROR: 05003 occur during compilation.

It causes the compilation to fail whenever the warning ERROR.05003 occurs.

It issues warnings whenever the code causes an unexpected action or wrong results performance problems.

It causes the compilation to fail whenever the code gives wrong results or contains statements that are never executed.

SCOTT’S session displays 5, and then 0, greets session displays 0.

SCOTT’S session displays 5, and then 0; green's session displays 5.

SCOTT’S session displays 5, and then 5 again, green's session displays 0.

SCOTT’S session displays 5, and then 5 again; green's session displays 5.

It executes successfully and gives the desired output.

It does not execute because the definition of type population is indexed by VARCHAR2.

It executes, and the string keys of an associative array are not stored in creation order, but in sorted order.

It does not execute because the value that is once assigned to the element of the associative array cannot be changed.

The code executes successfully and gives the desired output.

The code generates an error because the EMP_RECORD variable is not declared.

The code generates an error because the cursor is not opened before the FOR loop.

The code generates an error because the loop does not have the exit when clause.

All the blocks execute successfully and the anonymous block displays

1

2

3

cant: 45

45

cnt: 45

All the blocks execute successfully and the anonymous block displays

1

2

3

cut: 0

45

cart: 1

The anonymous block gives an error because the function invocation in line 2 is not valid.

The procedure creation gives an error because the function invocation in line 1 is not valid.

The function goes through only the parse and executes phases.

The function goes through the parse, bind, and execute phases.

The function goes through the parse, bind, execute, and fetch phases.

All the processing phases for the function are performed only at run time.

Only the EXECUTE IMMEDIATE statement inside the function is parsed at run time.

Users with definer's rights who are granted access to a procedure that updates a table must be granted access to the table itself.

Reuse of parsed PL/SQL code that becomes available in the shared SQL area of the server avoids the parsing overhead of SQL statements at run time.

Depending on the number of calls, multiple copies of the procedure are loaded into memory for execution by multiple users to speed up performance.

A PL/SQL procedure executing on the Oracle database can call an external procedure or function that is written in a different programming language, such as C or Java.

It should be an after trigger.

It should be a before trigger.

It should be a row-level trigger.

It should be a statement-level trigger.

It can be a before or an after trigger.

The trigger is fired, a message is displayed, and the update is successful

The trigger is fired and a message is displayed, but the update is rolled back.

The trigger is not fired because the when clause should be used to specify the condition, however, the update is successful.

The trigger is not fired because column names must be specified with the update event to identify which columns must be changed to cause the trigger to fire, however, the update is successful.

The PL/SQL wrapper detects and reports only syntax errors.

The PL/SQL wrapper detects and reports both syntax and semantic errors.

When wrapping a package or object type, both the body and specification should be wrapped.

When wrapping a package or object type, only the body should be wrapped, not the specification.

To change a wrapped object, the original source code needs to be modified and then wrapped again

To change a wrapped object, the wrapped code can be unwrapped, modified In a text file, and then wrapped again.

It displays null if no employee with employee_id 123 exists.

It produces the ora-01403: no data found error if no employee with employee_id 123 exists.

It displays an error because the select into clause cannot be used to populate the PL/SQL record type.

The code executes successfully even if no employee with employee_id 123 exists and displays Record Not Found.

Use the TO_DATE function in line 2.

Use the TO_DATE function in line 7.

Use the TO_NUMBER function in line 6.

Use both the TO_DATE function in line 2 and the TO_NUMBER function in line 6.