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 22 Discussion

Actual exam question for Fortinet's NSE7_LED-7.0 exam
Question #: 22
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
3 months ago
The FortiGate authentication interface using HTTPS is probably the culprit. It's like they're making it harder for users to connect just for the fun of it.
upvoted 0 times
Linn
3 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Shonda
3 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Blythe
3 months ago
Haha, I bet the IT team forgot to send the CA cert to the users' browsers. Classic IT move, always forgetting the basics!
upvoted 0 times
Stacey
2 months ago
Classic IT move, forgetting the basics like sending out the CA cert.
upvoted 0 times
...
Aaron
2 months ago
Yeah, that could be the issue. The IT team should check that.
upvoted 0 times
...
Kiley
3 months ago
Maybe the browser just needs the CA certificate installed.
upvoted 0 times
...
Esteban
3 months ago
The FortiGate authentication interface address using HTTPS could also be a factor. It needs to match the certificate.
upvoted 0 times
...
Carla
3 months ago
Maybe the external server FQDN is incorrect too. That could be causing the certificate error.
upvoted 0 times
...
Valentine
3 months ago
Yeah, that's a common mistake. CA cert needs to be installed on the user's browser.
upvoted 0 times
...
...
Hubert
4 months ago
Yes, I think both of those settings could be causing the certificate error.
upvoted 0 times
...
Antione
4 months ago
I agree, the external server FQDN and the user address are not likely the causes here. It's probably the SSL/TLS configuration that's causing the certificate error.
upvoted 0 times
Gearldine
3 months ago
Option C might also be a factor. The FortiGate authentication interface address using HTTPS could be causing the issue.
upvoted 0 times
...
Gearldine
4 months ago
I think option B is correct. The browser missing a CA certificate could be causing the certificate error.
upvoted 0 times
...
...
Cherry
4 months ago
The HTTPS POST URL looks correct, so the issue is likely due to the missing CA certificate or the FortiGate authentication interface using HTTPS.
upvoted 0 times
Noah
4 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Izetta
4 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Cristy
4 months ago
I believe another possible cause could be the user's browser missing a CA certificate.
upvoted 0 times
...
Gearldine
4 months ago
I agree with Yesenia, that could be one of the causes.
upvoted 0 times
...
Yesenia
5 months ago
I think the issue might be with the external server FQDN.
upvoted 0 times
...

Save Cancel