When does a Protection Pokey have to be removed from PowerStore storage resource? (Choose two.)

Question

Options

• ABefore expanding volume capacity
• BBefore moving the volume to a protected volume group
• CBefore refreshing a Storage Resources from a Clone
• DBefore deleting a volume

• A
  5% (3)
• B
  88% (57)
• C
  8% (5)

Explanation

A Protection Policy (likely what "Pokey" refers to - possibly an OCR or transcription artifact) in Dell PowerStore cannot coexist with certain operations because a storage resource can only belong to one protection context at a time. Option B is correct because a volume with an existing protection policy cannot be moved into a protected volume group - the policy must be removed first to avoid a conflict between the individual policy and the group-level policy. Option D is correct because PowerStore will block deletion of a volume that still has a protection policy attached; you must remove it first to cleanly delete the resource.

A is wrong because expanding a volume's capacity does not interfere with its protection policy - the policy remains intact through a capacity change. C is wrong because refreshing a storage resource from a clone is an operation that works with the existing policy in place and does not require its removal.

Memory tip: Think of the two "removal-required" scenarios as relationship changes - you must clean up the old policy before joining a group (B) or before ending the resource's life entirely (D). Expansion and refresh are just modifications, not relationship changes.

No community discussion yet for this question.