3V0-24.25リアル試験問題解答は更新された[2026年08月18日]
お手軽に合格させる 最新VMware 3V0-24.25問題集には85問があります
VMware 3V0-24.25 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 34
An administrator is maintaining several Kubernetes clusters deployed through a Supervisor Namespace in a vSphere Kubernetes Service environment. One of the micro-services (a containerized API gateway) is failing intermittently after a recent configuration update. The pod is entering aCrashLoopBackOffstate. The administrator needs to collect detailed runtime information directly from the pod, including both thestandard output (STDOUT)andstandard error (STDERR)streams, to analyze the application's behavior before the crash.
Which command produces the required output?
- A. kubectl get all
- B. kubectl describe
- C. kubectl logs
- D. kubectl events
正解：C
解説：
When a container repeatedly crashes (CrashLoopBackOff), the most direct way to capture what the application emitted right before termination is to retrieve the container logs. In Kubernetes, application output written toSTDOUTandSTDERRis captured by the container runtime logging mechanism and exposed through the Kubernetes API for retrieval. The kubectl logs command is designed specifically for this purpose: it fetches the log stream for a pod (and container, if multiple exist), allowing administrators to review the runtime messages that typically explain configuration errors, missing dependencies, failed probes, authentication problems, or other causes of the crash loop. This aligns with VMware operational guidance that uses kubectl to retrieve pod-level operational information and logs as part of troubleshooting Kubernetes functionality running on vSphere.
質問 # 35
A Cloud Administrator is designing a multi-tenant vSphere with Tanzu environment for two distinct business units: Finance and Engineering.
Requirements:
1. Finance requires strict egress filtering. All outbound traffic must originate from a predictable, static IP address range to pass through a legacy firewall.
2. Engineering requires high-volume ingress. They plan to deploy 50+ unique web services, each needing public access, but the available Floating IP Pool for the Load Balancer is limited to 10 IPs.
3. Isolation: Traffic between Finance and Engineering must be blocked by default.
Review the proposed design configuration:
# Namespace: finance-ns
Network: NSX (NAT Mode)
Egress: Configured with SNAT
# Namespace: engineering-ns
Network: NSX (NAT Mode)
Services: Developers instructed to use 'type: LoadBalancer' for all apps.
Which aspects of this design need correction or validation to meet the requirements? (Select all that apply.)
- A. The Finance design is valid; enabling NSX NAT Mode with SNAT ensures that all pod traffic leaves the namespace using a deterministic "Egress IP" assigned to the T1 Gateway, which satisfies the firewall requirement.
- B. The Engineering namespace needs a separate Supervisor Cluster to support that many services.
- C. The Isolation requirement is automatically met because NSX-backed Namespaces are deployed with distinct Tier-1 Gateways and a default "Deny All" Distributed Firewall policy between them is often required (or naturally isolated by T1 routing rules depending on T0 config). Self-correction: VKS Namespaces are isolated by default in terms of not sharing T1s, but traffic routing depends on T0.
However, the question asks about valid/invalid aspects. A DFW rule or Network Policy is the standard way to enforce "Blocked by default" between namespaces. - D. The Finance namespace should be configured in "Routed Mode" (No-NAT) to simplify the firewall rules.
- E. The Engineering design is flawed; using type: LoadBalancer for 50+ services will exhaust the 10-IP pool. An Ingress Controller (L7) architecture must be mandated to multiplex these services behind a single VIP.
正解：A、E
質問 # 36
An administrator is tasked with enabling a Supervisor cluster in VMware Cloud Foundation (VCF).
Arrange the steps below In the correct order to complete the process of enabling a Supervisor In the environment.
正解：
解説：
Explanation:
Answer (Correct Order):
* Select the target cluster in the workload domain.
* Open Workload Management and select "Enable Supervisor Cluster".
* Choose cluster networking mode and stack.
* Configure the control plane compute, networking, and storage policies.
* Configure the workload network configurations.
* Review, Validate, and Deploy Supervisor.
You start by selecting theexact vSphere cluster(in the workload domain) that will host the Supervisor, because Supervisor enablement is performedagainst a specific cluster. From there you launch the enablement workflow inWorkload Management("Enable Supervisor Cluster"). Early in the wizard you must decide thenetworking mode(for example, VDS-based vs NSX-backed) and theIP stack, because those choices drive the remaining configuration screens and what inputs are required. Next you define theSupervisor control plane settings-compute sizing and the core policies the Supervisor will use (including storage policy selections and related defaults). After the control plane foundation is defined, you configure theworkload networkingused by namespaces and Kubernetes workloads (IP ranges, routing/LB integration depending on the selected mode). Finally, youreview/validateall inputs anddeployso the platform can create and configure the Supervisor control plane and supporting components.
質問 # 37
A VI Administrator needs to configure a new vSphere Namespace called dev-team-a to ensure it uses a specific storage profile for persistent volumes.
Review the following configuration view:
Namespace: dev-team-a
Status: Active
Description: Development Team A Environment
[Resource Limits]
CPU: Unlimited
Memory: Unlimited
Storage: [Add Storage Policy...]
Which action must the administrator take to allow Kubernetes workloads in this namespace to provision persistent volumes using the gold-storage policy?
- A. Edit the Namespace in the vSphere Client and add the gold-storage policy to the "Storage Policies" card.
- B. Create a new Storage Class in Kubernetes referencing gold-storage and apply it to the namespace via kubectl.
- C. Tag the datastores associated with gold-storage with the tag namespace:dev-team-a.
- D. Configure the gold-storage policy on the Supervisor Cluster object directly.
正解：A
質問 # 38
Refer to the exhibit in the following StorageClass manifest, which field is used to specify the Volume Plugin driver used for the underlying storage array?
YAML
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: standard
provisioner: kubernetes.io/aws-ebs
parameters:
type: gp2
reclaimPolicy: Retain
allowVolumeExpansion: true
mountOptions:
- debug
volumeBindingMode: Immediate
- A. name
- B. provisioner
- C. parameters
- D. type
正解：B
解説：
In a Kubernetes-based architecture like the vSphere Kubernetes Service (VKS) within VMware Cloud Foundation (VCF) 9.0, a StorageClass manifest serves as the definition for dynamic volume provisioning. The provisioner field is the mandatory attribute that determines which specific volume plugin or driver is invoked to create the underlying storage resource. In the provided exhibit, the string provisioner: kubernetes.io/aws- ebs specifies that the AWS Elastic Block Store (EBS) driver is the orchestrator for the lifecycle of the volumes associated with this class.
In a standard on-premises VCF 9.0 deployment, the provisioner field typically points to csi.vsphere.vmware.
com, identifying the vSphere Container Storage Interface (CSI) driver. This driver acts as the translator between Kubernetes PersistentVolumeClaims (PVCs) and vSphere's Cloud Native Storage (CNS) layer. The other fields in the manifest serve supporting roles: name provides a reference for the StorageClass, parameters (such as type: gp2) pass configuration-specific details to the driver, and reclaimPolicy determines what happens to the data once a claim is deleted. However, only the provisioner field defines the " who " of the operation-the actual software driver responsible for communicating with the storage array or cloud provider to provision the physical or virtual disk. Understanding this distinction is critical for administrators managing hybrid-cloud workloads where different provisioners are used across diverse infrastructure backends.
質問 # 39
An administrator runs several critical workloads on vSphere Kubernetes Service (VKS). An audit identified an outdated container image with a known CVE that exposed internal APIs to unauthorized access. To mitigate this risk and enhance image security, the administrator enabled Harbor as a Supervisor Service.
Which two Harbor registry capabilities help the organization prevent a recurrence of this type of security incident? (Choose two.)
- A. Vulnerability scanning
- B. Automatic image update
- C. Image signing
- D. Automatic image validation
- E. Deploy both container and virtual machine images
正解：A、C
解説：
Harbor reduces the risk of running vulnerable or tampered images primarily throughvulnerability scanningandimage signing.Vulnerability scanning (E)detects known CVEs in image layers (OS packages and application dependencies, depending on the scanner configuration). This allows teams to identify-and gate the use of-images that contain high/critical vulnerabilities before those images are deployed to Kubernetes clusters. Enforcing scanning as part of the image promotion process helps prevent outdated images with known CVEs from being pulled into production.Image signing (A)provides integrity and provenance controls by enabling consumers to verify that an image was produced and approved by a trusted publisher and has not been altered. When combined with admission controls/policies (for example, only allowing signed images from specific projects), signing helps block unauthorized or unapproved images from being deployed, which is critical when the incident involves exposed internal APIs and supply-chain risk.
The other choices do not directly prevent recurrence:automatic image update (B)is not a core Harbor registry control,deploy both container and VM images (C)is a content capability rather than a security control, andautomatic image validation (D)is not a standard Harbor registry capability distinct from signing/scanning.
質問 # 40
A Platform Engineer is troubleshooting a failed installation of the external-dns Supervisor Service.
The service status in the vSphere Client is "Error".
The engineer retrieves the logs from the service's pod and sees the following:
time="2023-11-22T10:00:00Z" level=error msg="rfc2136: failed to send TSIG authenticated message:
dns: failed to pack message: dns: bad secret"
time="2023-11-22T10:00:05Z" level=error msg="source: failed to list vSphere resources: Unauthorized" The configuration YAML provided during installation included the following snippet for the DNS provider:
spec:
provider: rfc2136
rfc2136:
host: 192.168.10.5
zone: corp.local
tsigSecretName: external-dns-tsig-secret
What is the most likely cause of the failure? (Choose 2.)
- A. The Kubernetes Secret external-dns-tsig-secret referenced in the config does not exist in the namespace where the service is being deployed, or it contains an incorrect TSIG key.
- B. The Supervisor Cluster does not have a route to the DNS server 192.168.10.5.
- C. The external-dns service account does not have the necessary RBAC permissions on the Supervisor to watch/list Service and Ingress resources.
- D. The storage policy for the service is full.
- E. The rfc2136 provider is not supported by vSphere with Tanzu.
正解：A、C
質問 # 41
A Platform Engineer observes that a TKG cluster upgrade has failed with the status Condition:
Incompatible. The error message indicates that the VirtualMachineClass referenced in the cluster YAML (guaranteed-large-v1) is no longer available in the namespace.
The administrator realizes that the guaranteed-large-v1 class was recently removed from the Namespace configuration in favor of guaranteed-large-v2.
How should the engineer recover the cluster and complete the upgrade? (Select all that apply.)
- A. Once the manifest is updated to guaranteed-large-v2, the Supervisor will trigger a rolling update to replace the nodes with the new class (and new version if specified).
- B. Add the guaranteed-large-v1 class back to the Namespace in the vSphere Client to satisfy the current state requirements, allowing the controller to reconcile the current state before moving to the new state.
- C. The cluster must be deleted and recreated because the VM Class is immutable once provisioned.
- D. Edit the TanzuKubernetesCluster manifest to update the vmClass field to guaranteed-large-v2 for the node pools.
- E. Manually rename the VM Class in vCenter from guaranteed-large-v2 to guaranteed-large-v1.
正解：A、B、D
質問 # 42
A Cloud Administrator is troubleshooting a failed Tanzu Kubernetes Grid (TKG) cluster provisioning.
The cluster creation task in the vSphere Client indicates a failure, but the error message is generic. The administrator decides to investigate the specific controller logs on the Supervisor.
Which specific Kubernetes object events should the administrator inspect using kubectl to find the most detailed error messages regarding the infrastructure provisioning (VM cloning, networking) of the TKG cluster nodes?
- A. kubectl get events --namespace kube-system
- B. kubectl logs deployment/wcp-auth-proxy
- C. kubectl describe tanzukubernetescluster
- D. kubectl describe virtualmachine
正解：D
質問 # 43
The DevOps Engineer was tasked to deploy a new application on a local cluster. When the application was deployed in the Namespace, it was decided that a newer version of Kubernetes was required. The DevOps Engineer requested the vSphere Admin to upgrade their Kubernetes version. The vSphere Admin checked compatibility between the Supervisor and all running VKS clusters, and then successfully upgraded vSphere Supervisor to the latest version. The DevOps Engineer could not get the application to work. What caused the application to fail?
- A. The vSphere Admin did everything correctly and the DevOps Engineer is deploying the application wrong.
- B. The vSphere Admin pulled down the wrong version of the Supervisor.
- C. The vSphere Admin failed to complete all the pre-checks before the upgrade.
- D. The vSphere Admin upgraded the Supervisor Control Plane.
正解：D
解説：
The failure in this scenario stems from a misunderstanding of the decoupled lifecycle architecture within VMware Cloud Foundation (VCF) 9.0. In a vSphere Kubernetes Service (VKS) environment, the vSphere Supervisor (the management plane) and the Tanzu Kubernetes clusters (the workload plane) are upgraded independently. When the administrator upgraded the vSphere Supervisor to the latest version, they effectively updated the control plane that manages the SDDC resources and Kubernetes APIs, but this action did not automatically upgrade the Kubernetes version of the individual VKS workload clusters where the application was running.
Because the DevOps engineer ' s application required a specific, newer version of Kubernetes, the application remained incompatible because the workload cluster ' s distribution version remained unchanged. To resolve this, after the Supervisor is upgraded, the administrator must explicitly trigger an upgrade of the VKS cluster by updating the tkr.tanzu.vmware.com (Tanzu Kubernetes Release) version in the cluster ' s YAML specification. This triggers the Cluster API (CAPI) controllers to perform a rolling update of the worker and control plane nodes. In VCF 9.0, this separation is a feature designed to prevent global downtime; however, it requires administrators to perform a two-step process: first, the Supervisor Control Plane upgrade (Option D), followed by the individual workload cluster upgrades. Without the second step, the Kubernetes environment seen by the application remains at the legacy version.
質問 # 44
A VMware vSphere Kubernetes Service (VKS) cluster exposes three layers of controllers to manage its lifecycle. Which set identifies these layers?
- A. Virtual Machine Service, Cluster API, and Cloud Provider Plug-in.
- B. API Gateway, StatefulSet Controller, Ingress Controller.
- C. Cluster API, Node Problem Detector, CNI Plug-in.
- D. Virtual Machine Service, vCenter Server Appliance, Supervisor Service.
正解：A
解説：
VCF 9.0 explicitly states: "The VKS exposes three layers of controllers to manage the lifecycle of a VKS cluster," and then enumerates those layers. The first layer is the set of components that integrate the workload cluster with Supervisor-backed resources, including aCloud Provider Plug-inthat integrates with the Supervisor and enables infrastructure integrations such as persistent volume requests being passed to the Supervisor (which is integrated with Cloud Native Storage). The second layer isCluster API, described as providing "declarative, Kubernetes-style APIs for cluster creation, configuration, and management," driven by resources that represent the cluster, the VMs making up the cluster, and cluster add-ons. The third layer is theVirtual Machine Service, which provides a declarative API for managing VMs and associated vSphere resources and is used to manage the lifecycle of the control plane and worker node VMs hosting a VKS cluster.
Therefore, optionAis the only answer that matches the three lifecycle controller layers defined in the VCF 9.0 documentation.
質問 # 45
A Platform Engineer is enabling Workload Management on a vSphere Cluster to prepare it for a new development team. The environment utilizes NSX for networking.
Review the following configuration options available in the "Enable Workload Management" wizard:
[Network Stack]
1. NSX
2. VDS
[Load Balancer]
1. NSX Load Balancer
2. HAProxy
3. Avi Load Balancer
Which specific configuration combination facilitates the deployment of vSphere Pods (native pods)?
- A. Network Stack: NSX | Load Balancer: NSX Load Balancer
- B. Network Stack: VDS | Load Balancer: Avi Load Balancer
- C. Network Stack: VDS | Load Balancer: HAProxy
- D. Network Stack: NSX | Load Balancer: Avi Load Balancer
正解：A
質問 # 46
Which statement correctly describes the architectural role of the vSphere Supervisor in a vSphere with Tanzu deployment?
- A. It is a set of three virtual machines deployed on a vSphere Cluster that act as the Kubernetes control plane, transforming the cluster into a Kubernetes node.
- B. It is a specialized virtual machine that manages the lifecycle of Tanzu Kubernetes Grid clusters but does not host workloads itself.
- C. It is a distinct vCenter Server instance dedicated solely to managing containerized workloads and namespaces.
- D. It is a cluster of ESXi hosts enabled for Workload Management, where the ESXi hosts act as worker nodes for the Supervisor Control Plane.
正解：D
質問 # 47
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. Edit the YAML to set spec.topology.workers.replicas: 5 and apply the change using kubectl apply -f cluster.yaml.
- B. Delete the cluster and recreate it with the new worker count.
- C. Run the command kubectl scale --replicas=5 tanzukubernetescluster/prod-cluster-01.
- D. Edit the YAML to set spec.topology.controlPlane.replicas: 5 and apply the change.
正解：A
質問 # 48
Which three objects or object types are within the scope of a cluster backup for VMware vSphere Kubernetes Service (VKS)? (Choose three.)
- A. Objects identified by a tag
- B. Objects identified by a label selector
- C. Application
- D. Service
- E. Namespace
- F. Cluster
正解：B、D、E
解説：
VCF 9.0 describes backing up workloads on VKS clusters usingVelero(Velero Plugin for vSphere) and shows the backup command pattern scoping backup content bynamespace(for example, velero backup create ... -- include-namespaces=my-namespace). This demonstrates thatNamespacesare a primary object type within backup scope (you choose which namespace content is captured). The same section explains that after backup execution,Kubernetes metadata is uploaded to the object store. "Kubernetes metadata" in this context includes standard namespaced resources that represent running workloads and how they are exposed, such asServices(a core Kubernetes API object used to provide stable access to pods).
In addition to namespace scoping, Velero's selection model commonly includes filtering backed-up Kubernetes objects using selectors (for example, selecting subsets of resources), which aligns with the
"objects identified by a label selector" option as an object-selection mechanism within the scope of what Velero captures from Kubernetes APIs (metadata/resources) once the namespace is targeted.
Therefore, the best match to the documented Velero workload-backup model is:Namespace,Service, andlabel- selected objectswithin the included namespace(s).
質問 # 49
An administrator is adding a kubernetes cluster to an existing namespace. Click where the administrator navigates to create the cluster.
正解：
解説：
質問 # 50
In a vSphere with Tanzu environment, what is the primary Kubernetes resource used to define the specific storage provider parameters (such as the vSphere CSI driver retention policy) required to provision a volume snapshot?
- A. StorageClass
- B. PersistentVolumeClaim
- C. VolumeSnapshotClass
- D. ResourceQuota
正解：C
質問 # 51
An administrator had deployed a Supervisor cluster on vSphere in a multi-zone-enabled environment and now wants to create a zonal vSphere Namespace so that workloads can be scheduled across zones.
Drag and drop the six actions into the correct order from Configuration Option list on the left and place them Into the Configuration Sequence on the right.
(Choose six.)
正解：
解説：
1 - Create the vSphere Namespace
2 - Assign the zones
3 - Select workload networking
4 - Assign the zonal storage policy
5 - Define resource quotas / limits
6 - Grant RBAC / permissions
質問 # 52
An administrator is adding a kubernetes cluster to an existing namespace. Click where the administrator navigates to create the cluster.
正解：
解説：
Explanation:
Kubernetes Service
When adding a Kubernetes cluster to anexisting vSphere Namespace, the workflow is initiated from within that namespace's context in the vSphere Client. The administrator first opens the target namespace (as shown in the left navigation where the namespace is selected), then uses theKubernetes Servicearea to create and manage Kubernetes clusters associated with that namespace. In the namespaceSummaryview, theKubernetes Servicetile/card provides the entry point for cluster lifecycle actions, typically via an action link such asManage(and from thereCreate Cluster). This is because the Kubernetes cluster is anamespace-scoped resourcein the Supervisor environment: it inherits namespace-level policies and configuration such as permissions/RBAC, resource limits, storage policies, and networking selections that have already been defined for that namespace. Navigating to other areas likeStorageorNetworkis used to validate or adjust prerequisites (for example, storage policy availability or network settings), but the actual "create cluster" operation is launched fromKubernetes Servicewithin the namespace to ensure the cluster is created under the correct tenant boundary and governance model.
質問 # 53
A DevOps Engineer is architecting a "Hybrid-Cloud-Native" application stack to be deployed in the finance-app namespace.
Architecture Requirements:
1. Frontend: Stateless Nginx web servers running as containers, managed by Kubernetes, scaling based on CPU.
2. Backend: A legacy Microsoft SQL Server database running on Windows Server 2019. The DBA team demands full OS access and specific storage performance policies, preventing containerization.
3. Networking: The Frontend must connect to the Backend over the internal namespace network.
Review the proposed deployment strategy:
# Frontend Manifest
apiVersion: apps/v1
kind: Deployment
metadata:
name: web-front
spec:
replicas: 3
...
# Backend Manifest
apiVersion: vmoperator.vmware.com/v1alpha1
kind: VirtualMachine
metadata:
name: sql-backend
spec:
imageName: win-2019-sql.ova
className: guaranteed-xlarge
storageClass: sql-perf-policy
networkInterfaces:
- networkName: default
Which statements correctly validate this design for vSphere with Tanzu? (Select all that apply.)
- A. Because both the Pods and the VM are in the same Namespace and the VM uses the default network, they will share the same NSX Tier-1 Gateway context (or vDS segment), enabling direct connectivity.
- B. This validly utilizes the VM Service for the SQL backend, allowing it to be provisioned as a VM (kind:
VirtualMachine) within the same namespace as the Frontend pods. - C. The Backend must be deployed as a vSphere Pod (kind: Pod) to communicate with the Frontend deployment; VMs cannot talk to Pods in the same namespace.
- D. The Frontend Deployment should utilize a Kubernetes Service to expose itself, while the Backend VM can be accessed by the Frontend using the VM's assigned IP or DNS name (if external DNS is configured).
- E. The SQL Server VM must be manually created in vCenter first, then "onboarded" to the namespace.
正解：A、B、D
質問 # 54
What component is used to provision VMware vSphere Kubernetes Service (VKS) service mesh workload clusters?
- A. Cert-manager
- B. Cluster API
- C. Carvel
- D. Harbor
正解：B
解説：
In VCF 9.0, VKS cluster provisioning and lifecycle management is built around Kubernetes-native, declarative APIs. The VMware documentation describes thatCluster API provides declarative, Kubernetes- style APIs for cluster creation, configuration, and management, and that its inputs include the cluster definition plus the resources describing the virtual machines and "cluster add-ons." This is why Cluster API is the component associated withprovisioning(creating and managing) workload clusters in the VKS model.
By contrast,cert-manageris typically used to automate certificate issuance/renewal for in-cluster components, andCarvelis a set of tools often used to package, configure, and install Kubernetes software, but neither is the core provisioning controller for creating the clusters themselves. The VCF documentation is explicit that Cluster API is the API layer responsible for cluster creation/configuration/management, making it the correct answer for provisioning VKS workload clusters (including those intended to run service mesh capabilities).
質問 # 55
An administrator must create amulti-zone vSphere Supervisor deployment in a VMware Cloud Foundation (VCF) environment. What is the primary purpose of this configuration?
- A. To simplify the management of network pools and IP address ranges.
- B. To create isolated security domains using NSX micro-segmentation.
- C. To enable cross-site vSAN stretched clusters for data replication between data centers.
- D. To provide high availability for the Supervisor Cluster and vSphere Kubernetes clusters.
正解：D
解説：
Amulti-zone Supervisorin VCF 9.0 is designed to deliverplatform resiliency and high availability at the vSphere cluster (zone) failure-domain level. The VCF 9.0 documentation states that a multi-zone Supervisor "leverages three vSphere clusters" (each mapped to a vSphere Zone) and that these zones are used by both "workloads and Supervisor management components to deliver high availability," exposing "each cluster as an independent, consumable availability zone," resulting in a "resilient, HA-capable platform." This is reinforced in the vSphere Zones guidance: deploying the Supervisor onthree vSphere Zones spreads the control plane VMs across three zones, providing "cluster-level high availability" that protects the Supervisor control plane against asingle cluster-level failure(one control plane VM per management zone).
Because VKS (vSphere Kubernetes Service) runs on Supervisor, distributing Supervisor control plane and workload placement across zones improves overall availability of Supervisor services and Kubernetes consumption in that Supervisor instance.
質問 # 56
A Cloud Administrator is analyzing a recurring issue where TKG cluster creations fail intermittently with "IP Address Exhaustion" errors, despite the IP pools appearing to have capacity. The administrator suspects that finalizers on deleted Service objects are preventing IP addresses from being released back to the pool managed by the NSX Load Balancer.
Which specific kubectl command and output field would allow the administrator to confirm that a LoadBalancer Service in the dev-ns namespace is "stuck" in deletion and holding an IP? (Select all that apply.)
- A. Command: kubectl get endpoints -n dev-ns
- B. Command: kubectl get ipam -n dev-ns
- C. Command: kubectl get services -n dev-ns Confirmation: The IPAM block shows 100% utilization.
- D. Command: kubectl get services -n dev-ns -o yaml
- E. Command: kubectl describe service -n dev-ns
正解：C、D、E
質問 # 57
......
最新の3V0-24.25学習ガイド2026年最新の- 提供するのはテストエンジンとPDF：https://www.jpntest.com/shiken/3V0-24.25-mondaishu
最新版を今すぐ試そう3V0-24.25練習テスト問題解答：https://drive.google.com/open?id=1OUkh-Cj3RfMWLgAp0fmusyalG4aLWV7I