Hi,
Checked this with our MAA support team and got reply as below
Customizing the VM means all the task processing will hold, eth1 of the dirty line will use the same settings as backend eth0. Files that are being passed to MA will not be processed(scan), if CAS does not wait for the result from MAA, then that is alright, but otherwise, CAS will wait for the task processing to complete in getting the score.
The moment we rebuild the profile after customizing , we could see a lot of files being queued to be process. So suggestion would be to have CAS not wait for result or disable the sandboxing when performing profile customizing, just to avoid any report of delay in getting the file download.
Hope this helps