Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware Exam 5V0-23.20 Topic 9 Question 48 Discussion

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

A Namespace contains multiple Tanzu Kubernetes clusters.

How is access granted to a single Tanzu Kubernetes cluster?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Herminia
5 months ago
I see your point, but using kubectl commands gives more control and flexibility.
upvoted 0 times
...
Lauryn
5 months ago
Haha, D is just trying to confuse us. As if the vSphere Client would be the way to grant access to a specific Tanzu Kubernetes cluster. Nice try, question writer!
upvoted 0 times
...
Lamar
5 months ago
Hmm, I'm torn between A and C. Both involve creating a custom Role and RoleBinding, but the application step is different. I'll have to think this one through carefully.
upvoted 0 times
Magda
3 months ago
I'm leaning towards C. Applying the custom Role and RoleBinding directly to the Tanzu Kubernetes cluster using kubectl commands makes sense to me.
upvoted 0 times
...
Mammie
3 months ago
I agree, A seems like the right choice. It's all about applying it to the Namespace.
upvoted 0 times
...
Denna
3 months ago
I think A is the correct answer. You apply the custom Role and RoleBinding to the Namespace using kubectl commands.
upvoted 0 times
...
Tamesha
4 months ago
Yeah, A makes sense. It's about granting access to the Namespace with the custom Role and RoleBinding.
upvoted 0 times
...
Fernanda
4 months ago
I agree, A seems to be the right choice. It's all about applying it to the Namespace.
upvoted 0 times
...
Marg
4 months ago
I think A is the correct option. You apply the custom Role and RoleBinding to the Namespace using kubectl commands.
upvoted 0 times
...
...
Annmarie
5 months ago
But wouldn't it be easier to just use the vSphere Client?
upvoted 0 times
...
Melina
5 months ago
I agree with Herminia, creating custom Role and RoleBinding makes sense.
upvoted 0 times
...
Herminia
5 months ago
I think the answer is A.
upvoted 0 times
...
Jeffrey
5 months ago
D is a trap! You can't use the vSphere Client to grant access to a single Tanzu Kubernetes cluster. That's just silly.
upvoted 0 times
...
Karima
5 months ago
I think the answer is C. It makes the most sense to apply the custom Role and RoleBinding to the specific Tanzu Kubernetes cluster, not the Namespace.
upvoted 0 times
Golda
4 months ago
That makes sense. It ensures that access is granted specifically to the cluster.
upvoted 0 times
...
Adela
4 months ago
I agree, applying the custom Role and RoleBinding directly to the Tanzu Kubernetes cluster seems like the correct approach.
upvoted 0 times
...
Jani
4 months ago
C
upvoted 0 times
...
Kanisha
4 months ago
C) Create a custom Role and RoleBinding, and then apply to the Tanzu Kubernetes cluster using kubectl commands.
upvoted 0 times
...
Tamera
4 months ago
A) Create a custom Role and RoleBinding, and then apply to the Tanzu Kubernetes cluster using kubectl commands.
upvoted 0 times
...
Georgene
5 months ago
A
upvoted 0 times
...
...

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  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77