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 1 Question 14 Discussion

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

Bulah
6 months ago
Yes, that's a good point. It's important to check both settings.
upvoted 0 times
...
Elinore
6 months ago
But what about the browser missing a CA certificate? Could that also be a likely cause?
upvoted 0 times
...
Sheridan
6 months ago
I agree, that could definitely cause a certificate error.
upvoted 0 times
...
Cletus
6 months ago
I think the issue might be with the external server FQDN being incorrect.
upvoted 0 times
...
Han
6 months ago
I believe the FortiGate authentication interface address using HTTPS could also be a factor.
upvoted 0 times
...
Tracie
7 months ago
But what about the wireless user's browser missing a CA certificate? That could also be a possible cause.
upvoted 0 times
...
Vinnie
7 months ago
I agree with Hector. That could be one of the causes.
upvoted 0 times
...
Hector
7 months ago
I think the issue might be with the external server FQDN being incorrect.
upvoted 0 times
...
Tamar
8 months ago
Haha, I love how this exam question is trying to trick us. 'Wireless guest users are unable to authenticate' - that's like the IT version of 'the dog ate my homework'! But in all seriousness, I agree with Desirae and 2 that the missing CA certificate and the HTTPS interface are the likely culprits here.
upvoted 0 times
...
Dean
8 months ago
Hmm, I'm not so sure about option C. Using HTTPS for the authentication interface is actually a good practice to ensure secure communication. I think the real issue here is with the external server FQDN being incorrect, as mentioned in option A. That could definitely cause the certificate error.
upvoted 0 times
Harrison
8 months ago
Hmm, I'm not so sure about option C. Using HTTPS for the authentication interface is actually a good practice to ensure secure communication. I think the real issue here is with the external server FQDN being incorrect, as mentioned in option A. That could definitely cause the certificate error.
upvoted 0 times
...
Paris
8 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Ty
8 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Elsa
8 months ago
I agree with you, Desirae. The certificate error suggests that the browser is not able to verify the certificate used by the captive portal. So the missing CA certificate is probably the culprit here. And using HTTPS for the authentication interface could also be causing issues, since the user's browser may not trust the certificate.
upvoted 0 times
...
Desirae
8 months ago
Hmm, this is an interesting question. The issue seems to be with the captive portal login page not loading properly due to a certificate error. Based on the options provided, I think the likely causes are B) the wireless user's browser is missing a CA certificate, and C) the FortiGate authentication interface address is using HTTPS.
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