Exam 2V0-15.25 Topic 4 Question 27 Discussion
Actual exam question for VMware's 2V0-15.25 exam
Question #: 27
Topic #: 4
Question #: 27
Topic #: 4
An administrator has successfully deployed and configured the Application Monitoring Telegraf Agent to 30 virtual machines through VMware Cloud Foundation (VCF) Operations.
After 24 hours, the administrator is alerted to the fact that no additional data has been collected since the agents were deployed on the virtual machines.
What could be the possible cause of the issue?
After 24 hours, the administrator is alerted to the fact that no additional data has been collected since the agents were deployed on the virtual machines.
What could be the possible cause of the issue?
Suggested Answer: A Vote an answer
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-is clock 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.
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.
by Andrew at Oct 15, 2026, 06:23 AM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).