2025 – Real Questions and Verified
Correct Answers (Latest Version)
Zabbix Architecture (Questions 1-12)
Question: What are the three main components of Zabbix? Answer: Server, Frontend,
Database. Rationale: The Server processes data, the Frontend provides the UI, and the
Database stores configurations/metrics; essential for understanding core setup (Zabbix
Manual 7.0, Ch. 1; verified in official training).
Question: What are the three primary functions of the Zabbix Server? Answer: Data
collection, Problem detection, Notification. Rationale: Server gathers metrics, evaluates
triggers for issues, and sends alerts; foundational architecture (Zabbix Manual 7.0, Ch. 2).
Question: What is the minimum supported MySQL version for Zabbix 7.0? Answer: 8.0.x.
Rationale: Zabbix 7.0 requires MySQL 8.0 or higher for stability; 8.0.20 recommended
(Zabbix Installation Guide 2025).
Question: Can Zabbix Server be installed on Windows? Answer: No. Rationale: Server
supports Linux/Unix only; Windows limited to Agent/Proxy (Zabbix Manual 7.0, System
Requirements).
Question: Which libraries are required for Zabbix on Linux? Answer: Libpcre, Libevent,
Zlib. Rationale: These handle regex, events, and compression; mandatory for
compilation (Zabbix Installation Wiki, 2025).
Question: How often do Frontend changes update the database by default? Answer: Once
per minute. Rationale: Config cache sync interval; adjustable via zabbix.conf (Zabbix
Manual 7.0, Ch. 3).
Question: Can Zabbix Server reload configuration at runtime? Answer: Yes. Rationale: Use
zabbix_server -R config_cache_reload; no restart needed (Zabbix CLI Docs).
Question: What are the two modes for Zabbix Agent? Answer: Active and Passive.
Rationale: Active: Agent pushes data; Passive: Server polls (Zabbix Manual 7.0, Agent
Section).
, Question: What does the grey availability icon mean for a host? Answer: At least one
interface unknown, none unavailable. Rationale: Indicates partial status; yellow for
unavailable (Zabbix UI Guide).
Question: Default unreachable delay for pollers? Answer: 15 seconds. Rationale:
UnreachableDelay=15s; retries before marking down (Zabbix Server Config).
Question: When was Zabbix 1.0 released? Answer: March 23, 2004. Rationale: Historical
fact from Zabbix timeline; tests foundational knowledge.
Question: How often is a long-term support Zabbix version released? Answer: Every 18
months. Rationale: LTS versions (e.g., 6.0, 7.0) for stability; aligns with release cycle.
Domain 2: Host and Item Configuration (Questions 13-30)
Question: What options exist for filtering hosts? Answer: Host group, template, name, DNS,
IP, Port, Monitoring by (any, server, proxy), tags. Rationale: Comprehensive filters in
Host list; enables efficient management (Zabbix Manual 7.0, Monitoring Hosts).
Question: What tabs are in host creation/editing? Answer: Host, IPMI, Tags, Macros,
Inventory, Encryption, Value mapping. Rationale: UI sections for configuration; e.g.,
Macros for custom params (Zabbix Frontend Guide).
Question: What are the four types of macros and their syntax? Answer: Built-in {MACRO},
User-defined {$MACRO}, LLD {#MACRO}, Expression {?MACRO}. Rationale:
Syntax distinguishes scope; e.g., {$MACRO} for host-level (Zabbix Manual 7.0, Macros
Ch.).
Question: Macro for last received metric? Answer: {ITEM.LASTVALUE}. Rationale:
Retrieves latest value in triggers/items; common in expressions.
Question: Levels for macro definition and precedence order? Answer: Host, Template,
Global; precedence: Host > Template > Global. Rationale: Host overrides others; avoids
conflicts (Zabbix Manual 7.0).
Question: Inherited macros displayed by default? Answer: False. Rationale: Toggle in UI;
reduces clutter (Frontend config).
Question: Host groups used for? Answer: Logical grouping of hosts and templates.
Rationale: Permissions and inheritance; e.g., "Linux servers" group (Zabbix Manual).
Question: All access rights based on user groups and host groups? Answer: True. Rationale:
RBAC model; granular control (Zabbix Security Ch.).
Question: Required to create parent host group before nested? Answer: False. Rationale:
Flexible hierarchy; create in any order (UI behavior).