Question 190
At a regional logistics hub in Austin, a VPN gateway trusts every submitted password despite directory-based group restrictions. The change affects shipment planning. What outcome directly proves this configuration works?
Explanation
Correct Answer
At a regional logistics hub in Austin, this verifies the specific globalprotect authentication requirement rather than merely recording an intended configuration: An allowed directory user authenticates and a user outside the group is denied. The associated implementation is: enforce the intended authentication profile and user/group allowlist on the GlobalProtect gateway.
Incorrect Answers
The offered observation would confirm the separate intervention: Configure a supported GlobalProtect SAML authentication profile and identity-provider flow. It measures: An authorized contractor completes the IdP challenge and a denied account cannot establish a gateway session. The current globalprotect authentication configuration is Enforce the intended authentication profile and user/group allowlist on the GlobalProtect gateway, and must demonstrate: An allowed directory user authenticates and a user outside the group is denied. The two acceptance checks are not interchangeable even though they share a feature area.
That observation measures globalprotect portals after this other intervention: Configure the GlobalProtect portal agent configuration selection by appropriate user or group criteria. Its result is: Each test user receives the correct portal-delivered gateway and client settings after sign-in. The requested globalprotect authentication change is Enforce the intended authentication profile and user/group allowlist on the GlobalProtect gateway, which must demonstrate: An allowed directory user authenticates and a user outside the group is denied. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Install the correct server certificate chain and supported client trust profile. It measures: The client validates the full chain and connects without bypassing certificate verification. The current globalprotect authentication configuration is Enforce the intended authentication profile and user/group allowlist on the GlobalProtect gateway, and must demonstrate: An allowed directory user authenticates and a user outside the group is denied. The two acceptance checks are not interchangeable even though they share a feature area.