Brainscape's Knowledge GenomeTM

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


See full index

AWS SAA3 > Route53 > Flashcards

Route53 Flashcards

1
Q

Which type of DNS record should you use to resolve an IP address to a domain name?

  • An A record
  • A CName
  • An SPF record
  • A PTR record
A
  • A PTR record
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Which of the following are main functions of AWS Route 53? (Choose multiple)

  • Register domain names
  • Route internet traffic to the resources for your domain
  • Load-balance traffic among individual AWS resource instances
  • Check the health of your resources
  • Auto Scale your resources
A

Answer: A, B, D

Breakdown
Option C is incorrect because Route 53 is not used for load-balancing traffic among individual AWS resource instances (like a load balancer) rather we integrate it with resources for added functionality (https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/integration-with-other-services.html)
Option E is incorrect. In AWS, Autoscaling is used to scale underlying resources up or down based on pre-determined or dynamic factors.

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

Which protocol is primarily used by DNS to serve requests?

  • Transmission Control Protocol (TCP)
  • Hyper Text Transfer Protocol (HTTP)
  • File Transfer Protocol (FTP)
  • User Datagram Protocol (UDP)
A
  • User Datagram Protocol (UDP)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Your organization had setup a web application on AWS VPC with 4 EC2 instances in a private subnet. They had configured an elastic load balancer to distribute traffic between all 4 EC2 instances. They decided to route traffic from internet to the elastic load balancer via a domain “www.example-web-application.com” which they had already registered. Which type of record set you need to create?

  • A – IPv4 Address with Alias=NO
  • A – IPv4 Address with Alias=YES
  • CNAME – Canonical Name with ALIAS=NO
  • CNAME – Canonical Name with ALIAS=YES
A

Answer: B

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html
Note:
A Record (Address Record) is typically used when an IP address to name conversion is required. This is most commonly used.
A record points a name to a specific IP. If you want example.com to point to the server 10.120.13.14 then you will configure an A record like below
example.com A 10.120.13.14

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

In AWS Route 53 record set, which of the following is not a routing policy?

  • Weighted routing policy
  • Geolocation routing policy
  • Failover routing policy
  • Distributed routing policy
A
  • Distributed routing policy

Options A, B, C are valid routing policies for AWS Route 53.
Following are a list of routing policies.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html

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

Which protocol is used by DNS when response data size exceeds 512 bytes?

  • Transmission Control Protocol (TCP)
  • Hyper Text Transfer Protocol (HTTP)
  • File Transfer Protocol (FTP)
  • User Datagram Protocol (UDP)
A
  • Transmission Control Protocol (TCP)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a benefit of the ALIAS record type in Route53?

  • ALIAS is just a CNAME, and thus the same benefits of a CNAME
  • ALIAS provides a 303 redirect to another URL (eg. www.domain.com to domain.com)
  • ALIAS can be used to direct to a global AWS service endpoint name, even in an A record position
  • ALIAS record can be used to point to on-premises resources, rerouting the user and obfuscating the back end
A

ALIAS can be used to direct to a global AWS service endpoint name, even in an A record position

The ALIAS record can be used to provide a name entry, in a position such as an A record, where IP addresses typically would be required. The Route53 engine still returns an IP to the requestor, but the IP can be dynamic and will point to the necessary service endpoint closes to the user such as S3, CloudFront, etc. “ALIAS is just a CNAME, and thus the same benefits of a CNAME” is incorrect because an ALIAS record is not a CNAME. “ALIAS provides a 303 redirect to another URL (eg. www.domain.com to domain.com)” and “ALIAS record can be used to point to on-premises resources, rerouting the user and obfuscating the back end” are incorrect simply because this is not the way it works.

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

A Solutions Architect is designing a static website that will use the zone apex of a DNS domain (e.g. example.com). The Architect wants to use the Amazon Route 53 service. Which steps should the Architect take to implement a scalable and cost-effective solution? (choose 2)

  • Create a Route 53 hosted zone, and set the NS records of the domain to use Route 53 name servers
  • Host the website on an Amazon EC2 instance, and map a Route 53 Alias record to the public IP address of the EC2 instance
  • Host the website using AWS Elastic Beanstalk, and map a Route 53 Alias record to the Beanstalk stack
  • Serve the website from an Amazon S3 bucket, and map a Route 53 Alias record to the website endpoint
  • Host the website on an Amazon EC2 instance with ELB and Auto Scaling, and map a Route 53 Alias record to the ELB endpoint
A
  • Create a Route 53 hosted zone, and set the NS records of the domain to use Route 53 name servers
  • Serve the website from an Amazon S3 bucket, and map a Route 53 Alias record to the website endpoint

Explanation To use Route 53 for an existing domain the Architect needs to change the NS records to point to the Amazon Route 53 name servers. This will direct the name resolution to Route 53 for the domain name. The most cost-effective solution for hosting the website will be to use an Amazon S3 bucket. To do this you create a bucket using the same name as the domain name (e.g. example.com) and use a Route 53 Alias record to map to it Using an EC2 instance instead of an S3 bucket would be more costly so that rules out 2 options that explicitly mention EC3 Elastic Beanstalk provisions EC2 instances so again this would be a more costly option References: https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html

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

A Solutions Architect is creating an application design with several components that will be publicly addressable. The Architect would like to use Alias records. Using Route 53 Alias records what targets can you specify? (choose 2)

  • On-premise web server
  • Elastic BeanStalk environment
  • VPC endpoint
  • ElastiCache cluster
  • CloudFront distribution
A
  • Elastic BeanStalk environment
  • CloudFront distribution

Explanation Alias records are used to map resource record sets in your hosted zone to Amazon Elastic Load Balancing load balancers, Amazon CloudFront distributions, AWS Elastic Beanstalk environments, or Amazon S3 buckets that are configured as websites You cannot point an Alias record directly at an on-premises web server (you can point to another record in a hosted zone, which could point to an on-premises web server though I’m not sure if this is supported) You cannot use an Alias to point at an ElastiCache cluster or VPC endpoint

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

You host a web application across multiple AWS regions in the world, and you need to configure your DNS so that your end users will get the fastest network performance possible. Which routing policy should you apply?

  • Geolocation routing
  • Latency-based routing
  • Simple routing
  • Weighted routing
A
  • Latency-based routing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Which resource record set would not be allowed for the hosted zone example.com?

  • www.example.com
  • www.aws.example.com
  • www.example.ca
  • www.beta.example.com
A
  • www.example.ca
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Which of the following is not an AWS service that AWS Route 53 can route traffic to?

  • Amazon CloudFront
  • Elastic Load Balancing
  • Amazon RDS
  • Amazon CloudWatch
A

Amazon CloudWatch

Amazon Route 53 integrates with Amazon CloudWatch for monitoring, not for routing traffic.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/integration-with-other-services.html

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

Your company hosts 10 web servers all serving the same content in AWS. They want Route 53 to serve traffic to random web servers. Which routing policy should be used to meet this requirement?

  • Latency Routing
  • Multivalue Routing
  • Weighted Routing
  • Simple Routing
A
  • Multivalue Routing

Multivalue answer routing lets you configure Amazon Route 53 to return multiple values, such as IP addresses for your web servers, in response to DNS queries. Route 53 responds to DNS queries with up to eight healthy records and gives different answers to different DNS resolvers. The choice of which to use is left to the requesting service effectively creating a form or randomisation.

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

Amazon Route 53 cannot route queries to which AWS resource?

  • Amazon CloudFront distribution
  • Elastic Load Balancing loadbalancer
  • Amazon EC2
  • AWS OpsWorks
A

AWS OpsWorks

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

You have deployed a web application targeting a global audience across multiple AWS Regions under the domain name.exampIe.com. You decide to use Route53 Latency-Based Routing to serve web requests to users from the region closest to the user. To provide business continuity in the event of server downtime you configure weighted record sets associated with two web servers in separate Availability Zones per region. Dunning a DR test you notice that when you disable all web sewers in one of the regions Route53 does not automatically direct all users to the other region. What could be happening? {Choose 2 answers)

A. Latency resource record sets cannot be used in combination with weighted resource record sets.
B. You did not setup an HTTP health check for one or more of the weighted resource record sets associated with me disabled web servers.
C. The value of the weight associated with the latency alias resource record set in the region with the disabled sewers is higher than the weight for the other region.
D. One of the two working web sewers in the other region did not pass its HTIP health check.
E. You did not set “Evaluate Target Health” to “Yes” on the latency alias resource record set associated with example com in the region where you disabled the sewers.

A

B. You did not setup an HTTP health check for one or more of the weighted resource record sets associated with me disabled web servers.
E. You did not set “Evaluate Target Health” to “Yes” on the latency alias resource record set associated with example com in the region where you disabled the sewers.

How Health Checks Work in Complex Amazon Route 53 Configurations
Checking the health of resources in complex configurations works much the same way as in simple configurations. However, in complex configurations, you use a combination of alias resource record sets (including weighted alias, latency alias, and failover alias) and nonalias resource record sets to build a decision tree that gives you greater control over how Amazon Route 53 responds to requests.
For more information, see How Health Checks Work in Simple Amazon Route 53 Configurations.
For example, you might use latency alias resource record sets to select a region close to a user and use weighted resource record sets for two or more resources within each region to protect against the failure of a single endpoint or an Availability Zone. The following diagram shows this configuration.
Here’s how Amazon EC2 and Amazon Route 53 are configured:
You have Amazon EC2 instances in two regions, us-east-1 and ap-southeast-2. You want Amazon Route 53 to respond to queries by using the resource record sets in the region that provides the lowest latency for your customers, so you create a latency alias resource record set for each region.
(You create the latency alias resource record sets after you create resource record sets for the indMdual Amazon EC2 instances.)
Within each region, you have two Amazon EC2 instances. You create a weighted resource record set for each instance. The name and the type are the same for both of the weighted resource record sets in each region.
When you have multiple resources in a region, you can create weighted or failover resource record sets for your resources. You can also create even more complex configurations by creating weighted alias or failover alias resource record sets that, in turn, refer to multiple resources.
Each weighted resource record set has an associated health check. The IP address for each health check matches the I P address for the corresponding resource record set. This isn’t required, but it’s the most common configuration.
For both latency alias resource record sets, you set the value of Evaluate Target Health to Yes.
You use the Evaluate Target Health setting for each latency alias resource record set to make Amazon Route 53 evaluate the health of the alias targets-the weighted resource record sets-and respond accordingly.
The preceding diagram illustrates the following sequence of events:
Amazon Route 53 receives a query for exampIe.com. Based on the latency for the user making the request, Amazon Route 53 selects the latency alias resource record set for the us-east-1 region.
Amazon Route 53 selects a weighted resource record set based on weight. Evaluate Target Health is Yes for the latency alias resource record set, so Amazon Route 53 checks the health of the selected weighted resource record set.
The health check failed, so Amazon Route 53 chooses another weighted resource record set based on weight and checks its health. That resource record set also is unhealthy.
Amazon Route 53 backs out of that branch of the tree, looks for the latency alias resource record set with the next-best latency, and chooses the resource record set for ap-southeast-2.
Amazon Route 53 again selects a resource record set based on weight, and then checks the health of the selected resource record set . The health check passed, so Amazon Route 53 returns the applicable value in response to the query.
What Happens When You Associate a Health Check with an Alias Resource Record Set?
You can associate a health check with an alias resource record set instead of or in addition to setting the value of Evaluate Target Health to Yes. However, it’s generally more useful if Amazon Route 53 responds to queries based on the health of the underlying resources- the HTTP sewers, database servers, and
other resources that your alias resource record sets refer to. For example, suppose the following configuration:
You assign a health check to a latency alias resource record set for which the alias target is a group of weighted resource record sets.
You set the value of Evaluate Target Health to Yes for the latency alias resource record set.
In this configuration, both of the following must be true before Amazon Route 53 will return the applicable value for a weighted resource record set:
The health check associated with the latency alias resource record set must pass.
At least one weighted resource record set must be considered healthy, either because it’s associated with a health check that passes or because it’s not associated with a health check. In the latter case, Amazon Route 53 always considers the weighted resource record set healthy.
If the health check for the latency alias resource record set fails, Amazon Route 53 stops responding to queries using any of the weighted resource record sets in the alias target, even if they’re all healthy. Amazon Route 53 doesn’t know the status of the weighted resource record sets because it never looks past the failed health check on the alias resource record set.
What Happens When You Omit Health Checks?

In a complex configuration, it’s important to associate health checks with all of the non-alias resource record sets. Let’s return to the preceding example, but assume that a health check is missing on one of the weighted resource record sets in the us-east-1 region:
Here’s what happens when you omit a health check on a non-alias resource record set in this configuration:
Amazon Route 53 receives a query for exampIe.com. Based on the latency for the user making the request, Amazon Route 53 selects the latency alias resource record set for the us-east-1 region.

Amazon Route 53 looks up the alias target for the latency alias resource record set, and checks the status of the corresponding health checks. The health check for one weighted resource record set failed, so that resource record set is omitted from consideration.
The other weighted resource record set in the alias target for the us-east-1 region has no health check. The corresponding resource might or might not be healthy, but without a health check, Amazon Route 53 has no way to know. Amazon Route 53 assumes that the resource is healthy and returns the applicable value in response to the query.

What Happens When You Set Evaluate Target Health to No?
In general, you also want to set Evaluate Target Health to Yes for all of the alias resource record sets. In the following example, all of the weighted resource record sets have associated health checks, but Evaluate Target Health is set to No for the latency alias resource record set for the us-east-1 region:
Here’s what happens when you set Evaluate Target Health to No for an alias resource record set in this configuration:
Amazon Route 53 receives a query for exampIe.com. Based on the latency for the user making the request, Amazon Route 53 selects the latency alias resource record set for the us-east-1 region.
Amazon Route 53 determines what the alias target is for the latency alias resource record set, and checks the corresponding health checks. They’re both failing. Because the value of Evaluate Target Health is No for the latency alias resource record set for the us-east-1 region, Amazon Route 53 must choose one resource record set in this branch instead of backing out of the branch and looking for a healthy resource record set in the ap-southeast-2 region.

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

Which type of DNS record should you use to resolve a domain name to another domain name?

  • An A record
  • A CNAME record
  • An SPF record
  • A PTR record
A
  • A CNAME record
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

You need to create a simple, holistic check for your system’s general availability and uptime. Your system presents itself as an HTTP-speaking API. What is the simplest tool on AWS to achieve this with?

  • Route53 Health Checks
  • CloudWatch Health Checks
  • AWS ELB Health Checks
  • EC2 Health Checks
A
  • Route53 Health Checks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

The development team at X company have created a new web-based application that will soon be launched. The application will utilize 20 EC2 instances for the web front-end. Due to concerns over latency, you will not be using an ELB but still want to load balance incoming connections across multiple EC2 instances. You will be using Route 53 for the DNS service and want to implement health checks to ensure instances are available.

What two Route 53 configuration options are available that could be individually used to ensure connections reach multiple web servers in this configuration? (choose 2)

  • Use Route 53 simple load balancing which will return records in a round robin fashion
  • Use Route 53 multivalue answers to return up to 8 records with each DNS query
  • Use Route 53 weighted records and give equal weighting to all 20 EC2 instances
  • Use Route 53 failover routing in an active-active configuration
  • Use Route 53 Alias records to resolve using the zone apex
A
  • Use Route 53 multivalue answers to return up to 8 records with each DNS query
  • Use Route 53 weighted records and give equal weighting to all 20 EC2 instances

Explanation The key requirement here is that you can load balance incoming connections to a series of EC2 instances using Route 53 AND the solution must support health checks. With multi-value answers Route 53 responds with up to eight health records (per query) that are selected at random The weighted record type is similar to simple but you can specify a weight per IP address. You create records that have the same name and type and assign each record a relative weight. In this case you could assign multiple records the same weight and Route 53 will essentially round robin between the records We cannot use the simple record type as it does not support health checks Alias records let you route traffic to selected AWS resources, such as CloudFront distributions and Amazon S3 buckets. They do not provide equal distribution to multiple endpoints or multi-value answers Failover routing is used for active/passive configurations only

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

You have an application that for legal reasons must be hosted in the United States when U.S. citizens access it. The application must be hosted in the European Union when citizens of the EU access it. For all other citizens of the world, the application must be hosted in Sydney. Which routing policy should you choose in order to achieve this?

  • Latency-basedrouting
  • Simple routing
  • Geolocation routing
  • Failoverrouting
A
  • Geolocation routing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What main functions can Route 53 perform? Select the best answer from the following options.

  • Domain registration and DNS routing
  • Domain registration, DNS routing, and health checking in any combination
  • DNS routing and health checking for domains hosted on AWS
  • Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service that is designed to give developers and businesses an extremely reliable and cost-effective way to route end users to Internet applications. It can be used together with CloudWatch, a service which allows you to monitor and manage applications. While Route 53 is not a domain reseller, it allows customers to bring their own domain names with them.
A

Domain registration, DNS routing, and health checking in any combination

Route53 is Amazons DNS web service that delivers the domain registration, DNS routing and health checking function in any combination.

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

Which is a function that Amazon Route 53 does not perform?

  • Domain registration
  • DNS service
  • Load balancing
  • Health checks
A
  • Load balancing
22
Q

You are putting together a design for a web-facing application. The application will be run on EC2 instances behind ELBs in multiple regions in an active/passive configuration. The website address the application runs on is awsboy.com. You will be using Route 53 to perform DNS resolution for the application.

How would you configure Route 53 in this scenario based on AWS best practices? (choose 2)

  • Use a Failover Routing Policy
  • Connect the ELBs using CNAME records
  • Use a Weighted Routing Policy
  • Set Associate with Health Check to “Yes”
  • Connect the ELBs using Alias records
A

Use a Failover Routing Policy
Connect the ELBs using Alias records

The failover routing policy is used for active/passive configurations. Alias records can be used to map the domain apex (awsboy.com) to the Elastic Load Balancers. Weighted routing is not an active/passive routing policy. All records are active and the traffic is distributed according to the weighting You cannot use CNAME records for the domain apex record, you must use Alias records When using the failover routing policy with Alias records set Evaluate Target Health to “Yes”? and do not use health checks set “Associate with Health Check” to “No”

23
Q

A friend tells you he is being charged $100 a month to host his WordPress website, and you tell him you can move it to AWS for him and he will only pay a fraction of that, which makes him very happy. He then tells you he is being charged $50 a month for the domain, which is registered with the same people that
set it up, and he asks if it’s possible to move that to AWS as well. You tell him you aren’t sure, but will look into it. Which of the following statements is true in regards to transferring domain names to AWS?

A. You can’t transfer existing domains to AWS.
B. You can transfer existing domains into Amazon Route 53’s management.
C. You can transfer existing domains via AWS Direct Connect.
D. You can transfer existing domains via AWS Import/Expor

A

B. You can transfer existing domains into Amazon Route 53’s management.

With Amazon Route 53, you can create and manage your public DNS records with the AWS Management Console or with an easy-to-use API. If you need a domain name, you can find an available name and register it using Amazon Route 53. You can also transfer existing domains into Amazon Route 53’s management.
Reference: http://aws.amazon.com/route53/

24
Q

What are the different hosted zones that can be created in Amazon Route 53?

  1. Publichostedzone 2. Global hosted zone 3. Private hosted zone

1 and 2
1 and 3
2 and 3
1,2, and 3

A

1 and 3

25
Q

You wish to point mydomain.com to an Application Load Balancer in Route53. What is the record type ideal for this?

  • CNAME
  • A Record
  • Alias Record
  • Named Record
A
  • Alias Record

An Alias record will be ideal for this. Because this is a zone apex, an A record or Alias record are our only real choices because a CNAME cannot be used at the zone apex as per DNS standards. An Alias record can be used as an A record. One problem with using an A record is that an A record cannot point to a name. The Application Load Balancer (ALB) must be referenced by name. As such, an A record will not be sufficient. An Alias can be provided in place of an A record allowing us to point to the name. This will ultimately be treated as an A record per DNS RFC standards on the requests, providing an IP to the requestor; however, on the back-end allowing for a dynamic range of IP addresses of the ALBs.

26
Q

You are planning to launch a web based application in two different regions within US on AWS due to your organization compliance policies. You have setup 2 EC2 instances attached to an elastic load balancer in us-east-1. You have replicated the same setup in us-west-1. Now you have two load balancers which needs to listen traffic from internet. You would want to split the requests equally between both load balancers from a domain name hosted on your AWS Route 53. How should you configure your Route 53 record sets?

  • Create two record sets, one each for us-east-1 and us-west-1 load balancers. Set weighted routing policy with weights as 1 and 2 respectively.
  • Create two record sets, one each for us-east-1 and us-west-1 load balancers. Set weighted routing policy with weights as 1 and 1 respectively.
  • Create one record set and select both load balancers as Alias Targets. Set weighted routing policy with weights as 1 and 2 respectively.
  • Create one record set and select both load balancers as Alias Targets. Set weighted routing policy with weights as 1 and 1 respectively.
A

Create two record sets, one each for us-east-1 and us-west-1 load balancers. Set weighted routing policy with weights as 1 and 1 respectively.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-weighted
Option A is not correct.
According to the above screenshot, with weights 1 and 2, the request distribution is 1:2 which is not equal.
Option B is correct as the distribution ratio would be 1:1
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/TutorialManagingOver100WRR.html
Options C and D are not correct.
A recordset can only have one Alias Target
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-values-alias.html#rrsets-values-alias-alias-target

27
Q

Which type of record is commonly used to route traffic to an IPv6 address?

  • An A record
  • ACNAME
  • An AAAA record
  • An MX record
A
  • An AAAA record
28
Q

Which DNS record can be used to store human-readable information about a server, network, and other accounting data with a host?

  • A TXT record
  • An MX record
  • An SPF record
  • A PTR record
A
  • A TXT record
29
Q

You are configuring Route 53 for a customer’s website. Their web servers are behind an Internet-facing ELB. What record set would you create to point the customer’s DNS zone apex record at the ELB?

  • Create a CNAME record that is an Alias, and select the ELB DNS as a target
  • Create an A record pointing to the DNS name of the load balancer
  • Create an A record that is an Alias, and select the ELB DNS as a target
  • Create a PTR record pointing to the DNS name of the load balancer
A
  • Create an A record that is an Alias, and select the ELB DNS as a target

Explanation An Alias record can be used for resolving apex or naked domain names (e.g. example.com). You can create an A record that is an Alias that uses the customer’s website zone apex domain name and map it to the ELB DNS name A CNAME record can’t be used for resolving apex or naked domain names A standard A record maps the DNS domain name to the IP address of a resource. You cannot obtain the IP of the ELB so you must use an Alias record which maps the DNS domain name of the customer’s website to the ELB DNS name (rather than its IP) PTR records are reverse lookup records where you use the IP to find the DNS name

30
Q

When configuring Amazon Route 53 as your DNS service for an existing domain, which is the first step that needs to be performed?

  • Create hosted zones.
  • Create resource record sets.
  • Register a domain with Amazon Route 53.
  • Transfer domain registration from current registrar to Amazon Route 53.
A
  • Create hosted zones.
31
Q

You have a web application hosted on AWS VPC with a single EC2 instance with Auto Scaling enabled. You have also assigned elastic IP address to the EC2 instance. When you access the elastic IP address, you are able to successfully connect to your web application. You decided to route requests to your application from a custom domain through Route 53. You have performed the setup on Route 53. However, when you access your custom domain name from internet, you get “Server Not Found” error. Which of the following could be a reason?

  • Route 53 service is for internal application routing. It does not support routing traffic from internet.
  • You must configure elastic load balancer in order to use Route 53 for web application hosting.
  • IP address configured in Route 53 DNS record set might be incorrect.
  • The resource on EC2 instance that you’re routing traffic to is unavailable.
A

IP address configured in Route 53 DNS record set might be incorrect.

Option A and B are not valid statements.
Option C is correct.
Although option D looks correct, the question states the connection to web application was successful when connected through elastic IP address. So this option is not the cause of failure.

32
Q

You have launched an RDS instance in your VPC. The endpoint that is assigned to your DB instance is a long, partially random, alphanumeric string, for example, myexampledb.a1b2c3d4wxyz.us-west-2.rds.amazonaws.com. Your organization wants to use a name that’s easier to remember, so you registered a domain name using Route53 service. Which type of record set do you need to create?

  • A – IPv4 Address with Alias=NO
  • A – IPv4 Address with Alias=YES
  • CNAME – Canonical Name with ALIAS=NO
  • CNAME – Canonical Name with ALIAS=YES
A

CNAME – Canonical Name with ALIAS=NO

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-rds-db.html
Note:
A Record (Address Record) is typically used when an IP address to name conversion is required. This is most commonly used.
A record points a name to a specific IP. If you want example.com to point to the server 10.120.13.14 then you will configure an A record like below
example.com A 10.120.13.14
A CNAME record (Canonical record) points a name to another name. Typically a complex name with alphanumeric characters can be shortened to a user understandable format
blog.example.com CNAME blog235_github_VJSL.io.net
In the question, the AWS generated resource name is complex i.e myexambledb.a1b2c3d4…….
This can be converted to a user-friendly name by using a CNAME record.

33
Q

Your application has a global user base, and in order to improve user experience you have deployed an instance in both the us-east-1 and eu-central-1 regions. Which routing policy would you use to ensure users get the best experience possible?

  • Latency-based Routing
  • Geolocation Routing
  • Weighted Routing
  • Geoproximity Routing
A
  • Latency-based Routing

Latency Based routing will use data on the latency between the users’ location and the location of your services in AWS to return the address which has the lowest latency for the user that will result in an improved user experience. Although Geolocation or Geoproximity could be used to route users to instances closest to them, latency will change over time with changes to network connectivity and routing over the internet, and the closest location may not be the one with least latency. Weighted routing will not help in this scenario.

34
Q

Which of the following statements are true about Amazon Route 53 resource records? Choose 2 answers

  • An Alias record can map one DNS name to another Amazon Route 53 DNS name.
  • A CNAME record can be created for your zone apex.
  • An Amazon Route 53 CNAME record can point to any DNS record hosted anywhere.
  • TTL can be set for an Alias record in Amazon Route 53.
  • An Amazon Route 53 Alias record can point to any DNS record hosted anywhere.
A
  • An Alias record can map one DNS name to another Amazon Route 53 DNS name
  • An Amazon Route 53 CNAME record can point to any DNS record hosted anywhere.
35
Q

Which port number is used to serve requests by DNS?

  • 22
  • 53
  • 161
  • 67
A
  • 53
36
Q

You are rolling out A and B test versions of a web application to see which version results in the most sales. You need 10 percent of your traffic to go to version A, 10 percent to go to version B, and the rest to go to your current production version. Which routing policy should you choose to achieve this?

  • Simple routing
  • Weighted routing
  • Geolocation routing
  • Failover routing
A

Weighted routing

37
Q

Does Amazon Route 53 support NS Records?

  • Yes, it supports Name Service records
  • No
  • It supports only MX records.
  • Yes, it supports Name Server records.
A

Yes, it supports Name Server records.

38
Q

You recently got hired by a sole proprietor specializing in baking and selling oatcakes within the state of Maryland, which is in the East Coast of the United States. The sole proprietor is ready to launch a website to expand her business online and sell on a national scale. She wants assurance that the website is always available to customers throughout the United States. Using Amazon Route 53 and EC2, which of the following is the best course of action?

  • Set up a simple routing policy in Route 53 for the website that switches between the EC2 instance launched in the us-east 1 Availability Zone and a second EC2 instance launched in the us-west-1 Availability Zone.
  • Set up a failover routing policy in Route 53 for the website that has an EC2 instance in the us-east-1 Availability Zone as the primary resource and another EC2 instance in the us-west-1 Availability Zone as the secondary resource.
  • Set up a failover routing policy in Route 53 for the website that has an EC2 instance in the us-east-1 Availability Zone as the primary resource and another EC2 instance in the eu-west-2 Availability Zone as the secondary resource.
  • Set up a geolocation routing policy in Route 53 for the website that directs traffic to the EC2 instance in the us-east 1 Availability Zone as the area where the company is based. It will failover to the EC2 instance in the ap-southeast-1 Availability Zone as the secondary resource when necessary.
  • Set up a geolocation routing policy in Route 53 for the website that directs traffic to the EC2 instance in the us-east 1 Availability Zone as the area where the company is based. It will failover to the EC2 instance in the us-west-1 Availability Zone as the secondary resource when necessary.
A

Set up a failover routing policy in Route 53 for the website that has an EC2 instance in the us-east-1 Availability Zone as the primary resource and another EC2 instance in the us-west-1 Availability Zone as the secondary resource.

Ideally, you should architect AWS usage to take advantage of multiple Regions and Availability Zones. Based on the client’s demands, you need an active-passive failover configuration within the United States — not between the United States and Singapore, for example. So, setting up a failover routing policy for the website with both EC2 instances in North American Regions and Availability Zones is the correct option. With Maryland falling within the US East Region, the secondary resources can be deployed in the US West Region for coast-to-coast national coverage. A simple routing policy won’t work, since it distributes web traffic randomly. And while geolocation routing can address the client’s national reach plans, it will not address the website’s resiliency.

39
Q

A user has configured ELB with three instances. The user wants to achieve High Availability as well as redundancy with ELB. Which of the below mentioned AWS services helps the user achieve this for ELB?

  • Route 53
  • AWS Mechanical Turk
  • Auto Scaling
  • AWS EMR
A
  • Route 53
40
Q

Which DNS record must all zones have by default?

SPF
TXT
MX
SOA

A

SOA

41
Q

You would like to host a static website for awsboy.com on AWS. You will be using Route 53 to direct traffic to the website. Which of the below steps would help you achieve your objectives? (Choose 2)

  • Create an Alias record that points to the S3 bucket
  • Create an S3 bucket named digitalcloud.training
  • Create an “SRV” record that points to the S3 bucket
  • Create a CNAME record that points to the S3 bucket
  • Use any existing S3 bucket that has public read access enabled
A
  • Create an Alias record that points to the S3 bucket
  • Create an S3 bucket named digitalcloud.training

Explanation S3 can be used to host static websites and you can use a custom domain name with S3 using a Route 53 Alias record. When using a custom domain name the bucket name must be the same as the domain name The Alias record is a Route 53 specific record type. Alias records are used to map resource record sets in your hosted zone to Amazon Elastic Load Balancing load balancers, Amazon CloudFront distributions, AWS Elastic Beanstalk environments, or Amazon S3 buckets that are configured as websites You cannot use any bucket when you want to use a custom domain name. As mentioned above you must have a bucket name that matches the domain name You must use an Alias record when configuring an S3 bucket as a static website – you cannot use SRV or CNAME records

42
Q

Your company has its primary production site in Western Europe and its DR site in the Asia Pacific. You need to configure DNS so that if your primary site becomes unavailable, you can fail DNS over to the secondary site. Which DNS routing policy would best achieve this?

  • Weighted routing
  • Geolocation routing
  • Simple routing
  • Failover routing
A
  • Failover routing
43
Q

Which statements are true about Amazon Route 53? (Choose 2 answers)

  • Amazon Route 53 is a region-level service
  • You can register your domain name
  • Amazon Route 53 can perform health checks and failovers to a backup site in the even of the primary site failure
  • Amazon Route 53 only supports Latency-based routing
A
  • You can register your domain name
  • Amazon Route 53 can perform health checks and failovers to a backup site in the even of the primary site failure
44
Q

Which of the following types can be monitored for health checks by AWS Route 53? Choose 2 correct options.

  • Endpoints
  • State of CloudWatch alarm
  • EC2 instance health checks
  • DNS service health checks
A
  • Endpoints
  • State of CloudWatch alarm

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-types.html

45
Q

You have four EC2 instances deployed in four Availability Zones, and all of them are associated with a single domain name. You want Amazon Route 53 to split web traffic evenly between the four servers. Which of the following routing policies will accomplish that?

  • Failover routing policy
  • Simple routing policy
  • Weighted routing policy
  • Latency routing policy
A

Weighted routing policy

With weighted routing, you can associate the IP addresses with the domain name and route 25 percent of the web traffic to each of the four servers.

46
Q
  • Does Route 53 support MX Records?

Yes
It supports CNAME records, but not MX records.
No
Only Primary MX records. Secondary MX records are not supported.

A

Yes

47
Q

Which DNS records are commonly used to stop email spoofing and spam?

MX records
SPF records
A records
C names

A

SPF records

48
Q

Which DNS record should you use to configure the transmission of email to your intended mail server?

SPF records
A records
MX records
SOA record

A

MX records

49
Q

Which of the following are correct options for logging and monitoring AWS Route 53 service? Choose 3 correct options.

Amazon CloudWatch
AWS VPC Flow Logs
AWS Route 53 dashboard
Access logs in S3
AWS CloudTrail

A

Amazon CloudWatch
AWS Route 53 dashboard
AWS CloudTrail

Option A is correct.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/monitoring-health-checks.html
Option B is not correct.
VPC Flow logs are for logging the network traffic going in/coming out of a specific VPC. Route 53 is not a VPC specific service.
Option C is correct.
Option D is not correct.
Route 53 does not log directly into AWS S3. However, you can export the cloudwatch or cloudtrail logs into S3.
Option E is correct.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/logging-using-cloudtrail.html

50
Q

Your organization had created an S3 bucket for static website hosting. They had created and configured all necessary components for static website and ready to use with host name http://example-bucket.com.s3-website-us-east-2.amazonaws.com. However, they would like to get the website served through domain name www.example-bucket.com which is already registered. Which type of record set you need to create?

A – IPv4 Address with Alias=NO
A – IPv4 Address with Alias=YES
CNAME – Canonical Name with ALIAS=NO
CNAME – Canonical Name with ALIAS=YES

A

A – IPv4 Address with Alias=YES

https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html#root-domain-walkthrough-s3-tasks
In the recordset, the name is nginxroute53.com, this is the domain name, not IP. In the value, you are providing IP address for mapping. Here, you need to choose No for Alias, because the domain is mapping with IP.
Instead of IP, if you are choosing a load balancer DNS link, you can choose either A record or a Cname record, and Alias will be set to Yes. Because of your domain to the AWS ELB domain link.

AWS SAA3 (6 decks)

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