Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE7_LED-7.0 Topic 1 Question 33 Discussion

Actual exam question for Fortinet's NSE7_LED-7.0 exam
Question #: 33
Topic #: 1
[All NSE7_LED-7.0 Questions]

Refer to the exhibit.

Wireless guest users are unable to authenticate because they are getting a certificate error while loading the captive portal login page. This URL string is the HTTPS POST URL guest wireless users see when attempting to access the network using the web browser

Which two settings are the likely causes of the issue? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, B

According to the exhibit, the wireless guest users are getting a certificate error while loading the captive portal login page. This means that the browser cannot verify the identity of the server that is hosting the login page. Therefore, option A is true because the external server FQDN is incorrect, which means that it does not match the common name or subject alternative name of the server certificate. Option B is also true because the wireless user's browser is missing a CA certificate, which means that it does not have the root or intermediate certificate that issued the server certificate. Option C is false because the FortiGate authentication interface address is using HTTPS, which is a secure protocol that encrypts the communication between the browser and the server. Option D is false because the user address is not in DDNS form, which is not related to the certificate error.


Contribute your Thoughts:

Rima
1 months ago
Haha, I bet the network admin is pulling their hair out trying to figure this one out. At least it's not me this time!
upvoted 0 times
Slyvia
15 days ago
User 2: It could be because of the incorrect external server FQDN or missing CA certificate in the browser.
upvoted 0 times
...
Millie
19 days ago
User 1: I heard the guest users are having trouble with the captive portal login page.
upvoted 0 times
...
...
Alana
1 months ago
Hmm, I don't know about that. I'm just happy I'm not the one who has to fix this. Must be a real pain in the neck!
upvoted 0 times
...
Lashanda
1 months ago
I think C) The FortiGate authentication interface address is using HTTPS is also a likely cause. The captive portal needs to be on HTTPS.
upvoted 0 times
Carole
1 days ago
D) The user address is not in DDNS form
upvoted 0 times
...
Stevie
5 days ago
C) The FortiGate authentication interface address is using HTTPS
upvoted 0 times
...
Kasandra
6 days ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Kati
1 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Rosita
2 months ago
I believe another possible cause could be the wireless user's browser missing a CA certificate.
upvoted 0 times
...
Eve
2 months ago
I agree with Jannette. The incorrect external server FQDN could be causing the certificate error.
upvoted 0 times
...
Elly
2 months ago
Definitely B) The wireless user's browser is missing a CA certificate. That's why they're getting a certificate error.
upvoted 0 times
Franchesca
23 days ago
User4: It could also be that the user address is not in DDNS form.
upvoted 0 times
...
Art
24 days ago
User3: Maybe the FortiGate authentication interface address is using HTTPS.
upvoted 0 times
...
Tammara
25 days ago
User3: Maybe the FortiGate authentication interface address is using HTTPS as well.
upvoted 0 times
...
Anna
1 months ago
User2: I think the issue might be that the wireless user's browser is missing a CA certificate.
upvoted 0 times
...
Erick
1 months ago
User2: I think the issue might be that the wireless user's browser is missing a CA certificate.
upvoted 0 times
...
Alishia
1 months ago
User1: Have you checked if the external server FQDN is correct?
upvoted 0 times
...
Dalene
2 months ago
User1: Have you checked if the external server FQDN is correct?
upvoted 0 times
...
...
Jannette
2 months ago
I think the issue might be with the external server FQDN.
upvoted 0 times
...

Save Cancel