3V0-11.26 Advanced VMware Cloud Foundation 9.0 Administrator exam badge

VMware

Advanced VMware Cloud Foundation 9.0 Administrator (3V0-11.26) practice questions

★★★★★★ 4.6 53 reviews — aggregated from community votes by visitors who practiced this bank

Questions
49
Exam length
135 min
Passing score
300
  • Instant feedback per question
  • Explanation for every option
  • Free, no signup

Exam overview 3V0-11.26

Rotating a certificate across vCenter, NSX and the fleet management plane without leaving configuration drift behind is the kind of day-2 task 3V0-11.26, the Advanced VMware Cloud Foundation 9.0 Administrator exam, is built around. Passing earns the VMware Certified Advanced Professional – VMware Cloud Foundation Administrator credential (VCAP-VCF Administrator), delivered by Broadcom through Pearson VUE. The paper carries 60 items in a 135-minute appointment and needs 300 on the 100-500 scaled score, mixing multiple choice and selection with matching, build-list, drag-and-drop, point-and-click and hot-area formats.

The guide describes a minimally acceptable candidate as someone who can manage, maintain and scale a multi-region or multi-organization VCF private cloud — not somebody who can simply name the components. A beta candidate who sat the paper found the questions clear and direct and finished in about an hour, with point-and-click items standing out; that matches a blueprint rewarding people who have actually operated the platform rather than memorised product descriptions.

Its structure is unusual. Sections 1, 2, 3 and 5 carry no testable objectives at all, so every mark comes from Section 4, Install, Configure and Administrate — 60 objectives numbered 4.1 through 4.60. They split into vSAN and compute work inside the workload domain (clusters, stretched clusters, cross-cluster capacity sharing, storage policies, encryption), the Provider and Organization model in VCF Automation including the Provider Consumption Organization, Supervisor and VKS add-on services such as Harbor and external-dns, VCF Operations forecasting and configuration drift, and a substantial NSX block covering Federation, Edge clusters, Tier-0 and Tier-1 gateways, VRF, segments, DHCP and NAT.

The practice bank follows that operational split. Items place you inside a workload domain upgrade, an Organization quota decision or a syslog and backup task, and each explanation works through why one action satisfies the requirement while the alternatives do not. A timed run gets you used to point-and-click and build-list formats alongside the underlying decisions, so revision lands on the objectives that actually carry marks.

Sample questions 5 of 49 shown

  1. Q1
    A vSAN ESA cluster in a VI workload domain has six ESX hosts, each acting as its own fault domain. A new database VM must stay available through two simultaneous host failures, and the storage team wants the lowest capacity overhead that meets that requirement. Which vSAN storage policy settings should the administrator create and assign to the VM?
    1. Failure tolerance method RAID-1 (mirroring), Failures to tolerate 2
    2. Failure tolerance method RAID-5/6, Failures to tolerate 1
    3. Failure tolerance method RAID-5/6, Failures to tolerate 3
    4. Failure tolerance method RAID-5/6, Failures to tolerate 2
    The requirement is two simultaneous host failures, which rules out FTT=1 (option B). FTT=3 with RAID-5/6 (option C) would require more fault domains than the six hosts available — RAID-6 with FTT=3 needs at least seven hosts, so the policy could never be compliant. Between the two policies that do satisfy FTT=2, RAID-1 mirroring consumes roughly 3x raw capacity (two full mirrors plus the source), whereas RAID-6 erasure coding uses approximately 1.5x. Since RAID-5/6 with FTT=2 is satisfied by exactly six hosts in six fault domains, it is the lowest-overhead policy that still tolerates two failures.
  2. Q2
    An administrator is tasked with deploying a VMware Cloud Foundation (VCF) Workload Domain that meets the following requirements:
    • vSAN ESA as principal storage
    • RAID 6 with FTT=2
    • Support for Storage Traffic Separation
    • Cluster must support protection against an entire rack failure
    The administrator is provided the following hardware to perform the task: Four ESX hosts, each host contains:
    • 24 CPUs
    • 96 GB memory
    • Two 25GbE network NICs
    • 12 NVMe devices 4TB each, connected to a single SATA/SAS/NVMe Tri-mode controller
    What five changes must the administrator make to the hardware before deploying the new Workload Domain? (Choose five.)
    1. Increase the memory on each host to a minimum 128 GB.
    2. Deploy the vSAN nodes across 4 server racks and enable fault domains in the vSphere client under "Hosts and Clusters".
    3. Increase the Tri-mode controller quantity on each host to two, with six NVMe devices connected to each.
    4. Replace the network NICs on each host to a minimum of two 100 GbE network NICs.
    5. Deploy the vSAN nodes across 6 server racks and enable fault domains in the vSphere client under "Hosts and Clusters".
    6. Increase the ESX host count to a minimum of six.
    Each requirement maps to one hardware change. RAID-6 with FTT=2 in vSAN ESA is only supported from six hosts upward, and "protect against an entire rack failure" means every host must sit in its own fault domain, so the host count must rise from four to six (F) and the six hosts must be spread across six racks with fault domains enabled (E) — four racks cannot host six independent fault domains. Storage Traffic Separation requires dedicated physical uplinks for vSAN traffic, which two 25GbE NICs cannot provide; four 25GbE NICs give separate vSAN and non-vSAN paths (I). A single tri-mode controller shared by twelve NVMe devices is not a supported ESA configuration for that drive count, so a dedicated NVMe controller is required (H). 96 GB of memory is below the 128 GB minimum for a VCF workload domain host (A). Upgrading to 100 GbE NICs (D) or splitting drives across two tri-mode controllers (C) adds cost without addressing any stated requirement.
  3. Q3
    An administrator is planning to set up centralized network connectivity for a workload domain, deploying a new NSX Edge cluster on vSphere cluster WLD-02. DNS records for the Edge nodes exist, the Edge management port group can reach NSX Manager, and the cluster has capacity for two Edge nodes. The Edge TEPs will reuse the host TEP VLAN. The ESX hosts in WLD-02 use a vSphere Distributed Switch but have never been configured for NSX. Which prerequisite must the administrator complete before running the Edge cluster workflow?
    1. Attach a transport node profile to the WLD-02 cluster, so that its ESX hosts are prepared for NSX.
    2. Create the Tier-0 gateway in NSX Manager first, so that the workflow can place the new Edge nodes under that existing gateway.
    3. Allocate a separate Edge TEP VLAN, since Edge TEPs cannot share the VLAN that the host TEPs use.
    4. Deploy one Edge node manually, then let the workflow clone it to build out the rest of the cluster.
    Edge nodes are deployed as NSX transport nodes and must land on hosts that are already prepared for NSX. Until the WLD-02 cluster has a transport node profile applied, its hosts are not NSX transport nodes, so the Edge deployment has no prepared compute on which to place the Edge VMs. The Tier-0 gateway (B) is created afterwards and consumed by the Edge cluster, not before it. Edge TEPs can share a VLAN with host TEPs as long as the IP ranges do not overlap, so a separate VLAN (C) is not a hard prerequisite. Edge cluster members are deployed by the workflow itself; pre-deploying a node manually (D) is not part of the supported flow.
  4. Q4
    In a stretched vSAN cluster or 2-node topology, an administrator wants to separate the vSAN witness traffic from the high-bandwidth inter-site vSAN data replication traffic to optimize WAN bandwidth. Which operational configuration enables witness traffic to traverse a dedicated management/WAN network rather than the low-latency inter-site vSAN storage network?
    1. Enable jumbo frames on the physical switch port connecting the witness host.
    2. Configure Witness Traffic Separation by tagging a dedicated VMkernel adapter with the witness traffic type using esxcli vsan network ip add -i vmkX -T witness.
    3. Deploy a redundant NSX Tier-0 Gateway dedicated exclusively to the witness host.
    4. Change the vSAN cluster disk format to version 1.0.
    Witness Traffic Separation (WTS) lets the witness host be reached over a routed, higher-latency path — typically the management network — while bulk replication stays on the low-latency inter-site link. It is configured per host by adding the witness traffic type to the VMkernel adapter that can reach the witness, which is exactly what the -T witness flag does. Jumbo frames (A) only change MTU and do not move traffic to a different interface. vSAN VMkernel traffic is handled in the vSphere kernel and never traverses an NSX Tier-0 gateway (C). Disk format (D) affects on-disk layout only.
  5. Q5
    An administrator installs two certified NVMe SSDs into an existing ESXi host in a vSAN Express Storage Architecture (ESA) cluster. The cluster has "Automatic disk claiming" disabled. How should the administrator claim these new drives into the host's vSAN ESA Storage Pool using the vSphere Client?
    1. Format the drives as VMFS6 datastores and click "Mount as vSAN Extent".
    2. Navigate to Host > Configure > vSAN > Disk Management, select the host, click "Claim Unused Disks", and add the drives to the Storage Pool.
    3. Create a new Disk Group on the host, assigning one NVMe drive as Tier-1 cache and the other as capacity.
    4. Run esxcli storage core device set --state offline on both drives and reboot the host.
    vSAN ESA replaced disk groups with a single-tier storage pool per host, so newly installed NVMe devices are added with the "Claim Unused Disks" workflow under Host > Configure > vSAN > Disk Management, which is the only supported path when automatic claiming is turned off. Formatting the devices as VMFS (A) makes them ineligible, because vSAN requires raw block devices. Disk groups with cache and capacity tiers belong to vSAN OSA and no longer exist in ESA (C). Marking devices offline (D) removes them from the hypervisor's usable device list entirely.

Answer all 49 questions with instant feedback →

Reader reviews 53 ratings

4.6 ★★★★★★ Based on 53 ratings
  • I have tried many VMware practice tests and this 3V0-11.26 bank is by far the most accurate and well-organized.

    ★★★★★★ Kevin N.

  • Only used this for a week before my 3V0-11.26 exam and it was enough. Questions are very close to the real deal.

    ★★★★★★ Katherine W.

  • Comparing this with other VMware practice tests, this one feels the most like the real 3V0-11.26 exam.

    ★★★★★★ Mia R.

  • Covered all five domains of the 3V0-11.26 exam thoroughly. I especially appreciated the detailed breakdowns for the tricky questions.

    ★★★★★★ Natalie R.

  • Got the 3V0-11.26 certification after three weeks of self-study with this question bank. Very happy with the purchase.

    ★★★★★★ Victoria K.

  • Honestly, I wouldn’t have passed 3V0-11.26 without these. The explanations actually teach you instead of just giving the answer.

    ★★★★★★ Jordan P.

Log in to rate this exam and leave a review.

Frequently asked questions

Which blueprint section actually counts for 3V0-11.26?

Section 4 alone. Sections 1, 2, 3 and 5 carry no testable objectives, so all 60 objectives sit under Install, Configure and Administrate. Preparation is therefore practical: cluster operations, Automation organisations and NSX day-2 tasks, with almost nothing framed as design theory. Reading the objective numbers before booking helps you judge whether the paper matches your day job.

How deep does the VKS content go on the Administrator paper?

Deep enough to be operationally useful, not Kubernetes-specialist deep. You need to create Supervisors against NSX VPC, NSX Segment or vDS, install add-ons such as Harbor and external-dns, roll VKS cluster updates and manage package repositories. Know which service does what and where it is managed — the exam will not ask you to debug a container network.

Why does VCF Automation feel unfamiliar to vSphere administrators?

Because VCF 9 replaced the old console with a Provider Management portal, Organizations, the Provider Consumption Organization and an All Apps model built on Projects, Governance Policies and VPC connectivity profiles. Identity and access control are configured at both levels. If your background is vRealize or Aria Automation, budget real study time — this is new territory, not renamed menus.

How is configuration drift tested in this exam?

As an operational symptom with a documented cause and remedy. The VCF Operations objectives pair drift monitoring with What-If capacity forecasting, cost management, Business versus Operational Intent and rightsizing, so items give you a drift report or a capacity signal and ask what restores the intended state. Knowing where the baseline lives matters more than knowing the dashboard label.

How should a first timed attempt be paced?

Treat 60 items in 135 minutes as roughly two minutes each, but expect point-and-click and build-list items to take longer than plain multiple choice. One beta sitter finished in about an hour, so review time exists if you do not stall on one scenario. A timed practice run shows which formats slow you down before the appointment.

What do the workload-domain explanations add after a wrong answer?

They trace the dependency chain behind the correct action — why a storage policy change precedes a workload move, why a certificate update must include every node's names, why rightsizing shifts the capacity forecast. Each miss becomes an objective to revisit instead of a letter to memorise, which is what makes the question bank useful on a blueprint this operational.