Elastic IPs u0026 Route 53 DNS Fundamentals Quiz Quiz

Explore key concepts about Elastic IP addresses, DNS basics, and record management using Route 53. This quiz helps reinforce understanding of core principles and features relevant to cloud networking and domain management.

1. Understanding Elastic IP Addresses

   Which statement best describes an Elastic IP address in cloud networking?

   1. A private IP address used only within local networks
   2. A static IPv4 address designed for dynamic cloud resources
   3. An IPv6 address reserved for specific accounts
   4. A variable IP address that changes when resources restart

   Explanation: Elastic IP addresses are static public IPv4 addresses meant for cloud infrastructure, allowing flexible reassignment if resources change. They are not private addresses, so 'A private IP' is incorrect. An Elastic IP remains constant even if a resource is stopped and started, unlike a variable IP, making option three wrong. Elastic IPs are IPv4 only, not IPv6, which eliminates the last option.

2. Purpose of DNS with Route 53

   What is the primary function of DNS services like Route 53 when managing domain names?

   1. Encrypting all traffic between users and websites
   2. Translating domain names into IP addresses for network routing
   3. Storing files for website hosting
   4. Backing up cloud resources

   Explanation: DNS, or Domain Name System, converts readable domain names into machine-usable IP addresses, enabling proper direction of network traffic. Storing files is the role of storage services, not DNS. Traffic encryption is handled by security protocols such as HTTPS, not DNS itself. DNS does not back up resources, so that answer is also incorrect.

3. Elastic IP Association

   If you attach an Elastic IP address to a web server and later stop that server, what happens to the Elastic IP address?

   1. It is released and becomes available for general use
   2. It remains allocated and can be reassigned to another resource
   3. It becomes a private IP address automatically
   4. It is converted into a DNS record

   Explanation: When a server is stopped, the Elastic IP remains allocated to your account, allowing reassignment to new or restarted resources. It is not released automatically, as that would risk losing control. Elastic IPs do not become private nor magically convert to DNS records. The correct answer reflects its persistent and reusable design.

4. DNS Record Types

   Which DNS record type would you use to point a domain directly to an Elastic IP address?

   1. CNAME record
   2. MX record
   3. TXT record
   4. A record

   Explanation: An A record maps a domain name directly to an IPv4 address such as an Elastic IP. MX records specify mail exchangers, not web server IPs. CNAME records alias one domain to another but can’t point directly to an IP address. TXT records are for arbitrary text strings, not direct IP mapping.

5. Route 53 Hosted Zones

   Which best describes a hosted zone in Route 53?

   1. A temporary storage location for DNS logs
   2. An address range for Elastic IPs
   3. A single record assigning an IP to a domain
   4. A container for all DNS records for a specific domain

   Explanation: A hosted zone organizes all the DNS records for a domain, grouping various resource records under a single namespace. A single record just relates to part of DNS configuration, not the container. Hosted zones don't function as storage for DNS logs, nor do they relate to Elastic IP address ranges.

6. Elastic IP Limitation

   What happens if you allocate more Elastic IP addresses than your account’s default limit?

   1. Additional Elastic IPs are billed at a higher rate automatically
   2. Previously allocated Elastic IPs are automatically released
   3. You cannot allocate more Elastic IPs until you request and receive a limit increase
   4. Extra Elastic IPs become inactive until used

   Explanation: Cloud providers set default limits for Elastic IP allocation. Exceeding the limit requires a formal request for an increase before more can be allocated. No automatic billing rate changes apply nor are current IPs released. Inactive Elastic IPs do not accumulate beyond the limit.

7. DNS TTL Value

   In DNS records, what is the purpose of the TTL (Time To Live) value?

   1. It sets the maximum lifetime of a domain registration
   2. It determines the record’s priority level
   3. It specifies how long a record is cached by DNS resolvers
   4. It measures server bandwidth usage

   Explanation: TTL controls the duration a DNS resolver caches a record before refreshing it. Priority values apply to MX records, not TTL. Domain registration lifespans are not managed with TTL. Server bandwidth is unrelated to DNS TTL, so that option is inapplicable.

8. Elastic IP Release Scenario

   If you no longer need an Elastic IP address, what is the best practice action?

   1. Change it to a private address
   2. Release the Elastic IP to avoid unnecessary charges
   3. Keep it allocated for future use to prevent loss
   4. Convert it into a CNAME record

   Explanation: When not associated with a running resource, an unused Elastic IP may incur charges, so releasing it helps reduce unnecessary costs. Elastic IPs cannot be converted to CNAME records or private addresses. Keeping unused ones leads to extra billing and is not a recommended practice.

9. CNAME vs A Record

   Which is a key difference between a CNAME and an A record in DNS management?

   1. CNAME records are used only for email delivery
   2. A CNAME aliases a domain to another domain, while an A record maps a domain to an IP address
   3. A records are only for internal use within cloud networks
   4. A records can contain IPv6 addresses, while CNAME cannot

   Explanation: CNAME records point one domain to another, allowing redirects or aliases, while A records directly map domains to IP addresses. CNAME is not reserved for email, that is an MX record's role. A records map to IPv4, not IPv6. Both A and CNAME records are used publicly, not just internally.

10. Alias Record in Route 53

    What is an Alias record in Route 53 most commonly used for?

    1. Pointing a domain to another resource without needing a fixed IP address
    2. Allocating new Elastic IP addresses
    3. Automatically encrypting DNS queries
    4. Assigning a permanent email address to a user

    Explanation: Alias records allow domains to point to resources whose IP addresses may change, such as load balancers, without needing static addresses. They are not used for setting up email addresses or allocating IPs. Encrypting DNS queries is also not handled by Alias records, but by security protocols.