nerdexam
CompTIA

XK0-005 · Question #1651

A developer is unable to access a Linux server via SSH. Given the following output: Which of the following explains why the developer is unable to log in to the server?

The correct answer is B. The developer's account has been locked out. The developer is unable to log in to the server via SSH because their account has been locked, which prevents any successful authentication attempts.

Troubleshooting

Question

A developer is unable to access a Linux server via SSH. Given the following output: Which of the following explains why the developer is unable to log in to the server?

Exhibit

XK0-005 question #1651 exhibit

Options

  • AThe developer's private key has been deleted from the server.
  • BThe developer's account has been locked out.
  • CThe developer's public key is in the wrong location.
  • DSSH has been disabled for user log-in.

How the community answered

(33 responses)
  • A
    3% (1)
  • B
    88% (29)
  • C
    6% (2)
  • D
    3% (1)

Why each option

The developer is unable to log in to the server via SSH because their account has been locked, which prevents any successful authentication attempts.

AThe developer's private key has been deleted from the server.

A private key resides on the *client* machine, not the server. If the corresponding public key on the server was deleted, authentication would fail, but it wouldn't directly lead to an 'account locked' state.

BThe developer's account has been locked out.Correct

An account lockout explicitly prevents any further login attempts, regardless of correct credentials or SSH key setup, making it impossible for the developer to access the server.

CThe developer's public key is in the wrong location.

If the developer's public key is in the wrong location on the server, SSH key authentication would fail, but this failure itself does not inherently result in an account lockout unless a brute-force policy is triggered.

DSSH has been disabled for user log-in.

If SSH was disabled for user login, the connection would typically be refused at an earlier stage, and the server would not usually provide an 'account locked' message.

Concept tested: SSH login issues, account lockout

Source: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/sec-locking_out_user_accounts

Topics

#SSH#Account Lockout#User Authentication#Linux Troubleshooting

Community Discussion

No community discussion yet for this question.

Full XK0-005 Practice