Question 440
During a scheduled deployment at a food supply company in Sacramento, a directory migration changes group distinguished names and old mappings no longer resolve correctly. The team is verifying its effect on warehouse automation. Which acceptance outcome addresses the precise requirement?
Explanation
Correct Answer
At a food supply company in Sacramento, this verifies the specific group mapping and directory sync requirement rather than merely recording an intended configuration: Current directory memberships appear in group-mapping output and traffic matches the new groups. The associated implementation is: refresh directory mapping scope and adjust group identifiers in the policy.
Incorrect Answers
The offered observation would confirm the separate intervention: Limit group-mapping filters to required groups and authorized directory sources. It measures: Only the selected groups appear in the mapping set and policy scope matches the approved inventory. The current group mapping and directory sync configuration is Refresh directory mapping scope and adjust group identifiers in the policy, and must demonstrate: Current directory memberships appear in group-mapping output and traffic matches the new groups. The two acceptance checks are not interchangeable even though they share a feature area.
That observation measures user-id redistribution after this other intervention: Configure supported User-ID redistribution from an authoritative source to both peers. Its result is: Identical test identities resolve consistently on both firewalls for the same source IP. The requested group mapping and directory sync change is Refresh directory mapping scope and adjust group identifiers in the policy, which must demonstrate: Current directory memberships appear in group-mapping output and traffic matches the new groups. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Configure supported directory group mapping or Cloud Identity Engine integration and refresh membership. It measures: A new approved Finance member matches the group-based rule while an unrelated user does not. The current group mapping and directory sync configuration is Refresh directory mapping scope and adjust group identifiers in the policy, and must demonstrate: Current directory memberships appear in group-mapping output and traffic matches the new groups. The two acceptance checks are not interchangeable even though they share a feature area.