Examine the query and its output executed In an RDBMS Instance: 
Which three statements are true about the users (other than sys) in the output?
A.
The C # # B_ADMIN user can perform all backup and recovery operations using RMAN only.
B.
The C # # C_ADMIN user can perform the data guard operation with Data Guard Broker.
C.
The C # # A_ADMIN user can perform wallet operations.
D.
The C # # D_ADMIN user can perform backup and recovery operations for Automatic Storage
Management (ASM).
E.
The C # # B_ADMIN user can perform all backup and recovery operations using RMAN or
SQL* Plus.
Explanation:
A: a SYSBA can perform backup and recovery operations.
B: SYSDG administrative privilege has ability to perform Data Guard operations (including startup
and shutdown) using Data Guard Broker or dgmgrl.
Incorrect:
Not C: SYSKM. SYSKM administrative privilege has ability to perform transparent data encryption
wallet operations.
Should be B, D and E.
A is not correct. E option can replace A
Hi Sunil what about c?
The correct answers are: BDE; C wrong
I think it is B, C and E.
C is right: “The SYSKM administrative privilege enables the SYSKM user to manage Transparent Data Encryption (wait for it…) wallet operations!”
D is wrong, we don’t “backup and recover” ASM. You should rather try it on your database.
B: SYSDG administrative privilege has ability to perform Data Guard operations (including startup and shutdown) using Data Guard Broker or dgmgrl.
D: SYSASM The new (introduced in 11g) SYSASM role to manage the ASM instance, variable extent sizes to reduce shared pool usage, and the ability of an instance to read from a specific disk of a diskgroup
E (Not A): SYSDBA is like a role in the sense that it is granted, but SYSDBA is a special built-in privilege to allow the DBA full control over the database
Incorrect:
Not C: SYSKM. SYSKM administrative privilege has ability to perform transparent data encryption wallet operations.
Hi Shawn,
Regarding the “backup and recover” ASM, I kind of agree with you about the recovery bit. However, you can indeed backup and restore the ASM Metadata using md_backup and md_restore.
I wonder if one can discard D as it uses the word “Recover”…
Regards
SYSDBA – username SYS/PUBLIC – same system operations and privileges as 11g and earlier
SYSOPER – username SYS/PUBLIC – same system operations and privileges as 11g and earlier
SYSASM – username SYS – privileges for administering an ASM instance only (first introduced in 11g)
SYSBACKUP – username SYSBACKUP – the ability to perform RMAN backup and recovery commands both from SQL and RMAN command line – new in 12c
SYSDG – username SYSDG – the ability to perform Data Guard operations with Data Guard Broker or the DGMGRL command line – new in 12c
SYSKM – username SYSKM – the ability to manage the encryption keys for Transparent Data Encryption – new in 12c
BDE
BDE
C is correct
SYSKM Administrative Privilege for Transparent Data Encryption
The SYSKM administrative privilege enables the SYSKM user to manage Transparent Data Encryption (TDE) wallet operations.
https://docs.oracle.com/database/121/DBSEG/authorization.htm#DBSEG787
B D E
https://equizzing.com/oracle/which-three-statements-are-true-about-the-users-other-4/