What is the result of enabling data reduction on a LUN in a consistency group containing three LUNs?

Question

Options

• AAll writes to all consistency group LUNs will go through the data reduction logic.
• BData reduction will be enabled on all LUNs is the consistency group.
• CData reduction and advanced replication will be enabled on all LUNs
• DAny writes to the LUN will go through the data reduction logic.

• A
  10% (2)
• B
  14% (3)
• D
  76% (16)

Explanation

Enabling data reduction on a single LUN within a consistency group is a per-LUN operation - it only causes writes to that specific LUN to pass through the data reduction logic (deduplication/compression), which is exactly what D states.

Why the distractors are wrong:

• A is wrong because it claims all LUNs in the group are affected. Consistency groups synchronize I/O ordering and crash consistency, but they don't propagate individual LUN settings like data reduction.
• B is wrong for the same reason as A - data reduction does not auto-enable across the entire consistency group when set on one member.
• C introduces "advanced replication," which is completely unrelated to enabling data reduction; this is a classic distractor that bundles an unrelated feature to make it sound more comprehensive.

Memory tip: Think of a consistency group as a folder - putting a lock on one file in the folder doesn't lock all files. Data reduction is a per-LUN attribute; the consistency group only governs write ordering, not feature propagation.

No community discussion yet for this question.