SadServers - Linux & DevOps Troubleshooting Interviews

Troubleshooting Scenarios

advent2025 apache bash c caddy clickhouse csv data processing disk volumes dns docker envoy etcd git golang gunicorn hack haproxy harbor hashicorp vault helm java jenkins json kubernetes linux-other mysql nginx php postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord systemd

realistic / interviews new pro business

Clickhouse

ClickHouse database scenarios

#	Name	Level	Time	Type
1	"Solanea": ClickHouse mad house	Medium	20 m	Do New	"Solanea": ClickHouse mad house Scenario: "Solanea": ClickHouse mad house Level: Medium Type: Do Access: Email Description: You have a ClickHouse installation CHI running on a Kubernetes cluster and a set of requests (located at ~/data/requests.csv) that you must populate into the http_requests table in the monitoring database (table may not exist in all pod instances). Do this insert in all pod instances of the database. The user and password to connect to the database are default. The keeper pods provide clickhouse replication services. Test: You are able to query the database and see the data: `clickhouse-client -h --password default -q 'SELECT COUNT() FROM monitoring.http_requests'` The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute. Time to Solve:* 20 minutes.

Troubleshooting Scenarios

Clickhouse

ClickHouse database scenarios

"Solanea": ClickHouse mad house

Send Us Feedback or Get Notified