After settings up encryption for /dev/sdd1, you notice that the file system is not mounted during system startup.
You suspect a configuration error in /etc/crypttab:
# cat /etc/crypttab
# mapping device password options
sdd1 /dev/sdd1 TopSecretAssume that /etc/fstab is correct. Identify the reason why the file system is not mounted after system startup.
Which two statements about the yum-fs-snapshot plugin are true?
Which statement is true about udev?
A new iSCSI target configuration is created in /etc/tgt/targets2.conf using a text editor. The file is used to avoid accidental destructive errors in the normal working configuration file /etc/tgt/targets.conf while testing is in progress.
Which command would you use to activate this configuration without affecting the default configuration file?
You are required to create a file system that meets these requirements:
1. It must be created on /dev/ssd1.
2. It must be mounted on the already existing mount point/cryptfs.
3. Data stored on /cryptfs must be encrypted.
Examine this list of commands:
1. cryptsetup luksFormat /dev/sdd1
2. cryptsetup luksOpen /dev/sdd1/sdd1
3. mkfs --t ext4 /dev/sdd1
4. mkfs --t ext4 /dev/mapper/sdd1
5. mount /dev/sdd1/cryptfs
6. mount /dev/mapper/sdd1/cryptfs
7. cryptsetup/cryptfs
Which option represents the commands in the correct order to create a file system that meet the requirements?