3V0-22.25 Exam: Learn Workload Optimization as Two Intents
On the 3V0-22.25 exam, workload optimization comes down to two settings that answer two different questions. Operational Intent says how the clusters should be used: balanced, moderate or consolidated, with a headroom buffer. Business Intent says where each VM is allowed to run, using vCenter tags. If you can keep those two apart in a scenario, objective 4.6 becomes one of the easier parts of the exam.
I read every fact in this post on Broadcom’s own pages on 31 October 2026: the certification page, the exam guide and the VCF 9.0 TechDocs for VCF Operations.
What is the 3V0-22.25 exam?
It is the Advanced VMware Cloud Foundation 9.0 Operations exam, the test for the VMware Certified Advanced Professional - VCF Operations credential. Broadcom says it validates the skills to monitor, manage and optimize VCF environments for performance, capacity and cost.
Here are the exam details as Broadcom lists them today:
- Questions: 60
- Time: 135 minutes, which includes extra time for non-native English speakers
- Passing score: 300, scaled
- Price: $250 USD
- Languages: English and Japanese
- Item types: multiple choice, multiple selection, drag and drop, matching, build-list and sequencing
- Delivery: proctored, through Pearson VUE
- Product version: VCF 9.0
That gives you 2 minutes and 15 seconds per item. That is my own arithmetic, not a Broadcom figure. If you want one page that collects the exam details, sample questions and prep material for this code, see the 3V0-22.25 VCAP Operations exam overview.
Why does objective 4.6 deserve its own study week?
Because it is mostly vocabulary, and vocabulary questions are lost by people who know the product but blur the terms. Only Section 4 of the blueprint has testable objectives, and it holds 83 lines across 16 objectives. Objective 4.6, Workload Optimization in VCF Operations, has 7 of them.
Four of those seven lines start with “Differentiate” or “Identify” rather than “Given a scenario”. That is unusual for this exam, where 76 of the 83 lines are scenario lines. Matching and drag and drop are both listed item types, and a “differentiate” line fits them well, so expect to sort terms rather than read long stories.
It also sits next to the heaviest part of the blueprint. Capacity (4.2), forecasting (4.3), cost (4.4) and workload optimization (4.6) together make up 36 of the 83 lines, by my count. Workload optimization is where the capacity ideas turn into actual VM moves.
What is the difference between Operational Intent and Business Intent?
Operational Intent is about how hard to work the clusters. Business Intent is about which VMs may sit on which clusters or hosts. TechDocs shows them as two separate cards on the Workload Placement page, and a data center only shows as “Optimized” when both are satisfied: workloads are optimized for the Operational Intent and there are no tag violations under the Business Intent.
A quick way to sort a scenario:
- If the question talks about contention, spare capacity, freeing up clusters or saving power and licences, it is Operational Intent.
- If it talks about compliance, licensing zones, production versus test, an operating system or a tier that must stay together, it is Business Intent.
- If it talks about both, the answer usually needs both cards set, because “Optimized” needs both.
What do Balance, Moderate and Consolidate actually do?
They are the three utilization objectives you pick in the Workload Automation part of a VCF Operations policy. The TechDocs page on Workload Automation Details describes them like this:
- Balance: use it when workload performance is your first goal. It moves workloads so resource use is balanced, which leaves the most headroom on every resource.
- Moderate: use it when you want to minimize workload contention.
- Consolidate: use it to minimize the number of clusters your workloads use. Broadcom calls it good for cost optimization while still meeting performance goals, and says it might reduce licensing and power costs.
One small trap: the exam guide writes “Balanced”, while the product and TechDocs say “Balance”. Treat them as the same mode.
To remember them, I picture a slider (my memory aid, not Broadcom’s wording). Balance sits at the performance end, Consolidate at the cost end, and Moderate in between. When a scenario says “the CFO wants to retire a cluster”, slide right to Consolidate. When it says “users complain about slow VMs during month-end”, slide left to Balance.
What is the buffer in Operational Intent?
The buffer is the Cluster Headroom setting. TechDocs says headroom “establishes a required capacity buffer, for example, 20 percent”, so each cluster keeps spare room for growth.
Two details are worth learning word for word, because they make good exam options:
- A large headroom setting limits the system’s chances to optimize. More buffer means fewer clusters can take extra VMs.
- vSphere HA overhead is already counted in usable capacity, and the headroom setting does not change it. An option that says “increase headroom to cover HA failover” is a distractor.
How does Business Intent use tags?
Business Intent reads vCenter tags. A tag is a key:value pair, where the key is the tag category and the value is the tag name, as in OS: Linux. In the Edit Business Intent dialog you pick tags on a Placement tab, so tagged VMs land on hosts or clusters with matching tags. On an Exclusion tab you pick tags that keep VMs or clusters out of Workload Placement completely.
Get Daisy Scott’s stories in your inbox
Join Medium for free to get updates from this writer.
The dialog suggests five categories: Operating System, Environment, Tier, Network and Other. They are only suggestions. The real category has to exist in vCenter first, so a scenario where the tag was never created in vCenter cannot be fixed inside VCF Operations alone.
What changes between host-based and cluster-based Business Intent?
The choice is which object type you match the tagged VMs to: clusters or hosts. With clusters, VMs are kept on clusters whose tags match. With hosts, the constraint goes down to individual hosts, and that has a side effect you must know.
For host-based placement, VCF Operations creates and manages DRS rules itself and deactivates every conflicting user-created DRS rule. That covers VM-VM and VM-Host affinity and anti-affinity rules. You even have to tick a box that says you understand VCF Operations will deactivate all your current and future DRS rules.
So if a scenario says “the team relies on its own anti-affinity rules for a database pair”, host-based Business Intent is the risky answer. Cluster-based intent, or keeping the existing rules, is the safer one.
What does Advanced Workload Placement add with VCF Automation?
It brings VCF Operations into the first placement of a new VM. When VCF Automation provisions a VM in a cloud zone with its placement policy set to ADVANCED, it asks VCF Operations where the VM should go. VCF Operations uses the demand model by default, and that can’t be turned off. If you set overcommit ratios in the policy, it adds allocation awareness, so clusters are not over-allocated.
The benefit to name on the exam is better initial placement, based on real demand and, if you turn it on, your allocation limits. Note the limit TechDocs gives: the allocation awareness applies to advanced workload placement only and “is not extended to workload optimization feature”. Also, for VCF Automation custom data centers, the Business Intent window is not operational.
What are the stages for configuring each intent?
Two of the seven lines ask for the process or stages, so learn them as short build-lists. This is my summary of the TechDocs steps:
- Operational Intent: open the policy (Policy Definition, then the Workload Automation card), unlock the setting with the lock icon, pick Balance, Moderate or Consolidate, set the cluster headroom, choose the Storage vMotion option, save, and make sure that policy is the active one for the objects.
- Business Intent: create the tag categories and tags in vCenter, tag the VMs and the clusters or hosts, open Capacity, then Optimize, then Workload Placement, click Edit on the Business Intent card, choose Clusters or Hosts, include the tags on the Placement or Exclusion tab, then check the Selected Tags tab.
After both, run OPTIMIZE NOW, SCHEDULE or AUTOMATE. Remember that automation checks status every 5 minutes, and after an optimization the next check is 6 hours later. While automation is on, scheduled optimizations are switched off.
The lock icon matters for the policy hierarchy line in objective 4.5. A locked setting inherits the parent policy, and an unlocked one is set in this policy.
How should you practise this in a lab?
Set up one small lab data center with two clusters and run the same five tests in order:
- Run with the mode your policy has now and note the Optimization Recommendation.
- Switch to Consolidate, run OPTIMIZE NOW and read the BEFORE and AFTER plan.
- Raise the cluster headroom and see how the plan shrinks.
- Add a cluster-based Business Intent with one tag, then break it on purpose to see a tag violation.
- Read the host-based warning about DRS rules, but don’t accept it in a lab you share with others.
The official 3V0-22.25 exam guide lists all seven 4.6 lines. Tick each one only after you have seen it on screen.
If you want a short warm-up before booking the exam, this VMExam video lists three things to check first:
Frequently asked questions
1. How many questions are on the 3V0-22.25 exam?
Broadcom lists 60 questions in 135 minutes. The passing score is 300 on a scaled method, and the exam costs $250 USD.
2. Which VCF version does the 3V0-22.25 exam cover?
The exam guide says the content is based on VCF 9.0. Study the VCF 9.0 TechDocs for VCF Operations, not older Aria Operations guides.
3. What is the difference between Balance and Consolidate in VCF Operations?
Balance spreads workloads to give the most headroom and puts performance first. Consolidate packs workloads onto fewer clusters to save cost, and may free resources, licences and power.
4. Does cluster headroom include vSphere HA overhead?
No. TechDocs says HA overhead is already part of usable capacity, and the headroom setting does not change it. Headroom is an extra buffer on top.
5. What happens to my DRS rules with host-based Business Intent?
VCF Operations creates and manages its own DRS rules and deactivates every conflicting user-created rule, including affinity and anti-affinity rules. You must confirm this before it is applied.
