An administrator is attempting to remove a remote replication session for a test volume. The administrator selects the test volume from the Storage tab. From the More Actions dropdown list the…

Question

Options

• AProtection policy replication rule RPO value was not set to zero
• BOperation was performed from the replication destination
• CReplication session was not paused before the protection policy was unassigned
• DReplication rule was not deleted from the protection policy

• A
  5% (2)
• B
  68% (26)
• C
  8% (3)
• D
  18% (7)

Explanation

Option B is correct because in a replication setup, the destination volume is read-only and managed by the replication system - administrative changes like unassigning a protection policy can only be performed from the source side. Attempting to modify volume settings on the destination triggers a "Modify Volume" error because the system protects destination volumes from direct changes.

Why the distractors are wrong:

• A is incorrect - the RPO value has no bearing on whether you can unassign a protection policy; it controls recovery point frequency, not administrative permissions.
• C is incorrect - pausing the replication session is not a prerequisite for unassigning a protection policy; you can unassign without pausing.
• D is incorrect - you don't need to delete the replication rule from the protection policy before unassigning; the unassign operation handles the policy relationship directly.

Memory tip: Think "Source = Control" - in any replication relationship, the source side holds administrative authority. If you get a modify error, your first instinct should be to verify you're working from the source, not the destination.

No community discussion yet for this question.