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?
D imo
I still think C could be valid here, since a dashboard gives visibility without spamming alerts. If the team wants to monitor trends at their own pace, wouldn't that avoid alert overload too? Correct me if I'm missing something obvious.
C/D? Both look reasonable for reducing overload if timing is key, not sure which fits better.
C or D? If the requirement is just to not overload the team, wouldn't alerting during off-peak hours (D) technically avoid that too? Though if it's about being "proactive" vs just when, the wording matters a lot. Does the question specify whether alerts need to be immediate or could be delayed?
Be respectful. No spam.