Palo Alto Networks PSE-Endpoint Exam - Topic 2 Question 96 Discussion

Actual exam question for Palo Alto Networks's PSE-Endpoint exam

Question #: 96
Topic #: 2

During installation of the ESM and the agent, SSL was enabled on an endpoint. However, the agent communication is failing. The services.log on the endpoint has the following error.

*An error occurred while making the HTTP request to https: //hostname:2125/CyveraServer/. This could be due to the fact that the server certificate is not configured property with HTTP SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server."

Which certificate can be imported on the endpoint to solve this issue? Assume the hostname is a valid FQDN and the ESM Server and Console have different certificates.

AESM Server Public Certificate

BESM Server Serf-Signed Certificate

CESM Console Self-Signed Certificate

DESM Console Public Certificate

Show Suggested Answer

Suggested Answer: B

by Xochitl at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium PSE-Endpoint Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Tatum

4 days ago

Hmm, I'm not sure. The question says the ESM Server and Console have different certificates, so maybe the Console public cert is the answer?

upvoted 0 times

...

Bambi

9 days ago

I'd go with option A. The error message clearly indicates an issue with the server certificate configuration.

upvoted 0 times

...

Salena

14 days ago

The ESM Server Public Certificate should do the trick. It's the one that's trusted by the endpoint.

upvoted 0 times

...

Isreal

19 days ago

I recall that the client and server need to match in terms of security binding. I think the ESM Server Public Certificate is the right choice, but I’m not 100% certain.

upvoted 0 times

...

Lindy

24 days ago

I’m a bit confused about the difference between the public and self-signed certificates. I feel like the ESM Console Public Certificate could be relevant, but I’m not confident.

upvoted 0 times

...

Shakira

29 days ago

This question seems familiar! I think we had a similar one where the self-signed certificate was mentioned. Could it be the ESM Server Self-Signed Certificate?

upvoted 0 times

...

Brandon

1 month ago

I remember we talked about the importance of the server certificate during our practice sessions. I think it might be the ESM Server Public Certificate, but I'm not entirely sure.

upvoted 0 times

...

Natalya

1 month ago

Hmm, this is a tricky one. The question mentions that SSL was enabled on the endpoint, so I'm thinking the issue might be related to the self-signed certificates. In that case, I would try importing the ESM Server Self-Signed Certificate (option B) to see if that fixes the problem.

upvoted 0 times

...

Jolanda

1 month ago

I'm feeling pretty confident about this one. Based on the information provided, the issue is likely due to the agent not trusting the ESM server's certificate. The best approach would be to import the ESM Server Public Certificate (option A) on the endpoint to establish the trust relationship and resolve the communication failure.

upvoted 0 times

...

Martin

2 months ago

Okay, let me think this through. The error message indicates a mismatch in the security binding between the client (the agent) and the server (the ESM). Since the ESM Server and Console have different certificates, I would try the ESM Console Public Certificate (option D) first, as that seems like the most likely solution.

upvoted 0 times

...

Elke

2 months ago

Hmm, I'm a bit confused here. The question mentions that the ESM Server and Console have different certificates, so I'm not sure if the ESM Server Public Certificate would be the right solution. Maybe the ESM Console Public Certificate (option D) would be a better fit?

upvoted 0 times

...

Rosalind

2 months ago

I think the issue is related to the SSL/TLS configuration between the agent and the ESM server. The error message suggests a problem with the server certificate, so I would try importing the ESM Server Public Certificate (option A) to see if that resolves the communication failure.

upvoted 0 times

...