A team needs to store a growing collection of high-resolution images, videos, and extensive event logs that must remain accessible from multiple geographic areas. They prefer a design with a flat structure that uses unique identifiers for each item, includes redundancy, and can expand horizontally as new data arrives. Which option meets these requirements best?
A transient method that discards stored data when the host restarts
A key-based design that stores discrete items in multiple locations with metadata
A file share with nested directories requiring hierarchical organization
A block-based approach integrated with a local OS for small operations
A key-based design that saves large data sets as discrete items across multiple zones with built-in metadata is appropriate for unstructured content. It supports the needed redundancy and flexible growth. Other approaches such as a block-focused method or a file-based design are more suitable when an operating system requires direct interaction with the underlying storage. A volatile system, which clears data on reboot, does not meet long-term data retention needs.
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 a key-based design in storage systems?
Open an interactive chat with Bash
Why is redundancy important in distributed storage systems?
Open an interactive chat with Bash
How does metadata enhance functionality in key-based storage?