A technician is troubleshooting a network switch that seems to stop responding to requests intermittently whenever the logging level is set for debugging. Which of the following metrics should the technician check to begin troubleshooting the issue?
The reason it isn't Jitter is because:
In networking, jitter refers to the variation in the delay between when data packets are transmitted and when they are received. It's essentially the inconsistency or fluctuation in latency.
Because we aren't transmitting or receiving any data over the network, everything from the Logs is being done locally. That's why it has to do with the hardware of the local machine and wouldn't be in regards to a networking term like Jitter.
I think the key here is that they said the problem with the switch was that it entirely stopped responding to requests at times. It would be more likely to be Jitter if they had said that the ping requests were fluctuating in speed which were causing the switch requests to time out.
When the logging level is set to debugging, it generates extensive log messages, which can increase the processing load on the network switch, especially if the switch has limited resources. High CPU utilization can cause the switch to become unresponsive or slow in processing network traffic, leading to intermittent issues with responding to requests.
The receiving interface uses the same calculation. If it derives a different value, the frame is rejected. 183 is a high number errors getting rejected.
CPU can stop responding from the overload of requests occurring, debug utilizes a full assembly of tests that are only useful for the debug phase & can take up a lot of processing that can interfere with mainline production.
Debugging mode is a high level of logging, which means that the switch generates a large volume of logs, and it requires additional processing power to generate and process the logs. If the CPU utilization on the switch is too high, it may cause the switch to stop responding to requests intermittently.
- CPU utilization: High CPU utilization can indicate that the switch is overwhelmed with processing, which could cause it to stop responding to requests.
CPU utilisation is more of a metric. Additionally it has stated that it is only happening when the logging level is set for debugging. Given this will heavily utilise the CPU then that seems the logical thing to check
I am agreeing with Tyrial on this. The question asked for a metric to look at for what is causing the switch issues. Audit logs have to more with the accounting aspect of users on a network and not metrics that determine high system usage that would cause system sluggishness.
I'm pretty sure this should be A) Audit logs. If the logging level is configured to send too many logs to the SNMP server it can cause the device's throughput to suffer
Audit logs is wrong for a few reasons. One, the question is asking which metric to review. Logs are not metrics. Furthermore audit logs are for authentication/authorization which won't help with identifying the problem.
Looking at CPU utilization will help narrow down the problem.
This section is not available anymore. Please use the main Exam Page.N10-008 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
GeekSpunk
Highly Voted 2 years, 3 months agoEumousten
1 year, 11 months agodcdc1000
Highly Voted 2 years, 8 months agoJkeller
Most Recent 7 months, 3 weeks agoTheMichael
5 months, 2 weeks agoTheMichael
5 months, 2 weeks agoJaeide__X
7 months, 3 weeks agoSarmad_Mansour
7 months, 2 weeks agophoenix98
1 year agoMehsotopes
1 year agorah555
1 year, 6 months agofamco
1 year, 7 months agoStevenElev11n
1 year, 9 months agoJakeCharles
1 year, 9 months agoAaronS1990
2 years, 3 months agoalayeluwa
2 years, 4 months agowaqdhiyo
2 years, 8 months agoRRabbit_111
2 years agoFreddysoft
1 year, 10 months agoArchEpic
2 years, 8 months agoTimock
2 years, 9 months agoTyrial
2 years, 8 months agoitssnowyseason
2 years, 9 months ago