Capstone labs · Lesson 18 of 18 · 8 minutes

Capstone verified restore

Stage, compare, archive, and hash a restored web artifact.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Stage the restored file
Run cp restore/index.html lab/verified-restore.html.
Hint & worked example
Copy a file to a new location, leaving the original in place.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
cp restore/index.html lab/verified-restore.html
```
Remember: Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
2
Identify the staged artifact
Run file lab/verified-restore.html.
Hint & worked example
Identify a file from its characteristics rather than trusting only the filename extension.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
file lab/verified-restore.html
```
Remember: The simulator uses a small reviewed type classifier, not the full system magic database.
3
Compare source and staged copy
Run diff restore/index.html lab/verified-restore.html.
Hint & worked example
Compare two text files; a difference is a meaningful nonzero status, not necessarily an execution error.
Inspect the differences. diff exits 1 when files differ and 0 when they match.
```
diff restore/index.html lab/verified-restore.html
```
Remember: Status 1 means differences for diff; shell status must be interpreted in command context.
4
Archive the staged restore
Run tar -cf lab/verified-restore.tar lab/verified-restore.html.
Hint & worked example
Practice archive inventory, creation, and extraction in a simulated archive format.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
tar -cf lab/verified-restore.tar lab/verified-restore.html
```
Remember: These training archives are virtual data structures, not downloadable production tar files.
5
Hash the restore archive
Run sha256sum lab/verified-restore.tar.
Hint & worked example
Compare content digests to detect byte changes, not to establish who authored the file.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
sha256sum lab/verified-restore.tar
```
Remember: A checksum detects changes only relative to a trusted expected digest.

Understand the pattern

Proving a restore artifact before deployment helps operators explain what they know before they change anything.

cp: Copy a file to a new location, leaving the original in place.
Confirm the destination before replacing a file. This lab supports file copies, not every cp option.
file: Identify a file from its characteristics rather than trusting only the filename extension.
The simulator uses a small reviewed type classifier, not the full system magic database.
diff: Compare two text files; a difference is a meaningful nonzero status, not necessarily an execution error.
Status 1 means differences for diff; shell status must be interpreted in command context.
tar: Practice archive inventory, creation, and extraction in a simulated archive format.
These training archives are virtual data structures, not downloadable production tar files.
sha256sum: Compare content digests to detect byte changes, not to establish who authored the file.
A checksum detects changes only relative to a trusted expected digest.

Worked example and expected result

$ cp restore/index.html lab/verified-restore.html

(no output; exit 0)