Explanation/Reference:
Explanation:
Concatenate the files into one file using the cat command.
Make the contents of the repository .iso file available using the mount command.
To increase the performance of repository accesses and to avoid the need to remount the .iso image each time the system restarts, copy the repository files from /mnt/repo/to a ZFS file system. You can do this copy with rsync or with tar.

The framework enables providers of cryptographic services to have their services used by many consumers in the Oracle Solaris operating system. Another name for providers is plugins. The framework allows three types of plugins:
*User-level plugins - Shared objects that provide services by using PKCS #11 libraries, such as pkcs11_softtoken.so.1.
*Kernel-level plugins - Kernel modules that provide implementations of cryptographic algorithms in software, such as AES.
*Hardware plugins - Device drivers and their associated hardware accelerators. The Niagara chips, the ncp and n2cp device drivers, are one example. A hardware accelerator offloads expensive cryptographic functions from the operating system. The Sun Crypto Accelerator 6000 board is one example.
Many of the algorithms in the framework are optimized for x86 with the SSE2 instruction set and for SPARC hardware.
Reference: Oracle Solaris Cryptographic Framework
http://docs.oracle.com/cd/E19963-01/html/821-1456/scf-10.html

Explanation/Reference:

A: ZFS also allows you to use UFS files as virtual devices in your storage pool. This feature is aimed primarily at testing and enabling simple experimentation, not for production use.
The reason is that any use of files relies on the underlying file system for consistency. If you create a ZFS pool backed by files on a UFS file system, then you are implicitly relying on UFS to guarantee correctness and synchronous semantics. However, files can be quite useful when you are first trying out ZFS or experimenting with more complicated layouts when not enough physical devices are present. All files must be specified as complete paths and must be at least 64 Mbytes in size.
B, E: You can construct logical devices for ZFS using volumes presented by software-based volume managers, such as Solaris Volume Manager (SVM) or Veritas Volume Manager (VxVM). However, these configurations are not recommended. While ZFS functions properly on such devices, less-than-optimal performance might be the result.
Reference: Solaris ZFS Administration Guide, Managing ZFS Storage Pools