Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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

Actual exam question for Palo Alto Networks's PSE-Endpoint exam
Question #: 74
Topic #: 2
[All PSE-Endpoint Questions]

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.

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Shayne
2 months ago
Ah, the age-old dilemma of SSL certificates. It's like trying to navigate a maze of acronyms and gibberish. I'm just going to close my eyes and point at one of the answers. Eeny, meeny, miny, moe...
upvoted 0 times
...
Deandrea
2 months ago
This is a tough one. But I'm going to have to go with C) ESM Console Self-Signed Certificate. It's the only option that mentions a self-signed certificate, and that could be the culprit.
upvoted 0 times
...
Franchesca
2 months ago
Wait, wait, wait. If the ESM Server and Console have different certificates, then the issue could be with either one. I'm going to go with B) ESM Server Self-Signed Certificate just to be safe.
upvoted 0 times
Dianne
2 months ago
Alright, let's import the ESM Server Self-Signed Certificate and see if that resolves the communication issue.
upvoted 0 times
...
Krissy
2 months ago
I agree, it's worth a shot. Let's go with option B) ESM Server Self-Signed Certificate.
upvoted 0 times
...
Annett
2 months ago
I think the issue might be with the ESM Server certificate. Maybe try importing the ESM Server Self-Signed Certificate.
upvoted 0 times
...
...
Luisa
2 months ago
But the error message mentions the server certificate, so I still think it's the ESM Server Public Certificate.
upvoted 0 times
...
Margot
2 months ago
I disagree, I believe the ESM Console Self-Signed Certificate is the correct one to import.
upvoted 0 times
...
Lilli
3 months ago
Hmm, I'm not so sure. The question states that the ESM Server and Console have different certificates, so it might be D) ESM Console Public Certificate.
upvoted 0 times
Odette
1 months ago
I'm leaning towards D) ESM Console Public Certificate.
upvoted 0 times
...
Dalene
2 months ago
I believe it could be B) ESM Server Self-Signed Certificate.
upvoted 0 times
...
Evangelina
2 months ago
I think it might be A) ESM Server Public Certificate.
upvoted 0 times
...
...
Luisa
3 months ago
I think the ESM Server Public Certificate should be imported.
upvoted 0 times
...
Shizue
3 months ago
The error message clearly indicates that the issue is with the server certificate, so I think the correct answer is A) ESM Server Public Certificate.
upvoted 0 times
Bronwyn
2 months ago
That sounds like a good idea, let's give it a try and see if it works.
upvoted 0 times
...
Ona
2 months ago
I'm not sure, maybe we should try both options to see which one resolves the issue.
upvoted 0 times
...
Floyd
2 months ago
Yes, that makes sense. It should resolve the mismatch of the security binding between the client and the server.
upvoted 0 times
...
Cecily
2 months ago
But wouldn't the ESM Server Self-Signed Certificate also work?
upvoted 0 times
...
Maryann
2 months ago
I think the correct answer is A) ESM Server Public Certificate.
upvoted 0 times
...
Haydee
2 months ago
I think you're right, the ESM Server Public Certificate should be imported on the endpoint.
upvoted 0 times
...
...

Save Cancel