Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware 5V0-23.20 Exam - Topic 5 Question 47 Discussion

How are updates applied to Tanzu Kubernetes clusters?
C) New nodes are incrementally added with new Kubernetes versions so as a new node is added, an older node is removed.
A) The cluster is shutdown, Update Manager applies patches to VMs, and the cluster is restarted.
B) Worker nodes are shutdown while Controllers are patched and restarted after the update.
D) A new cluster is completely configured and runs in parallel to the primary cluster prior to switchover.

VMware 5V0-23.20 Exam - Topic 5 Question 47 Discussion

Actual exam question for VMware's 5V0-23.20 exam
Question #: 47
Topic #: 5
[All 5V0-23.20 Questions]

How are updates applied to Tanzu Kubernetes clusters?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Alysa
6 months ago
Option D sounds interesting, but is it really practical?
upvoted 0 times
...
Regenia
6 months ago
I’ve always seen option B as the standard method.
upvoted 0 times
...
Herminia
7 months ago
Wait, are we really shutting down the whole cluster for updates? That seems risky!
upvoted 0 times
...
Beatriz
7 months ago
Definitely agree with you, Cary!
upvoted 0 times
...
Cary
7 months ago
I think option C is the way to go for updates.
upvoted 0 times
...
Talia
7 months ago
I thought the cluster had to be shut down completely for updates, but now I'm questioning if that's really how it works with Tanzu.
upvoted 0 times
...
Margo
8 months ago
I practiced a question similar to this, and I feel like the answer was about configuring a new cluster in parallel before switching over.
upvoted 0 times
...
Krystina
8 months ago
I remember something about shutting down worker nodes, but I can't recall if it was just for patching or if it involved the controllers too.
upvoted 0 times
...
Eric
8 months ago
I think updates are done by adding new nodes and then removing the old ones, but I'm not entirely sure if that's the right process.
upvoted 0 times
...
Ligia
8 months ago
This seems straightforward. I'll go with the option that describes an incremental update approach to avoid a full cluster shutdown.
upvoted 0 times
...
Malcom
8 months ago
Okay, I think I've got this. The key is to look for the option that minimizes downtime and disruption to the running cluster.
upvoted 0 times
...
Margo
8 months ago
Hmm, I'm a bit unsure about this. I'll have to review the Tanzu documentation again to make sure I understand the update process.
upvoted 0 times
...
Jame
8 months ago
This is a tricky one. I'll need to think through the different update options carefully.
upvoted 0 times
...
Kayleigh
8 months ago
I'm confident I can figure this out. Let me analyze each of the choices and see which one best matches the Tanzu update process.
upvoted 0 times
...
Wenona
8 months ago
Hmm, I'm a bit unsure about this one. There are a lot of options and I want to make sure I understand the differences between them. I'll need to review the INVEST model to refresh my memory.
upvoted 0 times
...
Christiane
8 months ago
Ah, I remember learning about PIV cards in class. The inability to export the private key is a critical security measure to prevent unauthorized access. I'm confident option A is the correct answer.
upvoted 0 times
...
Odette
2 years ago
I bet the developers at VMware had a good laugh coming up with these options. 'Shutdown the cluster? What is this, the 90s?'
upvoted 0 times
Carmelina
2 years ago
C) New nodes are incrementally added with new Kubernetes versions so as a new node is added, an older node is removed.
upvoted 0 times
...
Roselle
2 years ago
B) Worker nodes are shutdown while Controllers are patched and restarted after the update.
upvoted 0 times
...
Amie
2 years ago
A) The cluster is shutdown, Update Manager applies patches to VMs, and the cluster is restarted.
upvoted 0 times
...
Cheryl
2 years ago
C) New nodes are incrementally added with new Kubernetes versions so as a new node is added, an older node is removed.
upvoted 0 times
...
Lajuana
2 years ago
B) Worker nodes are shutdown while Controllers are patched and restarted after the update.
upvoted 0 times
...
Maia
2 years ago
A) The cluster is shutdown, Update Manager applies patches to VMs, and the cluster is restarted.
upvoted 0 times
...
...
Artie
2 years ago
Hmm, A sounds like a recipe for a long outage. Definitely not the way to go for a production cluster.
upvoted 0 times
...
Grover
2 years ago
I think a new cluster is configured and runs in parallel before switchover for updates.
upvoted 0 times
...
Avery
2 years ago
I heard that new nodes are incrementally added with new Kubernetes versions, replacing older nodes.
upvoted 0 times
...
Elsa
2 years ago
B looks good to me. Patching the controllers while the workers are down should minimize disruption.
upvoted 0 times
Yolando
2 years ago
I agree. Patching the controllers while the workers are down seems like a good strategy for updating Tanzu Kubernetes clusters.
upvoted 0 times
...
Brittni
2 years ago
B looks like the best option. It's important to minimize disruption when applying updates.
upvoted 0 times
...
...
Lili
2 years ago
I believe the worker nodes are shutdown while Controllers are patched and restarted after the update.
upvoted 0 times
...
Aliza
2 years ago
I think the updates are applied by shutting down the cluster and applying patches to VMs.
upvoted 0 times
...
Martin
2 years ago
I'd go with D. Creating a new cluster and swapping it in is the safest approach for mission-critical systems.
upvoted 0 times
...
Jame
2 years ago
Option C seems the most logical. Upgrading incrementally without downtime is the way to go.
upvoted 0 times
Margurite
2 years ago
It definitely minimizes downtime and ensures a smooth upgrade process.
upvoted 0 times
...
Mitsue
2 years ago
I agree, option C does seem like the most logical approach.
upvoted 0 times
...
...

Save Cancel