A project team needs to store a large collection of unstructured data that is read from multiple remote offices. The files do not change once they are uploaded, but they must remain available on demand. Which setup meets these requirements?
Use ephemeral volumes that are tied to each running instance
Store data on local block devices for all content
Set up a shared file mount that spans all compute nodes
Adopt an object-based system for remote access to file data
An object-based solution is useful for large unstructured data that is read frequently but not modified. Ephemeral storage does not stay persistent once the instance is removed, making it unsuitable for long-term storage. Local block volumes are often used for applications that modify data regularly. A shared file system can handle collaboration but might not be as scalable or cost-effective for large unstructured data that is not updated.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is object-based storage, and why is it suited for unstructured data?
Open an interactive chat with Bash
Why is ephemeral storage not suitable for long-term data needs?
Open an interactive chat with Bash
How does a shared file system differ from object storage, and why is it less effective here?