Exam 200-301 topic 1 question 1147 discussion

Database synchronization traffic: This type of traffic is typically not time-sensitive but can consume significant bandwidth. It can be controlled using shaping (d) to limit the bandwidth it uses and prevent it from overwhelming the network. Standard web browsing traffic: This is generally considered as best-effort traffic, so it would match with best effort (a). It means that the network will attempt to deliver this traffic but without any guarantees of bandwidth, delay, or delivery. Video traffic: Video traffic requires a steady stream of data and can be sensitive to variations in delay (jitter). Therefore, it might require policing (b) to drop packets that exceed the contract, ensuring fair usage of network resources. VoIP traffic: Voice over IP (VoIP) is very sensitive to delay and jitter, so it is often given high priority on the network. It matches with priority queue ©, which ensures these packets are given precedence over other types of traffic.

Coorect me if I wrong but it should be: Database syn traffic - shaping Standart web - best effort Video - policing VoIP - priorty queue

1. Database synchronization traffic - Shaping 2. Standard web browsing traffic - Best effort 3. Video traffic - Policing 4. VoIP traffic - Priority queue policing will drop packets to maintain the latency which is what streaming needed. shaping provides low packet loss, that's what database needed.

Database synchronization traffic → Shaping Database synchronization is typically delay-tolerant but bandwidth-intensive, so traffic shaping can help manage it effectively without overwhelming the network. Standard Web browsing traffic → Best Effort Standard web traffic doesn't require special handling, so it is typically delivered using the best effort method. Video traffic → Policing Video traffic often requires consistent bandwidth but can tolerate some packet loss if necessary, so policing can be used to ensure it doesn’t exceed the allocated bandwidth. VoIP traffic → Priority Queue VoIP traffic is very sensitive to latency and jitter, making it ideal for priority queueing to ensure real-time delivery.

Correct options: 1. Database synchronization traffic - Shaping 2. Standard web browsing traffic - Best effort 3. Video traffic - Policing 4. VoIP traffic - Priority queue

VoIP traffic: This type of traffic is very sensitive to delay and jitter, so it's usually given high priority. Therefore, it should be placed in the priority queue. Video traffic: While also sensitive to delay and jitter, video traffic is often less sensitive than VoIP. It may not always be placed in the priority queue but could be shaped to smooth the bandwidth consumption over time. Standard Web browsing traffic: This is typically considered "best effort" traffic. It doesn't have strict requirements for timely delivery or jitter sensitivity. Database synchronization traffic: This type of traffic can be subject to policing to ensure it doesn't consume more than a certain amount of bandwidth and negatively impact other types of traffic. According to these typical associations, the drag-and-drop matches would be: VoIP traffic -> priority queue Video traffic -> shaping Standard Web browsing traffic -> best effort Database synchronization traffic -> policing