Git Recovering Abandoned Commits Quiz

Review

1. What does “abandoned commit” mean in this lesson?

   The commit can still exist in the object database even after current refs stop reaching it.
2. What should you normally inspect first after a local branch was accidentally moved backward?

   The reflog can identify an earlier value of the local reference.
3. What can `main@{1}` provide during recovery?

   Reflog selectors refer to earlier values in a reference’s local reflog.
4. Why can `git branch recovered "main@{1}"` recover an existing commit without creating a replacement commit?

   A branch is a reference, so pointing it at the recovered object makes that object reachable again.
5. Why is `--no-reflogs` useful with `git fsck --unreachable` in the fallback lab?

   Without `--no-reflogs`, reflog-referenced objects can be treated as reachable for fsck’s default head set.
6. What does `git fsck --unreachable` report?

   The official fsck manual defines `--unreachable` this way.
7. What does a `dangling commit` diagnostic mean at the recovery level?

   A dangling commit remains present and can be a recovery root.
8. What is the strongest simple proof that a recovery branch names the intended commit?

   The object ID identifies the exact commit object.
9. Which statement about recovery permanence is accurate?

   Git’s documented expiration and pruning behavior means local recovery is not an unlimited guarantee.
10. What is the correct high-level recovery order when a local commit disappears from a branch tip?

    The safe workflow preserves and investigates existing evidence before modifying repository state.