A - FALSE. The ARCH process backs up online redo logs (by creating Arch redo logs), never the DBA. DBAs backup Archive Redo Logs, not online redo logs. B - TRUE. Control files are DB wide - backing them up, from the Container Root, is exactly where you do this. C - TRUE. Part of the point of Multitenant is that you have control of all PDBs from the CDB level. D - FALSE. An application root container is still below the main Container, so you cannot administer control files from here. E - FALSE. For the same reason as above, you can only create control file backups from the Root Container. So, BC is correct.

B and C no doubt

I believe there are three correct answers to this question; b) obvious answer c) Tested in version 19.3: tablespace backup pdb1:tbs_name; e) Tested on version 19.3 connected to pdb1: backup current controlfile;

B, C not D : when connected to application root PDB: RMAN> backup archivelog all; skipping archived logs when connected to a PDB E , also correct, you can create cf backup: backup current controlfile;

BC correct

three answers are correct BCE. I tested E in lab and it works, I agree with xRodge for A

B and C is correct

E: controlfile can be created in PDB, but can it be created in PDB$SEED?

E- FALSE, TESTED RMAN> BACKUP CONTROLFILECOPY all; Starting backup at 30-MAR-24 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=505 device type=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 03/30/2024 16:43:06 RMAN-20220: control file copy not found in the repository

BC i agree

BE and C are correct A. Online Redo Log backups can be created while connected to the root container. FALSE - we don't backup online redo logs, we backup archived logs. ARCH backs up online redo B. Control file backups can be created while connected to the root container. TRUE - backup current controlfile; C. The BACKUP TABLESPACE command can back up a PDB tablespace even if RMAN is connected to CDB$ROOT. TRUE - backup tablepace pdb1:t1; D. Archived Redo Log backups can be created while connected to an application root CDB. FALSE - "skipping archived logs when connected to a PDB" E. Control file backups can be created while connected to a nonroot container. TRUE - During tests, I am able to backup a controlfile while connected to a nonroot container

Connected to: Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.12.0.0.0 SQL> SHOW PDBS CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 PDB1 READ WRITE NO SQL> alter session set container=PDB1; Session altered. SQL> ALTER DATABASE BACKUP CONTROLFILE TO '/tmp/control1.bak'; ALTER DATABASE BACKUP CONTROLFILE TO '/tmp/control1.bak' * ERROR at line 1: ORA-65040: operation not allowed from within a pluggable database SQL>

D incorrect: U must be connected to CDB root, not application root.

I think BD