Parks clones a production DFW policy onto the disaster-recovery clu…

Question

Parks clones a production DFW policy onto the disaster-recovery cluster but keeps the same production group names, and the cloned rules still match production members. What should the administrator change?

Accepted Answer

Give the DR copies environment-specific group names and membership so the cloned policy does not still hit production VMs — Copying the recipe is fine. Serving it on the same platter as production is not. Rename and re-scope the DR groups so the clone only tastes DR VMs.

Answer

Disable Identity Firewall at DR so cloned policies cannot fire

Answer

Replace NSX groups with Carbon Black sensor groups that ignore environment

Answer

Collapse prod and DR into one shared group so clone scope cannot drift

Parks clones a production DFW policy onto the disaster-recovery cluster but keeps the same production group names, and the cloned rules still match production members. What should the administrator change?

Short Explanation

Full Explanation