What are two reasons that agents maintain communication with the supervisor after registration? (Choose two.)

Question

Options

• ATo report incoming EPS value
• BTo report logs and events
• CTo report health and its status
• DTo collect new agent template

• A
  3% (1)
• B
  3% (1)
• C
  94% (32)

Explanation

After registration, agents maintain an ongoing communication channel with the supervisor primarily to report health and status (C) - sending periodic heartbeats so the supervisor knows the agent is alive and functioning - and to collect new agent templates (D), allowing the supervisor to push updated configurations or policy templates to the agent over time. These two functions represent the core purpose of the persistent post-registration channel: bidirectional lifecycle management.

Why the distractors are wrong:

• A (EPS values) - Incoming EPS (Events Per Second) is a performance metric, not a driver of the agent-supervisor communication channel itself.
• B (logs and events) - Log and event data typically flow through separate dedicated channels (e.g., syslog, SNMP traps) rather than through the supervisor registration/management channel.

Memory tip: Think "Health Check, Get Templates" - the supervisor needs to know the agent is alive (health/status), and the agent needs to know what to do next (new templates). It's a two-way lifecycle handshake: status up, config down.

No community discussion yet for this question.