WEBVTT

1
00:00.000 --> 00:06.880
In this challenge, we're asked to answer a few questions here to test our

2
00:06.880 --> 00:08.240
understanding

3
00:08.240 --> 00:14.000
of the principles and designs of connecting the SD-WAN environment to our

4
00:14.000 --> 00:15.160
software as

5
00:15.160 --> 00:17.080
a service providers.

6
00:17.080 --> 00:21.240
So let's go ahead and jump in here with our first question.

7
00:21.240 --> 00:28.480
What does SD-WAN use to ensure optimal performance when connecting to SaaS

8
00:28.480 --> 00:29.960
providers?

9
00:29.960 --> 00:33.000
Let's go ahead and go down our list of answers here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.960 --> 00:33.000
Let's go ahead and go down our list of answers here.

10
00:33.000 --> 00:36.560
First we have static IP addressing.

11
00:36.560 --> 00:41.600
Although we may use static IP addressing, this is not going to be increasing

12
00:41.600 --> 00:42.640
performance,

13
00:42.640 --> 00:45.640
so that's not going to be a good answer.

14
00:45.640 --> 00:47.400
VPN tunnels only.

15
00:47.400 --> 00:51.710
Well, we may or may not be using VPN tunnels, but again, that's not going to

16
00:51.710 --> 00:52.480
increase our

17
00:52.480 --> 00:54.640
performance.

18
00:54.640 --> 00:57.360
Manual routing configurations.

19
00:57.360 --> 01:01.560
That could mean a couple different things, but usually when we say the word
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.360 --> 01:01.560
That could mean a couple different things, but usually when we say the word

20
01:01.560 --> 01:02.160
manual, that's

21
01:02.160 --> 01:07.870
probably not going to also be optimal because if things change, well, then the

22
01:07.870 --> 01:08.720
routing is

23
01:08.720 --> 01:11.080
not going to update either.

24
01:11.080 --> 01:14.360
So this is probably not going to be our best answer here.

25
01:14.360 --> 01:20.340
So let's take a look at our last answer, dynamic path selection based on real-

26
01:20.340 --> 01:21.440
time performance

27
01:21.440 --> 01:23.080
metrics.

28
01:23.080 --> 01:27.590
That's going to be our best answer and remember those real-time metrics are

29
01:27.590 --> 01:28.680
going to be based

30
01:28.680 --> 01:34.760
on those HTTP pings that we're doing with our active monitoring.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:28.680 --> 01:34.760
on those HTTP pings that we're doing with our active monitoring.

31
01:34.760 --> 01:42.410
Next question, which feature of SD-WAN most directly improves the security of

32
01:42.410 --> 01:43.640
connections

33
01:43.640 --> 01:46.560
to SaaS providers?

34
01:46.560 --> 01:51.920
So looking at our answers, the first one is integrated firewall and encryption.

35
01:51.920 --> 01:55.560
That definitely sounds like something that would help improve security, but let

36
01:55.560 --> 01:55.880
's see

37
01:55.880 --> 01:59.040
if our other answers are any better.

38
01:59.040 --> 02:01.640
Next we have quality of service.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:59.040 --> 02:01.640
Next we have quality of service.

39
02:01.640 --> 02:06.600
Quality of service might help applications utilize a link a bit better.

40
02:06.600 --> 02:10.760
However, that's not really going to be related to security.

41
02:10.760 --> 02:12.800
Same with load balancing.

42
02:12.800 --> 02:17.330
Load balancing is going to help with things like performance and maybe even

43
02:17.330 --> 02:18.360
availability,

44
02:18.360 --> 02:22.650
but that's not necessarily directly related to security, maybe indirectly

45
02:22.650 --> 02:23.760
related to security

46
02:23.760 --> 02:28.260
as far as availability goes, but I think they're looking for a more direct

47
02:28.260 --> 02:29.240
answer here

48
02:29.240 --> 02:31.560
where firewall would fit in.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
02:29.240 --> 02:31.560
where firewall would fit in.

49
02:31.560 --> 02:35.160
And the same sort of thing with WAN optimization.

50
02:35.160 --> 02:39.910
These are all things related to performance where having the integrated

51
02:39.910 --> 02:42.200
firewall and encryption

52
02:42.200 --> 02:46.200
is definitely going to increase the security.

53
02:46.200 --> 02:48.800
So that's going to be our best answer.

54
02:48.800 --> 02:55.880
Next question, how does SD-WAN facilitate cloud-based application performance

55
02:55.880 --> 02:58.280
for remote users?

56
02:58.280 --> 03:01.240
Once again, let's look down our answers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:58.280 --> 03:01.240
Once again, let's look down our answers.

57
03:01.240 --> 03:05.040
First, utilizing only private MPLS connections.

58
03:05.040 --> 03:10.540
Well, that would imply that we're using our centralized internet gateway model,

59
03:10.540 --> 03:10.680
which

60
03:10.680 --> 03:15.770
again is a hub and spoke, causing all of that remote traffic to come back to

61
03:15.770 --> 03:16.840
headquarters

62
03:16.840 --> 03:19.200
and then go out to the internet.

63
03:19.200 --> 03:24.160
That's not going to be the best for performance in most applications.

64
03:24.160 --> 03:28.640
So this is probably not going to be our best answer here.

65
03:28.640 --> 03:31.440
By decreasing overall bandwidth.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
03:28.640 --> 03:31.440
By decreasing overall bandwidth.

66
03:31.440 --> 03:37.920
I'm not aware of a case ever where decreasing bandwidth increases performance.

67
03:37.920 --> 03:41.560
Maybe there's some weird situation I've never heard of, but I don't think that

68
03:41.560 --> 03:41.960
that's going

69
03:41.960 --> 03:43.840
to be a valid answer.

70
03:43.840 --> 03:46.760
By increasing the data payload size.

71
03:46.760 --> 03:52.010
Well, this would be implying that we're in some way trying to increase packet

72
03:52.010 --> 03:53.080
efficiency.

73
03:53.080 --> 03:55.160
That might increase performance.

74
03:55.160 --> 04:00.770
However, if we look at our last answer here through direct internet access at
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:55.160 --> 04:00.770
However, if we look at our last answer here through direct internet access at

75
04:00.770 --> 04:03.040
branch locations,

76
04:03.040 --> 04:06.700
allowing the branch locations to go directly to the internet, I think we can

77
04:06.700 --> 04:07.480
probably agree

78
04:07.480 --> 04:11.520
that this is not going to be our best answer.

79
04:11.520 --> 04:17.230
And therefore, this one is the direct internet access is definitely going to

80
04:17.230 --> 04:19.160
increase performance,

81
04:19.160 --> 04:22.320
particularly for those remote users.

82
04:22.320 --> 04:26.440
Next question in an SD WAN architecture.

83
04:26.440 --> 04:35.040
What mechanism is used to forward SaaS traffic to ensure quality of experience?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
04:26.440 --> 04:35.040
What mechanism is used to forward SaaS traffic to ensure quality of experience?

84
04:35.040 --> 04:40.320
So looking over our answers, application aware routing sounds like a really

85
04:40.320 --> 04:41.300
good answer.

86
04:41.300 --> 04:46.520
We discussed that, but let's look at the other choices just to make sure.

87
04:46.520 --> 04:48.840
First is traffic shaping.

88
04:48.840 --> 04:52.040
Traffic shaping is sort of a QOS mechanism here.

89
04:52.040 --> 04:55.750
And it's not really something we're going to be using with the SD WAN

90
04:55.750 --> 04:56.800
architecture for

91
04:56.800 --> 04:59.240
this particular traffic.

92
04:59.240 --> 05:01.160
Same with static routing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
04:59.240 --> 05:01.160
Same with static routing.

93
05:01.160 --> 05:05.290
Stick routing wouldn't really work here because we're trying to forward traffic

94
05:05.290 --> 05:05.720
based on the

95
05:05.720 --> 05:10.040
application, not based on the destination address.

96
05:10.040 --> 05:14.840
Now sort of the tricky one here is deep packet inspection.

97
05:14.840 --> 05:19.900
Deep packet inspection is certainly going to be used by the DNS intercept

98
05:19.900 --> 05:20.760
process.

99
05:20.760 --> 05:26.680
And it actually uses deep packet inspection for the application aware routing.

100
05:26.680 --> 05:33.990
However, since it's asking us which mechanism is used to forward the traffic,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
05:26.680 --> 05:33.990
However, since it's asking us which mechanism is used to forward the traffic,

101
05:33.990 --> 05:35.080
not identify

102
05:35.080 --> 05:40.610
the traffic, I'm still leaning towards application aware routing as being our

103
05:40.610 --> 05:41.960
better answer.

104
05:41.960 --> 05:47.390
It is a close call, but I would say again, deep packet inspection is used to

105
05:47.390 --> 05:48.080
identify

106
05:48.080 --> 05:54.800
the traffic where application aware routing is used for the actual forwarding.

107
05:54.800 --> 05:59.680
So I think that's going to make application aware routing our best answer.

108
05:59.680 --> 06:06.960
Final question, what is a benefit of using SD WAN for connecting to multiple S
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
05:59.680 --> 06:06.960
Final question, what is a benefit of using SD WAN for connecting to multiple S

109
06:06.960 --> 06:08.400
aaS providers

110
06:08.400 --> 06:11.040
in a multi-cloud strategy?

111
06:11.040 --> 06:13.960
Now we didn't cover this specifically.

112
06:13.960 --> 06:18.660
However, if we just look at the answers, I think it's fairly straightforward

113
06:18.660 --> 06:18.880
what we're

114
06:18.880 --> 06:20.920
looking for here.

115
06:20.920 --> 06:27.090
First, higher cost due to proprietary technology, that's certainly not the case

116
06:27.090 --> 06:27.120
.

117
06:27.120 --> 06:30.760
So that's not going to be our answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
06:27.120 --> 06:30.760
So that's not going to be our answer.

118
06:30.760 --> 06:36.320
Increased operational complexity, that's certainly not a feature of SD WAN

119
06:36.320 --> 06:37.200
either.

120
06:37.200 --> 06:40.490
Single point of failure, well, we certainly saw that we have a lot of

121
06:40.490 --> 06:41.680
redundancy available

122
06:41.680 --> 06:43.120
in these systems.

123
06:43.120 --> 06:45.120
So that's not going to be it.

124
06:45.120 --> 06:48.600
So I think that it's fairly straightforward that the correct answer here is

125
06:48.600 --> 06:49.080
going to

126
06:49.080 --> 06:53.560
be our simplified management and orchestration.

127
06:53.560 --> 06:58.160
So all of that being said, that concludes this challenge.

128
06:58.160 --> 07:02.240
If you find that you were not able to answer any of these questions, I would
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:58.160 --> 07:02.240
If you find that you were not able to answer any of these questions, I would

129
07:02.240 --> 07:02.800
encourage

130
07:02.800 --> 07:07.970
you to go back and review the related sections to try to pick up that missing

131
07:07.970 --> 07:09.080
knowledge.

132
07:09.080 --> 07:16.080
Otherwise, congratulations on completing connecting SD WAN to SaaS providers.

133
07:16.080 --> 07:20.080
I hope this has been informative for you, and I'd like to thank you for viewing

134
07:20.080 --> 07:20.120
.