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

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

Lakeesha
2 months ago
Wait, the user address isn't in DDNS form? What is this, the Stone Age?
upvoted 0 times
Angelo
1 months ago
User3: Maybe the wireless user's browser just needs to update the CA certificate.
upvoted 0 times
...
Dallas
1 months ago
The external server FQDN being incorrect could also be causing the issue.
upvoted 0 times
...
Eric
1 months ago
It's not about being in the Stone Age, it's about security.
upvoted 0 times
...
...
Arlette
2 months ago
I think the wireless user's browser is missing the CA certificate. That's always a pain to troubleshoot.
upvoted 0 times
Nathalie
1 months ago
User4: It could also be that the user address is not in DDNS form.
upvoted 0 times
...
Marsha
1 months ago
User3: Maybe the FortiGate authentication interface address is using HTTPS.
upvoted 0 times
...
Ayesha
1 months ago
I believe the issue might be with the CA certificate in the browser.
upvoted 0 times
...
Jeff
2 months ago
Have you checked if the external server FQDN is correct?
upvoted 0 times
...
...
Madelyn
2 months ago
Haha, the FortiGate team really loves their HTTPS, don't they? That's gotta be the issue.
upvoted 0 times
...
Hyman
2 months ago
That's a good point, it could be a combination of both issues causing the problem.
upvoted 0 times
...
Mariann
3 months ago
But what about the browser missing a CA certificate? Could that also be a possible cause?
upvoted 0 times
...
Nidia
3 months ago
I agree with Hyman, that could be causing the certificate error.
upvoted 0 times
...
Yuonne
3 months ago
The issue is definitely the external server FQDN being incorrect. It's a common problem we see in these setups.
upvoted 0 times
Dean
1 months ago
B) The wireless user's browser is missing a CA certificate
upvoted 0 times
...
Pok
1 months ago
A) The external server FQDN is incorrect
upvoted 0 times
...
...
Hyman
3 months ago
I think the issue might be with the external server FQDN.
upvoted 0 times
...

Save Cancel