The MySQL user adam currently has USAGE permissions to the database. The football database is transactional and has non-stop updates from application users. The adam user needs to be able to take…

Question

Options

• AThe adam user must also have SINGLE TRANSACTION global grant to take a consistent backup.
• BThe adam user needs the PROCESS privilege to be able to take a consistent backup while other users are connected.
• CThe adam user must have the SUPER privilege in order to take data backups.
• DThe adam user must also have SELECT on the football database for backups to work.

• A
  24% (6)
• B
  12% (3)
• C
  60% (15)
• D
  4% (1)

Explanation

SUPER privilege is required because mysqldump performs administrative operations internally - such as FLUSH TABLES or manipulating binary log state - that require elevated server-level access, even when --single-transaction is used to avoid explicit table locking for InnoDB tables. Without SUPER, the dump process cannot complete the necessary session-level operations to guarantee a consistent snapshot across the backup.

Why the distractors are wrong:

• A - "SINGLE TRANSACTION" does not exist as a MySQL grant/privilege; it is a mysqldump option flag, not a database permission that can be granted.
• B - PROCESS privilege allows a user to see other sessions' threads via SHOW PROCESSLIST; it is unrelated to obtaining a consistent backup snapshot.
• D - While SELECT is intuitive (you need to read data to back it up), the question is specifically about what enables a consistent backup under --single-transaction; SELECT alone is insufficient to authorize the server-level flush operations mysqldump requires.

Memory tip: Think of it this way - --single-transaction controls how the dump is consistent, but SUPER controls whether the user is allowed to perform the administrative operations mysqldump needs behind the scenes. The option and the privilege are a pair.

No community discussion yet for this question.