We have covered a lot of features here as part of the App QoE suite, and we want to make sure that
we understand all the different products, what they're doing, and be able to differentiate them
so we know if we're trying to accomplish a task, which one of these tools would actually do the
job. So first question here in this challenge is which of these features is used to reduce
bandwidth consumption? If we're reducing bandwidth consumption, that means we're reducing the amount
of data that we're placing on the link. And the one that we're talking about there that would reduce
data consumption would be data redundancy elimination. So this would be that world of
compression where we're using Lempel-Ziv-Welch or LZW there, LZW compression, in order to actually
reduce the data that we're sending and therefore reduce bandwidth consumption. Now number two here
is the opposite of that. It's increasing data consumption, and specifically it's asking which
two features increase data transmissions in order to reduce loss. So we're basically saying, hey,
we'll increase the data we're sending, and that will help us reduce loss if loss is the bigger
deal here. So there's two of these. First of all is my favorite one, which is deduplication. Nope,
it's actually duplication. How about that? We're duplicating packets and we're sending them out
multiple WAN links. Again, we need multiple WAN links to make duplication happen, and hopefully at
least one of those packet copies makes it to the other side. The other option would be forward
error correction, where we take those four packets and we add a parity packet, and that's going to
help us even if we have a single circuit site. And so we're increasing this by 20 percent,
whereas this one we're increasing by 100 percent, knowing that we have a whole second circuit's worth
of bandwidth that we can utilize. So we have to make sure that either one of these solutions is
going to work well with our applications. Number three, which Cisco platform gets integrated into
SD-WAN with AppNav? Anytime we're talking about AppNav, we are talking about that wide area
application services engine or WAAS, the WAAS platform that Cisco has. We've got a bunch of
acronyms. We need to know about the WAAS nodes or the WNs and the fact that our edges have ANCs
running, even though we're calling our edges SCs. And then of course we have the WAAS central
manager, WCM in there. And so we've got a lot of acronyms to keep track of there. And then number
four here, which unique method is used to achieve TCP optimization on the SD-WAN? So we're talking
about TCP optimization. What's that method we're using? It's sort of that man-in-the-middle concept
is what we're driving at here, where I'm going to have a TCP connection between the one host and the
edge, a normal TCP connection between the other host and the other edge. And then in the middle
here, we're going to run optimized TCP. And so we're actually segmenting our TCP connection,
which normally would extend from one host to the other all the way across the network. Instead,
we're now breaking it up and we're going to make sure that we're running controlled window sizes
there in the middle to try to prevent that shark fin type of behavior. And ultimately
to try to maximize the bandwidth on a link rather than constantly hitting congestion and then
backing off and congestion and backing off. We'll hopefully smooth things out and be able to,
you know, yeah, for lack of better words, use every megabit per second that we are given,
available to us on that wide area network circuit. So lots of potential methods for optimization
here to improve our wide area experience. SD-WAN gives us some of these baked in and we can leverage
WOS for some of the other features. But in the end, we just need to be equipped with the knowledge
and understanding that there's these features out there, they improve our application quality of
experience, and that we can deploy them if our end users are having a bad time and trying to
use applications across the SD-WAN. I hope this has been informative for you and I'd like to thank
you for viewing.