Question 390
At an insurance provider in Denver, an administrator permits any certificate signed by a broad public CA for privileged firewall login. The change affects claims services. What outcome directly proves this configuration works?
Explanation
Correct Answer
At an insurance provider in Denver, this verifies the specific certificate-based authentication requirement rather than merely recording an intended configuration: A corporate admin certificate is accepted and a different public certificate is refused. The associated implementation is: restrict the trusted CA/profile and subject mapping to approved administrator identities.
Incorrect Answers
The offered observation would confirm the separate intervention: Correct certificate-profile username field mapping and the policy consuming that identity. It measures: The expected authenticated username appears in the session and restricted group rules behave correctly. The current certificate-based authentication configuration is Restrict the trusted CA/profile and subject mapping to approved administrator identities, and must demonstrate: A corporate admin certificate is accepted and a different public certificate is refused. The two acceptance checks are not interchangeable even though they share a feature area.
The offered observation would confirm the separate intervention: Configure the supported certificate authentication profile and trust/identity mapping. It measures: An approved certificate signs in and an untrusted or revoked certificate fails the same flow. The current certificate-based authentication configuration is Restrict the trusted CA/profile and subject mapping to approved administrator identities, and must demonstrate: A corporate admin certificate is accepted and a different public certificate is refused. The two acceptance checks are not interchangeable even though they share a feature area.
That observation measures ssl/tls service profiles after this other intervention: Apply a suitable SSL/TLS service profile with an approved hostname-matching certificate. Its result is: Browser or VPN TLS negotiation validates the correct endpoint without name warnings. The requested certificate-based authentication change is Restrict the trusted CA/profile and subject mapping to approved administrator identities, which must demonstrate: A corporate admin certificate is accepted and a different public certificate is refused. The offered evidence does not validate the specified control.