Application PDBs, SALES_APP1 and SALES_APP2, must be created and they must access common tables of the SALES_APP application.
Examine these steps:
1. Install the SALES_APP application, including the common tables, in the application root.
2. Install the SALES_APP application in the application root and the common tables in both the CDB root and the application root.
3. Create an application seed.
4. Install the SALES_APP application in the application seed.
5. Create the SALES_APP1 and SALES_APP2 application PDBs.
6. Sync the SALES_APP1 and SALES_APP2 application PDBs with the application root.
7. Sync the SALES_APP1 and SALES_APP2 application PDBs with the application seed.
8. Sync the application seed with the application root.
Which are the minimum required steps in the correct sequence?

• A.2,5,6
• B.1,3,5,6,7
• C.3,4,1,6,8
• D.1,5,6
• E.1,3,5,7

Comment: *

Name: *

Email: *

Verification: *

While backing up to the Oracle Fast Recovery Area (FRA), you determined the backup istaking too long and suspect a performance bottleneck. Which three are true about diagnosing and tuning these problems? (Choose three.)

• A.Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a potential performance bottleneck when asynchronous I/O is used.
• B.If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then read I/O is a likely bottleneck.
• C.If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then both read and write I/O are likely bottlenecks.
• D.If an RMAN BACKUP VALIDATE command takes noticeably lessthan an actual backup, then write I/O is a likely bottleneck.
• E.Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using synchronous I/O.
• F.Data files with a high value in V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential performance bottleneck when synchronous I/O is used.
• G.Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using asynchronous I/O/

Comment: *

Name: *

Email: *

Verification: *

A database is configured in archivelog mode.
Full RMAN backups are taken daily and no backup to trace has been taken of the control file.
A media failure has occurred.
In which two scenarios is complete recovery possible?

• A.after losing the system tablespace
• B.after losing an archived log from before the most recent backup
• C.after losing an archived log from after the most recent backup
• D.after losing all copies of the control file
• E.when any archived log from, before, or after the most recent backup is corrupt

Comment: *

Name: *

Email: *

Verification: *

Examine this configuration:
* CDB1 is an Oracle Database 12c Release 2 database containing pluggable databases PDB$SEED, PDB1, and PDB2.
* PDB$SEED is open READ ONLY
* PDB1 is open READ WRITE
* PDB2 is MOUNTED.
* ORACLE_HOME is /u01/app/oracle/product/18.1.0/dbhome_1.
You execute these commands before upgrading the database to the current release:

For which databases will fixup scripts be created?

• A.CDB1, PDB1, and PDB2 only
• B.CDB1, PDB$SEED, and PDB1 only
• C.CDB1 and PDB$SEED only
• D.PDB$SEED, PDB1, and PDB2 only
• E.CDB1, PDB$SEED, PDB1, and PDB2

Comment: *

Name: *

Email: *

Verification: *

Examine these queries and their output:

After a system crash, an instance restart and an attempted opening of the PDBs result in:

Which two are true?

• A.Data file 24 must be recovered while PDB2 is closed.
• B.Data file 24 can be recovered while CDB$ROOT and PDB$SEED are opened.
• C.Data file 24 must be recovered while the CDB is opened.
• D.Data file 24 can be recovered while PDB2 is opened.
• E.Data file 24 cannot be recovered while the CDB is opened.

Comment: *

Name: *

Email: *

Verification: *