What actions are taken when reconfiguring Storage Data Servers during cluster expansion? (Choose two)

Question

Options

• AValidate new node compatibility with existing SDS configurations
• BReallocate storage pools for load balancing
• CConfigure Fault Sets for the new nodes
• DEnable data deduplication on new SDS nodes

• A
  77% (49)
• C
  9% (6)
• D
  14% (9)

Explanation

When expanding a cluster, validating new node compatibility (A) is essential to ensure the incoming SDS nodes meet hardware, software, and firmware requirements aligned with the existing configuration - skipping this risks instability or unsupported states. Reallocating storage pools (B) is equally critical because adding new nodes without rebalancing leaves capacity underutilized and load unevenly distributed across the cluster.

Option C (Fault Sets) is a fault domain grouping feature used to protect against correlated failures - it's an optional architectural decision, not a required reconfiguration step during expansion. Option D (deduplication) is a storage-pool-level policy set globally, not a per-node action taken during expansion.

Memory tip: Think "Check then Balance" - you always check compatibility before onboarding a new node, then balance the pools so the new capacity is actually used. Fault Sets and dedup are configuration choices made during design, not expansion housekeeping.

No community discussion yet for this question.