After installing an Oracle Solaris 11 system, you execute the following command to create a data set into which several non-global zones will be installed: What impact will this command have on any…

Question

Options

• AThe zones will have encrypted swap and /tmp file systems.
• BThe zones will not permit any move or clone operations.
• CThe zones will be required to be "Solaris" brands only.
• DThe zones will cache the encryption key while running.
• EThe zones will be unable to start during system boot.

• A
  4% (2)
• B
  2% (1)
• C
  11% (6)
• D
  5% (3)
• E
  79% (44)

Explanation

• Oracle Solaris 11 adds transparent data encryption functionality to ZFS. All data and file system metadata (such as ownership, access control lists, quota information, and so on) are encrypted when stored persistently in the ZFS pool. * A ZFS pool can support a mix of encrypted and unencrypted ZFS data sets (file systems and ZVOLs). Data encryption is completely transparent to applications and other Oracle Solaris file services, such as NFS or CIFS. Since encryption is a first-class feature of ZFS, we are able to support compression, encryption, and deduplication together. Encryption key management for encrypted data sets can be delegated to users, Oracle Solaris Zones, or both. Oracle Solaris with ZFS encryption provides a very flexible system for securing data at rest, and it doesn't require any application changes or qualification. ZFS makes it easy to encrypt data and manage data encryption. You can have both encrypted and unencrypted file systems in the same storage pool. You can also use different encryption keys for different systems, and you can manage encryption either locally or remotely.

No community discussion yet for this question.