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?

A missing private key on the client side would prevent authentication, but the server-side message "Account locked" points to an issue with the user's account state on the server, not a client-side key problem.

The error message "Account locked. Try again later" explicitly states that the developer's account is locked. This status directly prevents any login attempts, including those made via SSH, regardless of correct credentials or keys.

A public key in the wrong location on the server would typically result in "Permission denied (publickey)" or similar errors, not an "Account locked" message.

If SSH were disabled for user login, the server would likely refuse the connection much earlier or give a more general "Connection refused" error, not an "Account locked" message after the authentication attempt.