700-281 · Question #46
Bandwidth limits cannot be:
The correct answer is B. per (LDAP) group. Bandwidth limits cannot be applied per LDAP group because group-based bandwidth allocation requires the system to dynamically resolve group membership at the time of traffic enforcement, which many bandwidth management implementations do not support - LDAP group lookups add…
Question
Bandwidth limits cannot be:
Options
- Aoverall
- Bper (LDAP) group
- Cper user
How the community answered
(38 responses)- A5% (2)
- B87% (33)
- C8% (3)
Explanation
Bandwidth limits cannot be applied per LDAP group because group-based bandwidth allocation requires the system to dynamically resolve group membership at the time of traffic enforcement, which many bandwidth management implementations do not support - LDAP group lookups add complexity that falls outside the scope of standard traffic shaping engines. Overall bandwidth limits (A) are wrong as a distractor because setting a global cap is the most fundamental and universally supported form of bandwidth control. Per-user limits (C) are also incorrect as a distractor because individual user-based throttling is a standard feature in most bandwidth management tools, as users can be directly mapped to traffic flows.
Memory tip: Think "Groups = Gap" - LDAP Groups are the Gap in bandwidth limit support. You can go broad (overall) or narrow (per user), but the middle tier (group) is missing.
Topics
Community Discussion
No community discussion yet for this question.