Question 460
During a scheduled deployment at a utility operations center in Phoenix, two perimeter firewalls need consistent user-to-IP identity information but each reads a different subset of directory events. The team is verifying its effect on control-system reporting. Which acceptance outcome addresses the precise requirement?
Explanation
Correct Answer
At a utility operations center in Phoenix, this verifies the specific user-id redistribution requirement rather than merely recording an intended configuration: Identical test identities resolve consistently on both firewalls for the same source IP. The associated implementation is: configure supported User-ID redistribution from an authoritative source to both peers.
Incorrect Answers
That observation measures group mapping and directory sync after this other intervention: Refresh directory mapping scope and adjust group identifiers in the policy. Its result is: Current directory memberships appear in group-mapping output and traffic matches the new groups. The requested user-id redistribution change is Configure supported User-ID redistribution from an authoritative source to both peers, which must demonstrate: Identical test identities resolve consistently on both firewalls for the same source IP. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Restrict User-ID redistribution peer access and authenticated service configuration. It measures: Authorized firewalls receive the mappings and an unapproved listener is denied. The current user-id redistribution configuration is Configure supported User-ID redistribution from an authoritative source to both peers, and must demonstrate: Identical test identities resolve consistently on both firewalls for the same source IP. The two acceptance checks are not interchangeable even though they share a feature area.
The offered observation would confirm the separate intervention: Verify redistribution connectivity, refresh timing and event ordering between collectors and firewalls. It measures: Updated IP-to-user entries appear within the accepted delay window and stale entries are removed. The current user-id redistribution configuration is Configure supported User-ID redistribution from an authoritative source to both peers, and must demonstrate: Identical test identities resolve consistently on both firewalls for the same source IP. The two acceptance checks are not interchangeable even though they share a feature area.