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

King 17-JUN-87 1500

King 17-JUN-87 24000

King current sysdate 1500

King current sysdate 24000

All the exceptions in the code are trapped by the exception handler.

All the "no data found" errors in the code are trapped by the exception handler.

The PL/SQL program does not execute because an exception is not declared in the declare section.

An exception handler in the code traps the "no data found" error after executing the handler code and the program flow returns to the next line of code.

The program abruptly terminates and an exception is raised.

The program executes successfully and the output is No ROWS_FOUND.

The program executes successfully and the query fetches a null value in the V_LNAME variable.

Program executes successfully, fetches a NULL value in the V_LNAME variable and an exception is raised.

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.

line 5

line 8

line 2

line 7

It executes and displays null.

It executes and the condition returns true.

It executes and control goes to the else statement.

It fails because no value is assigned to the v_myage variable.

Delete operations cannot be performed using the instead of triggers.

The instead or triggers must be created to add or modify data through any view.

The instead of triggers can be written only for views, and the before and after timing options are not valid.

The check option for views is not enforced when Insertions or updates to the view are performed by using the instead of trigger.

Because the procedure call in the trigger is not valid

Because the condition specified in the when clause is not valid

Because both the procedure and trigger access the same table

Because the WHEN clause cannot be used with a row-level trigger

Because the column list specified with UPDATE in the trigger is not valid

It executes successfully.

It generates a run-time exception.

It does not execute because of syntax error

It executes successfully and generates a warning.

Bind

Parse

Fetch

Execute