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

The PL/SQL block execution terminates immediately.

The CONTINUE statement cannot appear outside a loop.

The loop completes immediately and control passes to the statement after end loop.

The statements after the continue statement in the iteration are executed before terminating the LOOP.

The current iteration of the loop completes immediately and control passes to the next iteration of the loop

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.

It compiles successfully and fires whenever the specified condition is met.

It compiles successfully but does not fire even when the condition is met

It gives an error on compilation because the new qualifier is prefixed with a colon.

It gives an error on compilation because the new qualifier can be used only in row-level triggers.

It drops both the MANAGE_EMP AND EMP__DET packages because of the cascading effect.

It drops the MANAGE_EMP package and invalidates only the body for the EMP_DET package.

It returns an error and does not drop the MAMAGE_EMP package because of the cascading effect.

It drops the MANAGE_EMP package and invalidates both the specification and body for the EMP_DET package.

Each fetch retrieves the first row and assigns values to the target variables.

Each fetch retrieves the next consecutive row and assigns values to the target variables.

They produce an error because you must close and reopen the cursor before each fetch -statement.

Only the first fetch retrieves the first row and assigns values to the target variables- the second produces an error.

When a query returns multiple rows

When a column name in a where clause is unknown at compile time.

When the number of columns selected in a query is not known until run time

When a table needs to be created based on an existing table structure at run time

When privileges need to be granted to a new user to access an existing schema at run time

The execution fails because of the misplaced else clause.

The execution is successful even if there is no employee with EMPLOYEE_ID 115.

The execution falls and throws exceptions if no employee with EMPLOYEE_ID us is found.

The execution is successful, but it displays an incorrect output if no employee with EMPLOYEE_ID 115 is found.

Add exception handlers whenever errors occur.

An exception handler should commit the transaction.

Handle named exceptions whenever possible instead of using when others in exception handlers.

Instead of adding exception handlers to your PL/SQL block, check for errors at every point where they may occur.

It executes successfully but no error messages get recorded in the DEBUG_OUTPUT table

It executes successfully and any error messages get recorded in the DEBUG_OUTPUT table.

It gives an error because PRAGMA AUTONOMOUS_TRANSACTION can be used only in packaged procedures.

It gives an error because procedures containing PRAGMA AUTONOMOUS_TRANSACTION cannot be called from the exception section.

The procedures can be either stand-alone or packaged.

The procedures should be created only as packaged subprograms

The procedures should be created only as stand-alone subprograms

Each subprogram's formal parameters should differ in both name and data type.

The formal parameters of each subprogram should differ in data type but can use the same names.

When you want to retrieve an entire row from a table and perform calculations

When you know the number of elements in advance and the elements are usually accessed sequentially

When you want to create a separate lookup table with multiple entries for each row of the main table, and access it through join queries

When you want to create a relatively small lookup table, where the collection can be constructed on memory each time a subprogram is invoked.

A row trigger fires once even if no rows are affected.

A statement trigger fires once even if no rows are affected.

Row triggers are useful if the trigger action depends on the data of rows that are affected or on data that is provided by the triggering event itself.

Statement triggers are useful if the trigger action depends on the data of rows that are affected or on data that is provided by the triggering event itself.