Cloud Watch Flashcards

1
Q

CloudWatch Default Host-Level Metrics Consist of

A
  • CPU
  • Network
  • Disk
  • Status Check
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

True or False: RAM Utilization requires a custom metric?

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

CloudWatch Metrics minimum granularity

A

1 minute; however, to see 1-minute intervals, you must enable detailed monitoring

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

CloudWatch Standard intervals

A

5 minutes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

CloudWatch Detailed intervals

A

1 minute

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

True or False: CloudWatch Detailed intervals cost more than standard.

A

True, although there is a free tier for small use cases, there is a higher cost for detailed metrics.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

True or False: Default host-level metrics for Disk include available storage.

A

False. To see storage available on the disk requires a custom metric.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

the four different EBS volume types consist of:

A
General Purpose (SSD) - gp2
Provisioned IOPS (SSD) - io1
Throughput Optimized (HDD) - st1
Cold (HHD) - sc1
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

EBS General Purpose SSD (gp2) use cases

A
  • Recommended for most workloads
  • System boot volumes
  • Virtual Desktops
  • Low-Latency interactive apps
  • Dev/Test environments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

EBS Provisioned IOPS SSD (io1) use cases

A
  • Critical applications that require sustained IOPS of more than 10,000 IOPS, or 160 MiB/s throughput per volume
  • Large database workloads such as MongoDB, Cassandra, MS SQL
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

EBS Throughput Optimized HDD (st1) use cases:

A
  • Streaming workloads that require consistent throughput at low cost
  • Big Data
  • Data warehouses
  • Log processing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Can a Throughput Optimized HDD (st1) be used as a boot volume?

A

No

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Cold HDD (sc1) use cases

A
  • Throughput-oriented storage for large volumes of data.
  • Infrequently accessed data
  • When cost is important
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Can Cold HDD (sc1) be used as a boot volume?

A

No

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

EBS General Purpose SSD maximum volume size

A

16,384 GiB

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

EBS General Purpose SSD maximum IOPS

A

10,000 IOPS. Use provisioned IOPS for applications requiring more.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Maximum IOPS and throughput - Provisioned IOPS

A
  • 32,000 IOPS

- 500 MB/S throughput

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Maximum IOPS and throughput - General Purpose SSD (gp2)

A
  • 10,000 IOPS

- 160MB/s throughput

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Maximum IOPS and throughput - Throughput Optimized HDD (st1)

A
  • 500 IOPS

- 500 MB/s Throughput

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Maximum IOPS and throughput - Cold HDD (sc1)

A
  • 250 IOPS

- 25 MB/s throughput

21
Q

EBS baseline IOPS (non-provisioned IOPS)

A

3 IOPS per GiB. Ex 100GiB EBS volume = 300 IOPS

22
Q

Minimum EBS volume size (GiB) to achieve maximum 10,000 IOPS for non provisioned IOPS volumes

A

3,334. Remember AWS baseline IOPS is 3 IOPS per GiB. 3,334 x 3 = 10,002, which provides 10k IOPS.

23
Q

Should you pre-warm an EBS volume?

A

No. Pre warming EBS volumes is no longer required to achieve maximum performance.

24
Q

In order to achieve maximum performace from a snapshot, what needs to be done?

A

Initialize the volume. Read all the blocks on a restored EBS volume by reading all of the blocks prior to use.

25
Q

EBS CloudWatch Metrics:
VolumeReadBytes
VolumeWriteBytes

A

provides information on I/O for a specified period of time. Examples include total transfered bytes, average size of I/O operations.

Units: Bytes

26
Q

EBS CloudWatch Metrics:
VolumeReadOps
VolumeWriteOps

A

Total number of I/O operations in a specified period of time.

units: Counts

27
Q

EBS CloudWatch Metrics:
VolumeTotalReadTime
VolumeTotalWriteTime

A

The total number of seconds spent by all operations that completed in a specified period of time. If multiple requests are submitted at the same time, the total requests will be greater than the time period measured.

units Seconds

28
Q

EBS CloudWatch Metrics:

VolumeIdleTime

A

The total number of seconds in a specified period of time when no read or write operations were submitted.

Units: Seconds

29
Q

EBS CloudWatch Metrics:

VolumeQueueLength

A

The number of read and write operation requests waiting to be completed in a specified period of time. If the number is greater than 0, you should adjust your disk to increase IOPS.

30
Q

EBS CloudWatch Metrics:

VolumeThroughputPercentage

A

Provisioned IOPS only. The percentage of I/O operations per second delivered or the total IOPS provisioned.

Units: Percent

31
Q

EBS CloudWatch Metrics:

VolumeConsumedReadWriteOps

A

Provisioned IOPS only. Total number of read and write operations in a specified period of time.

units: Count

32
Q

Explain how an I/O operation works

A

I/O are normalized at 256k. Operations =<256k=1 IOPS. Operations >256k equal 2 or more, in increments of 256k. Ex, a 1024k operation will equal 4 IOPS. That is 1024/256=4.

33
Q

EBS CloudWatch Metrics:

Name the volume status check statuses

A
  • Ok - Normal
  • Warning - Degraded, or severely degraded. Operating below expectations.
  • Impaired - Stalled, Not available. Severely impacted, or disabled.
  • Insufficient Data - Insufficient Data. Likely a new metric still collecting data.
34
Q

Can you modify an EBS volume?

A

Yes, in current generation EC2 instance types.

35
Q

How can you modify an EBS volume?

A

Issue the modification command via console or command line.

36
Q

True or False, when you increase an EBS volume, the OS immediatly has access to the extra storage space?

A

False: You must go into the OS and extend the volume.

37
Q

Are Dashboards multi-region?

A

Yes: Just create a widget and change the desired region.

38
Q

Do widgets and dashboards auto-save while you create them?

A

No. Remember to save.

39
Q

True or false: You can retrieve log data from any terminated EC2 or ELB instance after it’s terminated?

A

True: CloudWatch logs are by default stored indefinitely.

40
Q

Can CloudWatch be used for on-premises resources?

A

Yes.

41
Q

What are the requirements for using CloudWatch on-prem?

A

Download and install the SSM and CloudWatch agents.

42
Q

What is the maximum EBS IOPS burst?

A
  1. You can spend IOPS credits to burst IOPS at a lower volume size. Think 3 to 1 IOPS to GiB ratio.
43
Q

What size is an IO operation standardized?

A

256k

44
Q

If an IO operation is greater than 256k, how does AWS handle this?

A

Take the size of the operation and divide by 256k

45
Q

If an IO operation is 1024k, how many IO operations is this?

A

Four operations. 1024 (size of operation) / 256 (size of one IO)

46
Q

Name this volume status:

Ok

A

Normal

47
Q

Name this volume status:

Stalled, Not available. Severely impacted, or disabled.

A

Impaired

48
Q

Name this volume status:

Insufficient Data

A

Insufficient Data. (Likely a new metric still collecting data.)

49
Q

Name this volume status:

Degraded, or severely degraded. Operating below expectations

A

Warning