County operations staff created some civic segments in Policy mode and others in Manager mode, and membership and rules no longer line up. What GUI practice should they adopt going forward?
Select an answer to reveal the explanation.
Short Explanation
Two different city ledgers that never post to each other will not balance. Policy objects and Manager objects are separate books, so pick one mode and stay there. Mixing them, bouncing to Horizon, or fleeing to a physical switch does not fix the split.
Full Explanation
NSX-T Policy-mode objects and Manager-mode objects are not interchangeable. Operators should create all objects in one mode so groups, segments, and rules remain consistent for county operations—two different city ledgers that never post to each other will not balance. Mixing Policy-created and Manager-created objects freely is a documented anti-practice even if someone hopes NSX merges them at the vNIC. Creating Policy objects in NSX Manager and Manager objects in Horizon does not keep products in sync. Recreating every object only on a physical top-of-rack switch abandons the NSX GUI task. Exam caveat: consistency of mode matters more than clever cross-mode references; pick Policy for greenfield and stay there unless Advanced leftovers force Manager-mode work. Operational check: inventory whether civic objects are Policy or Manager, stop creating new objects in the other mode, migrate or rebuild toward one mode where required, and re-validate group membership and rules. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish.