Chapter 7, Using SecureFile LOBs

Question No.	Answer	Explanation
1	a, c, and d	SecureFiles can reside only on ASSM tablespaces. They are free from LOB index contention and high water mark contention. Up to 4 MB, SecureFile LOB data can be cached under the WGC component of the buffer cache.
2	a and d	Being part of the advanced compression, compression in SecureFile doesn't affect performance. It is intelligently handled by the LOB manager to perceive the impact of compression on LOB data.
3	b	Compression, deduplication, and encryption are mutually exclusive features of a SecureFile.
4	b	Table compression has nothing to do with SecureFile compression.
5	a and b	KEEP_DUPLICATES is the default option. The feature doesn't affect performance as the secure hash matching is a transparent process in the server.
6	c and d	The encryption keys are stored in the wallet directory. An encrypted SecureFile column cannot be modified for the encryption algorithm.
7	b	Online redefinition works with materialized views to get the latest snapshot of the source table, so that the ongoing data changes are not lost during redefinition processes.