Examine the RMAN command: RMAN> CONFIGURE ENCRYPTION FOR DATABASE ON; RMAN> BACKUP DATABASE PLUS ARCHIVELOG; Which prerequisite must be met before accomplishing the backup?

Question

Options

• AThe password for the encryption must be set up.
• BOracle wallet for the encryption must be set up.
• CAll the tablespaces in the database must be encrypted
• DOracle Database Vault must be enabled.

• A
  6% (2)
• B
  87% (27)
• C
  3% (1)
• D
  3% (1)

Explanation

When CONFIGURE ENCRYPTION FOR DATABASE ON is used without specifying a password, RMAN defaults to transparent encryption, which relies entirely on the Oracle Wallet (TDE keystore) to store and provide the master encryption key - the wallet must be configured and open before RMAN can encrypt or decrypt anything.

Why the distractors are wrong:

• A (password): A password would be needed for password-mode encryption (SET ENCRYPTION IDENTIFIED BY), but the command shown uses the default transparent mode - no runtime password is involved.
• C (all tablespaces encrypted): TDE tablespace encryption is independent of RMAN backup encryption; you can encrypt backups of plain tablespaces without encrypting the tablespaces themselves.
• D (Database Vault): Oracle Database Vault controls privileged user access and has no role in backup encryption.

Memory tip: Think "no wallet, no lock" - transparent backup encryption is essentially TDE for backups, so it needs the same keystore infrastructure TDE always requires. If the wallet isn't open, RMAN has nowhere to retrieve the key and the backup simply fails.

No community discussion yet for this question.