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 generates an error because the NO SALT option cannot be used with the ENCRYPT
option.

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

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

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



Leave a Reply 0

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