What is the outcome?

You opened the encryption wallet and then issued the following command:
SQL>CREATE TABLESPACE securespace
DATAFILE ‘/home/user/oradata/secure01.dbf’
SIZE 150M
ENCRYPTION USING ‘3DES168’
DEFAULT STORAGE(ENCRYPT);

Then you closed the wallet. Later, you issued the following command to create the EMPLOYEES
table in the SECURESPACE tablespace and you use the NO SALT option for the EMPID column.
What is the outcome?

You opened the encryption wallet and then issued the following command:
SQL>CREATE TABLESPACE securespace
DATAFILE ‘/home/user/oradata/secure01.dbf’
SIZE 150M
ENCRYPTION USING ‘3DES168’
DEFAULT STORAGE(ENCRYPT);

Then you closed the wallet. Later, you issued the following command to create the EMPLOYEES
table in the SECURESPACE tablespace and you use the NO SALT option for the EMPID column.
What is the outcome?

A.
It creates the table and encrypts the data in it.

B.
It generates an error because the wallet is closed.

C.
It creates the table but does not encrypt the data in it.

D.
It generates an error because the NO SALT option cannot be used with the ENCRYPT option.



Leave a Reply 5

Your email address will not be published. Required fields are marked *


TonyE

TonyE

Don’t believe the table creation detail is necessary here… The key to the question here is “Then you closed the wallet.”

“Before you can create an encrypted tablespace, the Oracle wallet containing the tablespace master encryption key must be open. The wallet must also be open before you can access data in an encrypted tablespace.”

TonyE

TonyE

Sorry ‘B’ is correct

TonyE

TonyE

Forgot to add that ‘B’ is indeed correct