3V0-13.26 Exam Guide
This 3V0-13.26 exam focuses on practical knowledge and exam application scenarios related to the subject area. It evaluates your ability to understand core concepts, apply best practices, and make informed decisions in realistic situations rather than relying solely on memorization.
This page provides a structured exam guide, including exam focus areas, skills measured, preparation recommendations, and practice questions with explanations to support effective learning.
Exam Overview
The 3V0-13.26 exam typically emphasizes how concepts are used in professional environments, testing both theoretical understanding and practical problem-solving skills.
Skills Measured
- Understanding of core concepts and terminology
- Ability to apply knowledge to practical scenarios
- Analysis and evaluation of solution options
- Identification of best practices and common use cases
Preparation Tips
Successful candidates combine conceptual understanding with hands-on practice. Reviewing measured skills and working through scenario-based questions is strongly recommended.
Practice Questions for 3V0-13.26 Exam
The following practice questions are designed to reinforce key 3V0-13.26 exam concepts and reflect common scenario-based decision points tested in the certification.
Question#1
A VKS (Tanzu Kubernetes) guest cluster is experiencing high API latency. You determine that the Control Plane nodes of the guest cluster are undersized (currently using best-effort-small VM classes) and need more CPU and RAM.
How do you properly scale up the Control Plane nodes for this running VKS cluster?
A. Power off the Control Plane VMs in the vSphere Client, edit their settings to add CPU and RAM, and power them back on.
B. Modify the TanzuKubernetesCluster (TKC) YAML manifest to change the controlPlane.vmClass property to a larger class (e.g., best-effort-large ), and apply the manifest using kubectl against the Supervisor AP
C. Use VCF Operations to execute a "Right-Size VM" action on the Control Plane VMs.
D. Delete the VKS cluster and redeploy it from scratch with the new VM class.
Explanation:
VKS clusters are managed declaratively via the Cluster API on the Supervisor. You must never manually modify the guest cluster VMs directly in vCenter (Option A or C), as the Cluster API controller will detect the drift and overwrite your changes or cause split-brain issues. The correct administrative procedure is to edit the cluster's declarative YAML file (changing the vmClass ) and apply it. The Supervisor will automatically perform a rolling upgrade, deploying new, larger control plane nodes and gracefully draining/removing the old ones.
Question#2
You are enabling Workload Management (Supervisor) on a vSphere cluster within a VCF Workload Domain. The configuration process runs for several minutes but eventually fails at the "Configuring NSX for Supervisor" stage. You have verified that the NSX Edge cluster is healthy, the Tier-0 gateway is active, and BGP routing is established.
Which specific network misconfiguration is the most common cause of this provisioning failure?
A. The Workload Network MTU is set to 1500 instead of the required 9000.
B. The starting IP address in the configured Ingress CIDR overlaps with the Egress CID
C. DRS is set to "Partially Automated" on the vSphere cluster instead of "Manual".
D. The NSX Manager machine SSL certificate was not manually imported into the vCenter Trusted Root store.
Explanation:
When configuring the Supervisor cluster network via NSX, you must define specific subnets for Ingress (load balancers) and Egress (SNAT for pod outbound traffic). A strict requirement is that the Ingress CIDR, Egress CIDR, and Pod/Service CIDRs must be completely non-overlapping. If the Ingress and Egress IP ranges overlap, the NSX configuration task will fail during the Supervisor provisioning phase. (Note: DRS must be Fully Automated, not Partially Automated or Manual).
Question#4
A developer attempts to deploy a legacy monitoring DaemonSet to a vSphere 8 VKS guest cluster. The deployment fails, and the ReplicaSet generates an event: Error creating: pods "monitor-agent-" is forbidden: violates PodSecurity "baseline": privileged (container "agent" must not set securityContext.privileged=true) .
The organization has transitioned away from the deprecated PodSecurityPolicies (PSP).
How should the cluster administrator resolve this deployment blockage using the modern vSphere 8 /Kubernetes 1.24+ security architecture?
A. Create a new PodSecurityPolicy (PSP) that allows privileged escalation and bind it to the developer's ServiceAccount.
B. Apply specific Pod Security Admission (PSA) labels (e.g., pod-security.kubernetes.io/enforce: privileged ) to the target namespace where the DaemonSet is being deployed.
C. Add the developer to the vCenter Administrators SSO group.
D. Disable the NSX Distributed Firewall for the worker node VMs.
Explanation:
Starting with Kubernetes 1.24 (and strongly enforced in vSphere 8 VKS environments), PodSecurityPolicies (PSP) are deprecated and replaced by Pod Security Admissions (PSA). PSA operates at the namespace level using labels. By default, VKS namespaces may enforce a "baseline" or "restricted" profile, which blocks privileged containers. To allow a privileged DaemonSet to run without completely disabling security, the administrator must label the specific namespace to enforce the "privileged" PSA profile, explicitly granting permission for privileged pods to execute within that boundary.
3V0-13.26 VCF Support - Mock Exam Practice Set 18
Phase 4: NSX Networking & Security
Difficulty: Level 1 & 2 (Tool Identification & Conceptual Routing)
Question#5
A virtual machine (VM-DB-02) fails to power on after an unexpected storage outage. The vCenter Server throws the error: "Cannot open the disk '/vmfs/volumes/Datastore1/VM-DB-02/VM-DB-02-000002.vmdk' or one of the snapshot disks it depends on.
The parent virtual disk has been modified since the child was created." What is the technical root cause of this specific error, and how is it typically resolved?
A. The VM's swap file ( .vswp ) is locked by another host; the resolution is to delete the .vswp file and power on the V
B. The VM's Content ID (CID) chain in the snapshot descriptor files is broken or mismatched; the resolution requires manually editing the .vmdk descriptor text files to realign the parent/child CID hexadecimal values.
C. The snapshot delta file has exceeded the maximum supported size; the resolution is to use Storage vMotion to consolidate the disks to a larger datastore.
D. The ESXi host's hostd agent cannot read the VMFS metadata; the resolution is to run voma to repair the datastore corruption.
Explanation:
VMware virtual machine snapshots rely on a strict chain of trust using a Content ID (CID). Each child snapshot descriptor file explicitly references the CID of its parent. If a parent disk is somehow booted directly, modified, or corrupted, its CID changes. When vSphere attempts to power on the VM using the child snapshot, the CID mismatch is detected, preventing data corruption by blocking the boot process. The fix for a CID mismatch involves manually tracing and correcting the hex values in the snapshot descriptor text files via the ESXi CLI.
Disclaimer
This page is for educational and exam preparation reference only. It is not affiliated with Broadcom, VCAP-VCF Support, or the official exam provider. Candidates should refer to official documentation and training for authoritative information.
