What is the impact of this setting on the usage of SecureFiles?

Evaluate the following command:
SQL>ALTER SYSTEM SET db_securefile = ‘IGNORE’;
What is the impact of this setting on the usage of SecureFiles?

A.
It forces BasicFiles to be created even if the SECUREFILE option is specified to create
the LOB.

B.
It forces SecureFiles to be created even if the BASICFILE option is specified to create the
LOB.

C.
It does not allow the creation of SecureFiles and generates an error if the SECUREFILE
option is specified to create the LOB.

D.
It ignores the SECUREFILE option only if a Manual Segment Space Management
tablespace is used and creates a BasicFile.

Explanation:
Parameter type String
Syntax DB_SECUREFILE = { NEVER | PERMITTED | ALWAYS | IGNORE }
Default value PERMITTED
Modifiable ALTER SESSION, ALTER SYSTEM

Basic No
DB_SECUREFILE specifies whether or not to treat LOB files as SecureFiles.
Values:
NEVER
Any LOBs that are specified as SecureFiles are created as BasicFile LOBs. All SecureFilespecific storage options and features (for example, compress, encrypt, deduplicate) will
cause an exception. The BasicFile LOB defaults will be used for storage options not
specified.
PERMITTED
LOBs are allowed to be created as SecureFiles.
ALWAYS
Attempts to create all LOBs as SecureFile LOBs but creates any LOBs not in an Automatic
Segment Space Managed tablespace as BasicFile LOBs, unless SECUREFILE is explicitly
specified. Any BasicFile LOB storage options that are specified will be ignored and the
SecureFile defaults will be used for all storage options not specified.
IGNORE
The SECUREFILE keyword and all SecureFile options are ignored.
If the COMPATIBLE initialization parameter is not set to 11.1.0 or higher, then
LOBs are not treated as SecureFiles.