Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

SolarWinds Exam SCP-NPM Topic 1 Question 28 Discussion

Actual exam question for SolarWinds's SCP-NPM exam
Question #: 28
Topic #: 1
[All SCP-NPM Questions]

Your network has critical devices on the opposite side of a WAN link from you SolarWinds server. You do not want alerts about the devices if the router (name = ''target'') that connects your SolarWinds server to the remote site is down. How do you configure Alert Suppression?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Jerilyn
5 months ago
I see your point, Danica. I think Hildegarde's answer makes more sense in this scenario. We should suppress alerts when the Interface Status is down.
upvoted 0 times
...
Danica
5 months ago
But if the router is down, wouldn't we want to suppress alerts when the Interface Status is down as well?
upvoted 0 times
...
Gaston
5 months ago
Option C all the way. Monitoring the interface status is the most logical approach here. Plus, it's just more efficient than checking the node status, which could be misleading.
upvoted 0 times
Felix
3 months ago
Definitely, option C is the way to go. It's important to suppress alerts based on the interface status to avoid unnecessary notifications.
upvoted 0 times
...
Corrina
3 months ago
Yeah, focusing on the interface status of the router is key. It's more accurate than just looking at the node status.
upvoted 0 times
...
Mayra
3 months ago
I agree, option C seems like the best choice. Monitoring the interface status is crucial for detecting issues.
upvoted 0 times
...
Hayley
3 months ago
Option C seems like the most efficient choice for this scenario.
upvoted 0 times
...
Rikki
3 months ago
Yeah, it makes sense to focus on the interface status for accurate alerts.
upvoted 0 times
...
Lavelle
4 months ago
I agree, monitoring the interface status is definitely the way to go.
upvoted 0 times
...
...
Kerry
5 months ago
Haha, I almost went with option D. Like, 'Hey, let's just ignore the device if it's completely offline!' Nice try, SolarWinds, but I'm not falling for that one.
upvoted 0 times
Sheron
4 months ago
Lizette: Definitely, better to be safe than sorry.
upvoted 0 times
...
Reena
4 months ago
I agree, we don't want to miss important alerts.
upvoted 0 times
...
Lizette
4 months ago
Yeah, I think option A is the safer choice.
upvoted 0 times
...
Nana
4 months ago
Yeah, option D seems a bit risky. We don't want to ignore the device completely if it's down.
upvoted 0 times
...
Rolande
4 months ago
I think option A is the way to go. It only suppresses the alert when the Interface Status is 'Warning'.
upvoted 0 times
...
Ivan
5 months ago
I know right, option D seems a bit extreme.
upvoted 0 times
...
...
Hildegarde
5 months ago
I disagree, I believe the answer is C) Suppress alert when any of the following apply: Node Name is equal to ''target'' / Interface Status is equal to ''Down''
upvoted 0 times
...
Ilda
5 months ago
I agree with Lashonda. Option C is the way to go. Monitoring the interface status instead of the node status is a more accurate way to detect the router being down.
upvoted 0 times
Brendan
4 months ago
I agree, monitoring the interface status will give a more precise indication of the router being down.
upvoted 0 times
...
Rima
4 months ago
I think Option C is the best choice. Monitoring the interface status is more accurate.
upvoted 0 times
...
...
Danica
5 months ago
I think the correct answer is A) Suppress alert when all of the following apply: Node Name is equal to ''target'' / Interface Status is equal to ''Warning''
upvoted 0 times
...
Lashonda
6 months ago
Option C is the correct answer. Suppressing alerts when the router's interface is down makes the most sense, as that's the key condition we want to monitor.
upvoted 0 times
Crista
5 months ago
User 2
upvoted 0 times
...
Barb
5 months ago
User 1
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77