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…
Question
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)- A2% (1)
- B4% (2)
- C9% (4)
- D83% (39)
- E2% (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 0in aGRANTstatement does not mean zero connections allowed - it means "inherit the globalmax_user_connectionsvalue." Bob is effectively unrestricted beyond the global cap of 10. - B is wrong because
max_user_connectionsis tracked per user account, not accumulated across all users sharing the same host pattern. - C is wrong because
connect_timeout = 10seconds 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
Community Discussion
No community discussion yet for this question.