A company has written a script that creates a log bundle from the Cisco DNA Center every day. The script runs without error and the log bundles are produced.
However, when the script is run during business hours, people report poor voice quality of phone calls. What explains this behavior?
When the script runs and generates logs, it causes the CPU on the network controller to spike. This spike could lead to delays in processing tasks that are crucial for managing network resources and maintaining quality of service (QoS). Although the network controller is primarily involved with the control plane, CPU spikes can slow down the overall system's ability to manage network functions effectively, thereby causing poor voice quality as a result of delays in packet forwarding.
Answer is C
If speed and duplex settings are incorrect, the problem should appears all the time. During office hours, users are using the IP phones, if the application is running on the voice LAN accidentally, it will impact the quality of the voice
The voice traffic uses QoS so it should not be affected due to other traffic due prioritization. So I believe the answer is D.
Not by default. You have to turn on autoQOS on Cisco switches. And who knows - this is most likely in a DC in this scenario. This question is also sorta far fetched. There are almost never voice issues on a LAN but that's my .02
Definitely D, on our network we avoid running scripts during day time because it might caused to increase the usage of the resources which might affect the performance of the device where you are getting the logs. C is wrong, it is not advisable to mixed up management traffic to a voice traffic, id rather have different vlan for managing the devices.
is'nt it correct that Network controller does not forward voice packets? so it does not effect voice trafic?
I'd go for C since it makes sense although I doubt any one would do that in the real world. The other choice D doesn;t seems to be very relevant since the network controller is supposed to impact the control plane not the data plane, thus the data plan should still forward without interruptions/drops.
Ans is C
Delay & jitter are not on the 'subnet' level, which is a L3 thing. C is worded by someone who has no idea about how networks operate. It has to be D.
For me it's D.
It is possible that the issue is caused by D. Generating the logs could cause the CPU on the network controller to spike, which could lead to delays in forwarding the voice IP packets. This could result in poor quality of phone calls during the time when the script is running. However, it is also possible that the issue could be caused by other factors, such as network congestion or issues with the configuration of the voice VLAN or the speed and duplex settings. It would be useful to gather more information about the network and the script to determine the root cause of the problem.
I don't think that would be it. The network controller isn't responsible for forwarding packets. It's responsible for making routing decisions. Packet forwarding is data plane while network controllers are control plane. Even if the data plane and control plane were on the same router, the data plane should be happening in the line card hardware under normal circumstances, not the CPU.
speed would case problems always, DNA doesnt control traffic, so its clearly C
answer is 'C'. DNAC is a controller, control plane only. Not responsible for forwarding traffic. If DNAC running impacts voice, which is normally isolated in its own VVLAN, then DNAC must be in the VVLAN
Well, they don't give us any details about the VLAN configurations so we must asume the they are configured following the best practices. That is, not mixing voice and data VLANS. If that's the case, then C is not correct. On the other hand, although the controller does not handle the data plane. Depending on the type of packet, it may require to go to the control plane for further processing and here is where D comes in. Again, if they don't say the VLANs are mixed, we must asume they're correctly configured.
I think the hint here is that controllers usually doens't forward traffic on data plane. So, any cpu spike woulnd't cause any issue on the packet forwarding. Based on that my answer would be C.
I’m going with D on this one.
Should be C, it seems to be the more logical option
The Answer is C. TCP and UDP should be separated to prevent such issues and is best practice to do so. You can bet your life savings the answer is C. lol
Answer is C.
Answer is C, it says the script is running in Voice Vlan it says in clear that script is running in Voice Vlan and the same subnet, and not Data Vlan, so if script is running in Voice Vlan, even if there is QoS, it could cause jitter and drop backets depends on traffic.
Answer is C. DNA is just the control plane, and does not have anything with the dataplane.