You decide to enable SnapMirror network compression on your NetApp clustered Data ONTAP environment. Which two statements are correct about enabling this feature?
I'll have to agree with the others on A and D. The compression happening only during network transfer makes sense, and the multi-threaded approach to leverage the source system's resources is a classic NetApp optimization trick. B and C feel a bit too restrictive to be true.
Haha, I love how they throw in these tricky options to really test our understanding. It's like NetApp is playing a game of 'Spot the Odd One Out' with us. I'm going with A and D, seems like the most straightforward answers here.
I'm not sure about B, the NDMP protocol requirement. I thought SnapMirror could work with other network protocols as well. And C also doesn't sound right, as I would expect the compression to be available cluster-wide, not limited to a single HA pair.
A and D seem correct. SnapMirror network compression is all about reducing the data transfer over the network, not about permanent storage compression. And the compression engine should be leveraging the available CPU resources on the source system.
That makes sense. It's important to optimize network performance while transferring data between clusters. Enabling compression can definitely help with that.
A and D are correct. SnapMirror network compression is focused on reducing network data transfer, not storage compression. The compression engine should utilize the CPU resources on the source system.
Caitlin
5 months agoMarci
4 months agoJohnetta
4 months agoAlyce
4 months agoAlfreda
4 months agoKimbery
5 months agoWillie
5 months agoPura
5 months agoRoyal
5 months agoArlyne
5 months agoDiane
4 months agoTaryn
5 months agoJerrod
5 months agoOdette
5 months agoDorothy
4 months agoAn
4 months agoMalcom
5 months agoMelvin
5 months agoReiko
5 months agoMicah
5 months agoHannah
5 months ago