nerdexam
Oracle

1Z0-888 · Question #87

An employee cannot access the company database. You check the connection variables: mysql> SHOW GLOBAL VARIABLES LIKE '%connect%'; +--------------------+-------+ | Variable_name | Value |…

The correct answer is D. Joe has exceeded the max_user_connections global limit. Option D is correct because Joe's per-user grant limit (MAX_USER_CONNECTIONS 10) exactly matches the global max_user_connections value of 10. If Joe already has 10 concurrent sessions open, any new connection attempt will be refused - he has hit his ceiling, which aligns with…

Installation and Configuration

Question

An employee cannot access the company database. You check the connection variables: mysql> SHOW GLOBAL VARIABLES LIKE '%connect%'; +--------------------+-------+ | Variable_name | Value | +--------------------+-------+ | connect_timeout | 10 | | innodb_buffer_pool_dump_at_shutdown | ON | | innodb_buffer_pool_load_at_startup | ON | | innodb_connect_stats_allow_query_stats | OFF | | max_connect_errors | 10 | | max_connections | 50 | | max_user_connections | 10 | +--------------------+-------+ 8 rows in set (0.00 sec) A look at the user privileges shows: GRANT ... TO 'bob'@'%.example.com' WITH MAX_USER_CONNECTIONS 0; GRANT ... TO 'kay'@'%.example.com' WITH MAX_USER_CONNECTIONS 1; GRANT ... TO 'joe'@'%.example.com' WITH MAX_USER_CONNECTIONS 10; What is a valid for why one of the users is unable to connect to the database?

Options

  • ABob has max_user_connections set to zero, which blocks all his connections.
  • BAll users are blocked because max_user_connections is accumulated over the host account information.
  • Cconnect_timeout is too small to allow a connection to occur.
  • DJoe has exceeded the max_user_connections global limit.
  • EKay is already connected elsewhere and attempting to log in again.

How the community answered

(47 responses)
  • A
    2% (1)
  • B
    4% (2)
  • C
    9% (4)
  • D
    83% (39)
  • E
    2% (1)

Explanation

Option D is correct because Joe's per-user grant limit (MAX_USER_CONNECTIONS 10) exactly matches the global max_user_connections value of 10. If Joe already has 10 concurrent sessions open, any new connection attempt will be refused - he has hit his ceiling, which aligns with (and is capped by) the global setting.

Why the distractors are wrong:

  • A is the classic trap: in MySQL, WITH MAX_USER_CONNECTIONS 0 in a GRANT statement does not mean zero connections allowed - it means "inherit the global max_user_connections value." Bob is effectively unrestricted beyond the global cap of 10.
  • B is wrong because max_user_connections is tracked per user account, not accumulated across all users sharing the same host pattern.
  • C is wrong because connect_timeout = 10 seconds is the time the server waits for the initial handshake packet - a perfectly normal value, not a bottleneck.
  • E is tempting (Kay's limit of 1 means a second login would fail), but it requires an assumption - that Kay is currently connected - which isn't established by the data shown. D is directly inferable from the configuration alone.

Memory tip: Remember that MAX_USER_CONNECTIONS 0 in a GRANT is a reset-to-global, not a block - think of it as "zero override." When a user's explicit grant limit equals the global limit, they're the first to be squeezed out under load.

Topics

#max_user_connections#connection limits#user privileges#MySQL configuration

Community Discussion

No community discussion yet for this question.

Full 1Z0-888 Practice