Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CyberArk Exam SECRET-SEN Topic 1 Question 12 Discussion

Actual exam question for CyberArk's SECRET-SEN exam
Question #: 12
Topic #: 1
[All SECRET-SEN Questions]

You start up a Follower and try to connect to it with a REST call using the server certificate, but you get an SSL connection refused error.

What could be the problem and how should you fix it?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Keshia
1 months ago
Wait, there's a PostgreSQL port involved? I thought this was a Follower issue. Now I'm even more confused.
upvoted 0 times
Lang
7 days ago
C) Port 443 is blocked; open that port.
upvoted 0 times
...
Josphine
13 days ago
B) One of the PostgreSQL ports (5432. 1999) is blocked by the firewall Open those ports.
upvoted 0 times
...
Tabetha
1 months ago
A) The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower.
upvoted 0 times
...
...
Adelle
2 months ago
I bet the person who came up with option D is the same one who thought putting a 'Please Hack Me' sign on their server was a good idea.
upvoted 0 times
Kristel
23 days ago
C) Port 443 is blocked; open that port.
upvoted 0 times
...
Patria
1 months ago
B) One of the PostgreSQL ports (5432. 1999) is blocked by the firewall Open those ports.
upvoted 0 times
...
Stevie
1 months ago
A) The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower.
upvoted 0 times
...
...
Latrice
2 months ago
D? Really? Using the command option to suppress SSL certificate checking seems like a bad idea. That's just asking for security issues.
upvoted 0 times
Ronny
8 days ago
A) The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower.
upvoted 0 times
...
Edna
18 days ago
C) Port 443 is blocked; open that port.
upvoted 0 times
...
Carole
24 days ago
B) One of the PostgreSQL ports (5432. 1999) is blocked by the firewall Open those ports.
upvoted 0 times
...
Cletus
27 days ago
A) The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower.
upvoted 0 times
...
Alaine
29 days ago
B) One of the PostgreSQL ports (5432. 1999) is blocked by the firewall Open those ports.
upvoted 0 times
...
Sharen
1 months ago
A) The certificate does not contain the Follower hostname as a Subject Alternative Name (SAN). Generate a new certificate for the Follower.
upvoted 0 times
...
...
Yoko
2 months ago
Interesting, I was leaning towards B, but now I'm not so sure. Maybe the firewall is blocking the wrong ports.
upvoted 0 times
...
Rutha
2 months ago
I think we should also check if Port 443 is blocked and open that port as a potential solution.
upvoted 0 times
...
Omega
2 months ago
Hmm, I think the answer is A. The certificate needs to have the Follower hostname as a SAN. Generating a new certificate should fix this.
upvoted 0 times
Alishia
15 days ago
Thanks for the help, I'll generate a new certificate with the correct SAN.
upvoted 0 times
...
Raymon
19 days ago
Yes, that's correct. Make sure the Follower hostname is included in the certificate.
upvoted 0 times
...
Felix
21 days ago
Generating a new certificate should fix this.
upvoted 0 times
...
Galen
2 months ago
I think the answer is A. The certificate needs to have the Follower hostname as a SAN.
upvoted 0 times
...
...
Jutta
2 months ago
I agree with Leah. Generating a new certificate for the Follower could fix the issue.
upvoted 0 times
...
Leah
3 months ago
I think the problem might be with the certificate not containing the Follower hostname as a SAN.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77