WEBVTT

1
00:00.000 --> 00:05.990
So, in this challenge, we're asked to answer just a few questions about the

2
00:05.990 --> 00:06.760
content in

3
00:06.760 --> 00:07.760
this skill.

4
00:07.760 --> 00:12.600
So, let's just go ahead and jump in with the first question.

5
00:12.600 --> 00:19.920
Which two of the following are true regarding NAT and SD-WAN controllers?

6
00:19.920 --> 00:22.480
So, let's go down our answers.

7
00:22.480 --> 00:26.440
All controllers can have their own public IP address.

8
00:26.440 --> 00:31.840
Well, that is definitely a true answer, so we'll go ahead and mark that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:26.440 --> 00:31.840
Well, that is definitely a true answer, so we'll go ahead and mark that.

9
00:31.840 --> 00:36.030
If you have a public IP address for each controller, then there's not going to

10
00:36.030 --> 00:37.760
be a problem.

11
00:37.760 --> 00:46.360
Number two, all controllers can be put behind one public IP address using NAT.

12
00:46.360 --> 00:50.040
The problem with this answer is the one.

13
00:50.040 --> 00:54.510
Since Cisco does not provide any documentation for which ports need to be

14
00:54.510 --> 00:55.600
forwarded to the

15
00:55.600 --> 01:01.020
validator or V-bond, there's really no way of doing this without possibly a lot
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:55.600 --> 01:01.020
validator or V-bond, there's really no way of doing this without possibly a lot

16
01:01.020 --> 01:02.000
of extensive

17
01:02.000 --> 01:03.000
research.

18
01:03.000 --> 01:07.680
You could figure it out, but this is generally not a supported configuration.

19
01:07.680 --> 01:11.120
So, we'll just go ahead and mark that as incorrect.

20
01:11.120 --> 01:16.390
Now, this brings us, of course, to answer three, that the validator or V-bond

21
01:16.390 --> 01:16.800
can be

22
01:16.800 --> 01:21.360
behind one-to-one NAT with the other controllers.

23
01:21.360 --> 01:27.840
So, the V-Smart controller and V-Manager itself can be behind a different

24
01:27.840 --> 01:29.680
public IP address

25
01:29.680 --> 01:32.080
and then just use port forwarding.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:29.680 --> 01:32.080
and then just use port forwarding.

26
01:32.080 --> 01:34.200
So, this one is correct.

27
01:34.200 --> 01:37.440
In fact, it was the main focus of this skill.

28
01:37.440 --> 01:40.920
That's how we have our environment currently configured.

29
01:40.920 --> 01:46.070
And, of course, that would make the last answer here incorrect, that NAT cannot

30
01:46.070 --> 01:46.960
be used at

31
01:46.960 --> 01:50.280
all with the SD-WAN controllers.

32
01:50.280 --> 01:51.680
But, of course, can.

33
01:51.680 --> 01:53.840
That's how we have it working right now.

34
01:53.840 --> 01:58.330
Of course, as we mentioned numerous times throughout this skill, having all of

35
01:58.330 --> 01:59.480
the controllers

36
01:59.480 --> 02:05.560
with their own public IP address is definitely going to be the preferred method
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:59.480 --> 02:05.560
with their own public IP address is definitely going to be the preferred method

37
02:05.560 --> 02:05.840
.

38
02:05.840 --> 02:11.470
Next question, which two of the following are true regarding SD-WAN on-ramp

39
02:11.470 --> 02:12.560
deployments

40
02:12.560 --> 02:15.080
into the different cloud providers?

41
02:15.080 --> 02:20.190
So, our first answer here says that all of the major cloud providers can be

42
02:20.190 --> 02:21.040
connected

43
02:21.040 --> 02:22.040
simultaneously.

44
02:22.040 --> 02:25.160
Well, hopefully we're all aware that this is true.

45
02:25.160 --> 02:28.520
We actually saw this functioning in this skill.

46
02:28.520 --> 02:34.640
So, we saw that our environment is connected to all three major providers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:28.520 --> 02:34.640
So, we saw that our environment is connected to all three major providers.

47
02:34.640 --> 02:39.790
That would, of course, automatically make answer two here incorrect, which says

48
02:39.790 --> 02:40.160
that

49
02:40.160 --> 02:44.160
it can only be connected to one cloud provider at a time.

50
02:44.160 --> 02:48.560
Clearly, those two answers cannot both be true.

51
02:48.560 --> 02:54.160
Answer number three, all the cloud providers have identical deployment models.

52
02:54.160 --> 02:59.370
Well, this is not true because some of the deployments use gateways, some of

53
02:59.370 --> 03:00.440
them don't.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:59.370 --> 03:00.440
them don't.

54
03:00.440 --> 03:05.040
So, there is slight differences between the different models.

55
03:05.040 --> 03:11.180
So, answer three here is not going to be true, leaving answer four that,

56
03:11.180 --> 03:12.240
although they are

57
03:12.240 --> 03:18.070
very similar, all three major cloud providers are deployed slightly differently

58
03:18.070 --> 03:18.400
.

59
03:18.400 --> 03:23.200
Again, they are very close, but there are minor differences.

60
03:23.200 --> 03:26.820
And of course, those differences revolve around the differences between the

61
03:26.820 --> 03:27.800
cloud providers

62
03:27.800 --> 03:29.480
themselves.

63
03:29.480 --> 03:35.910
Final question, which of the following commands will display the route table
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:29.480 --> 03:35.910
Final question, which of the following commands will display the route table

64
03:35.910 --> 03:37.320
for VPN 10 on

65
03:37.320 --> 03:40.240
a catalyst 8000V edge router?

66
03:40.240 --> 03:48.160
So, once again, going down our list, we have show SD WAN VPN 10 route.

67
03:48.160 --> 03:50.640
That is going to be an incorrect answer.

68
03:50.640 --> 03:53.000
That is not what it's going to be.

69
03:53.000 --> 03:55.720
Show OMP route VRF 10.

70
03:55.720 --> 03:59.400
Well, there's no show OMP route command.

71
03:59.400 --> 04:06.170
There is a show SD WAN OMP with a couple subtexts after it, but nonetheless,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:59.400 --> 04:06.170
There is a show SD WAN OMP with a couple subtexts after it, but nonetheless,

72
04:06.170 --> 04:06.960
that still

73
04:06.960 --> 04:09.920
makes this an incorrect answer.

74
04:09.920 --> 04:13.560
Show IP route VRF 10.

75
04:13.560 --> 04:17.680
That sounds like a good answer, but let's verify the last one first here.

76
04:17.680 --> 04:20.640
Show VRF 10 IP route.

77
04:20.640 --> 04:24.070
So we sort of have some of the correct components in this command, but they're

78
04:24.070 --> 04:24.720
in the wrong

79
04:24.720 --> 04:26.200
order.

80
04:26.200 --> 04:33.640
Therefore, the correct answer here is going to be show IP route for VRF 10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:26.200 --> 04:33.640
Therefore, the correct answer here is going to be show IP route for VRF 10.

81
04:33.640 --> 04:40.910
Remember that on the iOS XE edge routers, VPNs, such as VPN 10, are going to be

82
04:40.910 --> 04:42.160
represented

83
04:42.160 --> 04:46.520
as VRFs in the local router.

84
04:46.520 --> 04:51.080
So that makes show IP route VRF 10 the correct answer.

85
04:51.080 --> 04:56.040
And that concludes this challenge as well as this skill.

86
04:56.040 --> 05:00.710
So, if you found yourself missing any of the information to answer these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
04:56.040 --> 05:00.710
So, if you found yourself missing any of the information to answer these

87
05:00.710 --> 05:01.920
questions, I would

88
05:01.920 --> 05:06.520
encourage you to go back and review the necessary sections in this skill.

89
05:06.520 --> 05:12.080
Otherwise, congratulations on completing preparing for Cloud on-ramp.

90
05:12.080 --> 05:15.980
I hope this has been informative for you, and I'd like to thank you for viewing

91
05:15.980 --> 05:16.200
.

92
05:16.200 --> 05:25.240
[BLANK_AUDIO]