Optimal Snapshot Selection for Data Recovery
Short answer
C Restore the 11:00 a.m. snapshot because it is the most recent snapshot created before the 11:30 a.m. deletion, ensuring the 9:30 a.m. data is recovered while minimizing loss of subsequent writes.
Question
Key Takeaways
Tested: Point-in-time recovery logic. Trap: Selecting a snapshot taken after the corruption event or ignoring the 'minimize loss' constraint by picking an older snapshot.
Determine the correct snapshot time to restore deleted data while minimizing loss. The answer is the latest snapshot preceding the error.
Common mistake: Choosing Option A (12:00) because it seems 'newer', but it fails to contain the pre-deletion data. Or choosing B (9:00) thinking it's safer, but it loses more recent valid data.
Expert Analysis
The core concept here is snapshot restore logic within Huawei Intelligent Storage Systems (and general block storage principles). A snapshot captures the state of a LUN at a specific point in time. When data is deleted or corrupted, restoring from a snapshot reverts the LUN to that previous state.
The scenario involves:
- Data Deletion Time: The employee deleted data generated at 9:30 a.m. at 11:30 a.m.
- Goal: Retrieve the deleted data (from 9:30 a.m.) AND minimize service data loss.
To minimize data loss, we must choose the most recent snapshot that was created before the deletion occurred but after the data was successfully written.
- Snapshot at 9:00 a.m. (Option B): Created before the data existed (at 9:30 a.m.). Restoring this would lose the data generated between 9:00 and 9:30, which might be valid, but more importantly, it doesn't help retrieve data generated at 9:30 if the snapshot didn't include it yet. More critically, any data written after 9:00 is lost.
- Snapshot at 10:00 a.m. (Option D): This snapshot exists after the data was written (9:30 a.m.) and before the deletion (11:30 a.m.). It contains the 9:30 a.m. data. However, any data written between 10:00 a.m. and 11:30 a.m. will be lost.
- Snapshot at 11:00 a.m. (Option C): This snapshot exists after the data was written (9:30 a.m.) and before the deletion (11:30 a.m.). It is the most recent snapshot prior to the error. Restoring this brings back the 9:30 a.m. data and preserves all data written between 10:00 a.m. and 11:00 a.m., minimizing loss compared to earlier snapshots.
- Snapshot at 12:00 p.m. (Option A): This snapshot is created after the deletion event (11:30 a.m.). It likely reflects the state after the deletion, meaning the deleted data is not present, or if it's a copy-on-write mechanism, it might not contain the pre-deletion state depending on implementation. Regardless, it is logically invalid for recovering pre-deletion data because it occurred post-error.
Therefore, the 11:00 a.m. snapshot is the optimal choice as it is the latest safe point-in-time recovery available.
Common Mistake: Choosing the earliest possible snapshot (9:00 a.m.) or the one closest to the current time without checking if it predates the error. Candidates often confuse "latest snapshot" with "snapshot taken right now," failing to realize that snapshots taken after the corruption/deletion do not contain the good data.
Exam Strategy
When asked to minimize data loss during recovery, always select the chronologically latest snapshot that occurs strictly before the failure or deletion event. Exclude snapshots taken after the incident as they may reflect the corrupted state. Verify the target data creation time is included in the chosen snapshot window.
Frequently Asked Questions
Why can't I restore the 12:00 PM snapshot?
Does restoring a snapshot delete data created after the snapshot?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
DUKSCO 👍 1 Answered C11:00 (C) also contains the 9:30 a.m. data and minimizes data loss for any other valid work done between 10:00 and 11:00 a.m.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.