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 2 Question 35 Discussion

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

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:

Pearly
1 months ago
Missing a CA certificate, huh? Well, at least the wireless users aren't getting a 'Your connection is not private' warning. Silver linings, folks!
upvoted 0 times
Blair
11 days ago
C) The FortiGate authentication interface address is using HTTPS
upvoted 0 times
...
Paola
16 days ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Amalia
22 days ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Torie
2 months ago
The user address not being in DDNS form? What is this, the 90s? I doubt that's the issue here. Clearly, the CA certificate is the culprit.
upvoted 0 times
Tamala
15 days ago
User 3: Maybe the external server FQDN is incorrect too.
upvoted 0 times
...
Hoa
23 days ago
User 2: Yeah, the browser might be missing it.
upvoted 0 times
...
Keena
1 months ago
User 1: I think the issue is with the CA certificate.
upvoted 0 times
...
...
Jennie
2 months ago
Using HTTPS for the FortiGate authentication interface? That's a security best practice, so I don't think that's the problem. Gotta be something else.
upvoted 0 times
...
Elli
2 months ago
Hmm, the external server FQDN being incorrect could also be a possibility. I'd check that setting first before looking at the CA certificate.
upvoted 0 times
Amie
23 minutes ago
Let's check the external server FQDN setting first.
upvoted 0 times
...
...
Sarah
2 months ago
The HTTPS POST URL looks correct, so the issue is likely due to the wireless user's browser missing a CA certificate. That's the most probable cause here.
upvoted 0 times
...
Kris
2 months ago
I believe another possible cause could be the wireless user's browser missing a CA certificate.
upvoted 0 times
...
Twana
2 months ago
I agree with Zena, that could definitely be causing the problem.
upvoted 0 times
...
Zena
2 months ago
I think the issue might be with the external server FQDN being incorrect.
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