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