Refer to the exhibit.
An administrator needs to enable inline deduplication for a pre-existing storage container. When trying to enable deduplication on the storage container, this feature is grayed-out.
What is the reason for this behavior?
Refer to the exhibit.
An administrator needs to enable inline deduplication for a pre-existing storage container. When trying to enable deduplication on the storage container, this feature is grayed-out.
What is the reason for this behavior?
The correct answer is that the replication factor of 1 is configured on the storage container. Inline deduplication and Erasure Coding are not supported for storage containers with a replication factor of 1. This is why the deduplication feature is grayed-out in the exhibit.
Correct answer is B: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000LUKeCAO#:~:text=Dedup%20and%20EC%20are%20not%20supported%20for%20RF1,RF1%20container%20does%20not%20support%20increasing%20replication%20factor.
Dedup and EC are not supported for RF1 containers.
B is correct
C. The cluster has hybrid storage, and deduplication is supported only on all-flash clusters. Deduplication is typically associated with all-flash storage configurations. Hybrid storage clusters might not support inline deduplication. Therefore, if your cluster is using hybrid storage, the deduplication feature may be unavailable or grayed out.
Why do this? The other link clearly points out that RF1 doesn't allow deduplication or erasure coding. Dedup works great with hybrid storage if you have a large enough cache tier. And if you don't, it doesn't grey out the option...it just performs like crap.
B https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v6_8:wc-replication-factor1-recommend-r.html Deduplication Not supported for RF1-enabled storage containers.
B is correct. Exibhit clearly mentioned it is RF1 , and Dedublication not supported on RF1.