H12-323_V2.0 · Question #540
In a WLAN network, if a user is associated with the same WAC before and after roaming, it can be regarded as a special case of inter-WAC roaming, that is, the HAC and FAC overlap.
The correct answer is B. False. B is correct because when a user remains associated with the same WAC before and after roaming, this is classified as intra-WAC roaming - a fundamentally distinct category from inter-WAC roaming, not a special case of it. Inter-WAC roaming, by definition, requires two different…
Question
In a WLAN network, if a user is associated with the same WAC before and after roaming, it can be regarded as a special case of inter-WAC roaming, that is, the HAC and FAC overlap.
Options
- ATrue
- BFalse
How the community answered
(44 responses)- A27% (12)
- B73% (32)
Explanation
B is correct because when a user remains associated with the same WAC before and after roaming, this is classified as intra-WAC roaming - a fundamentally distinct category from inter-WAC roaming, not a special case of it. Inter-WAC roaming, by definition, requires two different controllers: the HAC (Home Access Controller) and FAC (Foreign Access Controller) must be separate entities. If the user stays on the same WAC, the HAC/FAC distinction is irrelevant - there is only one controller involved, so they cannot meaningfully "overlap."
A is wrong because it misapplies the inter-WAC framework to a same-WAC scenario. Saying HAC and FAC "overlap" when there's only one controller is a category error - you can't have inter-controller roaming without two controllers.
Memory tip: Use the prefixes: intra = within (one WAC), inter = between (two WACs). Same WAC = intra. Different WACs = inter. They are sibling categories, not parent-child - intra-WAC roaming is never a "special case" of inter-WAC roaming.
Topics
Community Discussion
No community discussion yet for this question.