A data architect is planning a new deployment of data storage virtualization before a cloud...

1. Understanding the Requirement:

The storage must support deduplication and backup policy management.

The solution must be virtualized and separate from data VMs, ensuring flexibility and centralized management.

2. Analyzing the Options:

A. Software-defined storage:

Correct. SDS abstracts storage resources from hardware, allowing for centralized deduplication, backup policies, and dynamic scalability. Ideal for pre-cloud deployment. ✅

B. Containerized storage:

Incorrect. Containerized storage focuses on ephemeral data storage for containerized applications, not ideal for deduplication or backups. ❌

C. Thick-provisioning storage:

Incorrect. Thick provisioning allocates fixed storage size but lacks deduplication and backup management features. ❌

D. RAID 10 disk-array storage:

Incorrect. RAID 10 provides fault tolerance and performance but is hardware-centric and does not address deduplication or centralized backup management. ❌

3. Why SDS is Ideal:

SDS enables policy-driven management for backups, snapshots, and data deduplication.

Supports seamless integration with cloud environments, facilitating migration.

4. References:

CompTIA Cloud+ Objectives:

Section 3.2 - Provision storage in cloud environments, "Software-defined storage for deduplication and backups."

CompTIA Cloud+ Study Guide: Discusses SDS for flexible and efficient storage management​​.

​