Question 400
During a scheduled deployment at a food supply company in Sacramento, a captive-portal or GlobalProtect service uses a certificate that does not match its configured hostname. 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 ssl/tls service profiles requirement rather than merely recording an intended configuration: Browser or VPN TLS negotiation validates the correct endpoint without name warnings. The associated implementation is: apply a suitable SSL/TLS service profile with an approved hostname-matching certificate.
Incorrect Answers
That observation measures certificate-based authentication after this other intervention: Correct certificate-profile username field mapping and the policy consuming that identity. Its result is: The expected authenticated username appears in the session and restricted group rules behave correctly. The requested ssl/tls service profiles change is Apply a suitable SSL/TLS service profile with an approved hostname-matching certificate, which must demonstrate: Browser or VPN TLS negotiation validates the correct endpoint without name warnings. The offered evidence does not validate the specified control.
The offered observation would confirm the separate intervention: Bind the desired certificate in the service profile used by that endpoint. It measures: A new connection to the actual service presents the intended certificate rather than the superseded one. The current ssl/tls service profiles configuration is Apply a suitable SSL/TLS service profile with an approved hostname-matching certificate, and must demonstrate: Browser or VPN TLS negotiation validates the correct endpoint without name warnings. The two acceptance checks are not interchangeable even though they share a feature area.
The offered observation would confirm the separate intervention: Use the supported SSL/TLS service profile to restrict acceptable protocol versions. It measures: Scanner and successful modern client handshakes demonstrate legacy versions are rejected. The current ssl/tls service profiles configuration is Apply a suitable SSL/TLS service profile with an approved hostname-matching certificate, and must demonstrate: Browser or VPN TLS negotiation validates the correct endpoint without name warnings. The two acceptance checks are not interchangeable even though they share a feature area.