Which statement is true regarding virtual private catalogs?
A.
A virtual private catalog owner can create a local stored script, and have read/write access to a global stored script.
B.
The virtual private catalog owner cannot create and modify the stored scripts.
C.
The set of views and synonyms that make up the virtual private catalog is stored in the schema of the RMAN recovery catalog owner.
D.
To perform most of the RMAN operations, the virtual catalog owner must have the SYSDBA or SYSOPER privilege on the target database.
Are you sure about this answer ? How can a user in RMAN database have sysdba privilege on the target database? I think that the correct answer is C .
“The set of views and synonyms that makes up the virtual private catalog is stored in the schema of the virtual private catalog owner.”
http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmcatdb.htm#BRADV89656
Not the same thing. You: “…is stored in the schema of the virtual private catalog owner.”. The answer: “…is stored in the schema of the RMAN recovery catalog owner”.
D is correct because EVERY USER needs SYSDBA and SYSOPER privilege to perform the most of RMAN operations. Regular privileges have limited privileges on RMAN.
The correct answer should be C
When you grant a catalog user restricted access, you give this user full read/write access to his own RMAN metadata, which is the virtual private catalog. Note that a virtual private catalog owner can create a local stored script, but only has read-only access to a global stored script. The set of views and synonyms that makes up the virtual private catalog is stored in the schema of the virtual private catalog owner. The mechanisms for virtual private catalogs exist in the recovery catalog schema itself. Security is provided by the recovery catalog database, not by the RMAN executable.
[..] Unlike SQL*Plus, RMAN does not require that you specify the SYSDBA privilege when connecting to a database. Because all RMAN database connections require SYSDBA privilege, RMAN always implicitly attempts to connect with this privilege. […]
https://docs.oracle.com/cd/B19306_01/backup.102/b14192/setup003.htm