Oracle 1z0-144 Exam Dumps

Question 6 of 76

What is the correct definition of the persistent state of a packaged variable?

It is a private variable defined in a procedure or function within a package body whose value is consistent within a user session.

It is a public variable in a package specification whose value is consistent within a user session.

It is a private variable in a package body whose value is consistent across all current active sessions.

It is a public variable in a package specification whose value is always consistent across all current active sessions.

Correct Answer: B

The correct definition of the persistent state of a packaged variable is a public variable in a package specification whose value is consistent within a user session. This means that the value of the public variable remains the same throughout the duration of that particular user's session, providing a consistent state for the session without affecting other sessions.

Question 7 of 76

Examine the following block of code:

Which line in the above code would result in errors upon execution?

line 5

line 8

line 2

line 7

Correct Answer: B

In line 8, the code is attempting to assign a BOOLEAN value to a VARCHAR2 type variable. In PL/SQL, this is not allowed since the two types are incompatible. This will result in an error. Specifically, PL/SQL will throw an error like 'PLS-00382: expression is of wrong type' when it encounters this type of assignment.

Question 8 of 76

View the Exhibit and examine the structure of the customer table.

Examine the following trigger code:

What is the outcome when the above trigger is compiled?

It compiles successfully.

It gives an error because the when condition is not valid.

It gives an error because when cannot be used for row-level triggers.

It gives an error because the statements under updating are not valid.

It gives an error because the new qualifier in the when clause requires a colon prefix.

Correct Answer: B

The correct answer is that it gives an error because the WHEN condition is not valid. The correct syntax for the WHEN condition in the trigger should include a semicolon at the end of each assignment statement inside the IF and ELSEIF blocks. Additionally, the condition `NEW/cust_category IS NULL` is not correctly framed; it should be written as `:NEW.cust_category IS NULL`. Therefore, the trigger will not compile successfully.

Question 9 of 76

Which statements are true about PL/SQL procedures? (Choose all that apply.)

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

Correct Answer: B, D

Reuse of parsed PL/SQL code in the shared SQL area minimizes parsing overhead, enhancing performance. Also, PL/SQL procedures can call external procedures or functions written in other programming languages, such as Java, offering flexibility in integration.

Question 10 of 76

The STRING_TAB table has the following structure:

View the Exhibit and examine the code.

What is the outcome on execution?

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

Correct Answer: A

The procedure attempts to concatenate the string 'This is my test string.' with itself and a '+', resulting in a string that is longer than 25 characters, which leads to a VALUE_ERROR being raised. The exception handler in the procedure catches this error, prints 'Output buffer not long enough.', and then the main block continues execution, resulting in 'This is my test string.-' being printed. Thus, it displays 'Output buffer not long enough. This is my test string.-.'