A.It can be used for applications and middleware.

B.It can be used only for Oracle Grid Infrastructure, excluding Oracle Restart.

C.It can be used only for Oracle Grid Infrastructure, including Oracle Restart.

D.It can be used for both Oracle Database and Oracle Grid Infrastructure, including Oracle Restart.

E.It can be used for both Oracle Database and Oracle Grid Infrastructure, excluding Oracle Restart.

A.Automatic block repair can repair blocks with no standby database if DB_BLOCK_CHECKING = TRUE.

B.Real-Time Query must be enabled on a primary database for automatic block repair to be done on any of its physical standby databases.

C.It is not possible for media corrupt blocks.

D.Real-Time Query must be enabled on a physical standby database for automatic block repair to be done on its primary database.

E.Real-Time Query must be enabled on a physical standby database for automatic block repair to be done on that physical standby database.

A.It can be performed using an auxiliary instance managed by a DBA.

B.It can be used to recover a dropped tablespace.

C.It can be performed repeatedly until the correct time is found without using an RMAN catalog.

D.RMAN always includes tablespaces containing undo segments in the recovery set.

E.It can be used to recover a truncated table.

F.It can be performed using an auxiliary instance managed by RMAN.

G.RMAN automatically adds any required tablespaces to the recovery set to make it self-contained.

H.flashback database must be enabled for it to work.

A.The REVENUEtable must be a list-partitioned table.

B.The MAPTABLE table is a metadata-linked table.

C.The MAPTABLEtables defines a logical partition key on a commonly used column for the REVENUEtable.

D.The CONTAINERSclause cannot be used in queries on the REVENUEtable.

E.A container map exists for the REVENUEtable, but is not enabled.

F.The REVENUEtable partitions are not pruned across the PDBs automatically.

A.Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET only after there is space pressure.

B.Flashback logs are monitored for being older than the retentionperiod defined in DB_FLASHBACK_RETENTION_TARGET and can be deleted by an administrator written event trigger.

C.Flashback logs areautomatically purged when DB_FLASHBACK_RETENTION_TARGET is set lower than the time they have already been retained.

D.Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET before there is space pressure.

E.Flashback logs are automatically purged whenever the value of
DB_FLASHBACK_RETENTION_TARGET is changed.