Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

AWS Advanced Network Specialty > Route 53 & DNS > Flashcards

Route 53 & DNS Flashcards

1
Q

What is the AWS term for zones in Route 53

A

Hosted zones

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

What does the AWS term “recordset” refer to?

A

A set of DNS records

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

How many nameservers does Route 53 host a given zone on?

A

Four nameservers

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

What type of DNS records manage the delegation process by pointing to authoritative nameservers for a given domain?

A

NS records

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

What type of DNS records resolve DNS names to IPv6 addresses?

A

AAAA records

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

What type of DNS records resolve DNS names to IPv4 addresses?

A

A records

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

What does CNAME stand for, and what does this type of record do?

A

Canonical name. They allow hostname to hostname mappings.

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

How do you map a CNAME to an IP address?

A

You can’t. CNAME records cannot do this (common exam question)

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

What type of DNS record can you use to add arbitrary information to your zone?

A

A TXT record

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

What is a typical use of TXT records?

A

Proof that you manage a given domain, by getting you to add a predefined TXT record.

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

How many regions is Route 53 available in?

A

Trick question. Route 53 is a global service.

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

True or False: Public hosted zones are accessible from VPCs.

A

True.

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

True or False: in R53 you can associate private hosted zones with VPCs in other AWS accounts.

A

True.

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

True or False: You can only associate private hosted zones with VPCs in other AWS accounts using the CLI or API.

A

True.

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

True or False: Private hosted zones are accessible from any of your VPCs.

A

False. They are accessible only from VPCs that have an association with that private zone.

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

What must you do in order to enable access to a private hosted zone from a VPC?

A

Associate that VPC with the private hosted zone.

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

In the context of AWS, what is the main limitation of CNAME records?

A

They cannot be used on naked/apex records (eg. catagram.io).

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

What Route 53 record type allows mapping a naked/apex record to an A/AAAA record?

A

The ALIAS record.

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

True or False: you can use an ALIAS record to map an A record to an AAAA record.

A

False. The from/to types must be the same type.

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

True or False: ALIAS records are a standard DNS feature.

A

False. ALIAS records are only supported by Route 53.

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

What is the shorter interval for R53 health checkers?

A

10 seconds.

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

You are in the us-east-1 region and have configured a R53 health check. Where will the health checkers be located?

A

Health checkers are ALWAYS distributed globally.
This is to gain a comprehensive picture of a host’s reachability.

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

True or False: ALIAS records are only for mapping naked/apex names to AWS resources.

A

False. ALIAS records can map both normal and naked/apex names.

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

How many DNS records per hostname does Simple Routing support? How many values can each record have?

A

One record per hostname.
That record can have multiple values (eg. IP addresses).

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

What is the drawback of simple routing in Route 53?

A

It doesn’t support health checks.
The A/AAAA record will return all values (IP addresses) irrespective of the health of the underlying server/application.

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

What is the default interval for R53 health checkers?

A

30 seconds.

27
Q

What are calculated health checks?

A

These are checks of other checks.

28
Q

What three types of things can a R53 health-check check?

A
  1. An endpoint (eg. a web server)
  2. Calculated checks (the status of health checks)
  3. The status of a CloudWatch alarm.
29
Q

True or False: health checks can be performed on any internet-accessible host.

A

True.

30
Q

What percentage of health checkers must succeed in order for a resource to be considered healthy?

A

18%

31
Q

What protocols/methods are supported by R53 health checks?

A

TCP, HTTP/HTTPS, and HTTP/HTTPS with string matching.

32
Q

How does R53 failover routing work?

A

A health check is performed on the primary resource. If it’s healthy, then the primary record is returned. If it’s unhealthy, the secondary record is returned.

33
Q

With R53 failover routing, what is typically used as the secondary resource?

A

Typically the secondary record points to an S3 bucket configured as a static website, containing a “down for maintenance” static page.

34
Q

How does R53 multi-value routing work?

A

Up to 8 records are returned. Any unhealthy records won’t be returned to the querying host.

35
Q

What happens in R53 multi-value routing if there are more than 8 records configured?

A

8 healthy records will be randomly chosen from.

36
Q

In R53 multi-value routing, how are health checks configured?

A

Each record is independent and can have an associated health check.

37
Q

What is the premise of R53 weighted routing?

A

Each record is assigned a weight value which determines how often it is returned, in proportion to the total of all weights.

38
Q

With R53 weighted routing, what happens if all weights are zero? Why?

A

All records are returned. This is a measure to prevent the accidental disabling of all records.

39
Q

With R53 weighted routing, what happens if all non-zero weighted records are unhealthy and one or more zero-weighted records are healthy?

A

The healthy zero-weighted records are returned.

40
Q

What is the premise of R53 latency based routing?

A

Each record (for the same name) is mapped to an AWS region. AWS then uses an IP database to ascertain the location of the client, and serves up the DNS record with the lowest expected latency for that client.

41
Q

Typically when would you choose R53 latency based routing?

A

When optimising for performance and user experience.

42
Q

How many records (per name) per region can be used with R53 latency based routing?

A

One record (per name) per region.

43
Q

With R53 latency based routing, what happens if the best record’s health check has failed?

A

R53 returns the next-lowest-latency record.

44
Q

What is the premise of R53 geolocation routing?

A

It returns the record that is most relevant to the client’s location. It does this by discerning the client’s location and attempting to match this to the record’s configured location tag, which can be a US State, Country, Continent, Default, or it can be empty.

45
Q

How does R53 geolocation routing work?

A

DNS records are tagged with a location field, which an be a US State, Country, Continent, Default, or empty. AWS ascertains the location of the user. It then attempts to match this against DNS records with the same location as the user, and only if there’s a match, is a DNS answer returned.

46
Q

With R53 geolocation routing, what happens if there’s no match between all records for the host, and the client’s location?

A

If a record is configured as Default, that record is returned. If no Default is configured, “NO ANSWER” is returned to the requestor.

47
Q

What are three use cases for R53 geolocation routing?

A
  1. Restricting content by territory.
  2. Language-specific or region-specific content.
  3. Load balancing across regional endpoints.
48
Q

True or False: R53 geolocation routing returns the closest record.

A

False!
It returns the most relevant record, location-wise.

49
Q

True or False: R53 geolocation routing returns the most relevant record, location-wise.

A

True.

50
Q

What is the aim of R53 geoproximity routing?

A

It aims to provide records that are as close to your end users as possible.

51
Q

How does R53 geoproximity routing work?

A

Resources are configured with an AWS Region value or a lat+long value. AWS ascertains the location of the user and routes traffic to the closest record available.

52
Q

In R53 geoproximity routing, what does the bias value do?

A

It allows you to expand or shrink the user catchment area around a resource - the area whose users will be routed to that resource.

53
Q

Does R53 geoproximity routing work with non-AWS resources?

A

Yes.

54
Q

With R53 geoproximity routing, what value is used to give the location of non-AWS resources?

A

Lat + long

55
Q

What VPC IP address does R53 DNS use?

A

The .2 VPC address.

56
Q

What other .2 address(es) can the R53 resolver be reached on?

A

The .2 address in each subnet.

57
Q

What kinds of zones can be accessed through the .2 address?

A

Public zones, and associated private zones.

58
Q

Is the R53 resolver accessible through site-to-site VPN or Direct Connect?

A

No. It is only accessible from within the VPC.

59
Q

How are DNS endpoints presented in a subnet?

A

As Elastic Network Interfaces.

60
Q

What do Inbound DNS endpoints do?

A

They allow DNS queries to your VPC from an on-prem network or another VPC.

61
Q

What do Outbound DNS endpoints do?

A

They allow DNS queries from your VPC to an on-prem network or another VPC.

62
Q

What do Outbound DNS endpoint rules do?

A

They control which requests are forwarded.

63
Q

How many ENIs does an R53 Endpoint consist of?

A

Two

64
Q

How many IP addresses are there per R53 Endpoint ENI?

A

One

AWS Advanced Network Specialty (8 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions