Store only regenerable cache data on temporary space that may be lost when a virtual machine is stopped or destroyed.
Which design statement is appropriate?
Keep regenerable data such as cache on volatile storage and place authoritative data on persistent storage with backups.
Detailed explanation
Correct. Important data should be kept on persistent storage or backups because volatile space can disappear.
Incorrect. Volatile storage must not be the only copy of authoritative data.
Incorrect. Encryption and protection depend on the service and configuration; volatility does not make storage inherently safer.
Incorrect. Provider operations and virtual machine lifecycle can remove volatile data.
Try it yourself
An example you can run in a temporary verification environment.
printf '%s\n' 'keep source data on durable storage'Expected result
keep source data on durable storageKey points
- Volatile storage
- Persistence
- Backup
Notes
- Environment: クラウドストレージの概念確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Lifecycle
Check whether data can disappear when an instance is stopped, destroyed, or moved.
Recovery
Cache data can be regenerated, but authoritative data belongs on storage that can be restored.