WEBVTT

1
00:00.000 --> 00:07.830
So for this challenge, we're asked to answer just a few questions here about

2
00:07.830 --> 00:08.840
Cloud OnRAMP

3
00:08.840 --> 00:14.520
for AWS, just to verify that we understood everything we saw during our

4
00:14.520 --> 00:16.120
demonstration.

5
00:16.120 --> 00:19.960
So let's go ahead and jump in here with our first question.

6
00:19.960 --> 00:28.760
What is a key feature of Cisco SD-WAN that benefits Cloud OnRAMP for AWS?

7
00:28.760 --> 00:31.840
So let's go ahead and look over the answers here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:28.760 --> 00:31.840
So let's go ahead and look over the answers here.

8
00:31.840 --> 00:37.200
And looking at our first answer, we have enhanced printing capabilities.

9
00:37.200 --> 00:40.750
Well of course, this has nothing to do with printing, so that's definitely

10
00:40.750 --> 00:41.200
going to be

11
00:41.200 --> 00:43.160
incorrect.

12
00:43.160 --> 00:46.360
Dedicated support for legacy systems only.

13
00:46.360 --> 00:53.010
Well actually Cloud OnRAMP doesn't just support legacy systems, so that's also

14
00:53.010 --> 00:53.640
not going

15
00:53.640 --> 00:56.280
to be a correct answer.

16
00:56.280 --> 00:59.480
Quick encryption of all local files.

17
00:59.480 --> 01:03.740
Well although that is a good practice, Cloud OnRAMP actually has nothing to do
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:59.480 --> 01:03.740
Well although that is a good practice, Cloud OnRAMP actually has nothing to do

18
01:03.740 --> 01:04.720
with encryption

19
01:04.720 --> 01:09.640
of files, so that's going to be incorrect as well.

20
01:09.640 --> 01:15.280
That leaves us with automated failover and intelligent path control.

21
01:15.280 --> 01:20.510
And we did see this during our demonstration where we didn't actually do a fail

22
01:20.510 --> 01:21.160
over and

23
01:21.160 --> 01:24.760
didn't really necessarily focus on the path control.

24
01:24.760 --> 01:30.560
However, we did see how it actually implements different availability zones to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:24.760 --> 01:30.560
However, we did see how it actually implements different availability zones to

25
01:30.560 --> 01:31.920
allow for redundancy

26
01:31.920 --> 01:36.200
and such in the event of a failover.

27
01:36.200 --> 01:37.800
Next question.

28
01:37.800 --> 01:44.970
Cisco Cloud OnRAMP for AWS can integrate with which AWS services to improve

29
01:44.970 --> 01:45.840
network

30
01:45.840 --> 01:48.600
efficiency and security.

31
01:48.600 --> 01:52.880
So looking over the answers here, there's really only one thing here we looked

32
01:52.880 --> 01:54.000
at directly,

33
01:54.000 --> 01:58.120
which was the AWS Transit Gateway.

34
01:58.120 --> 02:04.720
Now we discussed briefly the AWS Direct Connect when we looked at the different
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:58.120 --> 02:04.720
Now we discussed briefly the AWS Direct Connect when we looked at the different

35
02:04.720 --> 02:05.560
models that

36
02:05.560 --> 02:10.720
we can actually implement, although we didn't do this particular one.

37
02:10.720 --> 02:15.670
However, if we look over the rest of the answers where we have code commit and

38
02:15.670 --> 02:17.400
code deploy,

39
02:17.400 --> 02:24.670
there's nothing we saw at all, and if we look at S3 and AWS CloudTrail also not

40
02:24.670 --> 02:25.440
things

41
02:25.440 --> 02:33.160
we looked at at all, Lambda and CloudFormation also not things we looked at.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
02:25.440 --> 02:33.160
we looked at at all, Lambda and CloudFormation also not things we looked at.

42
02:33.160 --> 02:37.080
So given the list of choices, even though we only looked at one of these

43
02:37.080 --> 02:37.880
directly, this

44
02:37.880 --> 02:40.520
is going to be our best choice.

45
02:40.520 --> 02:46.120
And yes, Cloud OnRAMP does in fact also support Direct Connect.

46
02:46.120 --> 02:47.640
So, let's go with a little question.

47
02:47.640 --> 02:54.040
What is the main purpose of Cisco Cloud OnRAMP for AWS?

48
02:54.040 --> 02:59.210
So our first answer here says to optimize the connection and performance of

49
02:59.210 --> 03:00.240
applications
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:59.210 --> 03:00.240
applications

50
03:00.240 --> 03:02.800
hosted on AWS.

51
03:02.800 --> 03:04.640
That's a pretty good answer.

52
03:04.640 --> 03:09.630
Let's verify the other ones first, however, to offer a video conferencing

53
03:09.630 --> 03:10.600
service.

54
03:10.600 --> 03:11.960
That's definitely incorrect.

55
03:11.960 --> 03:16.050
This has nothing to do with video conferencing to provide a Cloud Storage

56
03:16.050 --> 03:16.880
solution.

57
03:16.880 --> 03:22.200
Well, it might indirectly give us access to a Cloud Storage solution, but that

58
03:22.200 --> 03:23.000
is certainly

59
03:23.000 --> 03:29.600
not its main purpose and to manage IoT devices, this is definitely not going to

60
03:29.600 --> 03:30.560
be correct
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
03:29.600 --> 03:30.560
be correct

61
03:30.560 --> 03:31.560
either.

62
03:31.560 --> 03:36.200
So, yes, our best answer here is definitely going to be to optimize the

63
03:36.200 --> 03:37.360
connection and

64
03:37.360 --> 03:42.440
performance of applications hosted on AWS.

65
03:42.440 --> 03:45.040
So that concludes this quiz.

66
03:45.040 --> 03:48.670
If you find that you are missing any of the information needed to answer these

67
03:48.670 --> 03:49.240
questions,

68
03:49.240 --> 03:54.080
I would encourage you to go back and review the material above.

69
03:54.080 --> 03:59.880
Otherwise, congratulations on completing Cloud OnRAMP for AWS.

70
03:59.880 --> 04:03.800
I hope this has been informative for you, and I'd like to thank you for viewing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:59.880 --> 04:03.800
I hope this has been informative for you, and I'd like to thank you for viewing

71
04:03.800 --> 04:04.080
.

72
04:04.080 --> 04:12.760
[BLANK_AUDIO]