U.S. Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Linux Foundation PCA Exam - Topic 2 Question 4 Discussion

What is considered the best practice when working with alerting notifications?
B) Have as few alerts as possible by alerting only when symptoms might become externally visible.
A) Minor alerts are as important as major alerts and should be treated with equal care.
C) Have as many alerts as possible to catch minor problems before they become outages.
D) Make sure to generate alerts on every metric of every component of the stack.

Linux Foundation PCA Exam - Topic 2 Question 4 Discussion

Actual exam question for Linux Foundation's PCA exam
Question #: 4
Topic #: 2
[All PCA Questions]

What is considered the best practice when working with alerting notifications?

Show Suggested Answer Hide Answer
Suggested Answer: B

The Prometheus alerting philosophy emphasizes signal over noise --- meaning alerts should focus only on actionable and user-impacting issues. The best practice is to alert on symptoms that indicate potential or actual user-visible problems, not on every internal metric anomaly.

This approach reduces alert fatigue, avoids desensitizing operators, and ensures high-priority alerts get the attention they deserve. For example, alerting on ''service unavailable'' or ''latency exceeding SLO'' is more effective than alerting on ''CPU above 80%'' or ''disk usage increasing,'' which may not directly affect users.

Option B correctly reflects this principle: keep alerts meaningful, few, and symptom-based. The other options contradict core best practices by promoting excessive or equal-weight alerting, which can overwhelm operations teams.


Verified from Prometheus documentation -- Alerting Best Practices, Alertmanager Design Philosophy, and Prometheus Monitoring and Reliability Engineering Principles.

Contribute your Thoughts:

0/2000 characters
Amber
2 months ago
D is too much! We need to prioritize alerts wisely.
upvoted 0 times
...
Murray
2 months ago
I feel overwhelmed with too many alerts. B is definitely better.
upvoted 0 times
...
Lauran
3 months ago
A is important too. Minor alerts can prevent bigger problems.
upvoted 0 times
...
Bok
3 months ago
I agree, B makes sense. Only alert on real issues.
upvoted 0 times
...
Myra
3 months ago
I think B is the best choice. Less noise means better focus.
upvoted 0 times
...
Nathalie
3 months ago
I think B strikes the right balance!
upvoted 0 times
...
Octavio
3 months ago
D just sounds like a recipe for alert fatigue.
upvoted 0 times
...
Cristina
4 months ago
B) Definitely the way to go. Less is more when it comes to effective alerting.
upvoted 0 times
...
Sabra
4 months ago
Haha, D) sounds like a recipe for alert fatigue. Good luck keeping up with all those notifications!
upvoted 0 times
...
Marion
4 months ago
D) Wow, that's a bit overkill. Monitoring every single metric is just going to create a mess.
upvoted 0 times
...
Julieta
4 months ago
A) I'm not sure I agree with that. Major and minor alerts should be prioritized differently.
upvoted 0 times
...
Cecilia
5 months ago
C) I disagree, more alerts are better! Catch those problems early before they cause any real damage.
upvoted 0 times
...
Blondell
5 months ago
B) Sounds like the most reasonable approach to me. Fewer alerts means less noise to sift through.
upvoted 0 times
...
Michal
5 months ago
I’m leaning towards D, but I remember someone mentioning that generating alerts for every metric could overwhelm the team. It’s tricky!
upvoted 0 times
...
Carlton
5 months ago
I think we practiced a question similar to this, and I recall that having fewer, more meaningful alerts is generally better. So, B sounds familiar.
upvoted 0 times
...
Jess
5 months ago
I'm not entirely sure, but I feel like we talked about the importance of prioritizing alerts. A seems a bit excessive to me.
upvoted 0 times
...
Kayleigh
5 months ago
I'm feeling pretty confident about this one. The answer is B - have as few alerts as possible, but make sure they're for the critical stuff that could cause real problems. Gotta be selective with alerts to avoid alert fatigue.
upvoted 0 times
...
Yasuko
6 months ago
Okay, I think I've got this. The key is to focus on the most important alerts that could lead to major outages. Minor issues can be handled through other monitoring, but the alerts need to be strategic and impactful.
upvoted 0 times
...
Annamae
6 months ago
I'm a bit confused on this one. Should we really be generating alerts for every single metric? That seems like it could get out of hand quickly. I'll need to review my notes on best practices for alerting.
upvoted 0 times
...
Jose
6 months ago
A little surprised that people think minor alerts aren't important.
upvoted 0 times
...
Jesus
6 months ago
B is definitely the way to go! Less noise, more focus.
upvoted 0 times
...
Melina
6 months ago
I remember discussing how too many alerts can lead to alert fatigue, so I think B might be the right approach.
upvoted 0 times
...
Jin
7 months ago
C could work, but it might create alert fatigue.
upvoted 0 times
...
Alba
7 months ago
I disagree, minor alerts can prevent bigger issues later.
upvoted 0 times
...
Xuan
7 months ago
I'm pretty sure the best practice is to have as few alerts as possible, but make sure they're for the really critical issues. Catching problems early is important, but too many alerts can be overwhelming.
upvoted 0 times
...
Edmond
7 months ago
Hmm, this is a tricky one. I'll need to think carefully about the trade-offs between alert volume and alert importance.
upvoted 0 times
Yvette
1 month ago
Balancing is key. Maybe a mix of A and B?
upvoted 0 times
...
Hershel
1 month ago
True, but D is overkill. We can't monitor everything!
upvoted 0 times
...
Man
2 months ago
But what if we miss something critical? C seems risky.
upvoted 0 times
...
Julian
2 months ago
Agreed! Too many alerts can lead to alert fatigue.
upvoted 0 times
...
Gail
2 months ago
I think B makes the most sense. Less noise is better.
upvoted 0 times
...
...

Save Cancel