220-1102 Question 278
Single answerRoot accountA technician is asked to install updates and modify network configuration files on a Linux workstation used by multiple employees. Company policy requires administrative actions to be traceable to an individual user account and discourages direct use of the root account except in emergencies. Which action should the technician take FIRST to complete the work while following best practices?
- A
Log in directly as root and perform all tasks from the root shell
- B
Use the technician's named account and run the required commands with sudo
- C
Reset the root password and share it with the help desk so changes can be completed faster
- D
Disable the root account permanently before starting the maintenance
Show answer and explanation
Correct answer: B
Explanation
On Linux systems, the root account has unrestricted administrative access, so it should be used carefully. For routine administration, best practice is to log in with a standard named account and use sudo for privileged commands. This supports accountability because actions can be logged per user, and it reduces exposure from operating continuously with full administrative rights. This approach is consistent with standard Linux administration guidance and the security principle of least privilege. Direct root login is generally discouraged for everyday maintenance, and sharing the root password is a significant security violation.
- A. Incorrect.
This is incorrect. Although the root account has the privileges needed to install updates and edit protected system files, logging in directly as root reduces accountability and increases risk. Best practice on Linux systems is to avoid routine direct root logins when sudo can be used instead, because sudo ties administrative actions to a specific user account and can be logged.
- B. Correct.
This is correct. Using a named user account with sudo allows the technician to perform only the necessary privileged tasks while maintaining accountability and auditability. This aligns with the principle of least privilege and common administrative best practices for Linux systems, where root-level tasks are elevated as needed rather than performed from a persistent root session.
- C. Incorrect.
This is incorrect. Sharing the root password violates security best practices because it removes individual accountability and increases the chance of unauthorized or untraceable administrative access. A common misconception is that shared credentials improve efficiency, but they create major auditing and security problems.
- D. Incorrect.
This is incorrect. Disabling the root account permanently is not the first step for this task and could prevent needed administrative recovery methods depending on system configuration. While some environments restrict direct root logins, the immediate best-practice action for completing the work is to use sudo from a named account, not to disable root access outright.