Cisco's validated guidance for connecting VAST Data storage through an ACI fabric explicitly configures the RDMA storage class with Weighted Random Early Detection and Congestion Notification enabled . This makes option A directly consistent with Cisco's documented configuration.

In Cisco's VAST Data ACI design example, storage traffic arrives marked with DSCP 26 and is assigned to the Level2 QoS class. PFC is enabled for the corresponding no-drop DSCP, bandwidth is reserved for storage traffic, the congestion algorithm is configured as WRED, and congestion notification is enabled.

WRED and ECN-style congestion notification work together to detect developing queue pressure before buffers overflow. Rather than waiting for tail-drop conditions, the network can mark congestion-capable traffic so RoCEv2 endpoints reduce their transmission rates. PFC provides the complementary no-drop behavior when congestion becomes sufficiently severe.

Option B disables the required congestion signaling. Options C and D use Tail Drop, which Cisco's documented VAST RDMA storage class does not use. Tail Drop is instead shown in the same Cisco design for control-plane and ordinary traffic classes where lossless RDMA behavior is not required.

This configuration is therefore not merely a generic QoS preference; it directly follows Cisco's published ACI-to-VAST storage design.

Study Guide Reference: AI Infrastructure Deployment and Data Management — QoS, ECN/WRED, PFC, RDMA storage, and lossless fabric configuration.