Q: 3
An administrator has noticed occasional performance degradation during peak usage times and
needs to address this issue proactively by creating a mechanism that doesn't give data or outputs too
often to overload the team.
Which of the following steps is required to create the mechanism in VMware Cloud Foundation (VCF)
Operations?
Options
Discussion
My pick: A here. Custom alert with metric, threshold, and duration lets you filter out short spikes and stop flooding the team with noise. Not as confident if it's about dashboards but feels like alerts are the proactive part. Agree?
A . The question's trick is about reducing alert noise, not just scheduling alerts for off-peak (trap in D). Setting metric, threshold, and duration (A) filters out the spammy alerts. Seen this on other exam practice questions.
Option A. The trap is thinking D solves the overload, but delaying alerts misses real-time issues. Metric plus threshold plus duration is what VMware recommends from similar exam reports.
A Only A covers the need to set metric, threshold, and duration to reduce alert noise without missing real issues.
Honestly, both A and D could make sense depending on how you read the question, but I think A fits better. Setting metric, threshold, and duration helps avoid alert spam while still catching real issues. Not totally sure though.
A for sure. Had something like this in a mock and it was all about using metric, threshold, and duration to tune how often alerts fire. That way, the team only gets notified if it's actually a persistent issue, not every tiny spike. Way less noise than default alerts or relying on dashboards alone. Pretty confident but open to other thoughts if someone disagrees.
I've seen similar questions on practice exams and the official study guide. A is correct since only configuring metric, threshold, and duration gives you that level of proactive control to avoid alert overload. Default settings or time-based alerts (B/D) don't really solve the main problem here. If anyone thinks differently, official docs or lab tests would help.
Pretty sure A here. D is tempting but it's kind of a decoy since just shifting alerts to off-peak doesn't really solve alert fatigue if they're triggered constantly. Customizing by metric, threshold, and duration keeps the noise down. Open to other thoughts though if I missed something.
D imo
Its A, saw a similar question in a practice test and it was definitely about setting metric, threshold, and duration.
Be respectful. No spam.