46.
Typing fdisk -l /dev/sda on a Linux computer with an MBR disk produces a listing
of four partitions: /dev/sda1, /dev/sda2, /dev/sda5, and /dev/sda6. Which of the
following is true?
- A.The disk contains two primary partitions and two extended partitions.
- B.Either /dev/sda1 or /dev/sda2 is an extended partition.
- C.The partition table is corrupted; there should be a /dev/sda3 and a /dev/sda4 before /dev/sda5.
- D.If you add a /dev/sda3 with fdisk, /dev/sda5 will become /dev/sda6 and /dev/ sda6 will become /dev/sda7.
- E.Both /dev/sda1 and /dev/sda2 are logical partitions.
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
47.
A new Linux administrator plans to create a system with separate /home, /usr/local, and
/etc partitions, in addition to the root (/) partition. Which of the following best describes
this configuration?
- A.The system won’t boot because critical boot-time files reside in /home.
- B.The system will boot, but /usr/local won’t be available because mounted partitions must be mounted directly off their parent partition, not in a subdirectory.
- C.The system will boot only if the /home partition is on a separate physical disk from the /usr/local partition.
- D.The system will boot and operate correctly, provided each partition is large enough for its intended use.
- E.The system won’t boot because /etc contains configuration files necessary to mount non-root partitions.
- Answer & Explanation
- Report
Answer : [E]
Explanation :
Explanation :
| The /etc/fstab file contains the mapping of partitions to mount points, so /etc must be an ordinary directory on the root partition, not on a separate partition, making option E correct. Although option A’s statement that the system won’t boot is correct, the reason is not; /home holds user files, not critical system files. Options B and C describe restrictions that don’t exist. Option D would be correct if /etc were not a separate partition. |
48.
Which of the following directories is most likely to be placed on its own hard disk partition?
- A./bin
- B./sbin
- C./mnt
- D./home
- E./dev
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
| The /home directory (option D) is frequently placed on its own partition in order to isolate it from the rest of the system and sometimes to enable use of a particular filesystem or filesystem mount options. The /bin and /sbin directories (options A and B) should never be split off from the root (/) filesystem because they contain critical executable files that must be accessible in order to do the most basic work, including mounting filesystems. The /mnt directory (option C) often contains subdirectories used for mounting floppy disks, CD-ROMs, and other removable media or may be used for this purpose itself. It’s seldom used to directly access hard disk partitions, although it can be used for this purpose. The /dev directory (option E) usually corresponds to a virtual filesystem, which holds pseudo-files but is not stored on a disk partition. |
49.
You discover that an MBR hard disk has partitions with type codes of 0x0f, 0x82, and
0x83. Assuming these type codes are accurate, what can you conclude about the disk?
- A.The disk holds a partial or complete Linux system.
- B.The disk holds DOS or Windows 9x/Me and Windows NT/200x/XP installations.
- C.The disk holds a FreeBSD installation.
- D.The disk is corrupt; those partition type codes are incompatible.
- E.route host gw 192.168.0.1
- Answer & Explanation
- Report
Answer : [A]
Explanation :
Explanation :
| The 0x0f partition type code is one of two common partition type codes for an extended partition. (The other is 0x05.) The 0x82 code refers to a Linux swap partition, and 0x83 denotes a Linux filesystem partition. Thus, it appears that this disk holds Linux partitions, making option A correct. DOS, Windows 9x/Me, Windows NT/200x/XP, FreeBSD, and Mac OS X all use other partition type codes for their partitions, so options B, C, and E are all incorrect. (Mac OS X is also rarely installed to MBR disks.) Partitions exist, in part, to enable different OSs to store their data side-by-side on the same disk, so mixing several partition types (even for different OSs) on one disk does not indicate disk corruption, making option D incorrect. |
50.
You run Linux’s fdisk and modify your partition layout. Before exiting the program,
you realize that you’ve been working on the wrong disk. What can you do to correct this
problem?
- A.Nothing; the damage is done, so you’ll have to recover data from a backup.
- B.Type w to exit fdisk without saving changes to disk.
- C.Type q to exit fdisk without saving changes to disk.
- D.Type u repeatedly to undo the operations you’ve made in error.
- E.Type t to undo all the changes and return to the original disk state.
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
| Linux’s fdisk doesn’t write changes to disk until you exit the program by typing w. Typing q exits without writing those changes, so typing q in this situation will avert disaster, making option C correct. Typing w (option B) would be precisely the wrong thing to do. Because fdisk doesn’t write changes until you type w, the damage is not yet done, contrary to option A. Typing u (option D) or t (option E) would do nothing useful because those aren’t undo commands. |
|
|
||||||||||||||||||||||||||||
