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
7 months agoProvidencia
7 months agoDorinda
7 months agoGoldie
8 months agoElfrieda
8 months agoThurman
8 months agoAlpha
8 months agoVirgina
8 months agoDarnell
8 months agoGerman
8 months agoAmber
8 months agoLuther
1 year agoAron
12 months agoGail
1 year agoCarlee
1 year agoJaleesa
1 year agoIzetta
1 year agoFrancoise
1 year agoRolf
1 year agoAlethea
1 year agoAlbina
11 months agoNicholle
12 months agoLavonna
1 year agoMarica
1 year agoTeresita
1 year agoMitzie
1 year agoVirgilio
1 year agoJesusita
1 year agoLeah
1 year agoMarvel
1 year agoKallie
1 year agoTimothy
1 year agoParis
1 year agoNoe
1 year agoCraig
1 year agoCarli
1 year agoGerri
1 year agoGeraldine
1 year agoGerri
1 year ago