What are two benefits of using Unity Asynchronous Local Replication to replicate storage resources between pools on a system? (Select 2)

Question

Options

• ABalance capacity
• BChange disk type
• CChange storage groups
• DChange NAS server names
• EEnable data reduction

• A
  86% (44)
• C
  8% (4)
• D
  4% (2)
• E
  2% (1)

Explanation

Unity Asynchronous Local Replication allows you to replicate storage resources between pools on the same system, making it a practical tool for two key goals: balancing capacity (A) across pools that may have uneven utilization, and changing disk type (B) by replicating data to a pool backed by different media (e.g., migrating from spinning SAS drives to all-flash). These are the primary use cases because local replication lets you move workloads without changing external connectivity or system configuration.

The distractors fail because they describe actions that are either unrelated to replication or require different tools: C (Change storage groups) is a VMAX/PowerMax concept not applicable to Unity pool architecture; D (Change NAS server names) is a simple configuration rename done in the management UI, not tied to replication; and E (Enable data reduction) is a pool-level or volume-level setting toggled independently - replication doesn't control whether data reduction is on or off.

Memory tip: Think of local replication as a "move truck between pools" - it's useful for where your data lives (which pool, which disk tier) and how full each pool is, not for renaming things or flipping feature switches.

No community discussion yet for this question.