From the Mobility tab of the Hitachi Command Suite (HCS), which two operations would you perform to optimize placement of data within a Hitachi Dynamic Tiering (HDT) environment? (Choose two.)

Question

Options

• ACreate an HDT tiering policy.
• BEdit Tier Relocation of HDT volumes.
• CExpand HDT volumes.
• DStart manual monitoring of HDT pools.

• A
  17% (10)
• B
  77% (46)
• C
  7% (4)

Explanation

Optimizing data placement in HDT requires two active operations from the Mobility tab: editing tier relocation settings (B) and starting manual monitoring (D). Tier relocation is the mechanism that physically moves data between storage tiers (e.g., SSD → SAS → SATA), and editing its settings lets you control when and how that movement occurs. Manual monitoring must be started first to collect I/O activity statistics - without this performance data, the system has no basis for deciding which data is "hot" (high-access) or "cold" (low-access) and cannot make intelligent relocation decisions.

Why A is wrong: Creating a tiering policy is a configuration prerequisite, not an active optimization operation performed from the Mobility tab - the question targets runtime operations that drive actual data movement.

Why C is wrong: Expanding an HDT volume is a capacity management task; it adds storage space but does nothing to optimize where existing data resides across tiers.

Memory tip: Think "Monitor → Move" - you start monitoring (D) to gather access-pattern data, then edit relocation (B) to act on it. Both must happen to optimize placement; one without the other accomplishes nothing.

No community discussion yet for this question.