Run a server that has imported ReferenceServer.NodeSet2.xml from OPCFoundation\UA-.NETStandard.
The CTT imported nodes should include a node with an id ...;s=CTT_Scalar_Static_Arrays_Byte that should be part of compliance tool setting on Settings\Server Test\NodeIds\Static\AllProfiles\Arrays Byte entry beside the other similar array nodes references.

Run the compliance tool selecting script option Attribute Services\Attribute Write Index\006.js

All ctt nodes provided in ctt settings array nodes are passing except CTT_Scalar_Static_Arrays_Byte which rise script exception Write().Response.Results[1].StatusCode = 'BadTypeMismatch (0x80740000)'; but StatusCode 'BadIndexRangeNoData (0x80370000)' was expected (Node Setting: '/Server Test/NodeIds/Static/All Profiles/Arrays/Byte') StatusCode expectations for this call were...

The OPCFoundation\UA-.NETStandard server actually converts the byte[] to ByteString based on documentation aka. https://reference.opcfoundation.org/v104/Core/docs/Part6/5.1.4/

Actually the issue happens on initialize.js line 25 if( ReadHelper.Execute( { NodesToRead: items } ) ) {
During the read the byte[] and ByteString is interpreted with the same type ByteString = 15 instead of Byte = 3 and the the js code does not try to split the received value into byte[] then the exception. Unfortunately the server respect the documentation considering byte[] as ByteString that is correct based on dcoumentation.