BlackFriday 2024! 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 24 Discussion

Actual exam question for Fortinet's NSE7_LED-7.0 exam
Question #: 24
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:

Stevie
4 months ago
Yes, if the FortiGate authentication interface address is using HTTPS, it might be causing the certificate error for the wireless guest users.
upvoted 0 times
...
Scot
4 months ago
Ha, the user's browser is probably stuck in the Stone Age! They need to get with the times and update their software. But seriously, the missing CA certificate is the obvious issue here. That, and maybe they need to turn it off and on again.
upvoted 0 times
Onita
2 months ago
Maybe a simple restart could also help with the problem.
upvoted 0 times
...
Chana
2 months ago
Yeah, they need to update their browser for sure.
upvoted 0 times
...
Luisa
3 months ago
The missing CA certificate is definitely causing the issue.
upvoted 0 times
...
Margurite
3 months ago
Turning it off and on again could also help, good point.
upvoted 0 times
...
Elza
3 months ago
They should update their browser too, it might be outdated.
upvoted 0 times
...
Jin
3 months ago
Yeah, the missing CA certificate is definitely causing the issue.
upvoted 0 times
...
...
Lasandra
4 months ago
Hmm, the FQDN looks correct, and the HTTPS setting is probably not the problem. I'd say the missing CA certificate in the user's browser is the main culprit here. Someone should tell them to update their browser.
upvoted 0 times
Noah
3 months ago
Yeah, the browser needs to be updated for sure.
upvoted 0 times
...
Belen
3 months ago
I think the missing CA certificate is causing the issue.
upvoted 0 times
...
...
Elke
4 months ago
I think the wireless user's browser is definitely missing the CA certificate. That's the most likely cause of the certificate error. The FQDN and HTTPS settings seem fine to me.
upvoted 0 times
...
Lashaun
4 months ago
I believe the FortiGate authentication interface address using HTTPS could also be a likely cause.
upvoted 0 times
...
Elenora
4 months ago
The external server FQDN looks good, and the wireless user's browser is likely missing the CA certificate. The FortiGate authentication interface is probably using HTTPS, which could be the issue.
upvoted 0 times
Izetta
4 months ago
The external server FQDN may still be incorrect, double-check that.
upvoted 0 times
...
Izetta
4 months ago
Verify the FortiGate authentication interface address is using HTTPS.
upvoted 0 times
...
Izetta
4 months ago
Check if the wireless user's browser has the CA certificate installed.
upvoted 0 times
...
...
Moon
4 months ago
I agree with Lili, that could be one of the causes.
upvoted 0 times
...
Lili
4 months ago
I think the issue might be with the external server FQDN.
upvoted 0 times
...

Save Cancel