An administrator is integrating Avi Load Balancer with a Supervisor Cluster that uses NSX VPC networking. The Avi controller is deployed, but the administrator is unsure which credentials to provide during the Supervisor creation wizard. The organization has a strict security policy that requires the use of a dedicated service account with minimal privileges. What is the correct approach?

Use the Avi admin account to ensure full functionality

Skip Avi integration and use NSX VPC's built-in load balancer

Create a service account in Avi with the required permissions and use it in the wizard

Use the vCenter service account for Avi integration

An administrator notices that a vSphere Namespace is running low on CPU and memory resources. The namespace has a resource limit set, but the team needs to temporarily increase capacity for a planned batch job. What is the correct way to adjust the namespace's resource limits?

Increase the limits on the underlying ESXi hosts

Edit the namespace's resource limits in the vSphere Client

Create a new namespace and migrate the workloads

Delete the namespace and recreate it with higher limits

When configuring vSphere Zones, which of the following is a key configuration step?

Creating a new storage policy for the zone

Creating a new vCenter Server for the zone

Assigning ESXi hosts to the zone

Configuring a new NSX VPC for the zone

When creating a Supervisor Cluster with a vSphere Distributed Switch (vDS) for networking, which of the following must be configured on the vDS before the cluster creation?

An NSX Segment for the Supervisor Cluster

A distributed portgroup for the Supervisor Cluster

An NSX VPC for the Supervisor Cluster

A VLAN for the Supervisor Cluster

An organization no longer needs the external-dns add-on service on their Supervisor Cluster. The administrator wants to remove it without affecting other workloads. What is the correct procedure?

Use the Supervisor Cluster's Services tab to uninstall external-dns

Remove the external-dns namespace from the Supervisor Cluster

Disable the external-dns service in the vSphere Namespace settings

Delete the external-dns pods from the Supervisor Cluster's Kubernetes API

VMwareVCAP-VCF VKS (3V0-24.25)

Domain 4Objective 1

Configure Supervisor Infrastructure VCAP-VCF-VKS Practice Questions (Page 2)

Part of the Install, Configure, Administrate the VMware Solution domain, which makes up ~25% of our current practice bank.

39questions here

8free pages

12concepts

Questions 6–10

6expert · hard
An administrator is integrating Avi Load Balancer with a Supervisor Cluster that uses NSX VPC networking. The Avi controller is deployed, but the administrator is unsure which credentials to provide during the Supervisor creation wizard. The organization has a strict security policy that requires the use of a dedicated service account with minimal privileges. What is the correct approach?
Select an answer first
7application · easy
An administrator notices that a vSphere Namespace is running low on CPU and memory resources. The namespace has a resource limit set, but the team needs to temporarily increase capacity for a planned batch job. What is the correct way to adjust the namespace's resource limits?
Select an answer first
8foundation · easy
When configuring vSphere Zones, which of the following is a key configuration step?
Select an answer first
9foundation · easy
When creating a Supervisor Cluster with a vSphere Distributed Switch (vDS) for networking, which of the following must be configured on the vDS before the cluster creation?
Select an answer first
10application · easy
An organization no longer needs the external-dns add-on service on their Supervisor Cluster. The administrator wants to remove it without affecting other workloads. What is the correct procedure?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to VCAP-VCF-VKS

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by VMware. “VCAP-VCF-VKS” is a trademark of its owner, used for identification only.