Study guide
16.1 Configure Service Discovery
VMware vSphere Foundation 9.0 Administrator VCP-VVF, 2V0-16.25
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Preparation Strategy
1.1 Exam Format, Passing Standard & Blueprint Structure 1.2 Preparation Strategy & Hands-On Lab Setup
2 Chapter 2: Virtualization & ESXi Host Fundamentals
2.1 Hypervisor Architecture & ESXi Operating Model 2.2 ESXi Deployment, DCUI & Initial Host Configuration 2.3 Workload Consolidation & Private Cloud Economics
3 Chapter 3: vCenter Server & Cluster Management
3.1 vCenter Server Appliance (VCSA) Architecture & Deployment 3.2 vSphere High Availability (HA) & Admission Control 3.3 Distributed Resource Scheduler (DRS) & EVC Configuration
4 Chapter 4: Virtual Machine Operations & Resource Management
4.1 Virtual Machine Provisioning, Templates & Content Libraries 4.2 Resource Allocation: Shares, Reservations & Limits 4.3 vMotion, Storage vMotion & Snapshot Management 4.4 Content Libraries, Publication & Template Versions
5 Chapter 5: vSphere Storage Architecture & Traditional Datastores
5.1 Block Storage Architecture, Fibre Channel & VMFS Datastores 5.2 NFS Datastores, Software iSCSI & Multipathing (NMP) 5.3 Storage Policy-Based Management (SPBM) Framework
6 Chapter 6: VMware vSAN Architecture & Storage Policies
6.1 vSAN Core Architecture: OSA vs Express Storage Architecture (ESA) 6.2 Deploying & Configuring a vSAN Cluster 6.3 vSAN Storage Policies, Resilience (FTT) & Fault Domains 6.4 vSAN Space Efficiency & Capacity Accounting
7 Chapter 7: vSphere Networking & Traffic Management
7.1 Standard Switches (vSS) vs Distributed Switches (vDS) 7.2 Port Groups, VMkernel Adapters & Traffic Isolation 7.3 NIC Teaming, Load Balancing, VLANs & NIOC
8 Chapter 8: VVF Deployment & Supervisor Configuration
8.1 VMware vSphere Foundation 9.0 Stack & Deployment Prerequisites 8.2 End-to-End VVF Deployment Workflow 8.3 Enabling & Configuring the vSphere Supervisor
9 Chapter 9: Identity, Licensing & Security Management
9.1 vCenter Single Sign-On (SSO), Identity Federation & RBAC 9.2 VVF 9.0 Core-Based Licensing & License Management 9.3 VMware Certificate Authority (VMCA) & TLS Configuration 9.4 Workload & Infrastructure Encryption
10 Chapter 10: Lifecycle Management with vLCM
10.1 vSphere Lifecycle Manager (vLCM) Image Architecture 10.2 Base Images, Vendor Add-ons & Hardware Support Managers (HSM) 10.3 Host Compliance Checks, Staging & Cluster Remediation
11 Chapter 11: VCF Operations: Performance, Capacity & Alerts
11.1 VCF Operations Architecture, Node Types & Adapters 11.2 Dashboards, Custom Views, Metrics & Reports 11.3 Capacity Planning, Rightsizing & Alert Policies
12 Chapter 12: VCF Operations for Logs & Compliance
12.1 VCF Operations for Logs Architecture & Ingestion 12.2 Interactive Log Analytics, Query Syntax & Dashboards 12.3 Security Hardening Compliance & Storage/App Monitoring
13 Chapter 13: Workload Consumption & Automation
13.1 vSphere VM Service: Classes, Images & Declarative Deployment 13.2 VMware Kubernetes Service & Workload Clusters 13.3 VCF Operations Orchestrator Workflows & Automation 13.4 Supervisor Services & vSphere Pods
14 Chapter 14: Operations Evidence, Policies & Financial Reporting
14.1 Metrics, Properties & Logs 14.2 Custom Views & Scheduled Reports 14.3 Effective Policies, Groups & Overrides 14.4 Cost Drivers, Pricing & Showback
15 Chapter 15: Log Integrations & Shared Operational Views
15.1 VVF Integrations & Log Events in Operations 15.2 Logs Dashboards, Queries & Sharing
16 Chapter 16: Guest Services & Application Monitoring
16.1 Configure Service Discovery 16.2 Application & Guest Monitoring
16.1 Configure Service Discovery
Key Takeaways Explain This Topic AI
Service Discovery identifies supported services and relationships; it does not prove application transaction health.
Credential-less discovery still requires compatible Tools/plugins and authorized integration access.
Verify a known service/port and current timestamp on representative VMs.
Use release-specific troubleshooting only after matching the documented failure condition.
Last updated: October 2026
Discovery Is a Specific Monitoring Task
Service Discovery identifies supported services and communication relationships inside guest VMs. It helps an operator understand what runs where and how tiers relate. This differs from collecting hypervisor CPU/memory metrics and from obtaining detailed application response-time or transaction measurements. Discovering a database process does not establish that the database serves requests correctly.
Operations can use VMware Tools-based discovery paths, including supported credential-less discovery . Credential-less means that a supported guest communication/plugin mechanism avoids separately supplied guest credentials for that discovery mode. It does not mean zero software, zero privileges or zero resource use. Tools/plugin compatibility and the required vCenter privileges still matter.
Validate the Prerequisites
Identify the supported Windows/Linux guest types, VMware Tools or open-vm-tools version, Service Discovery plugin and Operations/vCenter versions. Confirm that the VM is powered on, its Tools service is healthy and the Operations integration can discover the VM. For Linux, the supported open-vm-tools discovery plugin/package must be present where required; a healthy basic Tools heartbeat alone is insufficient.
- Layer Verification Why it matters
- Inventory The VM is present in the intended vCenter account Discovery needs the correct managed object
- Guest Supported OS and healthy Tools/plugin The communication path must expose discovery data
Authorization Required integration/guest-operation permissions Read-only inventory access may not authorize every discovery task
Discovery configuration Supported adapter/options and target scope Disabled or incorrectly scoped discovery produces no services
Result Current service objects and relationships Old objects can remain after collection stops
Keep a representative set of test VMs: one supported guest with a known web service, one with a database and one that should not expose that service. This allows you to check both missing detections and false assumptions. Do not select hundreds of production VMs before confirming the basic configuration with a small sample.
Configure and Observe
Configure the supported Service Discovery integration/options and collection scope for the installed Operations release. Select the correct vCenter connection and collector where applicable. Use credential-less discovery only where its prerequisites are satisfied; use a supported credentialed mode when needed rather than assuming every guest can use the same mechanism.
Allow discovery to complete, then inspect the selected VM's discovered services and relationship views. Compare the service name and port with the actual guest configuration. A process can listen on a nondefault port, multiple processes can share a service family and a service can be configured but not currently running. A failed signature match is not proof that no application exists.
Interpret Relationships
A relationship map is evidence of observed/discovered communication, not a complete architecture contract. Sampling windows, encrypted protocols, firewalls and inactive connections can affect visibility. Use the map to guide maintenance and troubleshooting, then confirm critical dependencies with application owners and additional telemetry.
For example, a front-end VM may depend on a database VM that also serves a nightly batch application. A discovery run outside the batch window may show only the front-end relationship. Before shutting down the database VM, check the full operating cycle and documented application dependencies. A missing line in one map does not authorize a maintenance outage.
Diagnose Failed Collection
When discovery fails for one VM, inspect its guest/plugin health and relevant discovery task/error before changing every adapter. When all VMs in an account fail, inspect common permissions, account configuration, vCenter connectivity and collection state. Preserve the exact error; an authentication failure, unsupported guest and plugin synchronization problem are different conditions.
Broadcom KB 427145 documents credential-less discovery issues involving particular VMware Tools builds and recommends the Linux open-vm-tools discovery plugin path where applicable. Treat this as a version-specific diagnosis. Do not indiscriminately edit the vCenter Managed Object Browser or delete discovery namespaces on healthy VMs because a troubleshooting article describes that remedy for a specific condition.
Keep Discovery Current
Services move, ports change and VMs are replaced. Review timestamps and stale service objects after deployments and upgrades. Verify the intended scope when adding a vCenter or changing group/tag rules. Restrict discovery outputs according to the team's access needs because service names and dependency maps can reveal sensitive application topology.
A useful lab completion record names the supported guest and Tools/plugin versions, integration scope, discovered service/port, relationship evidence and the collection timestamp. Test service stop/start in a disposable guest and observe how the result changes. This proves discovery behavior rather than merely proving that a configuration screen was saved.
For the exam, distinguish a request to identify services/dependencies from a request to monitor application-specific performance . The former calls for discovery; the latter often requires application monitoring and its own agent/plugin configuration. Both can be used together, but neither should be described as automatically delivering the other's full function.
Review Takeaways
Service Discovery identifies supported services and relationships; it does not prove application transaction health.
Credential-less discovery still requires compatible Tools/plugins and authorized integration access.
Verify a known service/port and current timestamp on representative VMs.
Use release-specific troubleshooting only after matching the documented failure condition.