Restore stock to a supported point before the bad import

The target moves past the faulty import

The mistaken import reached all current replicas. Select a historical target whose complete supporting log is retained.

BOTIE

The target is now position thirteen, which includes the bad north-to-zero update. What does a successful replay mean?

The inputs we are comparing

Backup snapshot

Same in both cases

{
  "seq": 10,
  "state": {
    "north": 8,
    "south": 2
  }
}

Retained recovery log

Same in both cases

[
  {
    "seq": 11,
    "id": "north",
    "units": 5
  },
  {
    "seq": 12,
    "id": "south",
    "units": 5
  },
  {
    "seq": 13,
    "id": "north",
    "units": 0
  }
]

Chosen recovery position

Stop before the faulty change

A later target includes the faulty import

Result for stop before the faulty change

{
  "seq": 12,
  "state": {
    "north": 5,
    "south": 5
  }
}

Choose an explanation to test

It correctly reconstructs that later point, including the unwanted updateA restore automatically recognises and omits every bad business operation

A restored interval introduces a new store

This check uses the pieces from “Reconstruct the chosen inventory point”.

BOTIE

The snapshot at twenty has west four. Retained position twenty-one sets east to three, twenty-two sets west to two, and twenty-three would zero east. Restore through twenty-two and predict the checkpoint.

Backup snapshot: { "seq": 20, "state": { "west": 4 } }
Retained recovery log: [ { "seq": 23, "id": "east", "units": 0 }, { "seq": 21, "id": "east", "units": 3 }, { "seq": 22, "id": "west", "units": 2 } ]
Chosen recovery position: 22

What result should your machine produce for this case?

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

Which legitimate later actions and external deliveries would need reconciliation after a historical cutover?

Your notes for later. These stay with this journey.

A restore changes stored state. It needs a measured, authorised service recovery plan and does not undo outside effects.

Consecutive positions and replacement records are a local teaching protocol. This is not a physical backup, restore guarantee or rollback of external effects.

Work through the Python challenges →

Continue the courseA Fast Feature Lookup Still Has to Mean the Right Thing →

← The New Sensor Sends a Different Document