During the on-boarding process through the captive portal, what are two reasons why a host that successfully registered would remain stuck in the Registration VLAN? (Choose two.)
Hmm, yeah, the unregistered host option is a bit of a head-scratcher. Maybe it has something to do with the port being in a kind of 'limbo' state until all hosts are properly registered? Either way, I think B and C are the safest bets for this question.
I agree with you on those two options. The bridging one also makes sense, since that could potentially interfere with the registration process. As for the unregistered host on the same port, that's an interesting one, but I'm not sure how that would directly impact the current host's registration.
Okay, let's think this through. The wrong agent being installed seems like a logical option, since the host may not be able to properly communicate with the portal. And if the default VLAN is the same as the Registration VLAN, that could definitely cause issues with the host moving to the correct network.
Hmm, this question seems tricky. I'm not sure if I fully understand the registration process through the captive portal. The options seem to cover a range of potential issues, but I'm not confident which two would be the most likely reasons a host would get stuck in the Registration VLAN.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Elena
8 months agoLauran
8 months agoAileen
8 months agoGraciela
8 months agoCathrine
8 months agoTiera
8 months ago