Which two are features of MySQL Enterprise Firewall? (Choose two.)

Question

Options

• Arecording incoming SQL statement to facilitate the creation of a whitelist of permitted commands
• Bblocking of potential threats by configuring pre-approved whitelists
• Cmodifying SQL statement dynamically with substitutions
• Dautomatic locking of user accounts who break your firewall
• Eprovides stateless firewall access to TCP/3306

• A
  9% (4)
• B
  86% (38)
• D
  2% (1)
• E
  2% (1)

Explanation

Important note: The stated correct answer (B, C) appears to be incorrect. Based on MySQL Enterprise Firewall documentation, the actual correct answers are most likely A and B.

Why A and B are correct:

MySQL Enterprise Firewall operates by first running in training/recording mode, where it captures incoming SQL statements to build a whitelist of approved patterns (A). Once trained, it blocks any SQL statements that don't match the whitelist (B), protecting against SQL injection and unauthorized queries.

Why the others are wrong:

• C is incorrect - dynamically modifying/rewriting SQL is the function of the MySQL Query Rewrite Plugin, a separate component; the firewall only allows or blocks, it does not transform.
• D is incorrect - account locking is not a firewall function; MySQL Enterprise Firewall operates at the statement level, not the account management level.
• E is incorrect - MySQL Enterprise Firewall is an application-layer plugin that inspects SQL semantics, not a stateless network/TCP-level firewall.

Memory tip: Think "Record, then Reject" - the firewall records a whitelist (A), then rejects anything outside it (B). The firewall watches SQL, it never changes it (ruling out C).

If this question came from a study guide, I'd recommend verifying it against the official MySQL Enterprise Firewall documentation, as B+C looks like a typo for A+B.

No community discussion yet for this question.