Sign in
Home/VMware/VMware Cloud Professional (2V0-33.22)/Free questions

VMware Cloud Professional (2V0-33.22) — Free Practice Questions

10 free sample questions from a bank of 84, with the correct answers and explanations. No signup required — start practising right now.

1A cloud administrator is managing a container environment. The application team has complained that they need to manually restart containers in the event of a failure. Which solution can the administrator implement to solve this issue?
  • Kubernetes
  • VMware vSphere High Availability
  • VMware vSphere Fault Tolerance
  • Prometheus
Answer: A

The short version

A — Kubernetes auto-restarts failed containers. Kubernetes restart policies remove the need for manual container restarts after failures.

Key concepts in this question

  • Kubernetes: Container orchestrator that schedules and self-heals workloads.
  • Restart policy: Pod setting such as Always that restarts terminated containers automatically.
  • vSphere HA and FT: Protect VMs, not container-level restart logic.

Why A is correct

Kubernetes provides self-healing for containers through pod restart policies, with Always as the default that restarts containers even after successful completion. This directly solves the application team complaint about manual restarts in a container environment. It is the container-native solution, unlike VM-centric availability features.

Why the others are wrong

  • B. vSphere HA restarts VMs on host failure, it does not manage restart of individual containers.
  • C. Fault Tolerance provides a live shadow VM for continuity, not container restart automation and is excessive here.
  • D. Prometheus is monitoring and alerting, it observes failures but does not restart containers.

2V0-3322 exam tip

Containers failing = Kubernetes; VMs failing = vSphere HA.

2A cloud administrator wants to migrate a virtual machine using VMware vSphere vMotion from their on-premises data center to their VMware Cloud on AWS software-defined data center (SDDC), using an existing private line to the cloud SDDC. Which two requirements must be met before the migration can occur? (Choose two.)
  • The versions of VMware vSphere need to match between the on-premises data center and the cloud SDDC.
  • A Layer 2 connection is configured between the on-premises data center and the cloud SDDC.
  • AWS Direct Connect is configured between the on-premises data center and the cloud SDDC.
  • IPsec VPN is configured between the on-premises data center and the cloud SDDC.
  • Cluster-level Enhanced vMotion Compatibility (EVC) is configured in the on-premises data center and the cloud SDDC.
Answer: C, D

The short version

CD — Direct Connect plus IPsec VPN enable vMotion to VMC on AWS. Private-line migration needs dedicated connectivity plus secure VPN for vMotion control.

Key concepts in this question

  • vMotion to VMC on AWS: Live migration from on-premises to cloud SDDC.
  • AWS Direct Connect: Private dedicated link to AWS and VMC.
  • IPsec VPN: Secure tunnel used with Direct Connect for migration traffic.

Why CD is correct

VMware Cloud on AWS migration over a private line requires AWS Direct Connect to provide reliable private connectivity to the cloud SDDC. An IPsec VPN is also required alongside it for the vMotion and hybrid connectivity path in this design. Together they satisfy the two prerequisites before migration can occur.

Why the others are wrong

  • A. Matching vSphere versions is best practice but not listed as the required pair; EVC and connectivity matter more.
  • B. A Layer 2 stretched network is used for L2 extension use cases, not the required connectivity pair here.
  • E. EVC helps CPU compatibility but is not one of the two required connectivity prerequisites in the settled key.

2V0-3322 exam tip

On-prem to VMC vMotion on private line = Direct Connect + IPsec VPN.

3Which three items should be considered when performing a hot migration of a virtual machine (VM)? (Choose three.)
  • The status of the guest operating system in the VM
  • The source and destination host must have shared access to the storage that contains the VM
  • The source and destination host management network IP address families must match
  • The vGPU configuration of the VM
  • The status of VMware Tools on the VM
  • The CPU instruction set required by the VM
Answer: B, C, F

The short version

B, C and F — hot vMotion needs shared storage visibility, matching management address family, and compatible CPU instruction sets. Powered-on migration has strict preconditions.

Key concepts in this question

  • Hot migration: moving a running VM without downtime using vMotion.
  • Shared storage access: both hosts must see the VM files unless combined with Storage vMotion.
  • CPU compatibility: destination CPU must support the guest instruction set, handled via EVC.

Why B, C and F are correct

Hot migration keeps memory and device state live, so the source and destination must share access to the storage holding the VM, must communicate over the same management network family, and must present a compatible CPU instruction set or the migration falls back to cold. Those three map directly to B, C and F.

Why the others are wrong

  • A. Guest OS power state describes hot versus cold, it is not an extra item to check.
  • D. vGPU configuration blocks vMotion in many cases, it is not a standard hot-migration prerequisite.
  • E. VMware Tools status affects quiescing and performance, not vMotion eligibility.

2V0-3322 exam tip

Hot vMotion = shared storage + same network family + same CPU.

4A cloud administrator is tasked with choosing a correct Elastic DRS policy. The existing VMware Cloud on AWS environment consists of a single cluster with two ESXi hosts. The following guidelines regarding the expected performance must be met: • The cluster should be able to scale automatically when additional resources are required. • Application performance should NOT be affected when the cluster scaling operation is being performed. Which Elastic DRS policy should the cloud administrator select?
  • Optimize for Best Performance
  • Elastic DRS Baseline
  • Optimize for Lowest Cost
  • Optimize for Rapid Scale-Out
Answer: A

The short version

A — Best Performance scales without hurting performance. Optimize for Best Performance adds capacity early to protect apps.

Key concepts in this question

  • Elastic DRS: Automatically adds and removes hosts in VMC on AWS clusters.
  • Optimize for Best Performance: Policy favoring headroom and fast scale-out.
  • Lowest Cost and Rapid Scale-Out: Cheaper or faster but with performance or manual-removal tradeoffs.

Why A is correct

The requirement is automatic scaling when resources are needed with no application impact during scaling. Optimize for Best Performance provisions additional hosts proactively and removes them slowly to preserve headroom. That behavior directly matches both guidelines, unlike cost-optimized or manual-removal options.

Why the others are wrong

  • B. Elastic DRS Baseline is the default conservative behavior, not the performance-optimized policy requested.
  • C. Optimize for Lowest Cost delays scale-out to save cost, risking performance impact.
  • D. Optimize for Rapid Scale-Out scales aggressively but can require manual removal and risks later performance impact.

2V0-3322 exam tip

Must not affect performance while scaling = Best Performance.

5Which vSphere HA default response is applied when a virtual machine crashes on a VMware Cloud cluster?
  • Restart the impacted virtual machine on the same host in the same SDDC cluster
  • Restart the impacted virtual machine on other hosts in other SDDC clusters
  • Restart the impacted virtual machine on other hosts in the same SDDC cluster
  • Shut down the impacted virtual machine and do not restart it anywhere
Answer: A

The short version

A is correct — a VM crash (guest-OS failure) is a VM Monitoring case, and the default response is to restart that VM on the same host in the same SDDC cluster.

Key concepts in this question

  • vSphere HA host failure vs. VM Monitoring: host failure = fail over to another host; guest-OS crash/hang = VM Monitoring restarts the VM.
  • Same-host restart: for OS crash, HA does not vMotion/fail over; it issues a reset/restart in place.
  • VMware Cloud SDDC cluster scope: restart stays within the same cluster/host; no cross-cluster restart.

Why A is correct

A — Restart the impacted virtual machine on the same host in the same SDDC cluster — matches documented VM Monitoring behavior: In the event of a guest operating system failure, vSphere HA can restart the affected virtual machine on the same physical server. A crashed VM is not a dead host, so no failover is needed; in-place restart is fastest and preserves placement.

Why the others are wrong

  • B — Restart ... on other hosts in other SDDC clusters: Wrong scope. Cross-cluster restart is never the default for a single-VM OS crash; other clusters are for site/cluster-level recovery, not VM Monitoring.
  • C — Restart ... on other hosts in the same SDDC cluster: This is the default for host failure (HA failover), not for a guest-OS crash. Distractor that confuses host failure with VM failure.
  • D — Shut down ... and do not restart it anywhere: This describes a disabled HA response / Disabled restart policy. Default is to restart, not to leave the VM down.

2V0-3322 exam tip

If the stem says VM crashes / OS failure / heartbeat lost but host is up, pick same-host restart. If it says host fails / isolation / partition, pick restart on other host(s) in same cluster.

6A cloud administrator is looking to migrate several dozen workloads from their on-premises location to a VMware public cloud using VMware HCX. A total of nine networks will need to be stretched for the migration. They will also be utilizing the capabilities of the WAN appliance for the migration. HCX appliance requirements are as follows: • HCX Manager: 4 vCPU, 12GB Memory • HCX-IX Interconnect: 8 vCPU, 3GB Memory • HCX Network Extension: 8 vCPU, 3GB Memory • HCX WAN Optimization: 8 vCPU, 14GB Memory What are the on-premises vCPU and memory component requirements for this VMware HCX deployment?
  • 36 vCPUs, 35GB of memory
  • 30 vCPUs, 36GB of memory
  • 28 vCPUs, 32GB of memory
  • 32 vCPUs, 40GB of memory
Answer: A

The short version

A — Nine stretched networks need extra Network Extension, totaling 36 vCPU 35GB. Extra NE appliance pushes the total to answer A.

Key concepts in this question

  • HCX Network Extension: Stretches L2 networks, one appliance handles up to 8 networks.
  • HCX IX and WAN OPT: Interconnect and WAN optimization appliances for migration.
  • HCX Manager: Management plane with fixed sizing.

Why A is correct

Nine networks exceed the 8-network limit of a single Network Extension appliance, so two NE appliances are required. Adding Manager plus IX plus two NE plus WAN Optimization yields 36 vCPUs and 35GB per the stated sizes. That math matches option A and no other option.

Why the others are wrong

  • B. 30 vCPUs 36GB understates vCPU by missing the second NE appliance.
  • C. 28 vCPUs 32GB reflects only one NE appliance and is insufficient for nine networks.
  • D. 32 vCPUs 40GB does not match the documented appliance sum with two NE appliances.

2V0-3322 exam tip

More than 8 networks = add a second HCX-NE, then recount.

7Which two statements depict the VMware Multi-Cloud vision? (Choose two.)
  • Reduce the number of developers to increase productivity.
  • Run the workloads in the cloud to eliminate security issues.
  • Standardize at the DevSecOps and infrastructure level.
  • Modernize applications in the cloud of choice using the cloud-native services of that cloud provider.
  • Deliver a consistent management and operations layer across any cloud.
Answer: C, E

The short version

C and E — VMware Multi-Cloud vision is standardize at DevSecOps and infrastructure, plus one consistent operations layer. Run anywhere, manage the same way.

Key concepts in this question

  • Standardization: common DevSecOps and infrastructure constructs across clouds.
  • Consistent operations: single management and operations layer for all clouds.
  • Vision versus benefit: vision statements describe the target model, not headcount or zero-security claims.

Why C and E are correct

VMware frames multi-cloud as standardizing the platform engineering and infrastructure layer while delivering a consistent management and operations plane, so teams build once and operate everywhere. C states the standardization pillar and E states the consistent-operations pillar.

Why the others are wrong

  • A. Reducing developers is not a vision statement and contradicts productivity goals.
  • B. No cloud eliminates security issues; it changes the shared-responsibility model.
  • D. Using each cloud native service ad hoc is the sprawl the vision replaces with consistency.

2V0-3322 exam tip

Multi-cloud vision = standardize platform + consistent operations.

8A company needs to increase its infrastructure capacity quickly to accommodate their rapid business growth. Which cloud use case describes their requirement?
  • Maintain and Modernize
  • Consolidate and Migrate
  • Disaster Recovery
  • Maintain and Expand
Answer: D

The short version

D — rapid capacity growth is Maintain and Expand. Keep the footprint and grow it.

Key concepts in this question

  • Maintain and Expand: extend existing infrastructure capacity for growth.
  • Consolidate and Migrate: shrink or move estates, the opposite motion.
  • Disaster Recovery: protection and failover, not growth capacity.

Why D is correct

The stem asks for quickly increasing infrastructure capacity to handle business growth, which is the expand-use case: retain the current model and add elastic capacity. That is exactly how VMware positions Maintain and Expand.

Why the others are wrong

  • A. Maintain and Modernize optimizes and updates existing apps, it does not add raw capacity.
  • B. Consolidate and Migrate reduces footprint or relocates it, not growth.
  • C. Disaster Recovery provides continuity, not steady-state growth capacity.

2V0-3322 exam tip

Growth capacity = Expand; moving = Migrate; protecting = DR.

9A cloud administrator is deploying a new private cloud in Google Cloud VMware Engine and wants to allow for maximum growth. What are two valid subnet sizes that meet the requirement for the VMware vSphere/vSAN subnet? (Choose two.)
  • /23
  • /20
  • /24
  • /21
  • /22
Answer: B, D

The short version

B (/20) and D (/21) are correct — for maximum growth in Google Cloud VMware Engine, use the largest vSphere/vSAN CIDR blocks; /20 and /21 give the highest maximum node counts.

Key concepts in this question

  • GCVE private-cloud networking: vSphere/vSAN subnet CIDR size caps private-cloud scale.
  • Smaller prefix = larger subnet = more growth: /20 > /21 > /22 > /23 > /24 in address space.
  • Maximum growth wording: always pick the two largest valid options from the CIDR table.

Why B and D are correct

B (/20) supports up to ~200 nodes and D (/21) supports ~90-200 nodes per Google Cloud docs: Specified prefix /21 supports up to 90-200 nodes and /20 up to 200 nodes. When the requirement is maximum growth, these two are the only choices that maximize headroom.

Why the others are wrong

  • A — /23: Smaller than /21//20; supports fewer nodes. Valid CIDR in general but does not meet maximum growth.
  • C — /24: Much smaller (~10 nodes per evidence). Quickly exhausts growth; opposite of requirement.
  • E — /22: Mid-size (~40 nodes). Larger than /24 but still smaller than /21//20, so fails the maximum-growth test.

2V0-3322 exam tip

For GCVE maximum growth / largest scale subnet questions, memorize order: /20 largest, then /21, then /22, then /24 smallest. Pick the two largest listed.

10What is the key difference between configuring Hybrid Linked Mode from the Cloud Gateway Appliance and the VMware vSphere Client?
  • Minimal overhead is required in the on-premises data center.
  • Centralized administration is available through the VMware vSphere Client.
  • VMware Cloud on AWS software-defined data center (SDDC) does NOT reveal the on-premises inventory.
  • The on-premises VMware vSphere version must be vSphere 6.5 or later.
Answer: A

The short version

A is correct — the key difference of configuring Hybrid Linked Mode from the Cloud Gateway Appliance is minimal overhead in the on-premises data center.

Key concepts in this question

  • Hybrid Linked Mode (HLM): links on-prem vCenter with VMware Cloud SDDC for unified inventory/view.
  • Cloud Gateway Appliance (CGA) method vs. vSphere Client / on-prem gateway method: CGA runs in the cloud SDDC, reducing on-prem footprint.
  • Centralized administration exists in both methods — not the differentiator.

Why A is correct

A — Minimal overhead is required in the on-premises data center — is the held banked answer: deploying/connecting via the cloud-hosted Gateway avoids installing and maintaining additional on-prem gateway infrastructure versus the older vSphere Client-linked approach.

Why the others are wrong

  • B — Centralized administration ... through vSphere Client: Both approaches aim at single-pane administration; not unique to CGA vs. Client, so not the key difference.
  • C — SDDC does NOT reveal on-premises inventory: Incorrect direction. HLM is specifically to reveal/share inventory across linked domains; hiding inventory is not its purpose.
  • D — On-premises vSphere must be 6.5 or later: Version prerequisite applies broadly to HLM regardless of configuration path, not a difference between CGA and vSphere Client methods.

2V0-3322 exam tip

When asked difference between Cloud Gateway Appliance vs vSphere Client for HLM, pick the overhead/footprint answer (A). Do not pick inventory-visibility or version answers.

Want the full bank of 84 questions for VMware Cloud Professional (2V0-33.22)? See all practice exams.