Which statement best describes FabricPool tiering in ONTAP?

Which statement best describes FabricPool tiering in ONTAP?

• A. Cease writes to SSD
• B. Tier cold data to cloud/object storage while hot remains on SSD
• C. Replicate data to another region
• D. Backup to tape

Answer: (B)

FabricPool tiering in ONTAP is about automatically moving less frequently accessed data from fast, primary storage (SSD) to cheaper cloud or object storage, while keeping the hot data on SSD for fast access. This design lets you save on storage costs and increase usable capacity without sacrificing performance for active data. When a piece of data that has been tiered is accessed again, ONTAP can retrieve it from the cloud-backed tier back to the active storage as needed, so operations remain seamless. The other ideas don’t describe what FabricPool does: it doesn’t stop writes to the SSD, it simply relocates cold data to cheaper storage; it isn’t primarily about replicating data to another region (that’s a DR/ replication feature); and it isn’t a backup-to-tape mechanism (that’s a separate archival method).

FabricPool tiering in ONTAP is about automatically moving less frequently accessed data from fast, primary storage (SSD) to cheaper cloud or object storage, while keeping the hot data on SSD for fast access. This design lets you save on storage costs and increase usable capacity without sacrificing performance for active data. When a piece of data that has been tiered is accessed again, ONTAP can retrieve it from the cloud-backed tier back to the active storage as needed, so operations remain seamless.

The other ideas don’t describe what FabricPool does: it doesn’t stop writes to the SSD, it simply relocates cold data to cheaper storage; it isn’t primarily about replicating data to another region (that’s a DR/ replication feature); and it isn’t a backup-to-tape mechanism (that’s a separate archival method).