2V0-16.25 Domain 2: Deploy, Configure, and Operate VMware vSphere Foundation (VVF) (Not published)

Overview

This domain maps to Section 4 of the Broadcom exam guide, Deploy, Configure, and Operate VMware vSphere Foundation (VVF). It is the larger of the two testable sections, with four objective groups: Deploy and Configure (4.1), Manage (4.2), Operate (4.3) and Consume and Automate (4.4). Operate alone lists nineteen bullets about VCF Operations and VCF Operations for Logs, covering views, reports, dashboards, alerts, policies, costing, integrations, application monitoring, service discovery and compliance.

The remaining groups cover the VVF component set and its deployment, Supervisor enablement, identity and RBAC, licensing, certificates and lifecycle with vSphere Lifecycle Manager, plus workloads delivered through Supervisor: the VM Service, VMware Kubernetes Service clusters, vSphere Pods and VCF Operations Orchestrator. Broadcom publishes no weights, and one Operate bullet repeats another, so this page counts 30 distinct objectives.

Why it matters on the exam

Section 4 is where VVF differs most from a plain vSphere certification. Candidates with years of vCenter experience often have little time in VCF Operations, the product formerly called Aria Operations, or in VCF Operations for Logs, yet the Operate group has more objectives than all of Section 2's storage and networking combined. The domain also tests 9.0 changes such as licensing handled through VCF Operations, the VCF Installer, and lifecycle with cluster images. Supervisor items expect you to know which networking choice enables which service, for example that vSphere Pods depend on NSX networking. A planning estimate puts close to two thirds of the 60 items here, so weak coverage of operations tooling is the most common reason experienced vSphere administrators struggle on this exam.

How it's tested

Domain 2 stems often name a role, such as an operations team, a cost analyst or a developer, and ask which VCF Operations feature, Supervisor service or management task meets their need. Many items test where a task is performed. Know which console owns licensing, certificates, dashboards, log queries and namespaces in VVF 9.0.

Which tool does it

A need such as searching syslog events, showing chargeback or checking hardening is described, and you choose between VCF Operations, VCF Operations for Logs and vCenter.
Build the alert

You order or select the parts of an alert: symptom definitions, alert definition, recommendation, notification and policy assignment.
Pick the Supervisor service

A developer or application team needs a VM, a Kubernetes cluster or a pod, and you match it to VM Service, VKS or vSphere Pods with their prerequisites.

Reasoning it through

A team wants an email when any production VM has had CPU ready above a threshold for fifteen minutes. A dashboard would show the problem but not notify anyone. A log alert in VCF Operations for Logs reacts to events, not metrics. The right path is a symptom on the CPU ready metric, an alert definition using it, a notification with an email outbound plugin, and the alert enabled in the policy for production objects.

Objectives 30

Official objectives from the Broadcom (VMware) outline, in outline order.

4.1.1 Identify the components of a VVF DeploymentThe products that make up VMware vSphere Foundation 9.0.

What it means: A VVF 9.0 deployment combines ESX hosts, vCenter, vSAN, vSphere Supervisor, VCF Operations with its fleet management appliance and collectors, and VCF Operations for Logs. Together they provide compute, storage, Kubernetes-based services and operations tooling under one license.
What to understand: Know what each component does and where it runs. vCenter manages hosts and clusters; vSAN provides storage; Supervisor turns a cluster into a platform for VMs, Kubernetes clusters and pods; VCF Operations analyses metrics, cost and compliance; VCF Operations for Logs collects and searches logs. The VCF Operations fleet management appliance handles deployment and lifecycle of the operations components.
How it shows up: Expect a list of products where you identify which belongs to VVF and what role it plays.
Common confusion: Assuming VVF includes the full VMware Cloud Foundation stack, such as NSX overlay networking and SDDC Manager workload domains.

4.1.2 Given a scenario, describe the deployment of a VMware vSphere Foundation-based environmentDeployment order, tooling and prerequisites for a VVF instance.

What it means: This objective covers how a VVF environment is stood up: preparing ESX hosts, using the VCF Installer or manual methods to deploy vCenter and the operations components, and meeting DNS, NTP, IP and password requirements.
What to understand: Prepare hosts with a supported ESX build and networking, then use the VCF Installer to deploy the management components from a deployment specification, or converge an existing vCenter. Validation checks DNS forward and reverse records, NTP, network reachability and host readiness before deployment starts. Know the order: hosts and vCenter first, then VCF Operations and its fleet management components, then VCF Operations for Logs.
How it shows up: Scenario items describe a failed validation or a missing prerequisite and ask what to fix first.
Common confusion: Thinking the operations components must exist before vCenter; they connect to vCenter as a data source.

4.1.3 Given a scenario, configure Supervisor within a ClusterEnabling vSphere Supervisor with VDS or NSX networking.

What it means: Supervisor is enabled on a vSphere cluster or across zones of clusters to run Kubernetes control plane VMs and expose namespaces. Configuration includes networking stack, management network, workload networks, load balancer, storage policies and the control plane size.
What to understand: Supervisor needs a vSphere Distributed Switch. With VDS networking it needs a supported load balancer such as Avi Load Balancer, while NSX networking provides load balancing and is required for vSphere Pods. You assign storage policies for control plane VMs and persistent volumes and choose one-zone or three-zone deployment. A content library supplies images for services.
How it shows up: Expect questions on which networking option enables a stated Supervisor feature.
Common confusion: Expecting vSphere Pods on a Supervisor configured with VDS networking only.

4.2.1 Given a scenario, configure Identity Management and Role-based Access Control (RBAC) in VMware vSphere FoundationIdentity sources, federation, roles and permissions.

What it means: This objective covers who can log in and what they can do. It includes the vCenter Single Sign-On domain, identity sources such as Active Directory over LDAPS, identity federation with an external provider, and vCenter roles, privileges and permissions.
What to understand: A permission joins a user or group, a role and an inventory object, and can propagate to child objects. Global permissions span solutions across vCenter instances. Built-in roles include Administrator, Read-only and No access; custom roles are cloned and edited. VCF 9.0 adds the VCF Identity Broker for single sign-on across VCF components with external providers. Know that an explicit No access permission on an object overrides inherited access.
How it shows up: Scenario items ask how to give a group limited rights on part of the inventory.
Common confusion: Editing a built-in sample role instead of cloning it, or granting rights at the root when a folder would do.

4.2.2 Given a scenario, configure license management within VMware vSphere FoundationAssigning and reporting VVF 9.0 licenses.

What it means: In 9.0, licensing is managed centrally through VCF Operations rather than by typing keys into each vCenter. Licenses are core-based and are registered with the Broadcom licensing portal, then assigned to vCenter instances and their hosts.
What to understand: Understand connected and disconnected registration modes, the need to report usage on a schedule, and what happens when a vCenter is not licensed in time. Licensing is per physical core with a minimum per CPU, and the vSAN capacity entitlement included with VVF is tied to core count. Know where to view license usage and compliance inside VCF Operations.
How it shows up: Expect questions about where to apply a license in 9.0 and what must be done in an air-gapped site.
Common confusion: Looking for the old vSphere Client license key entry for each host.

4.2.3 Given a scenario, configure certificate management within VMware vSphere FoundationVMCA modes, custom certificates and certificate replacement.

What it means: Certificate management covers the certificates that secure vCenter, ESX and the operations components. vCenter includes the VMware Certificate Authority, which can issue certificates itself, act as a subordinate of an enterprise CA, or be bypassed with custom certificates.
What to understand: Know the modes: VMCA default, VMCA as intermediate CA, full custom, and hybrid, where the machine SSL certificate is custom and VMCA still signs ESX certificates. Replacing the machine SSL certificate requires a CSR, the signed certificate and the full chain. VCF Operations can track certificate expiry and help manage certificates across components. Expired certificates break trust between components.
How it shows up: Scenario items ask which mode satisfies a policy that browsers must trust vCenter without extra effort for hosts.
Common confusion: Treating the hybrid approach as replacing every certificate with enterprise CA certificates.

4.2.4 Given a scenario, manage the lifecycle of VMware vSphere FoundationUpgrading and patching vCenter, ESX and operations components.

What it means: Lifecycle management keeps every VVF component on supported, compatible versions. ESX hosts are managed with vSphere Lifecycle Manager images, vCenter is updated through its own process, and VCF Operations components are updated through fleet management.
What to understand: A vLCM image defines the ESX base image, vendor add-on, firmware and drivers add-on and extra components. You check compliance, run a pre-check, stage and remediate. Baselines are not supported in 9.0, so clusters must use images. vCenter supports reduced downtime upgrade. Follow interoperability order: check the matrix, update management components, then hosts.
How it shows up: Expect questions about the order of updates or why a cluster cannot use baselines.
Common confusion: Remediating hosts before checking firmware and driver compatibility in the hardware support manager.

4.3.1 Given a scenario, identify the use case for VCF Operations and VCF Operations for LogsMetric analytics versus log analytics.

What it means: VCF Operations collects metrics and properties to deliver performance troubleshooting, capacity planning, cost, compliance and health views. VCF Operations for Logs collects syslog and agent logs for searching, dashboards and log-based alerts.
What to understand: Pick VCF Operations for trends, capacity remaining, rightsizing, chargeback and configuration compliance. Pick VCF Operations for Logs to find root cause in event text, audit who did what, or alert on a message pattern. The two integrate so you can open related logs from an object in VCF Operations.
How it shows up: A scenario describes a question to answer, and you choose which product answers it.
Common confusion: Using VCF Operations for Logs to forecast capacity, which needs metric history.

4.3.2 Given a scenario, describe the cluster components and deployment options of VCF OperationsAnalytics nodes, collectors and availability options.

What it means: A VCF Operations cluster is made of analytics nodes: a primary node, an optional replica for high availability, and data nodes for scale. Collectors, formerly cloud proxies, gather data from remote or segmented environments and forward it to the cluster.
What to understand: Deployment size depends on objects and metrics collected. High availability uses a replica node in the same site; continuous availability splits nodes across two fault domains with a witness node. Collectors reduce firewall rules and bandwidth for remote sites. Deployment and scale-out are handled through fleet management.
How it shows up: Expect questions about adding nodes for scale or protecting against site loss.
Common confusion: Thinking collectors store and analyse data; they forward it to the analytics cluster.

4.3.3 Given a scenario, describe the cluster components and deployment options of VCF Operations for logsPrimary and worker nodes, load balancing and ingestion.

What it means: VCF Operations for Logs runs as a single node or as a cluster with a primary node and worker nodes. An integrated load balancer gives the cluster a virtual IP for ingestion and the user interface.
What to understand: Production clusters use at least three nodes so the integrated load balancer can distribute traffic and survive a node loss. Size nodes by ingestion rate and retention. Sources send data by syslog, by the cfapi protocol from agents, or through integrations with vCenter and ESX. The guide lists this objective twice, so expect it to carry noticeable attention.
How it shows up: Scenario items ask how to make log ingestion survive a node failure.
Common confusion: Pointing sources to a single node IP instead of the integrated load balancer virtual IP.

4.3.4 Given a scenario, differentiate between metrics, properties ,and logsThree kinds of operational data.

What it means: Metrics are numeric values collected over time, such as CPU usage. Properties describe configuration or state that changes rarely, such as the number of vCPUs or the ESX version. Logs are timestamped text messages emitted by systems and applications.
What to understand: VCF Operations stores metrics and properties for objects; VCF Operations for Logs stores log events and can extract fields from them. Symptoms can be built on metrics or properties; log-based alerts use queries. Properties suit compliance checks, metrics suit performance trends and logs suit event investigation.
How it shows up: Expect items asking which data type answers a question, such as when a setting changed or how busy a host was.
Common confusion: Calling a VM's configured memory size a metric when it is a property.

4.3.5 Given a scenario, create custom Views and Reports in VCF OperationsBuilding list, trend and distribution views and scheduled reports.

What it means: Views present data about objects in forms such as list, summary, trend, distribution, image or text. Reports combine views and dashboards into documents that can be generated on demand or on a schedule as PDF or CSV.
What to understand: Choose the view type that matches the question: list for inventory tables, trend for change over time, distribution for spread across objects. Set the subject object type, data columns and time range. Report templates control layout and can be scheduled and emailed to stakeholders.
How it shows up: Expect questions on producing a scheduled monthly inventory or capacity document for managers.
Common confusion: Building a dashboard when the request is for a scheduled emailed document, which is a report.

4.3.6 Given a scenario, create and share dashboards in VCF OperationsCustom dashboards, widgets and sharing.

What it means: Dashboards are interactive canvases of widgets, such as views, scoreboards, heat maps and object lists, that update with live data. They can be created, cloned, organised and shared with users and groups.
What to understand: Use widget interactions so selecting an object in one widget filters others. Share dashboards with user groups or by URL, and export or import them as files. Out-of-the-box dashboards can be cloned and edited rather than changed in place.
How it shows up: Scenario items ask how to give a team a read-only operational view of their own clusters.
Common confusion: Editing a built-in dashboard directly instead of cloning it first.

4.3.7 Given a scenario, configure Alerting in VCF OperationsSymptoms, alert definitions, recommendations and notifications.

What it means: Alerts in VCF Operations are built from symptom definitions that test metrics, properties or events, combined into alert definitions with impact, criticality and recommendations. Notifications send alerts to people or systems through outbound plugins.
What to understand: Configure outbound settings such as SMTP email or webhooks, then notification rules filtering by object, criticality or alert type. Alert definitions are enabled or disabled through policies, so an alert may exist but be inactive for a group. Payload templates shape webhook content.
How it shows up: Expect ordering or missing-step questions about turning a metric threshold into an email.
Common confusion: Creating a notification rule without an outbound plugin, so nothing is sent.

4.3.8 Given a scenario, monitor log events in VCF OperationsViewing log data in the context of objects.

What it means: With VCF Operations for Logs integrated, VCF Operations can show log events for an object alongside its metrics and alerts. This lets operators correlate a spike in a metric with the messages logged at the same time.
What to understand: Know that the integration must be configured before log content appears and that you can launch in context from an object to filtered logs. Log events can also feed alerts through the integration.
How it shows up: Scenario items ask how an operator can see related logs without leaving the object view.
Common confusion: Expecting log events in VCF Operations without configuring the logs integration.

4.3.9 Given a scenario, create and share dashboards in VCF Operations for logsLog dashboards from queries and content packs.

What it means: VCF Operations for Logs dashboards are built from saved queries shown as charts or tables. Content packs provide prebuilt dashboards, queries, extracted fields and alerts for products such as vSphere and vSAN.
What to understand: Create a query in Explore Logs, add it to a dashboard, then share the dashboard with other users. Personal dashboards stay private until shared, and content pack dashboards are read-only but can be cloned.
How it shows up: Expect questions on reusing vendor content or sharing a query-based dashboard.
Common confusion: Trying to edit a content pack dashboard directly.

4.3.10 Given a scenario, use the Explore Logs feature to analyse the logsSearching, filtering and charting log events.

What it means: Explore Logs is the interactive search page of VCF Operations for Logs. You filter by text, time range and fields, group results, view event trends and save queries for dashboards or alerts.
What to understand: Use extracted fields to filter precisely, for example by hostname or event type. Event types group similar messages, which speeds root cause analysis. Queries can be turned into alerts that notify when matching messages appear.
How it shows up: Scenario items ask how to find all failed logins on ESX hosts in the last hour.
Common confusion: Searching free text when a field filter would be faster and more exact.

4.3.11 Given a scenario, configure costing and pricing in VCF OperationsCost drivers, pricing cards and showback.

What it means: Costing in VCF Operations estimates what infrastructure costs to own and run using cost drivers such as hardware, licensing, facilities and labour. Pricing applies rates to consumers through pricing cards for showback or chargeback.
What to understand: Cost drivers set the provider view; pricing cards set what consumers are charged per vCPU, GB of memory or storage. Currency is set once. Cost calculations run on a schedule, so changes do not appear instantly.
How it shows up: Expect questions on showing a department its monthly charge for VMs.
Common confusion: Confusing cost drivers, which describe what the provider pays, with pricing cards, which set what consumers pay.

4.3.12 Given a scenario, configure integration with VCF OperationsAdding accounts and management packs for external systems.

What it means: Integrations connect VCF Operations to other data sources and tools, for example other VMware products, cloud accounts, ticketing systems and third-party management packs, so their data appears alongside vSphere objects.
What to understand: Integrations are configured as accounts with credentials and a collector. Management packs add adapters, dashboards and alerts for the integrated product. Check collection status after adding an account, and assign it to the correct collector for remote sites.
How it shows up: Scenario items ask how to bring data from another product into VCF Operations.
Common confusion: Expecting data from a new integration without selecting a collector or valid credentials.

4.3.13 Given a scenario, monitor vSAN storage using VCF Storage OperationsCapacity, performance and health of vSAN in VCF Operations.

What it means: VCF Operations provides storage-focused dashboards and views for vSAN clusters, showing capacity used and remaining, performance, health findings and efficiency savings across clusters.
What to understand: Use the storage views to spot clusters running out of capacity, objects with resync activity or disk groups with high latency. Capacity forecasting uses history, so it complements the vSAN pages in vCenter. Alerts can surface vSAN health problems centrally.
How it shows up: Expect questions on monitoring vSAN across several clusters from one place.
Common confusion: Thinking vCenter's vSAN capacity page gives a multi-cluster forecast.

4.3.14 Given a scenario, configure VCF Operations policiesPolicies that control analysis, alerts and capacity settings.

What it means: A policy in VCF Operations is a set of rules applied to groups of objects. It controls which alerts and symptoms are active, capacity thresholds and buffers, workload settings, compliance and which metrics are collected.
What to understand: Policies inherit from a base or default policy, and custom groups let you apply different policies to production and test. Only one policy applies to an object at a time, decided by priority. Changing a policy changes alerts and capacity results for its objects.
How it shows up: Scenario items ask how to apply stricter capacity buffers to production clusters only.
Common confusion: Editing the default policy when only one group of objects needs different settings.

4.3.15 Given a scenario, monitor the application using VCF OperationsApplication monitoring with agents and Telegraf.

What it means: Application monitoring collects metrics from operating systems and applications inside VMs, such as databases and web servers, using agents installed through VCF Operations and a collector.
What to understand: The open-source Telegraf agent is deployed to VMs and sends OS and application metrics through the collector. You need guest credentials and VMware Tools for the agent to be deployed from VCF Operations. Application metrics then appear on dashboards and can drive alerts.
How it shows up: Expect questions on what is needed to see SQL Server metrics inside a VM.
Common confusion: Assuming VCF Operations sees application metrics without an agent.

4.3.16 Given a scenario, configure Service Discovery in VCF OperationsFinding services and dependencies inside VMs.

What it means: Service Discovery identifies services and processes running in VMs and maps the relationships between them, helping you understand which VMs make up an application.
What to understand: It uses VMware Tools and guest credentials to inspect processes and network connections. Discovered services can be grouped into applications and used in dependency maps for troubleshooting and change impact.
How it shows up: Scenario items ask how to learn which VMs talk to a database before maintenance.
Common confusion: Confusing Service Discovery, which maps services, with application monitoring, which collects their metrics.

4.3.17 Given a scenario, monitor security hardening and compliance using VCF OperationsCompliance benchmarks and hardening checks.

What it means: VCF Operations evaluates objects against compliance benchmarks, such as the vSphere security configuration guide and regulatory packs, and reports violations as alerts and scores.
What to understand: Enable the benchmarks you need, apply them through policies, and review compliance scores and failing rules on the compliance pages. Remediation is done in the managed system, then compliance is rechecked on the next collection.
How it shows up: Expect questions on showing which hosts fail a hardening rule.
Common confusion: Expecting VCF Operations to change host settings automatically when a rule fails.

4.3.18 Given a scenario, configure the integration with VVF componentsConnecting VCF Operations to vCenter, vSAN and Logs.

What it means: This objective covers integrating VCF Operations with the other VVF components: vCenter accounts with vSAN collection, VCF Operations for Logs, and the Supervisor and Kubernetes objects managed by vCenter.
What to understand: Add vCenter as an account with a service account that has the required privileges, enable vSAN collection, and integrate VCF Operations for Logs in both directions for launch in context and log alerts. Verify collection status after integration.
How it shows up: Scenario items ask why vSAN data or logs are missing in VCF Operations.
Common confusion: Using a vCenter account without enough privileges and then wondering why actions fail.

4.4.1 Given a scenario, describe the deployment of Supervisor-based Services in VMware vSphere FoundationInstalling services on Supervisor from a service catalog.

What it means: Supervisor Services are add-ons, such as Harbor, Contour or Velero, that run on Supervisor and serve namespaces. They are registered with a service definition and then installed on the Supervisor with configuration values.
What to understand: The flow is register the service version in vCenter, then install it on a Supervisor. Each service runs in its own namespace. Upgrades register a new version and update the installation.
How it shows up: Expect questions on the steps to add a registry or backup service for developers.
Common confusion: Thinking services are installed into each user namespace separately.

4.4.2 Deploy Virtual Machines using the VM ServiceSelf-service VMs defined in Kubernetes YAML.

What it means: The VM Service lets developers create VMs through the Kubernetes API in a vSphere Namespace. Administrators control what is available by associating VM classes, which set CPU and memory, and content libraries, which supply images, with the namespace.
What to understand: A VirtualMachine manifest names a class, an image, a storage class and network settings, and cloud-init or similar can customise the guest. VMs created this way are managed through kubectl, not edited freely in vCenter.
How it shows up: Scenario items ask what an administrator must associate with a namespace before developers can create VMs.
Common confusion: Forgetting to add a VM class or content library to the namespace.

4.4.3 Deploy Kubernetes workloads using VMware Kubernetes ServicesProvisioning VKS clusters and running workloads.

What it means: VMware vSphere Kubernetes Service, formerly the Tanzu Kubernetes Grid Service, provisions conformant Kubernetes clusters inside a vSphere Namespace. Developers then deploy pods, deployments and services to those clusters with kubectl.
What to understand: A Cluster manifest sets the Kubernetes release, control plane and worker node counts, VM classes and storage classes. Persistent volumes use storage policies exposed as storage classes. Node VMs run in the namespace and follow its quotas.
How it shows up: Expect questions on scaling workers or choosing a storage class.
Common confusion: Running application workloads directly on Supervisor when a VKS cluster is the stated target.

4.4.4 Deploy vSphere Pods and other servicesRunning pods directly on ESX through Supervisor.

What it means: vSphere Pods run containers in lightweight VMs directly on ESX hosts managed by Supervisor, without a separate Kubernetes cluster. Other services from the catalog can be deployed to support workloads.
What to understand: vSphere Pods require Supervisor with NSX networking. They suit workloads needing strong isolation with fast startup. They consume namespace quotas and storage classes like other workloads.
How it shows up: Scenario items ask which networking prerequisite is missing when pods cannot be deployed.
Common confusion: Expecting vSphere Pods on a VDS-networked Supervisor.

4.4.5 Given a scenario, describe the use case for VCF Operations OrchestratorWorkflow automation with Orchestrator.

What it means: VCF Operations Orchestrator, formerly Aria Automation Orchestrator, is a workflow engine that automates multistep tasks against vCenter and other systems using a library of workflows, actions and plug-ins.
What to understand: Use it to automate repeatable processes such as VM provisioning steps, host configuration or integration with ticketing systems. Workflows can be scheduled or triggered, and plug-ins extend reach to external systems through REST and other interfaces.
How it shows up: Expect questions where a repeatable, multi-system task should be automated.
Common confusion: Choosing a VCF Operations alert action for a complex multistep process.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

VCF Operations

Metric and property analytics for performance, capacity, cost and compliance.

Remember
Formerly Aria Operations.

Tested as
Most Operate objectives refer to it.

Trap
Using it for raw log search.
VCF Operations for Logs

Log collection, search, dashboards and log alerts.

Remember
Formerly Aria Operations for Logs.

Tested as
Explore Logs and log dashboard items.

Trap
Using it for capacity forecasts.
Integrated load balancer

Virtual IP that spreads log ingestion across Logs cluster nodes.

Remember
Production clusters use at least three nodes.

Tested as
Availability items for log ingestion.

Trap
Sending syslog to one node IP.
Collector

Component that gathers data near sources and forwards it to analytics nodes.

Remember
Formerly called a cloud proxy.

Tested as
Remote site and integration scenarios.

Trap
Thinking it stores data.
Policy

Rule set controlling alerts, capacity and compliance for object groups.

Remember
One policy applies per object by priority.

Tested as
Alerting and capacity items.

Trap
Changing the default policy for one group.
Symptom and alert definitions

Symptoms test conditions; alerts combine symptoms with recommendations.

Remember
Notifications need an outbound plugin.

Tested as
Alert workflow questions.

Trap
Skipping policy enablement.
Cost drivers and pricing cards

Provider cost inputs versus consumer charge rates.

Remember
Calculations run on a schedule.

Tested as
Showback and chargeback items.

Trap
Mixing the two.
vSphere Lifecycle Manager images

Desired-state ESX image for a whole cluster.

Remember
Baselines are not supported in 9.0.

Tested as
Lifecycle questions.

Trap
Choosing baseline remediation.
VMCA hybrid mode

Custom machine SSL certificate with VMCA-signed host certificates.

Remember
Common recommended approach.

Tested as
Certificate scenarios.

Trap
Thinking it replaces ESX certificates with enterprise ones.
Supervisor networking

VDS with a load balancer, or NSX.

Remember
vSphere Pods need NSX networking.

Tested as
Supervisor enablement items.

Trap
Expecting all services on VDS-only setups.
VM Service

Kubernetes API for creating VMs in a namespace.

Remember
Needs VM classes and a content library on the namespace.

Tested as
Developer self-service questions.

Trap
Forgetting the content library.
VMware vSphere Kubernetes Service

Provisions Kubernetes clusters in vSphere Namespaces.

Remember
Formerly the Tanzu Kubernetes Grid Service.

Tested as
Workload deployment items.

Trap
Running apps on Supervisor itself.
VCF Operations Orchestrator

Workflow engine with plug-ins for multi-system automation.

Remember
Formerly Aria Automation Orchestrator.

Tested as
Automation use case items.

Trap
Confusing it with alert actions.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

VCF Operations vs VCF Operations for Logs

Concept	Meaning	Key difference	Common trap
VCF Operations	Analyses metrics and properties.	Capacity, cost, compliance, performance.	Searching it for message text.
VCF Operations for Logs	Collects and searches log events.	Root cause from messages, audit trails.	Asking it for rightsizing.

Views, reports and dashboards

Concept	Meaning	Key difference	Common trap
View	Single data presentation such as a list or trend.	Building block for reports and dashboards.	Expecting a view to be emailed alone.
Report	Document of views and dashboards, scheduled as PDF or CSV.	Static and distributable.	Using it for live monitoring.
Dashboard	Interactive set of live widgets.	Shared with users, not scheduled.	Using it for a monthly emailed summary.

VM Service vs VKS vs vSphere Pods

Concept	Meaning	Key difference	Common trap
VM Service	VMs created by Kubernetes manifest.	Needs VM class and library.	Editing the VM freely in vCenter.
VKS cluster	Full Kubernetes cluster in a namespace.	Runs standard Kubernetes workloads.	Deploying apps to Supervisor itself.
vSphere Pod	Container in a lightweight VM on ESX.	Requires NSX networking.	Expecting it on VDS-only Supervisor.

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

Pods on VDS networking

What candidates pick
Deploy vSphere Pods on any Supervisor

Why it looks right
Supervisor supports VMs and VKS on VDS

Why it's wrong
vSphere Pods need Supervisor with NSX networking; VDS-only setups cannot run them.

Clue to watch for Networking stack named in the stem.
Notification without a channel

What candidates pick
Create a notification rule only

Why it looks right
The rule feels like the whole setup

Why it's wrong
A notification needs an outbound plugin such as SMTP or webhook, or nothing is delivered.

Clue to watch for Requirement to email or call a webhook.
Editing the default policy

What candidates pick
Modify the default policy

Why it looks right
It is the quickest place to change settings

Why it's wrong
That affects all objects; a custom group with its own policy limits the change.

Clue to watch for Only production or only one team.
Logs for capacity

What candidates pick
Use VCF Operations for Logs

Why it looks right
Logs show resource messages

Why it's wrong
Capacity forecasting needs metric history in VCF Operations, not log events.

Clue to watch for Words like forecast, remaining or rightsizing.
Baseline remediation in 9.0

What candidates pick
Attach a patch baseline

Why it looks right
It was standard in older releases

Why it's wrong
VVF 9.0 clusters use vLCM images; baselines are not supported.

Clue to watch for Version 9.0 in the scenario.
Single-node log ingestion

What candidates pick
Point syslog at the primary node

Why it looks right
It is the first node deployed

Why it's wrong
The integrated load balancer virtual IP spreads load and survives node failure.

Clue to watch for Requirement for resilient ingestion.

Answer framework

Apply these steps to Section 4 scenarios about deployment, management, operations and Supervisor workloads.

Classify the task as deploy, manage, operate or consume so you know which product and console owns it in VVF 9.0.
For operations items, decide whether the data is a metric, property or log, which tells you whether VCF Operations or Logs applies.
For alerting and policy items, trace the chain from symptom to alert, policy enablement, notification and outbound plugin.
For Supervisor items, confirm the networking stack, load balancer, storage policy, VM class and content library before picking a service.
For management items, check 9.0 changes such as licensing in VCF Operations and vLCM images before choosing an older method.

Practice question

Developers must create virtual machines through kubectl in a vSphere Namespace on a Supervisor that uses VDS networking with a supported load balancer. Their manifests fail because no image is found. What should the administrator do?

Associate a content library with VM images to the namespace Reconfigure Supervisor to use NSX networking Grant the developers the Administrator role in vCenter Install a VKS cluster in the namespace

Show the answer

Answer A. The VM Service pulls images from content libraries associated with the namespace, alongside VM classes. Without a library, manifests cannot resolve an image. NSX networking is needed for vSphere Pods, not the VM Service. Broad vCenter admin rights do not fix a missing image and break least privilege. A VKS cluster runs Kubernetes workloads but is not required for VM Service virtual machines.

Want more like this? The 2V0-16.25 practice test has questions for every domain.

Study strategy

Split this domain into its four groups and give most of your time to Operate, which holds eighteen distinct objectives. Deploy VCF Operations and VCF Operations for Logs in a lab, connect them to vCenter, and work through each bullet: a custom view and scheduled report, a shared dashboard, an alert with email notification, a policy for a custom group, a pricing card, a compliance benchmark and a Telegraf agent on one VM. In VCF Operations for Logs, write Explore Logs queries and build a dashboard from them.

Next, cover Manage. Practise roles and permissions, replace a machine SSL certificate in a lab, review license usage in VCF Operations and remediate a cluster with a vLCM image. Read the 9.0 release notes so you can spot older methods in wrong answers.

Finish with Deploy and Consume. Enable Supervisor, create a namespace with VM classes and a content library, deploy a VM through the VM Service, and provision a VKS cluster. Learn which features need NSX networking. Close with timed mixed practice across both domains.

FAQ

How much of the exam is Domain 2, Deploy, Configure, and Operate VMware vSphere Foundation (VVF)?

Broadcom does not publish weights. Section 4 holds 30 of the 47 distinct testable objectives, so a planning estimate is around 38 of the 60 items.

Why does this page count 30 objectives when the guide lists 31 bullets?

Objective 4.3 repeats the bullet on VCF Operations for Logs cluster components and deployment options, so the duplicate is counted once.

Do I need Kubernetes experience?

Broadcom's candidate description expects foundational Kubernetes knowledge. You should read manifests, use kubectl and know namespaces, storage classes and clusters.

Is VCF Operations the same as Aria Operations?

Yes. In the 9.0 release, Aria Operations was renamed VCF Operations and Aria Operations for Logs became VCF Operations for Logs.

Which Supervisor features need NSX?

vSphere Pods require NSX networking. VM Service and VKS clusters can run on a Supervisor that uses VDS networking with a supported load balancer.

Where are licenses managed in VVF 9.0?

Licensing is handled through VCF Operations and registered with Broadcom, instead of entering separate keys in each vCenter and host.

Does Orchestrator appear on the exam?

Yes. Objective 4.4.5 asks for the use case of VCF Operations Orchestrator, so know what workflows and plug-ins are used for.

Other Cloud Computing certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 2 knowledge

Practise Section 4 scenarios on VCF Operations, VCF Operations for Logs, lifecycle, certificates and Supervisor services before booking 2V0-16.25.

Take the 2V0-16.25 practice test Check your 2V0-16.25 readiness

2V0-16.25 Domain 2: Deploy, Configure, and Operate VMware vSphere Foundation (VVF)

Overview

How it's tested

Which tool does it

Build the alert

Pick the Supervisor service

Objectives 30

High-yield concepts

VCF Operations

VCF Operations for Logs

Integrated load balancer

Collector

Policy

Symptom and alert definitions

Cost drivers and pricing cards

vSphere Lifecycle Manager images

VMCA hybrid mode

Supervisor networking

VM Service

VMware vSphere Kubernetes Service

VCF Operations Orchestrator

Side by side

VCF Operations vs VCF Operations for Logs

Views, reports and dashboards

VM Service vs VKS vs vSphere Pods

Exam traps

Pods on VDS networking

Notification without a channel

Editing the default policy

Logs for capacity

Baseline remediation in 9.0

Single-node log ingestion

Answer framework

Practice question

Checklist

Study strategy

FAQ

Other Cloud Computing certifications

Test your Domain 2 knowledge

Keep going

Overview

How it's tested

Which tool does it

Build the alert

Pick the Supervisor service

Objectives 30

High-yield concepts

VCF Operations

VCF Operations for Logs

Integrated load balancer

Collector

Policy

Symptom and alert definitions

Cost drivers and pricing cards

vSphere Lifecycle Manager images

VMCA hybrid mode

Supervisor networking

VM Service

VMware vSphere Kubernetes Service

VCF Operations Orchestrator

Side by side

VCF Operations vs VCF Operations for Logs

Views, reports and dashboards

VM Service vs VKS vs vSphere Pods

Exam traps

Pods on VDS networking

Notification without a channel

Editing the default policy

Logs for capacity

Baseline remediation in 9.0

Single-node log ingestion

Answer framework

Practice question

Checklist

Study strategy

FAQ

Related domains

Other Cloud Computing certifications

Test your Domain 2 knowledge

Keep going