What are three methods to reduce MySQL server exposure to remote connections? (Choose three.)

Question

Options

• Ausing SSL when transporting data over remote networks
• BUsing the sql_mode=STRICT_SECURE after connections are established for encrypted communications
• Csetting --skip-networking when remote connections are not required
• Dsetting specific grant privileges to limit remote authentication
• Esetting --mysql_secure_configuration to enable paranoid mode

• A
  74% (25)
• B
  9% (3)
• E
  18% (6)

Explanation

Reducing MySQL remote exposure requires a layered approach: encrypting traffic in transit, restricting the network surface, and controlling who can authenticate. SSL (A) protects data traveling over untrusted networks by encrypting the connection, preventing eavesdropping. --skip-networking (C) disables TCP/IP entirely so MySQL only accepts local Unix socket connections - the strongest possible protection when no remote access is needed. Grant privileges (D) let you restrict user accounts to specific hostnames or IP ranges (e.g., GRANT ... TO 'user'@'192.168.1.10'), so even if the port is open, unauthorized hosts cannot authenticate.

B is wrong because sql_mode controls data validation behavior (e.g., strict inserts) - it has nothing to do with network security or encryption. E is wrong because --mysql_secure_configuration with a "paranoid mode" does not exist; the real tool is mysql_secure_installation, a setup script, not a runtime flag.

Memory tip: Think S-S-G - Secure the wire (SSL), Silence the socket (skip-networking), Guard the gate (Grants). The two distractors are giveaways: one misuses a real but unrelated setting (sql_mode), and the other invents a plausible-sounding but fictional flag.

No community discussion yet for this question.