Compression is supported on a Nutanix two-node cluster. Compression reduces physical capacity consumption by encoding eligible data more efficiently before it is retained in the distributed storage fabric. It remains available because its operation does not require the additional node count or data-placement structure demanded by certain other storage-efficiency features.
Nutanix explicitly identifies deduplication as unsupported for the two-node configuration while stating that compression is supported. Cluster expansion is also not a supported scale-out path for a cluster originally created as a two-node cluster. If a larger cluster is required, the environment must be designed and deployed as the appropriate multi-node configuration rather than treating the two-node deployment as an incrementally expandable starting point.
Two-node clusters also have specialized architecture. They use RF2 across the nodes and require a Witness VM in a separate failure domain to resolve leadership when communication between the two nodes is lost.
The Witness does not contain workload data; it provides quorum-related arbitration during applicable failures.
Network configuration is similarly subject to two-node guidelines and limitations, making Network Segmentation an incorrect selection in this answer set.
The question tests recognition that a two-node cluster retains selected AOS capabilities but is not functionally identical to a conventional three-node-or-larger cluster.
NHCF/NCA reference: Two-node cluster capabilities, limitations, Witness operation, and storage efficiency.
Official references: Two-Node Clusters and Two-Node Cluster Guidelines .