Question 260
During a scheduled deployment at a utility operations center in Phoenix, a RADIUS-backed management login fails even though the username exists in the directory. 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 authentication profiles requirement rather than merely recording an intended configuration: Test authentication succeeds using the expected service and the remote server records the correct request. The associated implementation is: check the firewall's RADIUS server profile, shared secret, reachability and authentication-profile reference.
Incorrect Answers
That observation measures administrative roles after this other intervention: Remove the temporary administrator entitlement and verify role bindings are updated. Its result is: A new sign-in cannot reach the removed administrative functions while permanent staff retain access. The requested authentication profiles change is Check the firewall's RADIUS server profile, shared secret, reachability and authentication-profile reference, which must demonstrate: Test authentication succeeds using the expected service and the remote server records the correct request. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Configure a supported external authentication profile and connect it to the administrator login policy. It measures: An authorized directory account signs in and an unrecognized directory account is rejected. The current authentication profiles configuration is Check the firewall's RADIUS server profile, shared secret, reachability and authentication-profile reference, and must demonstrate: Test authentication succeeds using the expected service and the remote server records the correct request. The two acceptance checks are not interchangeable even though they share a feature area.
The offered observation would confirm the separate intervention: Assign authentication profiles to the intended user populations without broadening local admin privileges. It measures: An external user uses the IdP and the carefully scoped break-glass identity is validated separately. The current authentication profiles configuration is Check the firewall's RADIUS server profile, shared secret, reachability and authentication-profile reference, and must demonstrate: Test authentication succeeds using the expected service and the remote server records the correct request. The two acceptance checks are not interchangeable even though they share a feature area.