I think the key here is understanding how IGMP works to control multicast traffic. Enabling IGMP snooping and setting the timeout seem like the right choices to me.
Hmm, I'm a bit confused. I thought we had to use the setStorable() method in the JavaScript client-side code to enable caching. I'll need to double-check the documentation on this.
I'd choose C) Tag-based placement rules. It's the only one that sounds remotely cloud-native. Unless, of course, the answer is 'all of the above' - because you can never have too many storage policies, right?
As a vSphere expert, I can confidently say the answer is A) Host-based rules. This is a core feature of vSAN that can be leveraged for cloud-native deployments.
Hmm, I'm not too familiar with vSAN Direct, but I'd guess D) Storage performance-based rules. That seems like it would be a logical choice for cloud-native workloads.
Katy
4 months agoProvidencia
4 months agoDorinda
4 months agoGoldie
4 months agoElfrieda
5 months agoThurman
5 months agoAlpha
5 months agoVirgina
5 months agoDarnell
5 months agoGerman
5 months agoAmber
5 months agoLuther
10 months agoAron
9 months agoGail
9 months agoCarlee
9 months agoJaleesa
10 months agoIzetta
9 months agoFrancoise
9 months agoRolf
10 months agoAlethea
10 months agoAlbina
8 months agoNicholle
8 months agoLavonna
9 months agoMarica
9 months agoTeresita
9 months agoMitzie
9 months agoVirgilio
10 months agoJesusita
10 months agoLeah
11 months agoMarvel
10 months agoKallie
10 months agoTimothy
11 months agoParis
10 months agoNoe
10 months agoCraig
10 months agoCarli
10 months agoGerri
11 months agoGeraldine
11 months agoGerri
11 months ago