Dashboard design for agent monitoring in Agentic AI - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key Metrics for Agent Monitoring Dashboard

Which of the following metrics is most important to display on a dashboard monitoring multiple AI agents' health and performance?

A CPU usage, memory consumption, and response latency of each agent

B Number of user clicks on the dashboard interface

C Total number of agents deployed without status details

D Color scheme preferences of the dashboard users

💡 Hint

Think about what helps you understand if agents are working well or need attention.

CPU usage, memory consumption, and response latency directly show agent health and performance, which are critical for monitoring.

💻 Command Output

intermediate

Output of Agent Status Query Command

What is the output of the following command querying agent statuses?

Agentic AI

agentctl status --all --format json

A Error: Unknown command 'agentctl'

B [{"agent_id": "a1", "status": "active"}, {"agent_id": "a2", "status": "inactive"}]

C {"agent_id": "a1", "status": "active"}

D ["a1", "a2", "a3"]

💡 Hint

The command lists all agents with their statuses in JSON format.

The command outputs a JSON array with each agent's ID and current status, showing active and inactive agents.

❓ Configuration

advanced

Configuring Alert Thresholds for Agent Latency

Which configuration snippet correctly sets an alert to trigger if any agent's response latency exceeds 500ms?

A

alerts:
  latency_threshold_ms: 500
  trigger_on: agent_cpu_usage
  action: notify_admin

B

alerts:
  trigger_on: agent_response_latency
  latency_threshold: 'five hundred'
  action: notify_admin

C

alerts:
  latency_threshold_ms: 500
  action: notify_admin

D

alerts:
  latency_threshold_ms: 500
  trigger_on: agent_response_latency
  action: notify_admin

💡 Hint

Look for correct keys and values that match latency and threshold.

Option D correctly specifies the latency threshold in milliseconds, the trigger metric, and the action to notify admin.

❓ Troubleshoot

advanced

Troubleshooting Missing Agent Data on Dashboard

After deploying the dashboard, some agents show no data. What is the most likely cause?

A Dashboard refresh interval is set to 1 second

B Dashboard color scheme is incompatible with agent data format

C Agents are not sending telemetry data due to network issues

D Agent IDs are too long to display on the dashboard

💡 Hint

Think about what stops data from reaching the dashboard.

If agents cannot send telemetry data because of network problems, the dashboard will show missing data for those agents.

🔀 Workflow

expert

Steps to Add a New Agent to the Monitoring Dashboard

What is the correct order of steps to add a new AI agent to the monitoring dashboard?

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 3,1,2,4

💡 Hint

Think about registering first, then configuring data flow, then updating dashboard, then verifying.

The new agent must be registered first, then configured to send data, then the dashboard updated, and finally verification done.