You created an encrypted tablespace: You then closed the encryption wallet because you
were advised that this is secure. Later in the day, you attempt to create the EMPLOYEES
table in the SECURESPACE table space with the SALT option on the EMPLOYEE column.
Which is true about the result?
A.
It generates error when creating the table, because the salt option cannot be used with
encrypted tablespaces.
B.
It creates the table successfully, and encrypts any inserted data in the EMPNAME
column because the wallet needs to be open only for tablespace creation.
C.
It creates the table successfully but does not encrypt any inserted data in the EMPNAME
column because the wallet must be opened to encrypt columns with SALT.
D.
It generates an error when creating the table because the wallet is closed.
D
so much wonderful information on here, : D.
http://www.bastcilkdoptb.com/
http://www.oracle.com/technetwork/testcontent/o19tte-086996.html
– B
Alexis, from your link I would suggest that B is incorrect and D is the right answer:
“Oracle provides two different types of wallets: encryption wallet and (local) auto-open wallet. The encryption wallet (filename ‘ewallet.p12’) is the one recommended for TDE. It needs to be opened manually after database startup and prior to TDE encrypted data being accessed. Because data is encrypted in REDO logs, UNDO and TEMP tablespaces, the TDE master encryption key needs to be available to the database before it is opened:”
To me, it looks like the wallet needs to be opened to use it.
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.
we got new OCP 12c questions. These are latest questions.
http://www.aiotestking.com/oracle/category/exam-1z0-063-update-august-9th-2017/