3V0-24.25 Online Practice Questions

Home / Broadcom / 3V0-24.25

Latest 3V0-24.25 Exam Practice Questions

The practice questions for 3V0-24.25 exam was last updated on 2025-12-17 .

Viewing page 1 out of 9 pages.

Viewing questions 1 out of 48 questions.

Question#1

A Platform Engineer needs to configure a vSphere Namespace to allow a specific Active Directory group, [email protected], to have full administrative access to the Kubernetes namespace, including the ability to create and delete TKG clusters. The solution must follow the principle of least privilege within vSphere.
Which configuration steps in the vSphere Client will achieve this? (Select all that apply.)

A. Assign the NSX Administrator role to [email protected] in NSX Manager.
B. In the Namespace permissions, add [email protected] with the CanEdit role.
C. Ensure the Identity Source corp.local is configured in vCenter Single Sign-On.
D. In the Namespace permissions, add [email protected] with the Owner role.
E. Assign the Administrator role to [email protected] at the vCenter Server Global Permissions level.

Question#2

A VI Administrator wants to install the Velero Supervisor Service.
The administrator has downloaded the velero-service.yaml (Service Definition) from the VMware Marketplace.
What is the first step to make this service available for installation on a Supervisor Cluster?

A. Install the Velero plugin on the vCenter Appliance.
B. Create a vSphere Namespace named velero.
C. Run kubectl apply -f velero-service.yaml on the Supervisor.
D. Upload the Service Definition to vCenter Server via Workload Management > Services > Manage > Add New Service . This registers the service version globally in vCenter.

Question#3

A VKS Administrator needs to scale out a production Tanzu Kubernetes Grid (TKG) cluster named prod-cluster-01 to handle increased load. The goal is to increase the number of worker nodes from 3 to 5.
Review the following YAML snippet of the cluster definition:
apiVersion: run.tanzu.vmware.com/v1alpha3
kind: TanzuKubernetesCluster
metadata:
name: prod-cluster-01
namespace: production
spec:
topology:
controlPlane:
replicas:
3
vmClass:
guaranteed-medium
storageClass: gold-policy
workers:
replicas:
3
vmClass:
best-effort-large
storageClass: silver-policy
Which specific modification to the YAML file or kubectl command will achieve the scaling requirement?

A. Delete the cluster and recreate it with the new worker count.
B. Run the command kubectl scale --replicas=5 tanzukubernetescluster/prod-cluster-01.
C. Edit the YAML to set spec.topology.controlPlane.replicas: 5 and apply the change.
D. Edit the YAML to set spec.topology.workers.replicas: 5 and apply the change using kubectl apply -f cluster.yaml.

Question#4

A Cloud Administrator initiates a Supervisor upgrade. The process hangs at 55% for an extended period.
The administrator checks the vCenter events and sees:
Event: Supervisor Upgrade Stalled
Detail: Waiting for Control Plane VM 'Supervisor-Control-Plane-VM-02' to power on.
Error: The operation failed due to a file lock on the datastore '[vsanDatastore]'.
Further investigation reveals that a backup job from a third-party tool is currently running on the old Control Plane VMs, holding a lock on the VM files.
What is the correct remediation to allow the upgrade to proceed? (Choose 2.)

A. Cancel the backup job to release the file locks.
B. The upgrade process will automatically retry once the locks are released; no manual intervention is strictly required if the backup finishes within the timeout window, but cancelling is the immediate fix.
C. Restart the vCenter Server service.
D. Migrate the Supervisor to a different datastore during the upgrade.
E. Manually delete the 'Supervisor-Control-Plane-VM-02' from disk.

Question#5

A developer is unable to log in to a specific TKG cluster using the command kubectl vsphere login. They receive an "Unauthorized" error.
The Security Analyst reviews the role bindings in the target namespace dev-team-1:
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: dev-read-access
namespace: dev-team-1
subjects:
- kind: User
name: sso:[email protected]
apiGroup:
rbac.authorization.k8s.io
roleRef:
kind: ClusterRole
name:
psp:vmware-system-privileged
apiGroup:
rbac.authorization.k8s.io
The analyst confirms the user is valid in Active Directory.
What is the misconfiguration in the RoleBinding preventing successful interaction/authorization?

A. The binding is in the wrong namespace.
B. The roleRef is pointing to a Pod Security Policy (PSP) role, which grants pod execution permissions but does not grant the basic get, list, or watch permissions required to view resources or authenticate successfully to the API context.
C. kubectl vsphere login does not support Active Directory users.
D. The kind must be Group, not User.
E. The name field in subjects is using the prefix sso:, but for vCenter SSO backed users, the Supervisor typically expects the format [email protected] (UPN) without a manual prefix, or the prefix depends on the specific claim mapping, but sso: is generally incorrect for standard AD integration.

Exam Code: 3V0-24.25Q & A: 300 Q&AsUpdated:  2025-12-17

 Get All 3V0-24.25 Q&As