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

Fortinet Exam NSE7_LED-7.0 Topic 3 Question 26 Discussion

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

Nakita
3 months ago
Yes, that could definitely be another reason. We should consider all these options when troubleshooting.
upvoted 0 times
...
Rosio
4 months ago
Wait, is the issue that the users are getting a certificate error? That's just classic 'forgot to configure the SSL cert' right there.
upvoted 0 times
Joni
3 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Micaela
3 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Dallas
4 months ago
Haha, DDNS? What is this, 1998? That's not even a real option.
upvoted 0 times
...
Lucy
4 months ago
HTTPS on the authentication interface? That's a rookie mistake. Definitely going to flag that one.
upvoted 0 times
...
Verda
4 months ago
You're right, the missing CA certificate is probably the other cause. Gotta install that on the users' browsers.
upvoted 0 times
Bambi
3 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Dominic
3 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Lucina
4 months ago
I believe the FortiGate authentication interface address using HTTPS could be causing the problem as well.
upvoted 0 times
...
Lashaun
4 months ago
The external server FQDN is incorrect. That's the issue for sure.
upvoted 0 times
Von
4 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Beatriz
4 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Sherill
4 months ago
I agree with you, Nakita. The browser missing a CA certificate could also be a possible cause.
upvoted 0 times
...
Nakita
4 months ago
I think the issue might be with the external server FQDN.
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