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 node.js php podman postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord systemd

realistic / interviews new pro business

Git

Git Scenarios

#	Name	Level	Time	Type
1	"Gitega": Find the Bad Git Commit	Easy	15 m	Do Pro	"Gitega": Find the Bad Git Commit Scenario: "Gitega": Find the Bad Git Commit Level: Easy Type: Do Access: Paid Description: The directory at /home/admin/git has a Git repository with a Golang program and a test for it. To execute the test, from this "git" directory run: `go test`. The last (current HEAD) commit fails the test. Suppose the first commit passed the test. Find the (long hash) commit that first broke the test and enter it in the /home/admin/solution file. For example: `echo 9e80a7eb1b09385e93ab4a76cb2c93beec48fd9f > /home/admin/solution` Test: Doing `md5sum /home/admin/solution` returns `f7db1bb6b7bfcd66a4eb66782804b39d`. The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute. Time to Solve: 15 minutes.

Troubleshooting Scenarios

Git

Git Scenarios

"Gitega": Find the Bad Git Commit

Send Us Feedback or Get Notified