Day one on the box
Your first morning at Halvard Freight and the nightly rate sync failed. Orient on an unfamiliar machine, find the failure in the logs, work out which config value actually ran, and prove the fix with a dry run.
- beginner
- about 20 min
- 4 objectives
- par 10 steps
- Halvard Freight
Orient on an unfamiliar Linux box: the service unit, its logs and its working directory
Read the current task at the top of the console. Inspect evidence with the terminal or Files tab, then use the answer field to submit your findings. Tasks that ask for a fix check your file or service changes automatically.
No installation needed. The terminal runs supported commands and recorded programs in a simulated system. Need help? offers a starting point, then a clue or a worked example. Take time to investigate; the debrief includes a question about applying the lesson elsewhere. Your run is saved in this browser, and completed runs can be verified and saved to your account.
- Customer
- Halvard Freight (synthetic customer; every file and log on this box is made up for the exercise)
- Situation
- It is 09:14 on your first day on the Halvard engagement. The ops lead's handover note says the nightly
rate-syncjob pulls carrier rates into Halvard's pricing table and that it failed overnight. The engineer who built it left last month. You have a shell on the box it runs on and nothing else. - Your role
- You are the FDE taking over the integration. You may read anything on
halvard-int-01, edit the job's configuration, and run the job in dry-run mode. Do not guess: every answer in this mission is on the box. - Goal
- Find how last night's run ended, name the cause, correct the value that actually ran, and show the job completing a dry run.
- 1.State the exit code last night's rate-sync run ended with (you commit to an answer)
- 2.Name the cause of the failure (you commit to an answer)
- 3.Correct the value that actually ran, at the layer that supplied it
- 4.Show the job completing a dry run with the corrected configuration