Which two MySQL Server accounts are locked by default? (Choose two.)

Question

Options

• Aany user set as DEFINER for stored programs
• Bany internal system accounts
• Cany new ROLE accounts
• Dany user created without a password
• Eany user created with a username, but missing the host name

• A
  95% (58)
• C
  2% (1)
• D
  3% (2)

Explanation

MySQL ships with internal system accounts - such as mysql.sys@localhost, mysql.session@localhost, and mysql.infoschema@localhost - that are locked by default so the server can use them internally without exposing them as interactive login targets (option B). Accounts named as the DEFINER for stored programs (procedures, functions, triggers, events) are also locked by default, allowing the server to use them as a privilege execution context without permitting direct client connections (option A).

Why the distractors are wrong:

• C (ROLE accounts): While roles in MySQL 8.0 are technically stored as locked accounts, the question targets a different category - roles are a separate construct from ordinary user accounts, and the built-in locking there is a side effect of their design, not the same default-lock policy being tested here.
• D (users without a password): Creating a user without a password leaves the account insecure, but it is not locked - the user can still log in unless explicitly locked with ACCOUNT LOCK.
• E (users missing a host name): Omitting the host name causes MySQL to default to % (any host), which is also unlocked by default.

Memory tip: Think "Internal accounts stay Inside, DEFINER accounts Don't let you in" - both categories exist to serve the server, not humans, so MySQL locks them to enforce that boundary.

No community discussion yet for this question.