On elections night a Distributed Firewall rule has inverted source and destination members, so poll-book VMs are blocked incorrectly. What is the correct administrative fix?
Select an answer to reveal the explanation.
Short Explanation
Swapped source and destination is a one-way street sign hung backwards—turn the sign, do not shut down every road in the city. Fix the members on that rule. Disabling all Distributed Firewall on elections night is the outage, not the fix.
Full Explanation
On elections night, a Distributed Firewall rule with inverted source and destination that blocks poll-book VMs incorrectly should be fixed by correcting the source and destination members on that malformed rule. Surgical repair restores access without abandoning citywide micro-segmentation during a sensitive event.
Disabling Distributed Firewall citywide until after certification of results removes all east-west controls for the outage of one bad rule. Deleting all Emergency-category rules so Application rules can fire is unrelated vandalism of category design. Moving poll-book VMs into Carbon Black isolation ignores the NSX misconfiguration and may worsen availability.
Exam caveat: fix the bad rule members; do not disable the entire DFW for a single inverted pair.
Operational check: correct source/destination on the rule, verify poll-book traffic resumes, confirm hit counters on the fixed rule, and keep a change record for the elections security checklist.
Surgical rule repair on elections night preserves the rest of the city’s east-west shield. Pair the fix with a peer review checklist for source/destination orientation, and keep a pre-approved Emergency allow for poll-book break-glass that still logs heavily instead of disabling DFW wholesale.