Deploy Linux instances repeatedly with the same base OS, packages, and initial configuration.
Prepare a read-only template from which instances can boot.
What is the most appropriate role for this template?
A system image preserves a reusable OS and filesystem baseline from which consistent VMs, cloud instances, or containers can be created.
Detailed explanation
Incorrect. CPU time is runtime accounting, not an image.
Incorrect. CPU time is runtime accounting, not an image.
Incorrect. Reusing SSH host keys across instances creates an identity and security problem.
Incorrect. Reusing SSH host keys across instances creates an identity and security problem.
Correct. A reusable root filesystem and OS image is the source for new instances.
Correct. A reusable root filesystem and OS image is the source for new instances.
Incorrect. Directly exposing a physical host network is unrelated to the image's role.
Incorrect. Directly exposing a physical host network is unrelated to the image's role.
Try it yourself
An example you can run in a temporary verification environment.
findmnt -no SOURCE,FSTYPE /Expected result
現在のルートファイルシステムの元デバイスと形式。元イメージ自体の識別は基盤側で行うKey points
- It is a deployment template
- Clone-specific settings are applied later
- It is not a live runtime state
Notes
- Environment: 一般的なVM・クラウドイメージモデル
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.