220-1201 Practice Question: A technician is configuring a cloud-based backup…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Block storage

  Why it's wrong here

  Block storage presents raw, unformatted volumes directly to an operating system, much like a local hard drive. While it offers high performance for applications that manage their own file systems, such as databases or virtual machines, it inherently lacks native capabilities for file-level versioning or rich metadata management. Therefore, it's not optimized for a cloud backup solution requiring granular recovery of previous file versions without additional software layers.

• ✗

  File storage

  Why it's wrong here

  File storage organizes data into a traditional hierarchical structure of files and folders, making it intuitive for human users and shared network access. However, its native capabilities for robust, object-level versioning across multiple iterations of a file are typically limited or non-existent without relying on external applications or snapshots. This makes it less ideal for a cloud backup solution specifically requiring granular recovery of individual file versions over an extended period.

• ✓

  Object storage

  Why this is correct

  Object storage manages data as discrete, self-contained units called objects, each comprising the data itself, a unique identifier, and extensive custom metadata. This architecture inherently supports robust versioning, where every modification or upload of an object automatically creates a new, retrievable version. Its scalability, cost-effectiveness, and built-in features like granular version control and lifecycle management make it the optimal choice for cloud-based backup solutions requiring the ability to recover previous file versions efficiently.

• ✗

  Cold storage

  Why it's wrong here

  Cold storage is a specialized, highly cost-effective tier designed for long-term data archival with extremely infrequent access patterns. Its primary characteristic is high latency, meaning data retrieval can take hours or even days, often incurring additional retrieval fees. This makes it entirely unsuitable for a cloud backup solution that requires quick recovery of individual files within a 30-day window, as its design prioritizes cost savings for dormant data over rapid accessibility.