You have created a new user with this statement: CREATE USER 'erika'@'localhost' IDENTIFIED BY 'first#1Pass' PASSWORD EXPIRE; What is the outcome?

Question

Options

• AWhen 'erika'@'localhost' tries to log in with the MySQL command-line client, the user will have to change the password before seeing the MySQL> prompt.
• BWhen 'erika'@'localhost' tries to log in with the MySQL command-line client, the user will not be permitted to log in because the password is expired.
• CWhen 'erika'@'localhost' tries to log in with the MySQL command-line client, the user will be permitted to log in but will not be able to issue any statements until the user changes the password.
• DYou receive a syntax error that indicates that you cannot set a password and expire it at the same time.

• A
  4% (2)
• B
  6% (3)
• C
  88% (43)
• D
  2% (1)

Explanation

When PASSWORD EXPIRE is used in CREATE USER, MySQL allows the user to connect successfully but places the session into sandbox mode - the user reaches the mysql> prompt but every SQL statement they attempt returns an error instructing them to change their password first (via SET PASSWORD or ALTER USER). This is by design: MySQL separates authentication (can you log in?) from authorization to act (can you run queries?).

Why the distractors are wrong:

• A is wrong because the password change does not block the prompt itself - the user gets to mysql> normally; the restriction kicks in on statement execution.
• B is wrong because MySQL does not refuse the connection; the login succeeds, only statement execution is blocked.
• D is wrong because this is perfectly valid MySQL syntax - PASSWORD EXPIRE is an explicit option in CREATE USER and combines legally with IDENTIFIED BY.

Memory tip: Think of sandbox mode as a hotel check-in where you get your key and enter the room (logged in, see the prompt), but the room is locked down until you reset your PIN at the front desk (change the password). You're in - you just can't do anything yet.

No community discussion yet for this question.