WEBVTT

1
00:00.000 --> 00:07.440
So, in this challenge, we're asked to answer a series of questions to verify

2
00:07.440 --> 00:08.440
our understanding

3
00:08.440 --> 00:10.720
of the topics in this skill.

4
00:10.720 --> 00:15.120
So, let's go ahead and jump in here with our first question.

5
00:15.120 --> 00:19.400
What is the primary goal of Cisco App QOE?

6
00:19.400 --> 00:23.280
So, let's go ahead and go down our answers.

7
00:23.280 --> 00:25.440
First is to provide network redundancy.

8
00:25.440 --> 00:31.760
Now, we may or may not have network redundancy, and that may be part of SD-WAN,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:25.440 --> 00:31.760
Now, we may or may not have network redundancy, and that may be part of SD-WAN,

9
00:31.760 --> 00:32.160
but that's

10
00:32.160 --> 00:35.520
not specifically part of App QOE itself.

11
00:35.520 --> 00:38.600
So, that would be incorrect.

12
00:38.600 --> 00:43.930
To enhance network security, again, network security is something we want to

13
00:43.930 --> 00:44.360
have, but

14
00:44.360 --> 00:47.440
that's not a specific job of App QOE.

15
00:47.440 --> 00:51.280
So, I would say that is also incorrect.

16
00:51.280 --> 00:53.600
Reduce network bandwidth usage.

17
00:53.600 --> 00:58.150
Now, this is sort of an interesting answer, because, well, we are sort of going

18
00:58.150 --> 00:58.400
to be

19
00:58.400 --> 01:03.240
reducing network bandwidth usage with some of the App QOE features.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:58.400 --> 01:03.240
reducing network bandwidth usage with some of the App QOE features.

20
01:03.240 --> 01:09.240
So, let's look at our last answer here and see which one is better.

21
01:09.240 --> 01:13.880
Improve the quality of application delivery and end user experience.

22
01:13.880 --> 01:19.520
Well, I mean, this answer practically has App QOE in it.

23
01:19.520 --> 01:22.080
It's application and experience.

24
01:22.080 --> 01:25.640
So, this seems like the better answer.

25
01:25.640 --> 01:31.110
And if we look back at our reduced network bandwidth usage, throughout this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:25.640 --> 01:31.110
And if we look back at our reduced network bandwidth usage, throughout this

26
01:31.110 --> 01:31.520
skill, network

27
01:31.520 --> 01:36.840
has sort of referred to the end devices, in other words, the LAN.

28
01:36.840 --> 01:38.560
And this is more about the WAN.

29
01:38.560 --> 01:42.720
Now, again, generically speaking, the WAN is part of the network.

30
01:42.720 --> 01:46.960
I could certainly see making an argument for the third answer here.

31
01:46.960 --> 01:52.660
However, I think we could also agree that the fourth answer is better, and

32
01:52.660 --> 01:52.920
given that

33
01:52.920 --> 01:59.560
this is only a single answer question, we'll choose this as our best answer.

34
01:59.560 --> 02:04.840
Improve the quality of application delivery and end user experience.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:59.560 --> 02:04.840
Improve the quality of application delivery and end user experience.

35
02:04.840 --> 02:12.360
Next question, which three of the following features are commonly used by Cisco

36
02:12.360 --> 02:13.080
App QOE

37
02:13.080 --> 02:15.800
to improve application quality?

38
02:15.800 --> 02:18.880
So, we're looking for three answers here.

39
02:18.880 --> 02:21.720
Let's go ahead and go down our list.

40
02:21.720 --> 02:23.520
First is data compression.

41
02:23.520 --> 02:27.320
Well, data compression is definitely one of the features we looked at.

42
02:27.320 --> 02:31.040
So, I would consider that to be a correct answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
02:27.320 --> 02:31.040
So, I would consider that to be a correct answer.

43
02:31.040 --> 02:34.040
Next is application layer encryption.

44
02:34.040 --> 02:37.720
Well, we don't really do encryption with App QOE.

45
02:37.720 --> 02:42.160
So, I would consider that an incorrect answer.

46
02:42.160 --> 02:45.600
Next is transport layer transparency.

47
02:45.600 --> 02:47.480
I'm not really sure what that means.

48
02:47.480 --> 02:51.080
So, I think we'll probably consider that one an incorrect answer.

49
02:51.080 --> 02:53.320
That sounds a bit made up.

50
02:53.320 --> 02:59.080
Then of course, we have our forward error correction or FEC or FEC.

51
02:59.080 --> 03:02.600
And then of course, we have packet duplication.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:59.080 --> 03:02.600
And then of course, we have packet duplication.

52
03:02.600 --> 03:05.000
Both of these last two we of course discussed.

53
03:05.000 --> 03:09.870
So, our three answers are going to be data compression, forward error

54
03:09.870 --> 03:11.080
correction, and

55
03:11.080 --> 03:13.320
packet duplication.

56
03:13.320 --> 03:14.800
Next question.

57
03:14.800 --> 03:19.160
How does FEC contribute to App QOE?

58
03:19.160 --> 03:24.080
Once again, let's go over our answers by merging multiple network paths for

59
03:24.080 --> 03:25.000
faster data

60
03:25.000 --> 03:26.000
delivery.

61
03:26.000 --> 03:29.560
Well, that actually sounds like some sort of bundling.

62
03:29.560 --> 03:33.920
So, that's definitely not going to be something that FEC takes care of.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
03:29.560 --> 03:33.920
So, that's definitely not going to be something that FEC takes care of.

63
03:33.920 --> 03:36.240
That's going to be incorrect.

64
03:36.240 --> 03:43.450
Next is by proactively adding redundant data to correct packet loss without ret

65
03:43.450 --> 03:44.760
ransmission.

66
03:44.760 --> 03:50.910
So, this is clearly talking about our parity information and being able to do

67
03:50.910 --> 03:52.120
data recovery

68
03:52.120 --> 03:54.680
without having to resend it.

69
03:54.680 --> 03:57.680
So, this is clearly what FEC does.

70
03:57.680 --> 04:01.430
We'll go ahead and mark this, but of course, we'll review the last couple
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:57.680 --> 04:01.430
We'll go ahead and mark this, but of course, we'll review the last couple

71
04:01.430 --> 04:02.120
answers just

72
04:02.120 --> 04:04.520
to make sure they're not better.

73
04:04.520 --> 04:07.360
By encrypting data to secure transmissions.

74
04:07.360 --> 04:11.720
And again, App QOE doesn't have anything to do with encryption.

75
04:11.720 --> 04:12.720
That's IPsec.

76
04:12.720 --> 04:15.960
So, that's not going to be correct.

77
04:15.960 --> 04:19.600
By compressing data to reduce bandwidth usage.

78
04:19.600 --> 04:25.400
Now, this is interesting because we know that App QOE does do data compression.

79
04:25.400 --> 04:28.840
However, that's not part of FEC specifically.

80
04:28.840 --> 04:34.270
So, this is going to be incorrect just for this specific question, although
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:28.840 --> 04:34.270
So, this is going to be incorrect just for this specific question, although

81
04:34.270 --> 04:35.000
that is, of

82
04:35.000 --> 04:38.080
course, like we said, part of App QOE.

83
04:38.080 --> 04:44.050
So, that leaves by proactively adding redundant data to correct packet loss

84
04:44.050 --> 04:46.080
without retransmission

85
04:46.080 --> 04:48.480
as our correct answer.

86
04:48.480 --> 04:50.080
Final question.

87
04:50.080 --> 04:58.140
Which two types of applications benefit most from packet duplication in App QOE

88
04:58.140 --> 04:58.560
?

89
04:58.560 --> 05:04.580
So, we're looking for two answers here and we're talking about packet
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
04:58.560 --> 05:04.580
So, we're looking for two answers here and we're talking about packet

90
05:04.580 --> 05:04.960
duplication.

91
05:04.960 --> 05:11.200
Say that packet duplication is going to work best with real-time applications.

92
05:11.200 --> 05:15.940
So, going down our list, we have voiceover IP.

93
05:15.940 --> 05:17.760
That is definitely going to be real-time.

94
05:17.760 --> 05:21.120
So, that's going to be a correct answer.

95
05:21.120 --> 05:22.480
Email communication.

96
05:22.480 --> 05:25.480
Of course, email is not in any way real-time.

97
05:25.480 --> 05:28.640
So, that's going to be incorrect.

98
05:28.640 --> 05:33.440
Video conferencing is also going to be real-time.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
05:28.640 --> 05:33.440
Video conferencing is also going to be real-time.

99
05:33.440 --> 05:38.400
It's driving a two-way conversation between two people with voice and video.

100
05:38.400 --> 05:41.600
Now, the next one might throw us a little bit.

101
05:41.600 --> 05:43.040
SSH sessions.

102
05:43.040 --> 05:45.200
They're pretty close to real-time.

103
05:45.200 --> 05:47.400
It's an interactive session.

104
05:47.400 --> 05:52.310
But also, keep in mind, the SSH would take care of its own packet loss fairly

105
05:52.310 --> 05:53.080
easily.

106
05:53.080 --> 05:57.320
So, SSH is really just not going to be one of our better answers here.

107
05:57.320 --> 06:01.560
And, of course, file downloads are nowhere near real-time.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
05:57.320 --> 06:01.560
And, of course, file downloads are nowhere near real-time.

108
06:01.560 --> 06:04.000
They just come in as fast as they can.

109
06:04.000 --> 06:05.000
And that's it.

110
06:05.000 --> 06:11.780
So, our two answers here would be voiceover IP and video conferencing the two

111
06:11.780 --> 06:12.800
real-time

112
06:12.800 --> 06:16.440
apps here on this answer.

113
06:16.440 --> 06:18.600
So that concludes this challenge.

114
06:18.600 --> 06:22.410
If you find that you were missing any of the information needed to answer these

115
06:22.410 --> 06:23.120
questions,

116
06:23.120 --> 06:27.410
I would encourage you to go back and review the sections above to find the

117
06:27.410 --> 06:28.760
correct answers.

118
06:28.760 --> 06:33.960
Otherwise, congratulations on completing Examining App QOE.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
06:28.760 --> 06:33.960
Otherwise, congratulations on completing Examining App QOE.

119
06:33.960 --> 06:37.780
I hope this has been informative for you, and I'd like to thank you for viewing

120
06:37.780 --> 06:38.000
.

121
06:38.000 --> 06:46.920
[BLANK_AUDIO]