H12-891_V1.0 · Question #148
After a wireless user passes Portal authentication, which of the following parameters is not supported for authorization to the user?
The correct answer is B. IP address. After Portal authentication on a wireless network, the system pushes authorization parameters to control what the user can access - but IP address assignment happens via DHCP before or during the authentication process, not as a post-authentication authorization attribute…
Question
After a wireless user passes Portal authentication, which of the following parameters is not supported for authorization to the user?
Options
- Afree-rule
- BIP address
- CACL
- DUCL
How the community answered
(17 responses)- A12% (2)
- B76% (13)
- C6% (1)
- D6% (1)
Explanation
After Portal authentication on a wireless network, the system pushes authorization parameters to control what the user can access - but IP address assignment happens via DHCP before or during the authentication process, not as a post-authentication authorization attribute. Since IP addresses are not delivered as part of the Portal authorization payload, B (IP address) is the correct answer for what is not supported.
Why the distractors are wrong:
- A (free-rule): Free rules define traffic permitted to bypass or pass without full authentication checks and are a valid authorization parameter pushed after Portal auth.
- C (ACL): Access Control Lists are commonly pushed post-authentication to restrict or permit specific traffic flows for the user.
- D (UCL): User Control Lists are supported authorization attributes that define per-user access policies after Portal authentication succeeds.
Memory tip: Think of Portal authorization as pushing policy to the user (ACL, UCL, free-rule = access rules), not identity (IP address = who you are, already handled by DHCP). If it's a network policy attribute, it fits; if it's a network identity attribute, it doesn't.
Topics
Community Discussion
No community discussion yet for this question.