Route 53 Flashcards

1
Q

What does DNS stand for?

A

Domain Name System

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

Translates the human friendly hostnames into the machine IP addresses

A

DNS

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

(DNS Terminologies) .. Amazon Route 53, GoDaddy, …

A

Domain Registrar

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

(DNS Terminologies) … A, AAAA, CNAME, NS, …

A

DNS Records

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

(DNS Terminologies) … contains DNS records

A

Zone File

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

(DNS Terminologies) … resolves DNS queries (Authoritative or Non-Authoritative)

A

Name Server

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

(DNS Terminologies) … .com, .us, .in, .gov, .org, …

A

Top Level Domain (TLD)

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

(DNS Terminologies) … amazon.com, google.com, …

A

Second Level Domain (SLD)

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

A highly available, scalable, fully
managed and Authoritative DNS

A

Amazon Route 53

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

The customer (you)
can update the DNS records

A

Authoritative DNS

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

Is a Domain Registrar

A

Amazon Route 53

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

Does Amazon Route 53 have the ability to check the health of your resources?

A

YES

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

The only AWS service which provides 100% availability SLA

A

Amazon Route 53

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

How you want to route traffic for a domain

A

Route 53 - Records

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

What does each Record contain? (5)

A
  • Domain/subdomain Name – e.g., example.com
  • Record Type – e.g., A or AAAA
  • Value – e.g., 12.34.56.78
  • Routing Policy – how Route 53 responds to queries
  • TTL – amount of time the record cached at DNS Resolvers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

(must know)A /AAAA / CNAME / NS
(advanced)CAA/DS/MX/NAPTR/PTR/SOA/TXT/SPF/SRV

A

DNS record types Route 53 supports

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

Must know Route 53 RecordTypes

A

A
AAAA
CNAME
NS

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

maps a hostname to IPv4

A

Route 53 – Record Types
A

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

maps a hostname to IPv6

A

Route 53 – Record Types
AAAA

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

maps a hostname to another hostname

A

Route 53 – Record Types
CNAME

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

For a CNAME record type, the target is a domain name which must have an _____ or ______ record

A

Route 53 – Record Types
A
AAAA

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

Can’t create a ______ record for the top node of a DNS namespace (Zone Apex)

A

Route 53 – Record Types
CNAME

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

Name Servers for the Hosted Zone

A

Route 53 – Record Types
NS

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

Control how traffic is routed for a domain

A

Route 53 – Record Types
NS

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

A container for records that define how to route traffic to a domain and its subdomains

A

Hosted Zones

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

2 types of Hosted Zones

A

Public Hosted Zones
Private Hosted Zones

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

contains records that specify how to route traffic on the Internet (public domain names) application1.mypublicdomain.com

A

Public Hosted Zones

28
Q

contain records that specify how you route traffic within one or more VPCs (private domain names) application1.company.internal

A

Private Hosted Zones

29
Q

How much do you pay per month per hosted zone??

A

$0.50

30
Q

What does TTL stand for??

A

Time To Live

31
Q

What are Records TTL

A

The time the records is on the cache

32
Q

TTL is mandatory for each DNS record except for which type of Record?

A

Alias Records

33
Q

Points a hostname to any other hostname. (app.mydomain.com => blabla.anything.com)

A

CNAME

34
Q

ONLY FOR NON ROOT DOMAIN (aka. something.mydomain.com)

A

CNAME

35
Q

Points a hostname to an AWS Resource (app.mydomain.com => blabla.amazonaws.com)

A

Route 53 – Alias Records

36
Q
  • Free of charge
  • Native health check
A

Alias

37
Q
  • Maps a hostname to an AWS resource
  • An extension to DNS functionality
  • Automatically recognizes changes in the resource’s IP addresses
A

Alias Records

38
Q

Unlike CNAME, it can be used for the top node of a DNS namespace (Zone Apex)

A

Alias Records

39
Q

is always of type A/AAAA for AWS resources (IPv4 / IPv6)

A

Alias Records

40
Q

You can’t set the TTL

A

Alias Records

41
Q

What are the Alias Records Targets

A
  • Elastic Load Balancers
  • CloudFront Distributions
  • API Gateway
  • Elastic Beanstalk environments
  • S3 Websites
  • VPC Interface Endpoints
  • Global Accelerator accelerator
  • Route 53 record in the same hosted zone
42
Q

Can set an ALIAS record for an EC2 DNS name?

A

NO

43
Q

Define how Route 53 responds to DNS queries

A

Routing Policies

44
Q

Route 53 Supports the following Routing Policies (8)

A
  • Simple
  • Weighted
  • Failover
  • Latency based
  • Geolocation
  • Multi-Value Answer
  • Geoproximity (using Route 53 Traffic Flow feature)
  • IP based
45
Q
  • Typically, route traffic to a single resource
  • Can specify multiple values in the same record
  • If multiple values are returned, a random one is chosen by the client
  • When Alias enabled, specify only one AWS resource
  • Can’t be associated with Health Checks
A

Routing Policies – Simple

46
Q
  • Control the % of the requests that go to each specific resource
  • Assign each record a relative weight:
  • 𝑡𝑟𝑎𝑓𝑓𝑖𝑐(%)= !”#$%&’()*+,”-#’#-)”-().
    /01 (‘ *22 &%” 3”#$%&+ ‘() *22 )”-().+
  • don’t need to sum up to 100
  • DNS records must have the same name and type
  • Can be associated with Health Checks
  • Use cases: load balancing between regions, testing new application versions…
  • Assign a value of 0 to a record to stop sending traffic to a resource
  • If all records have a value of 0, then all records will be returned equally
A

Routing Policies – Weighted

47
Q
  • Redirect to the resource that is close to us
  • Is based on traffic between users and AWS Regions
  • Germany users may be directed to the US
  • Can be associated with Health Checks (has a failover capability)
A

Routing Policies – Latency-based

48
Q

HTTP Health Checks are only for _______?

A

public resources

49
Q

What are 3 ways that a Health Checks can monitor?

A

Endpoints
Other Health Checks (Calculated Health Checks)
CloudWatch Alarms

50
Q

Are Health Checks integrated with CloudWatch metrics??

A

YES

51
Q

About _______ global health checkers will check the endpoint health

A

15

52
Q

For a Health check monitoring an Endpoint, What is the Healthy/UnhealthyThreshold by default?

A

3

53
Q

For a Health check monitoring an Endpoint, what is the monitoring interval and what could you set it at for a higher cost??

A

30 secs
10 secs

54
Q

For a Health check monitoring an Endpoint, what protocols are supported??

A

HTTP, HTTPS, andTCP

55
Q

If > _______% of health checkers report the endpoint is healthy, Route 53 considers it Healthy. Otherwise, it’s Unhealthy

A

18

56
Q

Health Checks pass only when the endpoint responds with the ______ and _____ status codes

A

2XX
3XX

57
Q

Health Checks can be setup to pass / fail based on the text in the first ________ of the response

A

5120 bytes

58
Q

Do you need to configure your router/firewall to allow incoming requests from Route 53 Health Checkers

A

YES

59
Q
  • Combine the results of multiple Health Checks into a single Health Check
  • You can use OR, AND, or NOT
A

Calculated Health Checks

60
Q

Calculated Health Checks can monitor up to ______ Child Health Checks

A

256

61
Q

Can you specify how many of the health checks need to pass to make the parent pass???

A

YES

62
Q
  • Route 53 health checkers are outside the VPC
  • They can’t access private endpoints (private VPC or on-premises resource)
  • You can create a CloudWatch Metric and associate a CloudWatch Alarm, then create a Health Check that checks the alarm itself
A

Health Checks for Private Hosted Zones

63
Q
  • Different from Latency-based!
  • This routing is based on user location
  • Specify location by Continent, Country or by US State (if there’s overlapping, most precise location selected)
  • Should create a “Default” record (in case there’s no match on location)
  • Use cases: website localization, restrict content distribution, load balancing, …
  • Can be associated with Health Checks
A

Routing Policies – Geolocation

64
Q
  • Route traffic to your resources based on the geographic location of users and resources
  • Ability to shift more traffic to resources based on the defined bias
  • To change the size of the geographic region, specify bias values:
    • To expand (1 to 99) – more traffic to the resource
    • To shrink (-1 to -99) – less traffic to the resource
  • Resources can be:
    • AWS resources (specify AWS region)
    • Non-AWS resources (specify Latitude and Longitude)
  • You must use Route 53 Traffic Flow to use this feature
A

Routing Policies – Geoproximity

65
Q
  • Use when routing traffic to multiple resources
  • Route 53 return multiple values/resources
  • Can be associated with Health Checks (return only values for healthy resources)
  • Up to 8 healthy records are returned for each Multi-Value query
  • Multi-Value is not a substitute for having an ELB
A

Routing Policies – Multi-Value

66
Q
  • Routing is based on clients’ IP addresses
  • You provide a list of CIDRs for your clients and the corresponding endpoints/locations (user-IP-to-endpoint mappings)
  • Use cases: Optimize performance, reduce network costs…
  • Example: route end users from a particular ISP to a specific endpoint
A

Routing Policies – IP-based Routing