Class 39 visual reference. Use it as the map, then prove it in the reading, lesson, and lab.
Overview
Module: ARR Data Model & Compose Activity type: Quiz / retrieval practice Target: ≥80% Objective: Explain why a configuration archive alone is not a complete recovery strategy.
Learn
Questions
In plain words: Read this block, then try the next action. If you feel stuck, tap What this means.
Why is successful creation of a compressed configuration file insufficient proof that recovery will work?
What is the difference between an archive checksum and semantic configuration validation?
Why should a backup normally be restored into a candidate directory before it replaces active configuration?
In the lab, why does the drifted app.json pass the Python validator but fail comparison with the backup manifest?
What security limitation remains when an archive and its checksum are writable by the same compromised account?
What is the purpose of retaining config.drifted and rollback/pre-recovery-config during promotion?
Why should relative paths in a checksum manifest be verified from the intended package root?
What does a successful configuration promotion fail to prove about a real application?
In plain words: Make a safety copy first so a mistake does not erase your work.
Learn
After scoring
In plain words: Read this block, then try the next action. If you feel stuck, tap What this means.