Refer to the exhibit. What is the result of the configuration?

Question

Options

• ANo-drop CoS values are advertised by the DCBX.
• BLFC is prioritized over PFC on Ethernet 1/10.
• CPFC operates on Ethernet 1/10 regardless of the capability of the peer.
• DPFC fails to operate properly unless LFC is disabled on Ethernet 1/10.

• A
  82% (18)
• B
  5% (1)
• C
  9% (2)
• D
  5% (1)

Explanation

Option A is correct because when PFC (Priority Flow Control) is configured on an interface with DCBX (Data Center Bridging Exchange), DCBX uses LLDP to advertise the no-drop CoS (Class of Service) values to the peer - this is DCBX's core purpose: exchanging DCB capabilities and parameters, including which 802.1p priority values will receive lossless treatment.

Option B is wrong because LFC (Link-level Flow Control) and PFC are mutually exclusive mechanisms - LFC pauses all traffic on a link, while PFC operates per-priority; neither is "prioritized over" the other, as enabling one typically displaces the other.

Option C is wrong because PFC requires bilateral negotiation via DCBX - if the peer doesn't support or agree to PFC, it cannot operate correctly; PFC is not a unilateral, peer-agnostic feature.

Option D is wrong because it reverses the relationship - LFC and PFC are indeed incompatible on the same interface, but the configuration shown is establishing PFC operation, not a dependency that requires manually disabling LFC first.

Memory tip: Think of DCBX as a "menu broadcaster" - once PFC is configured, DCBX announces to neighbors which CoS lanes are no-drop zones, like a host telling guests which seats are reserved. The advertisement is always the immediate result of enabling DCBX with PFC.

No community discussion yet for this question.