nerdexam
CompTIA

CAS-002 · Question #223

After being informed that the company DNS is unresponsive, the system administrator issues the following command from a Linux workstation: - SSH-p 2020-l user dnsserver.company.com Once at the…

The correct answer is A. The administrator must use the sudo command in order to restart the service. Restarting system services such as BIND on Linux requires root-level privileges, and a non-root SSH user must use sudo to execute privileged commands.

Technical Integration of Enterprise Components

Question

After being informed that the company DNS is unresponsive, the system administrator issues the following command from a Linux workstation:

  • SSH-p 2020-l user dnsserver.company.com

Once at the command prompt, the administrator issues the below commanD.

  • Service bind restart
  • The system returns the below response:
  • Unable to restart BIND

Which of the following is true about the above situation?

Options

  • AThe administrator must use the sudo command in order to restart the service.
  • BThe administrator used the wrong SSH port to restart the DNS server.
  • CThe service was restarted correctly, but it failed to bind to the network interface.
  • DThe service did not restart because the bind command is privileged.

How the community answered

(36 responses)
  • A
    89% (32)
  • B
    8% (3)
  • D
    3% (1)

Why each option

Restarting system services such as BIND on Linux requires root-level privileges, and a non-root SSH user must use sudo to execute privileged commands.

AThe administrator must use the sudo command in order to restart the service.Correct

The 'service bind restart' command modifies system service state, which requires root or sudo privileges. Because the administrator logged in as a non-root user ('user'), the OS refused the operation and returned 'Unable to restart BIND' - the fix is to prepend sudo to the command so the OS elevates privileges for that single operation.

BThe administrator used the wrong SSH port to restart the DNS server.

The administrator successfully reached the server command prompt, proving the SSH connection on port 2020 worked correctly - the port is not the issue.

CThe service was restarted correctly, but it failed to bind to the network interface.

The error message indicates the service failed to restart entirely, not that it started successfully but could not bind to a network interface, which would produce a different error from BIND itself.

DThe service did not restart because the bind command is privileged.

BIND is not inherently a privileged binary in the sense of being restricted from elevated users - it simply requires root or sudo elevation, which is exactly what choice A addresses.

Concept tested: Linux sudo privilege escalation for service management

Source: https://man7.org/linux/man-pages/man8/sudo.8.html

Topics

#Linux privileges#sudo#DNS administration#least privilege

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CAS-002 Practice