Route 53 Flashcards

1
Q

Route 53

A

Fully managed DNS Service

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

Location

Route 53

A

Not Regional

Route 53

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

High availability

Route 53

A

Region-based routing failover

Route 53

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

SLA

Route 53

A

100% Availability

Route 53

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

target monitoring option

Route 53

A

May set up health checks

Route 53

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

Record composition (5)

Route 53

A
  • Name
  • Type
  • Value
  • Routing Policy
  • TTL

Route 53

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

CNAME limitation

Route 53

A

record cannot be the apex of the zone

Route 53

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

Alias record

Route 53

A

points hostname to AWS resource

Route 53

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

domain root option

Alias record

A

may be the root doman name

Alias record

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

cost

Alias record

A

free of charge to query

Alias record

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

health option

Alias record

A

can include native health check

Alias record

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

automation option

Alias record

A

automatically recognizes changes to resource IP address

Alias record

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

record type

Alias record

A

A or AAAA

Alias record

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

TTL limitation

Alias record

A

not configurable

Alias record

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

target limitation

Alias record

A

target may not be an EC2 DNS name

Alias record

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

health check

R53

A

monitor resources

R53

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

purpose

R53 health check

A

automate DNS failover

R53 health check

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

types of health checks (3)

R53 health check

A
  • monitor endpoint
  • calculated health check
  • monitor CloudWatch alarms

R53 health check

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

monitor endpoint

R53 health check

A

query HTTP (or HTTPS, TCP) and confirm response

R53 health check

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

number of global, public health checkers

monitor endpoint

A

15

monitor endpoint

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

interval options (2)

monitor endpoint

A
  • 30s
  • 10s (fast)

monitor endpoint

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

threshold for when endpoint is healthy

monitor endpoint

A

> 18% health checkers report healthy

monitor endpoint

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

status codes required for pass

monitor endpoint

A

2## or 3##

monitor endpoint

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

additional health check monitor option

monitor endpoint

A

health check can monitor for text in first 5kB of response

monitor endpoint

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
firewall requirement | monitor endpoint
public monitor IPs must be allowed by firewall rules | monitor endpoint
26
Calculated health check | R53 health check
combines multiple health checkes into one | R53 health check
27
how you can organize checks | Calculated health check
can use OR, AND, or NOT logic | Calculated health check
28
child health check limit | Calculated health check
256 | Calculated health check
29
customizable option | Calculated health check
customize how many health checks are needed to pass | Calculated health check
30
monitor CloudWatch alarms | R53 health check
allows for health checks on private hosted zones | R53 health check
31
3rd party registrar | R53
may purchase domain through 3rd party and use R53 | R53
32
how to link registray | R53 3rd party registrar
set NS entries on registrars to AWS nameservers | R53 3rd party registrar
33
Fully managed DNS Service
Route 53
34
Not Regional | Route 53
Location | Route 53
35
Region-based routing failover | Route 53
High availability | Route 53
36
100% Availability | Route 53
SLA | Route 53
37
May set up health checks | Route 53
target monitoring option | Route 53
38
* Name * Type * Value * Routing Policy * TTL | Route 53
Record composition (5) | Route 53
39
record cannot be the apex of the zone | Route 53
CNAME limitation | Route 53
40
points hostname to AWS resource | Route 53
Alias record | Route 53
41
may be the root doman name | Alias record
domain root option | Alias record
42
free of charge to query | Alias record
cost | Alias record
43
can include native health check | Alias record
health option | Alias record
44
automatically recognizes changes to resource IP address | Alias record
automation option | Alias record
45
A or AAAA | Alias record
record type | Alias record
46
not configurable | Alias record
TTL limitation | Alias record
47
target may not be an EC2 DNS name | Alias record
target limitation | Alias record
48
monitor resources | R53
health check | R53
49
automate DNS failover | R53 health check
purpose | R53 health check
50
* monitor endpoint * calculated health check * monitor CloudWatch alarms | R53 health check
types of health checks (3) | R53 health check
51
query HTTP (or HTTPS, TCP) and confirm response | R53 health check
monitor endpoint | R53 health check
52
15 | monitor endpoint
number of global, public health checkers | monitor endpoint
53
* 30s * 10s (fast) | monitor endpoint
interval options (2) | monitor endpoint
54
>18% health checkers report healthy | monitor endpoint
threshold for when endpoint is healthy | monitor endpoint
55
2## or 3## | monitor endpoint
status codes required for pass | monitor endpoint
56
health check can monitor for text in first 5kB of response | monitor endpoint
additional health check monitor option | monitor endpoint
57
public monitor IPs must be allowed by firewall rules | monitor endpoint
firewall requirement | monitor endpoint
58
combines multiple health checkes into one | R53 health check
Calculated health check | R53 health check
59
can use OR, AND, or NOT logic | Calculated health check
how you can organize checks | Calculated health check
60
256 | Calculated health check
child health check limit | Calculated health check
61
customize how many health checks are needed to pass | Calculated health check
customizable option | Calculated health check
62
allows for health checks on private hosted zones | R53 health check
monitor CloudWatch alarms | R53 health check
63
may purchase domain through 3rd party and use R53 | R53
3rd party registrar | R53
64
set NS entries on registrars to AWS nameservers | R53 3rd party registrar
how to link registrar | R53 3rd party registrar