MENU
The web console is showing the status of a network router as ''down'', however the node is up and running. Which two of the following causes could be creating the issue? (Choose two.)
Suggested Answer: B, D
Get Premium Hybrid Cloud Observability Network Monitoring Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
AR
Arleen
10 months ago
Nah, I don't think A is the issue, the agent should still report correctly.
ON
Ona
10 months ago
I agree with B, ICMP blocking is a classic problem.
ER
Ernest
10 months ago
Wait, how can the router be up if the console says down? Sounds weird.
MA
Marya
10 months ago
Definitely B and D, ICMP and SNMP issues are common.
PE
Peggie
10 months ago
I think C could also be a factor, dependencies can mess things up.
KA
Karma
11 months ago
I feel like the dependency configuration could play a role too, but I can't recall if C is a common cause in these scenarios.
TA
Tayna
11 months ago
I practiced a question like this before, and I think D about SNMP blocking might also be a possibility.
SA
Sabra
11 months ago
I'm not entirely sure, but I think ICMP blocking could definitely cause the router to show as down, so B seems likely.
NI
Nicolette
11 months ago
I remember something about agent connection issues, so maybe A could be one of the answers?
GO
Golda
12 months ago
I feel pretty confident about this one. The agent connection status and the ICMP/SNMP blocks are the two most probable causes. I'll focus on those in my answer.
MA
Margot
12 months ago
I'm a bit confused on the node dependency part. Does that mean the router is set up as a parent node? I'll have to double-check that.
CL
Claudio
12 months ago
I'm guessing it could be either the agent connection status or the ICMP/SNMP being blocked. Those seem like the most likely culprits.
CO
Coletta
1 year ago
Okay, let's see. The router is up, but the web console is showing it as down. That's definitely an issue.
WH
Whitley
1 year ago
Hmm, this seems like a tricky one. I'll need to think through the possible causes carefully.
LI
Lisbeth
1 year ago
Option C is an interesting one too - if the router is set up as a parent in a dependency, that could be causing the 'down' status to propagate. But B and D seem more likely in this case.
ED
Eden
1 year ago
B) ICMP is blocked between the device and the polling engine
PE
Penney
1 year ago
A) agent connection status with the polling engine is 'down'
HE
Heike
1 year ago
Haha, reminds me of the time our network team 'fixed' a 'down' router by unplugging it and plugging it back in. Gotta love those easy solutions!
BR
Brandon
1 year ago
B) ICMP is blocked between the device and the polling engine
DE
Denae
1 year ago
A) agent connection status with the polling engine is 'down'
AD
Adolph
1 year ago
I'm not sure about ICMP or SNMP, but I think A) agent connection status could also be a cause.
JA
Jacqueline
1 year ago
I was thinking the same thing! Blocking ICMP and SNMP are the classic ways to make a healthy network device look 'down' to the monitoring system.
BE
Beatriz
1 year ago
B) ICMP is blocked between the device and the polling engine
TO
Tonja
1 year ago
A) agent connection status with the polling engine is 'down'
EU
Eun
1 year ago
B) ICMP is blocked between the device and the polling engine
LA
Larue
1 year ago
A) agent connection status with the polling engine is 'down'
DY
Dyan
1 year ago
Options B and D sound like the most likely culprits here. If the monitoring engine can't ping the router or access its SNMP data, that would definitely explain the 'down' status.
LA
Lavonna
2 years ago
I agree with Refugia, but I also think D) SNMP could be blocked.
RE
Refugia
2 years ago
I think it could be B) ICMP is blocked.