Which two actions protect an Infinite volume from the loss of a namespace constituent? (Choose two)

Question

Options

• AMinor the namespace constituent by using an intracluster data protection mirror
• BMirror the namespace constituent by using an Intercluster data protection mirror
• CMirror the namespace constituent by using a load-sharing mirror
• DMirror the namespace constituent by using a FlexCache mirror

• A
  81% (34)
• C
  7% (3)
• D
  12% (5)

Explanation

An Infinite Volume's namespace constituent is a critical metadata component that maps file paths to their corresponding data constituents. Loss of the namespace constituent would make the entire Infinite Volume inaccessible. To protect it, NetApp supports two mirroring strategies: (A) Intracluster DP mirror - replicates the namespace constituent to another node within the same cluster, protecting against node or disk failure locally; (B) Intercluster DP mirror - replicates the namespace constituent to a node in a remote cluster, protecting against site-level failures. Load-sharing mirrors (C) are used for read-only distribution of data (e.g., SVM root volumes) and do not provide the data protection needed here. FlexCache mirrors (D) are a caching mechanism for improving read performance and are not applicable for namespace constituent protection.

No community discussion yet for this question.