I'd go with B and D. Strict Priority is great for mission-critical apps, but you gotta make sure the higher priority queues are being used properly. Otherwise, you're just asking for trouble!
Haha, I bet the network admin who has to configure this is gonna have a headache! Strict Priority sounds like a recipe for chaos if you don't plan it out carefully.
I'm not sure about C - I thought Strict Priority alone could lead to starvation of lower priority queues, so you'd need to use it with something like Weighted Round Robin to prevent that.
B and D seem correct to me. Strict Priority ensures higher priority queues are always served first, even if there is only one packet waiting. And it works best when the majority of traffic uses the higher priority queues.
Ernest
3 months agoJesus
1 months agoBettye
1 months agoChan
2 months agoMireya
3 months agoCarlee
2 months agoAnissa
2 months agoGwen
3 months agoWenona
3 months agoCarline
1 months agoStefany
2 months agoLore
2 months agoMozelle
2 months agoVallie
2 months agoTwana
2 months agoBuck
3 months agoErinn
3 months agoWhitley
3 months agoHoa
4 months agoHaydee
4 months agoPearlene
4 months agoLazaro
4 months agoAlisha
4 months agoAmie
4 months ago