[Free] 2018(Jan) EnsurePass Pass4sure Oracle 1z0-053 Dumps with VCE and PDF 381-390 | 70-740 Exams Free Real Practice Questions and Answers

Ensurepass.com : Ensure you pass the IT Exams
2018 Jan Oracle Official New Released 1z0-053
100% Free Download! 100% Pass Guaranteed!
http://www.EnsurePass.com/1z0-053.html

Oracle Database 11g: Administration II

Question No: 381 – (Topic 11)

What are the prerequisites for performing flashback transactions? (Choose all that apply)

Supplemental log must be enabled
Supplemental log must be enabled for the primary key
Undo retention guarantee for the database must be configured
quot;EXECUTE quot; permission on the DBMS_FLASHBACK package must be granted to the user

Answer: A,B,D

Question No: 382 – (Topic 11)

View the following SQL statements: Transaction T1

SQLgt; INSERT INTO hr.regions 2 VALUES (5,#39;Pole#39;);

3 COMMIT;

Transaction T2

SQLgt; UPDATE hr.regions 2 SET region_name=#39;Poles#39;

WHERE region_id = 5;
COMMIT;

Transaction T3

SQLgt; UPDATE hr.regions

2 SET region_name=#39;North and South Poles#39; 3 WHERE region_id = 5;

You want to back out transaction T2. Which option would you use?

It is possible, but transaction T3 also backs out.
It is possible with the NOCASCADE_FORCE option.
It is possible with the NONCONFLICT_ONLY option.
It is not possible because it has conflicts with transaction T3.

Answer: B Explanation:

Table 12-2 Flashback TRANSACTION_BACKOUT Options

CASCADE

Backs out specified transactions and all dependent transactions in a post-order fashion (that is, children are backed out before parents are backed out).

Without CASCADE, if any dependent transaction is not specified, an error occurs.

NOCASCADE

Default. Backs out specified transactions, which are expected to have no dependent transactions. First dependent transactions causes an error and appears in

*_FLASHBACK_TXN_REPORT.

NOCASCADE_FORCE

Backs out specified transactions, ignoring dependent transactions. Server runs undo SQL statements for specified transactions in reverse order of commit times. If no constraints break and you are satisfied with the result, you can commit the changes; otherwise, you can roll them back.

NONCONFLICT_ONLY

Backs out changes to nonconflicting rows of the specified transactions. Database remains consistent, but transaction atomicity is lost.

Question No: 383 – (Topic 11)

Which of the following can be used in conjunction with a Flashback Versions Query to filter the results? (Choose all that apply.)

A range of SCN values
A list of SCN values
A starting and ending timestamp
Minimum and maximum sequence values
A list of sequence values

Answer: A,C

Question No: 384 – (Topic 11)

Examine the following commands and their output:

SQLgt; SELECT ename, sal FROM emp WHERE ename=#39;JAMES#39;; ENAME SAL

— — JAMES 1050

SQLgt; UPDATE emp SET sal=sal sal*1.2 WHERE ename=#39;JAMES#39;; 1 row updated.

SQLgt; SELECT ename, sal FROM emp WHERE ename=#39;JAMES#39;; ENAME SAL

— — JAMES 2310

View the exhibit and examine the Flashback Version Query that was executed after the

preceding commands.

What could be the possible cause for the query not displaying any row? Exhibit:

Ensurepass 2018 PDF and VCE

Flashback logging is not enabled for the database.
The changes made to the table are not committed.
Supplemental logging is not enabled for the database.
The database is not configured in ARCHIVELOG mode.

Answer: B

Question No: 385 – (Topic 11)

Which method could be utilized to identify both DML operations and the SQL statements needed to undo those operations for a specific schema owner? (Choose all that apply.)

Query DBA_TRANSACTION_QUERY for TABLE_NAME, OPERATION, and UNDO_SQL. Limit rows by START_SCN and TABLE_OWNER.
Query FLASHBACK_TRANSACTION_QUERY for TABLE_NAME, OPERATION, and UNDO_SQL. Limit rows by START_SCN and TABLE_OWNER.
Query FLASHBACK_TRANSACTION_QUERY for TABLE_NAME, OPERATION, and UNDO_SQL. Limit rows by START_TIMESTAMP and TABLE_OWNER.
Query DBA_TRANSACTION_QUERY for TABLE_NAME, OPERATION, and UNDO_SQL. Limit rows by START_TIMESTAMP and TABLE_OWNER.

Answer: B,C

Question No: 386 – (Topic 11)

The RECYCLEBIN parameter is set to ON for your database. You drop a table, PRODUCTS, from the SCOTT schema.

Which two statements are true regarding the outcome of this action? (Choose two)

All the related indexes and views are automatically dropped
The flashback drop feature can recover only the table structure
Only the related indexes are dropped whereas views are invalidated
The flashback drop feature can recover both the table structure and its data

Answer: C,D

Question No: 387 – (Topic 11)

Which of the following Oracle features utilize the undo tablespace? (Choose all that apply)

Flashback Query
Flashback Drop
Flashback Table
Flashback Database
Transaction Processing
Recycle Bin

Answer: A,C,E

Question No: 388 – (Topic 11)

Which are the prerequisites for performing flashback transactions on your database? (Choose all that apply.)

Undo retention guarantee for the database must be configured.
Supplemental log must be enabled for the primary key.
Supplemental log must be enabled.
Execute permission on the DBMS_FLASHBACK package must be granted to the user.

Answer: B,C,D

Question No: 389 – (Topic 11)

Which of the following statements is true regarding the VERSIONS BETWEEN clause?

The VERSIONS BETWEEN clause may be used in DML statements.
The VERSIONS BETWEEN clause may be used in DDL statements.
The VERSIONS BETWEEN clause may not be used to query past DDL changes to tables.
The VERSIONS BETWEEN clause may not be used to query past DML statements to tables.

Answer: C

Question No: 390 – (Topic 11)

You discover that your Recycle Bin contains two tables with the same name, MY_TABLE. You also have a table named MY_TABLE in your schema.

You execute the following statement:

FLASHBACK TABLE my_table TO BEFORE DROP RENAME TO my_table2; What will be the result of executing this statement?

One of the tables is recovered from the Recycle Bin using a First In First Out (FIFO) approach.
One of the tables is recovered from the Recycle Bin using a Last In First Out (LIFO) approach.
Both the tables are recovered from the Recycle Bin with one table renamed to MY_TABLE2 and the other to a system-generated name.
None of the tables are recovered from the Recycle Bin, and the statement returns an error.