156-215.76 · Question #301
What gives administrators more flexibility when configuring Captive Portal instead of LDAP query for Identity Awareness authentication?
The correct answer is D. Captive Portal works with both configured users and guests. See the full explanation below for the reasoning.
Question
What gives administrators more flexibility when configuring Captive Portal instead of LDAP query for Identity Awareness authentication?
Options
- ACaptive Portal is more secure than standard LDAP
- BCaptive Portal is more transparent to the user
- CNothing, LDAP query is required when configuring Captive Portal
- DCaptive Portal works with both configured users and guests
How the community answered
(37 responses)- A11% (4)
- B5% (2)
- C3% (1)
- D81% (30)
Community Discussion
5
Mei-Ling H.Jun 5, 2026D is the correct answer. LDAP query only works for users that already exist in your directory, so the moment you have a guest or unregistered user trying to get through, LDAP cannot authenticate them, but Captive Portal handles both configured (directory) users and guests, which is exactly what gives admins that extra flexibility.
Brenda K.Jun 14, 2026D is right, Captive Portal handles guests too, not just directory accounts.
Orla P.Jun 19, 2026Thought A made sense at first, but D is right because guests need no directory account at all.
Samuel O.May 31, 2026Captive Portal literally depends on LDAP to resolve identities, C is the only logical pick.
Mei-Ling H.Jun 2, 2026Samuel, Captive Portal does not require LDAP specifically, it redirects unauthenticated clients to a web login page and typically hands off credentials to a RADIUS server for authentication, which is why D is correct here.