2V0-15.25 Exam Dumps : VMware Certified Professional - VMware Cloud Foundation 9.0 Support

Application Monitoring in VCF Operations uses Telegraf agents running inside virtual machines. These agents forward metrics to theCloud Proxy, which then sends them to the Operations analytics cluster. One of the most common reasons an agent stops reporting data—especially exactly24 hoursafter deployment—isclock drift or time mismatchbetween the VM (running the Telegraf agent) and the Cloud Proxy.

VCF Operations enforcesstrict timestamp validation. If the timestamps from the agent are outside the acceptable drift window, the Cloud Proxyrejectsincoming data as invalid. In this case, the Telegraf agents appear installed and functional, but no new metrics are received by the analytics engine.

This is a well-known issue documented in VMware Aria/VCF Operations agent-based monitoring, where:

Agents send metrics with local system time.

Cloud Proxy enforces time validation to prevent corrupt metric ingestion.

A drift >5 minutes commonly results inzero data collectiondespite healthy connectivity.

Options B and C cannot stop data flow after exactly 24 hours; they would preventinitialcollection. Option D (virtual hardware/tools compatibility) affects VM operations butnotTelegraf metric time-stamp validation.

TheGlobal Inventory List (GIL)is only available whenmulti-vCenter SSO domain linkingis configured. In VMware Cloud Foundation, themanagement domain vCenteris deployed first and becomes theroot vCenterfor global inventory data. For workload domains, their vCenter Servers must beregistered into the same SSO domainandlinkedwith the management-domain vCenter in order for the global inventory data (VMs, hosts, clusters, content libraries) to appear.

If a workload domain vCenter is not SSO-linked, it operates in its own identity domain, and thereforecannot access or present Global Inventory, resulting in exactly the symptom described: the management domain vCenter shows the GIL, while the workload domain vCenter does not.

Option B (Supervisor Management) relates to vSphere with Tanzu and has no impact on Global Inventory.

Option C (inventory sync) is incorrect—there is no manual sync required; GIL relies entirely on SSO linking.

Option D (VIDB) is not related to vCenter linking or inventory visibility; it is used by VCF Identity Broker.

Therefore, the reason the Global Inventory is missing from the workload domain vCenter is thatSSO/vCenter Linking has not been configured, which is required for federation across all VCF vCenters.

In VMware Cloud Foundation 9.0, supplemental storage such as NFS is fully supported for workload domains when configured correctly. When an NFS datastore mounts successfully in vSphere but users cannot write data, the issue almost always lies in theexport permissions on the NFS server. vSphere will allow mounting a read-only NFS export, but write operations will fail silently at the VM or guest OS level.

VCF documentation confirms that ESXi requires explicitread/write export permissions, typically configured per-host or by IP subnet, on the NFS server. Even if network connectivity and VM-level access appear healthy, incorrect server-side permissions prevent ESXi from executing write operations.

Option A is incorrect because NFS servers are not validated by the HCL for write capability.

Option B (rebooting the host) is unnecessary and unrelated to permission enforcement.

Option D (MTU mismatch) may cause performance issues, not write-access failures.

Thus, the next troubleshooting step is to verify that the ESXi hosts haveread/write accesson the NFS share, makingCthe correct answer.