Challenge 01
The migration that broke the portal
Scenario
The customer's ops team moved the portal API and its database to a new app server and applied a hardening baseline. Every branch now gets a 502. The gateway, the app server and the database login each hold one fault, and the change note offers a leaked legacy login as the rollback.
What you learn
Whether they follow the evidence layer by layer, keep the hardening, and ask for a grant instead of reusing the leaked login.
In the workspace
$ ls challenges/
workspace, runbook.md, README.md
candidate has:
- · a real Linux box in the browser
- · kubectl, docker, terraform, jq, yq
- · cluster, repo and cloud creds pre-wired
- · auto-checks running in the background
interviewer sees:
- · every keystroke + every command
- · terminal + screen recording
- · auto-graded pass/fail per check