WEBVTT

1
00:00.000 --> 00:07.890
So in this challenge, we're asked to jump in and answer a few questions here,

2
00:07.890 --> 00:08.560
particularly

3
00:08.560 --> 00:11.720
about SD-WAN policies.

4
00:11.720 --> 00:16.120
So let's go ahead and start off here with our first question.

5
00:16.120 --> 00:21.760
Which two of the following are part of the six-tuple match?

6
00:21.760 --> 00:25.630
So we're looking for two answers here out of our list of choices, and we're

7
00:25.630 --> 00:26.880
talking specifically

8
00:26.880 --> 00:29.320
about that six-tuple match.

9
00:29.320 --> 00:31.400
So let's go down our list.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.320 --> 00:31.400
So let's go down our list.

10
00:31.400 --> 00:36.600
First we have the source and destination, TCP, and UDP port.

11
00:36.600 --> 00:39.240
So that is definitely a correct answer.

12
00:39.240 --> 00:43.540
Now you could almost make the argument here that that is two things, but we're

13
00:43.540 --> 00:43.920
looking

14
00:43.920 --> 00:47.920
for two answers, not just two items.

15
00:47.920 --> 00:50.480
Next is the layer seven header.

16
00:50.480 --> 00:56.130
Now application aware routing does in fact use the layer seven header, however

17
00:56.130 --> 00:56.720
that's

18
00:56.720 --> 00:59.760
not part of the six-tuple match.

19
00:59.760 --> 01:04.170
That's application aware routing, so that's going to be an incorrect choice
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:59.760 --> 01:04.170
That's application aware routing, so that's going to be an incorrect choice

20
01:04.170 --> 01:04.560
here.

21
01:04.560 --> 01:09.360
Next is the source and destination application ID.

22
01:09.360 --> 01:14.230
Now that sounds like a really cool thing, and it might be a correct answer if

23
01:14.230 --> 01:15.280
it existed.

24
01:15.280 --> 01:16.640
That's just completely made up.

25
01:16.640 --> 01:21.960
There's no application ID in the TCP header.

26
01:21.960 --> 01:25.280
Next of course is the source and destination IP address.

27
01:25.280 --> 01:28.240
Hopefully everybody got this one correct.

28
01:28.240 --> 01:31.440
That is definitely part of the six-tuple match.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:28.240 --> 01:31.440
That is definitely part of the six-tuple match.

29
01:31.440 --> 01:35.570
Finally, and of course we already have our two answers, so we know that this

30
01:35.570 --> 01:36.320
one is not

31
01:36.320 --> 01:37.600
correct.

32
01:37.600 --> 01:41.320
It has LACP listed and it says QOS.

33
01:41.320 --> 01:46.120
So first off LACP is link aggregation control protocol.

34
01:46.120 --> 01:51.150
This has nothing to do with QOS, and it certainly has nothing to do with the

35
01:51.150 --> 01:52.760
six-tuple match.

36
01:52.760 --> 01:57.890
So the two answers we're looking for here, source and destination TCP or UDP

37
01:57.890 --> 01:59.120
port number,

38
01:59.120 --> 02:03.360
and the source and destination IP itself.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:59.120 --> 02:03.360
and the source and destination IP itself.

39
02:03.360 --> 02:11.120
Next question, policies can also be used to enable which three other features.

40
02:11.120 --> 02:14.640
So here of course we're looking for three answers, and we're looking for things

41
02:14.640 --> 02:14.920
that

42
02:14.920 --> 02:18.360
can be enabled using policies.

43
02:18.360 --> 02:22.800
Our first answer here is network address translation or NAT, and that is

44
02:22.800 --> 02:24.080
actually going to be a

45
02:24.080 --> 02:25.720
correct answer.

46
02:25.720 --> 02:29.800
We can enable NAT with our policies.

47
02:29.800 --> 02:33.520
Next is quality of service classification.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:29.800 --> 02:33.520
Next is quality of service classification.

48
02:33.520 --> 02:35.200
This one is also correct.

49
02:35.200 --> 02:39.120
In fact, this one we actually saw when we were doing our demonstration of

50
02:39.120 --> 02:39.880
configuring

51
02:39.880 --> 02:41.240
a policy.

52
02:41.240 --> 02:45.240
We did a very rough version of one, but that was essentially a QOS

53
02:45.240 --> 02:47.960
classification policy.

54
02:47.960 --> 02:50.760
Next up is zero touch provisioning.

55
02:50.760 --> 02:54.440
Zero touch provisioning is a cool feature in SD-WAN.

56
02:54.440 --> 02:59.080
However, this is not related to policies.

57
02:59.080 --> 03:04.140
Next up is service chaining, which is directing traffic through other things
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:59.080 --> 03:04.140
Next up is service chaining, which is directing traffic through other things

58
03:04.140 --> 03:05.600
such as firewalls,

59
03:05.600 --> 03:10.520
network load balancers, intrusion prevention systems, and so on.

60
03:10.520 --> 03:14.530
Since it has to do with traffic manipulation, that's definitely going to be a

61
03:14.530 --> 03:15.240
good choice

62
03:15.240 --> 03:17.560
for our policies.

63
03:17.560 --> 03:21.290
Of course, we already have three answers, but just to make sure the other two

64
03:21.290 --> 03:22.760
are incorrect,

65
03:22.760 --> 03:25.160
HTTP content scanning.

66
03:25.160 --> 03:30.490
Now, that might be something that in our service chaining can be done, but not
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:25.160 --> 03:30.490
Now, that might be something that in our service chaining can be done, but not

67
03:30.490 --> 03:31.000
by the

68
03:31.000 --> 03:38.200
policy itself, and there's not a local ASA firewall in the SD-WAN environment.

69
03:38.200 --> 03:40.920
Again, could it be part of our service chaining?

70
03:40.920 --> 03:44.520
Absolutely, but that's not what this question was.

71
03:44.520 --> 03:48.210
Again, our answers are going to be network address translation, quality of

72
03:48.210 --> 03:50.600
service classification,

73
03:50.600 --> 03:52.760
and service chaining.

74
03:52.760 --> 03:59.360
Final question, which two of the following describe the function of application

75
03:59.360 --> 03:59.920
-aware

76
03:59.920 --> 04:00.920
routing?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:59.920 --> 04:00.920
routing?

77
04:00.920 --> 04:05.320
Again, we're looking for two answers here specifically about AAR.

78
04:05.320 --> 04:08.040
Let's go down our list.

79
04:08.040 --> 04:14.160
Ensure that application traffic arrives on the correct destination port.

80
04:14.160 --> 04:18.830
This isn't really about changing the port number or controlling the port number

81
04:18.830 --> 04:19.400
, so that

82
04:19.400 --> 04:23.770
doesn't sound like a great answer, but let's not mark it wrong until we've seen

83
04:23.770 --> 04:24.360
the rest

84
04:24.360 --> 04:25.880
of them.

85
04:25.880 --> 04:31.880
Route questionable application traffic to the AV inspection engine.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:25.880 --> 04:31.880
Route questionable application traffic to the AV inspection engine.

86
04:31.880 --> 04:36.280
That's also possible given our service chaining.

87
04:36.280 --> 04:39.520
Let's see if any of these again match better.

88
04:39.520 --> 04:42.560
Perform deep packet inspection to identify traffic.

89
04:42.560 --> 04:49.510
Okay, now that one is definitely part of AAR, so that's going to be a really

90
04:49.510 --> 04:51.000
good answer.

91
04:51.000 --> 04:56.680
Use a SLA policy to choose the best tunnel for the traffic.

92
04:56.680 --> 05:02.080
That again is one of the primary functions of AAR, so we're going to mark that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
04:56.680 --> 05:02.080
That again is one of the primary functions of AAR, so we're going to mark that

93
05:02.080 --> 05:03.000
as a correct

94
05:03.000 --> 05:04.080
answer.

95
05:04.080 --> 05:09.610
So although these other two things may ultimately be possible, these are not

96
05:09.610 --> 05:11.000
the main functions

97
05:11.000 --> 05:16.680
of AAR, so I would consider those to be incorrect answers.

98
05:16.680 --> 05:20.810
That would leave our correct answers at performing deep packet inspection to

99
05:20.810 --> 05:22.480
identify traffic

100
05:22.480 --> 05:29.400
and using a SLA policy to choose the best tunnel for the traffic.

101
05:29.400 --> 05:33.600
So that concludes this quiz and therefore this challenge.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:29.400 --> 05:33.600
So that concludes this quiz and therefore this challenge.

102
05:33.600 --> 05:37.950
If you find you are not able to answer any of these questions correctly, I want

103
05:37.950 --> 05:38.400
to encourage

104
05:38.400 --> 05:43.680
you to go back and review the necessary sections in the skill above.

105
05:43.680 --> 05:49.560
Otherwise, congratulations on completing introducing SDWAN policies.

106
05:49.560 --> 05:53.800
I hope this has been informative for you and I'd like to thank you for viewing.

107
05:53.800 --> 06:03.300
[BLANK_AUDIO]