1. NetApp Knowledge Base
Article 1030213
"How to test for jumbo frames with ping": This article explicitly states
"To test for jumbo frames
use the ping command with the -packet-size option set to a value less than the MTU
and the -disallow-fragmentation option set to true." It provides a specific example using a packet size of 8972 for a 9000 MTU
which aligns with the logic for selecting option C.
2. NetApp Technical Report TR-4336
"iSCSI Configuration and Implementation Guide for Clustered Data ONTAP": In the "Jumbo Frames" section (page 17)
this guide recommends verifying jumbo frame configuration using the ping command with a large packet size (e.g.
8972) and with fragmentation disallowed. This confirms that the test packet size must be less than the 9000-byte MTU.
3. ONTAP 9 Commands
Manual Page Reference for ping: The documentation for the ping command details the -packet-size parameter
which specifies the number of data bytes in the ICMP packet
and the -disallow-fragmentation {true|false} parameter
which controls the DF bit. This confirms the command structure and the function of the options used in the correct answer.