Free Download 1z0-148 Examp Dump: Oracle.1z0-148.SelfTestEngine.2020-02-07.49q.vcex

File Info

Exam	Oracle Database 12c: Advanced PL/SQL
Number	1z0-148
File Name	Oracle.1z0-148.SelfTestEngine.2020-02-07.49q.vcex
Size	2 MB
Posted	Feb 07, 2020
Download	Oracle.1z0-148.SelfTestEngine.2020-02-07.49q.vcex

How to open VCEX & EXAM Files?

Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase

Coupon: MASTEREXAM
With discount: 20%

Demo Questions

Question 1

The STUDENTS table exists in your schema.

Examine the DECLARE section of a PL/SQL block:

Which two blocks are valid?

BEGIN
OPEN cursor3 FOR SELECT * FROM students;
cursor1 :=cursor3;
END;
BEGIN
OPEN stcur;
cursor1 :=stcur;
END;
BEGIN
OPEN cursor1 FOR SELECT * FROM students;
stcur :=cursor1;
END;
BEGIN
OPEN stcur;
cursor3 :=stcur;
END;
BEGIN
OPEN cursor1 FOR SELECT * FROM students;
cursor2 :=cursor1;
END;

Correct answer: AE

Question 2

Examine the code:

Which two subprograms will be created successfully?

CREATE FUNCTION p4 (y pkg.tab_typ) RETURN pkg.tab_typ IS
BEGIN
EXECUTE IMMEDIATE ‘SELECT pdt_id, pdt_name FROM TABLE (:b)’
BULT COLLECT INTO pkg.x USING y;
RETURN pkg.x;
END p4;
CREATE PROCEDURE p1 (y IN OUT pkg.tab_typ) IS
BEGIN
EXECUTE IMMEDIATE ‘SELECT f (:b) FROM DUAL’ INTO y USING pkg.x;
END p1;
CREATE PROCEDURE p2 (v IN OUT VARCHAR2) IS
BEGIN
EXECUTE IMMEDIATE ‘SELECT f (:b) FROM DUAL’ INTO v USING pkg.x;
END p2;
CREATE FUNCTION p3 RETURN pkg. tab_typ IS
BEGIN
EXECUTE IMMEDIATE ‘SELECT f (:b) FROM DUAL’ INTO pkg.x;
END p3;
CREATE PROCEDURE p5 (y pkg. rec_typ) IS
BEGIN
EXECUTE IMMEDIATE ‘SELECT pdt_name FROM TABLE (:b)’ BULK COLLECT INTO y USING pkg.x;
END p5;

Correct answer: AC

Question 3

Which two statements are true regarding edition-based redefinition (EBR)?

There is no default edition defined in the database.
EBR does not let you upgrade the database components of an application while in use.
You never use EBR to copy the database objects and redefine the copied objects in isolation.
Editions are non-schema objects.
When you change an editioned object, all of its dependents remain valid.
Tables are not editionable objects.

Correct answer: EF

Explanation:

Reference: https://docs.oracle.com/cd/E11882_01/appdev.112/e41502/adfns_editions.htm#BABEHGAF

Question 4

Which two blocks of code execute successfully?

DECLARE
SUBTYPE new_one IS BINARY_INTERGER RANGE 0..9;
my_val new_one;
BEGIN
my_val :=0;
END;
DECLARE
SUBTYPE new_string IS VARCHAR2 (5) NOT NULL;
my_str_new_string;
BEGIN
my_str := ‘abc’;
END;
DECLARE
SUBTYPE new_one IS NUMBER (2, 1);
my_val new_one;
BEGIN
my_val :=12.5;
END;
DECLARE
SUBTYPE new_one IS INTEGER RANGE 1..10 NOT NULL;
my_val new_one;
BEGIN
my_val :=2;
END;
DECLARE
SUBTYPE new_one IS NUMBER (1, 0);
my_val new_one;
BEGIN
my_val := -1;
END;

Correct answer: AD

Question 5

Which statement is correct about DBMS_LOB.SETOPTIONS and DBMS_LOB.GETOPTIONS for SecureFiles?

DBMS_LOB.GETOPTIONS can only be used for BLOB data types.
DBMS_LOB.SETOPTIONS can perform operations on individual SecureFiles but not an entire column.
DBMS_LOB. SETOPTIONS can set option types COMPRESS, DUPLICATE, and ENCRYPT.
If a table was not created with compression specified in the store as securefile clause then DBMS_LOB.SETOPTIONS can be used to enable it later.

Correct answer: D

Explanation:

Reference: https://docs.oracle.com/cd/E11882_01/appdev.112/e18294/adlob_smart.htm

Question 6

You are designing and developing a complex database application built using many dynamic SQL statements. Which option could expose your code to SQL injection attacks?

Using bind variables instead of directly concatenating parameters into dynamic SQL statements
Using automated tools to generate code
Not validating parameters which are concatenated into dynamic SQL statements
Validating parameters before concatenating them into dynamic SQL statements
Having excess database privileges

Correct answer: D

Question 7

Examine this code executed as SYS:

Examine this code executed as SPIDER and the error message received upon execution:

What is the reason for this error?

The procedure needs to be granted the DYNAMIC_TABLE_ROLE role.
The EXECUTE IMMEDIATE clause is not supported with roles.
Privileges granted through roles are never in effect when running definer’s rights procedures.
The user SPIDER needs to be granted the CREATE TABLE privilege and the procedure needs to be granted the DYNAMIC_TABLE_ROLE.

Correct answer: C

Question 8

Which codes executes successfully?

CREATE PACKAGE pkg AS
TYPE rec_typ IS RECORD (price NUMBER, inc_pct NUMBER);
PROCEDURE calc_price (price_rec IN OUT rec_typ);
END pkg;
/
CREATE PACAKGE BODY pkg AS
PROCEDURE calc_price (price_rec IN OUT rec_typ) AS
BEGIN
price_rec.price := price_rec.price + (price_rec.price * price_rec.inc_pct)/100;
END calc_price;
END pkg;
/
DECLARE
1_rec pkg. rec_typ;
BEGIN
1_rec_price :=100;
1_rec.inc_pct :=50;
EXECUTE IMMEDIATE ‘BEGIN pkg. calc_price (:rec); END;’ USING IN OUT 1_rec;
END;
CREATE PACKAGE pkg AS
TYPE rec_typ IS RECORD (price NUMBER, inc_pct NUMBER);
END pkg;
/
CREATE PROCEDURE calc_price (price_rec IN OUT pkg. rec_typ) AS
BEGIN
price_rec.price := price_rec.price + (price_rec.price * price_rec.inc_pct)/100;
END
/
DECLARE
1_rec pkg.rec_typ;
BEGIN
EXECUTE IMMEDIATE ‘BEGIN calc_price (:rec); END;’ USING IN OUT 1_rec (100, 50);
END;
CREATE PACKAGE pkg AS
TYPE rec_typ IS RECORD (price NUMBER, inc_pct NUMBER);
END pkg;
/
CREATE PROCEDURE calc_price (price_rec IN OUT pkg. rec_typ) AS
BEGIN
price_rec.price := price_rec.price + (price_rec.price * price_rec.inc_pct)/100;
END ;
/
DECLARE
1_rec pkg. rec_typ;
BEGIN
1_rec_price :=100;
1_rec.inc_pct :=50;
EXECUTE IMMEDIATE ‘BEGIN calc_price (1_rec); END;’;
END;
DECLARE
TYPE rec_typ IS RECORD (price NUMBER, inc_pct NUMBER);
1_rec rec-typ;
PROCEDURE calc_price (price_rec IN OUT rec_typ) AS
BEGIN
price_rec.price := price-rec.price+ (price_rec.price * price_rec.inc_pct)/100;
END;
BEGIN
1_rec_price :=100;
1_rec.inc_pct :=50;
EXECUTE IMMEDIATE ‘BEGIN calc_price (:rec); END;’ USING IN OUT 1_rec;
END;

Correct answer: B

Question 9

Examine this function header:

FUNCTION calc_new_sal (emp_id NUMBER) RETURN NUMBER;

You want to ensure that whenever this PL/SQL function is invoked with the same parameter value across active sessions, the result is not recomputed.

If a DML statement is modifying a table which this function depends upon, the function result must be recomputed at that point in time for all sessions calling this function.

Which two actions should you perform?