An administrator is implementing a new network-based storage device. In selecting a storage protocol, the administrator would like the data in transit's integrity to be the most important concern…

SMB 3.0 implements AES-CMAC for packet signing to verify data integrity, while SMB 2.x used HMAC-SHA256 for the same purpose. These cryptographic signing mechanisms protect data from tampering while traversing the network, making SMB the only listed protocol that directly implements either of the two specified algorithms for data integrity.

NFS does not natively implement AES-CMAC or HMAC-SHA256 for data signing - it relies on Kerberos or AUTH_SYS for authentication rather than cryptographic integrity signing of packets in transit.

FCoE is a Layer 2 encapsulation protocol that carries Fibre Channel frames over Ethernet and does not natively implement AES-CMAC or HMAC-SHA256 for data integrity signing.

iSCSI can leverage IPsec for security at the network layer but does not natively implement AES-CMAC or HMAC-SHA256 at the iSCSI protocol level for signing data in transit.