4A0-107 · Question #48
Individual application streams are considered microflows, whereas __________ are considered macroflows.
The correct answer is F. Forwarding classes. Forwarding classes (F) represent aggregated groups of traffic - they bundle many individual application streams into broad categories (e.g., voice, video, best-effort), which is precisely the "macro" level of flow classification. Queues (D) and schedulers (E) are mechanisms…
Question
Individual application streams are considered microflows, whereas __________ are considered macroflows.
Options
- ASAPs
- BSDPs
- CServices
- DQueues
- ESchedulers
- FForwarding classes
How the community answered
(32 responses)- B3% (1)
- C3% (1)
- F94% (30)
Explanation
Forwarding classes (F) represent aggregated groups of traffic - they bundle many individual application streams into broad categories (e.g., voice, video, best-effort), which is precisely the "macro" level of flow classification. Queues (D) and schedulers (E) are mechanisms that act on forwarding classes (queues hold packets; schedulers drain them), not classifications of flow granularity themselves. Services (C), SAPs (A), and SDPs (B) relate to service architecture and delivery infrastructure, not to the micro/macro flow hierarchy used in QoS traffic classification. The distinction is architectural: a microflow is one conversation (one TCP stream), while a macroflow (forwarding class) is the aggregate bucket that many conversations share.
Memory tip: Think of scale - "micro" = one stream, "macro" = the class that forwards many streams together. The word Forwarding Class literally describes its job: classify at a higher (macro) level for forwarding treatment.
Topics
Community Discussion
No community discussion yet for this question.