Deal of The Day! Hurry Up, Grab the Special Discount - Save 25%
- Ends In
00:00:00
Coupon code:
SAVE25
X
Welcome to Pass4Success
Login
|
Sign up
-
Free
Preparation Discussions
Mail Us
support@pass4success.com
Location
PL
MENU
Home
Popular vendors
Salesforce
Microsoft
Nutanix
Cisco
Amazon
Google
CompTIA
SAP
VMware
Oracle
Fortinet
PeopleCert
Eccouncil
HP
Palo Alto Networks
Adobe
ServiceNow
Dell EMC
CheckPoint
Linux Foundation
Discount Deals
New
About
Contact
Login
Sign up
Home
Discussions
VMware Discussions
Exam 5V0-23.20 Topic 5 Question 49 Discussion
VMware Exam 5V0-23.20 Topic 5 Question 49 Discussion
Actual exam question for VMware's 5V0-23.20 exam
Question #: 49
Topic #: 5
[All 5V0-23.20 Questions]
How are updates applied to Tanzu Kubernetes clusters?
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.
C
New nodes are incrementally added with new Kubernetes versions so as a new node is added, an older node is removed.
D
A new cluster is completely configured and runs in parallel to the primary cluster prior to switchover.
Show Suggested Answer
Hide Answer
Suggested Answer:
C
by
Gilma
at
Jul 12, 2024, 03:31 PM
Limited Time Offer
25%
Off
Get Premium 5V0-23.20 Questions as Interactive Web-Based Practice Test or PDF
Contribute your Thoughts:
Submit
Cancel
Hassie
21 days ago
Hah, imagine the poor admin who has to manually patch each VM. I'll take the automated approach of C, thank you very much.
upvoted
0
times
Raina
21 hours ago
User 1: Imagine having to manually patch each VM, that would be a nightmare!
upvoted
0
times
...
...
Shawnna
27 days ago
D is interesting, but setting up a parallel cluster just for an update feels like overkill. I'm going with C.
upvoted
0
times
Lorrine
19 hours ago
C sounds like a simpler approach to updating Kubernetes clusters.
upvoted
0
times
...
Twana
14 days ago
I agree, setting up a parallel cluster seems like a lot of extra work.
upvoted
0
times
...
Beatriz
16 days ago
C sounds more efficient in terms of managing node versions.
upvoted
0
times
...
Lashawnda
20 days ago
D is a good option for ensuring no downtime during updates.
upvoted
0
times
...
...
Odelia
1 months ago
I think a new cluster is set up and runs alongside the primary cluster before switching over.
upvoted
0
times
...
Rodolfo
1 months ago
I agree, C is the way to go. Shutting down the whole cluster or just the worker nodes is way too disruptive.
upvoted
0
times
...
Weldon
1 months ago
I heard that new nodes are added incrementally with new Kubernetes versions, replacing older nodes.
upvoted
0
times
...
Jesusita
1 months ago
I believe the worker nodes are shutdown while the Controllers are patched and then restarted.
upvoted
0
times
...
Elke
1 months ago
Option C seems the most logical to me. Gradually upgrading the nodes while keeping the cluster running is a smart approach.
upvoted
0
times
Lenna
17 days ago
It definitely seems like a more efficient way to keep the cluster up to date.
upvoted
0
times
...
Edelmira
20 days ago
I agree, option C sounds like a smooth way to update without causing downtime.
upvoted
0
times
...
...
Jolene
1 months ago
I think the updates are applied by shutting down the cluster and then restarting it.
upvoted
0
times
...
Log in to Pass4Success
×
Sign in:
Forgot my password
Log in
Report Comment
×
Is the comment made by
USERNAME
spam or abusive?
Commenting
×
In order to participate in the comments you need to be logged-in.
You can
sign-up
or
login
Save
Cancel
az-700
pass4success
az-104
200-301
200-201
cissp
350-401
350-201
350-501
350-601
350-801
350-901
az-720
az-305
pl-300
Hassie
21 days agoRaina
21 hours agoShawnna
27 days agoLorrine
19 hours agoTwana
14 days agoBeatriz
16 days agoLashawnda
20 days agoOdelia
1 months agoRodolfo
1 months agoWeldon
1 months agoJesusita
1 months agoElke
1 months agoLenna
17 days agoEdelmira
20 days agoJolene
1 months ago