What are the considerations for configuring new Metadata Managers during cluster expansion? (Choose two)

Question

Options

• AEnsure even distribution of metadata across nodes
• BValidate replication protocols between clusters
• CAssign the new nodes to an existing Fault Set
• DMaintain redundancy for metadata storage

• A
  58% (39)
• B
  12% (8)
• C
  30% (20)

Explanation

When expanding a cluster with new Metadata Managers, even distribution (A) prevents metadata hotspots and load imbalances that would degrade performance - new nodes should absorb a proportional share of metadata responsibility rather than leaving existing nodes overloaded. Redundancy (D) is equally critical because metadata is the backbone of data access; losing it makes stored data unreachable, so maintaining redundant metadata copies across nodes is non-negotiable during expansion.

Why the distractors are wrong:

• B addresses inter-cluster replication protocols, which is a separate concern unrelated to configuring Metadata Managers within a single cluster expansion.
• C is a distractor because assigning new nodes to an existing Fault Set actually undermines fault tolerance - new Metadata Managers should ideally be placed in separate fault domains to maximize redundancy, not consolidated into an existing one.

Memory tip: Think "Always Distribute" - the two core rules of any metadata layer are spread the load (A) and survive failures (D). If an answer choice shifts focus to cross-cluster protocols or fault set consolidation, it's solving a different problem entirely.

No community discussion yet for this question.