Questions | Grade A | Pass Guaranteed - A+ Graded
SECTION 1: Zabbix Frontend & User Interface (Q1-Q15)
Q1: Which PHP configuration parameter in the Zabbix frontend controls the maximum
execution time for a single script, and what is the recommended minimum value for
large environments?
A. max_execution_time; 300 seconds [CORRECT]
B. memory_limit; 512M
C. upload_max_filesize; 64M
D. post_max_size; 32M
Correct Answer: A
Rationale: The max_execution_time directive defines how long a PHP script can run
before termination, with 300 seconds being the Zabbix-recommended minimum for
large environments to prevent timeouts during complex operations like report
generation. Option B controls memory allocation, while C and D govern file upload and
POST data size limits, not execution duration.
Q2: A Zabbix administrator needs to change the default language for all users across
the entire frontend. Where should this global setting be configured?
A. Administration → General → GUI, under the "Default language" dropdown [CORRECT]
B. User settings → Profile → Language
C. Administration → Users → Default preferences
D. Configuration → Hosts → Global settings
Correct Answer: A
,Rationale: The global default language is set in Administration → General → GUI, which
affects all users unless they override it in their personal profile. Option B only changes
the language for the current logged-in user, while C and D do not contain language
configuration options in the Zabbix frontend.
Q3: An administrator notices that timestamps in the Zabbix frontend are displaying
incorrectly for users in different geographic locations. Which setting should be
configured to ensure consistent time display across all user sessions?
A. Administration → General → GUI, set the default timezone and ensure users have
"System default" selected in their profiles [CORRECT]
B. Set the timezone in each host's configuration under Configuration → Hosts
C. Modify the PHP date.timezone in php.ini only
D. Configure the timezone in the Zabbix server configuration file (zabbix_server.conf)
Correct Answer: A
Rationale: The Zabbix frontend timezone is controlled through Administration →
General → GUI, where setting a default timezone ensures all users see consistent time
unless they explicitly override it. While PHP date.timezone (C) affects the server, the
frontend-specific setting in A is the proper GUI-level control; host configuration (B) and
server config (D) do not control frontend time display.
Q4: A user reports that their Zabbix dashboard bookmarks are no longer visible after a
browser cache clear. How are Zabbix frontend bookmarks actually stored?
A. Bookmarks are stored in the Zabbix database associated with the user profile and are
accessible from the "Favorites" section in the user menu [CORRECT]
B. Bookmarks are stored in browser localStorage only
C. Bookmarks are stored in browser cookies and expire after the session
D. Bookmarks are stored in the Zabbix server configuration cache
Correct Answer: A
,Rationale: Zabbix frontend bookmarks (favorites) are persisted in the database as part
of the user's profile data, making them available across different browsers and
sessions. Options B, C, and D incorrectly suggest client-side or server-cache storage,
which would not survive cache clearing or provide cross-device access.
Q5: Which Zabbix frontend menu path allows an administrator to configure the
maximum number of rows displayed in search results and the default search limit for
dropdowns?
A. Administration → General → GUI, under "Search/limits" parameters [CORRECT]
B. Administration → General → Other
C. User settings → Profile → Frontend
D. Configuration → Templates → Display options
Correct Answer: A
Rationale: The search and limit parameters, including maximum search results and
dropdown limits, are configured in Administration → General → GUI. This centralizes
frontend display behavior controls. Options B, C, and D do not contain these specific
search limit settings in the Zabbix frontend structure.
Q6: An administrator wants to customize the Zabbix login page branding by replacing
the default Zabbix logo with a corporate logo. Which approach is supported in the
standard Zabbix frontend?
A. Modify the custom CSS or replace the logo image in the frontend assets directory,
ensuring the file matches the expected filename and format [CORRECT]
B. Use Administration → General → GUI → "Login page branding" option
C. Upload the logo via Configuration → Maps → Background images
D. Change the logo through User settings → Profile → Theme customization
Correct Answer: A
Rationale: The Zabbix frontend supports login page customization by replacing the logo
file (typically logo.png) in the frontend assets directory or applying custom CSS, as there
, is no built-in GUI option for logo replacement. Options B and D describe non-existent
GUI options, while C is for map backgrounds, not login branding.
Q7: In the Zabbix frontend, where can an administrator configure the maximum number
of elements (such as hosts or triggers) displayed per page in monitoring views?
A. User settings → Profile → "Rows per page" setting, or Administration → General →
GUI for global defaults [CORRECT]
B. Configuration → Hosts → Display settings
C. Administration → General → Other → "Page limits"
D. Monitoring → Overview → View options
Correct Answer: A
Rationale: The "Rows per page" setting in the user profile controls pagination for
individual users, while the global default is set in Administration → General → GUI.
Options B, C, and D do not contain page limit configuration in the standard Zabbix
frontend menu structure.
Q8: Which Zabbix frontend PHP setting directly impacts the ability to import large
configuration files (such as XML templates with thousands of items)?
A. upload_max_filesize and post_max_size [CORRECT]
B. max_execution_time only
C. memory_limit and max_input_vars
D. display_errors and error_reporting
Correct Answer: A
Rationale: Large file uploads require both upload_max_filesize (controls maximum
uploaded file size) and post_max_size (controls maximum POST data size) to be
configured appropriately. While memory_limit (C) and max_execution_time (B) are
important for processing, they do not directly control the upload size capability; D is for
error display, not uploads.