Oracle 1z0-148 Exam Dumps

Question 6 of 74

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;

Correct Answer: A, E

The code block in option A defines a subtype `new_one` as a BINARY_INTEGER within the range 0 to 9 and assigns a value of 0 to `my_val`, which is valid and will execute successfully. The code block in option E defines a subtype `new_one` as a NUMBER with precision 1 and scale 0 and assigns a value of -1 to `my_val`, this is also valid and will execute successfully. Other options contain errors: Option B requires an initialization for the NOT NULL constraint, option C exceeds the precision for NUMBER(2,1) by trying to assign 12.5, and option D requires an initialization assignment for the NOT NULL constraint.

Question 7 of 74

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: B

DBMS_LOB.SETOPTIONS performs operations on individual SecureFiles but not an entire column. This procedure allows enabling or disabling compression and deduplication settings on a per-LOB basis, thereby overriding any default settings specified at the column level. Consequently, the operation does not apply to the entire column, but targets specific LOBs within the SecureFile.

Question 8 of 74

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: C

Not validating parameters which are concatenated into dynamic SQL statements could expose your code to SQL injection attacks. This vulnerability arises because malicious users can inject harmful SQL code via the parameters if they are directly concatenated into the SQL statements without proper validation and sanitization.

Question 9 of 74

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

Privileges granted through roles are never in effect when running definer’s rights procedures. When a PL/SQL procedure is created with definer's rights, it executes with the privileges of the owner of the procedure, and only direct grants are recognized, not roles. Therefore, the error occurs because the CREATE TABLE privilege granted to the dynamic_table_role is not being recognized in the context of the definer’s rights procedure.

Question 10 of 74

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;

Correct Answer: A

The correct answer is A. The package definition and body are correctly created, and the procedure uses the record type correctly. The anonymous block declares a record of this type, assigns values to its fields (though there is a typo: it should be '1_rec.price' not '1_rec_price'), and then calls the procedure correctly using EXECUTE IMMEDIATE with the USING IN OUT clause. All other options contain syntax or logical errors that would prevent them from executing successfully.