WEBVTT

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

2
00:07.760 --> 00:08.640
that we understand

3
00:08.640 --> 00:11.800
the topics presented in this skill.

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

5
00:16.160 --> 00:22.670
Which of the following are usually considered security benefits of using cloud

6
00:22.670 --> 00:23.960
providers?

7
00:23.960 --> 00:29.440
Remember that we're specifically looking for benefits, so keep that in mind.

8
00:29.440 --> 00:32.680
That said, let's work down our answers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:29.440 --> 00:32.680
That said, let's work down our answers.

9
00:32.680 --> 00:37.120
First, a secure and uniform infrastructure.

10
00:37.120 --> 00:42.130
This was definitely listed as one of our advantages to being in a cloud

11
00:42.130 --> 00:43.840
environment, so that's

12
00:43.840 --> 00:46.120
going to be correct.

13
00:46.120 --> 00:48.140
Internet facing services.

14
00:48.140 --> 00:52.640
This was actually one of our concerns that we have to secure things that are

15
00:52.640 --> 00:53.280
facing the

16
00:53.280 --> 00:55.200
internet.

17
00:55.200 --> 01:00.200
This is a high tenant environment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:55.200 --> 01:00.200
This is a high tenant environment.

18
01:00.200 --> 01:04.310
This was also one of our concerns, so that's not going to be one of our

19
01:04.310 --> 01:05.200
benefits.

20
01:05.200 --> 01:10.090
The availability of resources is also going to be a big positive in the cloud

21
01:10.090 --> 01:11.200
environment,

22
01:11.200 --> 01:14.200
so that's definitely going to be correct.

23
01:14.200 --> 01:19.610
The ability to have specialized staff, particularly focused around security, is

24
01:19.610 --> 01:20.200
also going to be

25
01:20.200 --> 01:22.200
a correct answer.

26
01:22.200 --> 01:25.320
Those two are actually not correct.

27
01:25.320 --> 01:27.520
Loss of administrative control over systems.

28
01:27.520 --> 01:33.370
Yeah, this is definitely one that we had listed as a concern, but also a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:27.520 --> 01:33.370
Yeah, this is definitely one that we had listed as a concern, but also a

29
01:33.370 --> 01:34.480
benefit.

30
01:34.480 --> 01:39.960
So this one is sort of on the fence, maybe, however, whether it ultimately

31
01:39.960 --> 01:40.920
benefits us

32
01:40.920 --> 01:44.480
or not, it is still a concern.

33
01:44.480 --> 01:48.890
So I would still list it as a concern, even though ultimately it may be why we

34
01:48.890 --> 01:49.560
're moving

35
01:49.560 --> 01:51.640
to the cloud to begin with.

36
01:51.640 --> 01:54.080
And of course, complex systems.

37
01:54.080 --> 01:58.020
This was another one of our concerns, just because of the possible learning

38
01:58.020 --> 01:58.920
curve involved

39
01:58.920 --> 02:01.280
in going to the cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:58.920 --> 02:01.280
in going to the cloud.

40
02:01.280 --> 02:02.560
Next question.

41
02:02.560 --> 02:07.620
Which of the following statements best describes the difference between North,

42
02:07.620 --> 02:08.840
South, and East

43
02:08.840 --> 02:10.440
West network traffic?

44
02:10.440 --> 02:13.800
Let's work our way down our answers.

45
02:13.800 --> 02:19.840
North, South traffic refers to data moving horizontally within the data center.

46
02:19.840 --> 02:22.160
Now, we can stop right there.

47
02:22.160 --> 02:27.450
That's definitely not correct because North, South would not be considered

48
02:27.450 --> 02:28.560
horizontal.

49
02:28.560 --> 02:29.960
That would be vertical.

50
02:29.960 --> 02:32.840
Let's go on to our next answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:29.960 --> 02:32.840
Let's go on to our next answer.

51
02:32.840 --> 02:37.300
North, South traffic refers to data moving vertically between the data center

52
02:37.300 --> 02:38.000
and external

53
02:38.000 --> 02:39.500
locations.

54
02:39.500 --> 02:41.360
So far, so good.

55
02:41.360 --> 02:47.750
While East West traffic refers to data moving horizontally within a data center

56
02:47.750 --> 02:47.920
.

57
02:47.920 --> 02:49.920
That one sounds really good.

58
02:49.920 --> 02:52.640
Let's just verify the other answers quickly.

59
02:52.640 --> 02:56.280
North, South traffic involves data moving within a single server.

60
02:56.280 --> 02:57.440
Well, that's not correct.

61
02:57.440 --> 02:59.040
So we can just skip that one.

62
02:59.040 --> 03:02.080
We'll just go ahead and mark that one is wrong.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:59.040 --> 03:02.080
We'll just go ahead and mark that one is wrong.

63
03:02.080 --> 03:07.010
North, South traffic is concerned with data moving between different servers

64
03:07.010 --> 03:07.560
within a

65
03:07.560 --> 03:09.320
data center.

66
03:09.320 --> 03:11.280
Once again, we know that's not true.

67
03:11.280 --> 03:13.440
That would be East West traffic.

68
03:13.440 --> 03:19.040
So that's going to make this one incorrect, leaving us with North, South

69
03:19.040 --> 03:20.320
traffic refers

70
03:20.320 --> 03:25.920
to data moving vertically between a data center and external locations.

71
03:25.920 --> 03:30.990
While East West traffic refers to data moving horizontally within a data center
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:25.920 --> 03:30.990
While East West traffic refers to data moving horizontally within a data center

72
03:30.990 --> 03:31.760
as our correct

73
03:31.760 --> 03:38.200
answer, which of the following correctly describes a feature of Google Cloud

74
03:38.200 --> 03:39.080
Platform

75
03:39.080 --> 03:42.760
or GCPs Cloud Firewall.

76
03:42.760 --> 03:47.750
This answer, it integrates directly with Google Cloud Load Balancer to

77
03:47.750 --> 03:49.200
distribute traffic

78
03:49.200 --> 03:51.520
across multiple instances.

79
03:51.520 --> 03:56.160
Well, it can integrate, but it doesn't integrate directly.

80
03:56.160 --> 03:59.400
So this is not going to be a correct answer.

81
03:59.400 --> 04:04.480
It supports the creation of stateful firewall rules that can be applied to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:59.400 --> 04:04.480
It supports the creation of stateful firewall rules that can be applied to

82
04:04.480 --> 04:05.960
individual instances

83
04:05.960 --> 04:12.000
or entire networks, ensuring flexible and granular security control.

84
04:12.000 --> 04:16.160
That sounds like a really good answer, but let's verify the last two.

85
04:16.160 --> 04:20.840
It automatically encrypts all data at, okay, we can stop right there.

86
04:20.840 --> 04:25.200
It doesn't encrypt data, particularly not at rest.

87
04:25.200 --> 04:28.360
So that's going to be an incorrect answer.

88
04:28.360 --> 04:33.690
It provides network address translation services to allow private instances to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
04:28.360 --> 04:33.690
It provides network address translation services to allow private instances to

89
04:33.690 --> 04:34.560
connect to the

90
04:34.560 --> 04:36.640
Internet securely.

91
04:36.640 --> 04:41.120
Google actually provides a separate NAT engine for handling NAT.

92
04:41.120 --> 04:44.520
So this is actually not correct.

93
04:44.520 --> 04:50.110
Leaving again, it supports the creation of stateful firewall rules that can be

94
04:50.110 --> 04:50.760
applied

95
04:50.760 --> 04:55.830
to individual instances or entire networks, ensuring flexible and granular

96
04:55.830 --> 04:57.040
security control

97
04:57.040 --> 04:59.600
as our correct answer.

98
04:59.600 --> 05:07.370
Final question, which of the following is a key feature of the AWS Cloud Fire
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:59.600 --> 05:07.370
Final question, which of the following is a key feature of the AWS Cloud Fire

99
05:07.370 --> 05:07.800
wall?

100
05:07.800 --> 05:11.920
This is going to be very similar to the Google answer.

101
05:11.920 --> 05:14.760
So let's go ahead and take a look at these answers.

102
05:14.760 --> 05:20.150
It provides a built-in DDoS protection service to automatically mitigate

103
05:20.150 --> 05:21.800
attacks without user

104
05:21.800 --> 05:23.520
configuration.

105
05:23.520 --> 05:27.690
And that's actually sort of the key to that one as far as why that answer is

106
05:27.690 --> 05:28.560
incorrect.

107
05:28.560 --> 05:31.440
It does require user configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
05:28.560 --> 05:31.440
It does require user configuration.

108
05:31.440 --> 05:34.440
So this one is going to be incorrect.

109
05:34.440 --> 05:39.250
It supports the creation of stateful firewall rules that can be applied to

110
05:39.250 --> 05:40.160
specific VPC

111
05:40.160 --> 05:44.560
subnets to control inbound and outbound traffic.

112
05:44.560 --> 05:46.200
Again, a good answer.

113
05:46.200 --> 05:48.480
Let's verify the other ones.

114
05:48.480 --> 05:54.650
It integrates with AWS WAF or the web application firewall to protect against

115
05:54.650 --> 05:55.800
web exploits and

116
05:55.800 --> 05:57.440
bot attacks.

117
05:57.440 --> 06:00.560
This is also an incorrect answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:57.440 --> 06:00.560
This is also an incorrect answer.

118
06:00.560 --> 06:05.550
It allows for the creation and management of stateless firewall rules that

119
06:05.550 --> 06:06.640
apply globally

120
06:06.640 --> 06:10.480
across all AWS regions.

121
06:10.480 --> 06:12.640
That's where it's incorrect.

122
06:12.640 --> 06:19.930
The firewall service in AWS, much like the network ACLs, are applied directly

123
06:19.930 --> 06:21.920
to VPC subnets.

124
06:21.920 --> 06:24.360
So that's going to make this answer.

125
06:24.360 --> 06:28.830
It supports the creation of stateful firewall rules that can be applied to

126
06:28.830 --> 06:29.720
specific VPC

127
06:29.720 --> 06:36.280
subnets to control inbound and outbound traffic are correct answer.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
06:29.720 --> 06:36.280
subnets to control inbound and outbound traffic are correct answer.

128
06:36.280 --> 06:41.640
So that concludes this challenge and therefore this skill.

129
06:41.640 --> 06:45.630
If you had any issues answering any of these questions, I would encourage you

130
06:45.630 --> 06:46.200
to go back

131
06:46.200 --> 06:48.920
and review the above sections.

132
06:48.920 --> 06:54.520
Otherwise, congratulations on completing native cloud security features.

133
06:54.520 --> 06:58.600
I hope this has been informative for you and I'd like to thank you for viewing.

134
06:58.600 --> 07:08.600
[BLANK_AUDIO]