Click the exhibit button below. Given the output of the #show pools 1/2/2 network-egress command on a GigE port, what can the service provider deduce? (Choose two)

Question

Exhibit

Options

• AQoS is not configured on the router.
• BPackets in forwarding classes "be" and "12" are being queued.
• CTraffic belonging to forwarding class "ef" is not experiencing queuing delays.
• DTraffic belonging to forwarding class "11 "will never make use of the shared buffer pool.
• EOut-of-profile traffic in the shared buffer pool is being dropped.

• A
  6% (1)
• B
  75% (12)
• D
  6% (1)
• E
  13% (2)

Explanation

Options B and C are correct because the show pools output on a GigE egress port reveals real-time queue depths per forwarding class: non-zero depth values for "be" (Best Effort) and "l2" (Loss Priority 2) confirm those packets are actively waiting in buffers, while a queue depth of zero for "ef" (Expedited Forwarding) confirms EF traffic is being serviced immediately with no buffering delay - which is the expected behavior of a strict-priority class.

Why the distractors are wrong:

• A is wrong because the presence of per-forwarding-class pool statistics proves QoS is configured - traffic classification and queue separation require it.
• D is wrong because L1 traffic can access the shared buffer pool when its dedicated allocation is exhausted; only explicit configuration (e.g., a no-shared-buffer policy) would prevent it, which cannot be inferred here.
• E is wrong because a show pools output shows occupancy and queue depths, not drop statistics - you'd need show class-of-service interface or RED drop counters to confirm active tail/RED drops.

Memory tip: Think of EF as a VIP lane - if show pools shows zero depth for EF, the VIP is never waiting. BE and L2 are coach class - if they show depth, they're queued up. The show pools command is a depth snapshot, not a drop report, so never conclude drops or QoS absence from it alone.

No community discussion yet for this question.