AWS Solution Architecture Associate is the comprehensive Training for those who run enterprise architecture programs, as well as solutions architects or Beginners who want to learn AWS Solution Architecture Associate covering Identity Access Management (IAM), Amazon Simple Storage Service (S3), Serverless Websites, Autoscaling & Load Balancing, etc. If you are new to AWS, then I would recommend you to check our blog on AWS Solution Architecture and Its Roles and Responsibilities.
This blog will cover the FAQs of AWS Certified Solution Architect Associate Training covering Object Storage Options and Designing Computing Environment. This blog will help you to clear your concepts with AWS Solution Architect.
On Day 6 we have covered Module 6: LoadBalancer, Route53 & AutoScaling, which includes the following Modules:
The course which is available on the Membership Portal looks like below.
Q1. Why do we use Auto-Scaling?
A1. Auto Scaling is a service in AWS that automatically monitors resources to maintain performance for applications as demand increases or decreases. As the demand increases it scales up the resources and as the demand decreases it scales down the resources.
Q2. What is the difference between auto-scaling and load balancing?
A2. Load balancing evenly distributes load to application instances in all availability zones in a region while auto-scaling makes sure instances scale up or down depending on the load.
Also Read: AWS Elastic Load Balancing
Q3. How many auto-scaling groups can you have per region?
A3. You can have 200 Auto Scaling Groups per region. (defined by AWS)
Q4. What is the price of Amazon Route 53?
A4. Amazon Route 53 charges are based on actual usage of the service for Hosted Zones, Queries, and Health Checks. You pay only for what you use.
Q5. Can I use spot and on-demand instances with an Autoscaling group?
A5. When you specify the settings as part of the Auto Scaling group, you can request to launch Spot Instances only after launching a certain number of On-Demand Instances and then continue to launch some combination of On-Demand Instances and Spot Instances as the group scales.
Q6. Difference between Horizontal and Vertical autoscaling?
A6. In short, the main difference between vertical and horizontal autoscaling in AWS is that in vertical autoscaling the capacity or size of the instance is increased as per demand while in horizontal autoscaling the number of instances under the load balancer is expanded as per requirement.
Q7. What can I scale with AWS Auto Scaling?
A7. Amazon EC2 Auto Scaling groups.
Amazon Elastic Container Service services
Amazon EC2 Spot Fleets.
Amazon DynamoDB throughput capacity.
Aurora replicas for Amazon Aurora.
Q8. What is Route 53 hosted zone?
A8. A hosted zone is analogous to a traditional DNS zone file; it represents a collection of records that can be managed together, belonging to a single parent domain name. All the resource record sets within a hosted zone must have the hosted zone’s domain name as a suffix.
Also Read: Amazon Route 53
Q9. How load balancing can be used to control traffic?
A9. When users send requests to your website, the requests go to the load balancer and the load balancer then decides which server to use according to various load balancing algorithms. In mission-critical applications where high availability is a necessity, load balancers can route traffic to failover servers.
Q10. What is an internal and external load balancer?
A10. The external load balancer is used to route external HTTP traffic into the cluster. The internal load balancer is utilized for internal service discovery and load balancing within the cluster.
Q11. Why do we need a sticky session?
A11. A sticky one keeps a user’s session on the server where it started. A non-sticky balancer puts each request in a session on a different server. The advantage of sticky sessions is that it is not necessary to move session-related data from one server to another server. This can produce more efficient performance.
Q12. Can an ELB classic load balancer span across multiple regions?
A12. No, you cannot set up ELB with its member nodes spread across regions. ELBs currently can only be set up for EC2 instances spread across AZ’s. You can also spread the ELB itself across AZs by using cross-zone load balancing.
Q13. What if too many requests are sent to the sticky server?
A13. A server can become overloaded if it accumulates too many sessions, or if specific sticky sessions require a high number of resources. This could result in your load balancer having to shift the client to a different server mid-session, resulting in data loss.
Q14. On what layer the classic load balancer works?
A14. The AWS Classic Load Balancer works on Layer 4 of the OSI model. This means that the load balancer routes traffic between clients and backend servers based on IP address and TCP port. For example, an ELB at the given IP address receives a request from a client on TCP port 80 (HTTP).
Now let’s talk about Module 7: Networking and Monitoring Services which includes the following lessons
The course which is available on the Membership Portal looks like below.
Q1. Can I buy a domain from AWS?
A1. You can register new domain names with Route 53 as well as manage DNS records for your domain. Select Get Started Now under Domain Registration then Click the Register Domain button.
Q2. What is the difference between public and private subnet in AWS?
A2. The instances in the public subnet can send outbound traffic directly to the Internet, whereas the instances in the private subnet can’t. While the instances in the private subnet can access the Internet by using a network address translation (NAT) gateway that resides in the public subnet.
Q3. What is the significance of name servers?
A3. Nameservers play an essential role in directing traffic on the Internet by helping to connect your domain name with the IP address of your web server. To do this, they help web browsers and other services access your domain’s DNS records.
Q4. Does AWS use IPv6?
A4. EC2 instances in an Amazon VPC now offer native support for the IPv6 protocol. IPv6 can be enabled for existing and new VPCs through the AWS management console, API/SDK, and CLI. There is no extra charge to use IPv6 in VPC. By default, every IPv6 address is public and internet routable.
Q5. How does AWS DHCP work?
A5. The Dynamic Host Configuration Protocol (DHCP) provides a standard for passing configuration information to hosts on a TCP/IP network. The options field of a DHCP message contains configuration parameters, including the domain name, domain name server, and the NetBIOS-node type.
Q6. What is ARN in AWS?
A6. Amazon Resource Names (ARNs) uniquely identify AWS resources. We require an ARN when you need to specify a resource unambiguously across all of AWS, such as in IAM policies, Amazon Relational Database Service (Amazon RDS) tags, and API calls. Contents. Format. Resource ARNs.
Q7. What is CloudWatch vs CloudTrail?
A7. AWS CloudWatch monitors your AWS resources and applications, whereas CloudTrail monitors the activity in your AWS environment. For instance, with CloudWatch, you can scale your applications, whereas, with CloudTrail, you can see who did what to your applications, you might find issues. They are not mutually exclusive, and you can set CloudTrail to send events to a CloudWatch log, for instance.
Also Read: Difference between ClouldTrail and CloudWatch
Q8. What are IPV4 and IPV6?
A8. IPV4 - IPv4 stands for Internet Protocol version 4. It is the underlying technology that makes it feasible for us to connect our devices to the web. Every time a device accesses the Internet, it will be assigned a unique, numerical IP address like 99.48.227.227. To send the data from one computer to another computer through the web, a data packet must be transferred across the network containing the IP addresses of both devices.
IPV6 – IPv6 is the next-generation Internet Protocol (IP) address standard considered to supplement and eventually replace IPv4. Every computer, mobile phone, home automation component, and any other device connected to the Internet requires a numerical IP address to communicate between other devices.
Q9. Is VPC peering is one-directional and what is transitive peering?
A9. VPC peering connections are confined in A REGION. Multiple VPC’s in a SINGLE REGION can talk to each other provided they have the appropriate route table configuration. VPC peering connections can be bidirectional, totally depends on the route table configuration. VPC Peering connections are not transitive. Rather than using VPC peering, you can use an AWS Transit Gateway that acts as a network transit hub, to interconnect your VPCs and on-premises networks. You cannot route packets directly from VPC B to VPC C through VPC A.
Also Read: Amazon Virtual Private Cloud
Q10. What is a VPC subnet?
A10. A subnet is a key component in VPC. A VPC can contain all public subnets or public/private subnet combinations. A private Subnet is a subnet that does not have a route to the internet gateway. A subnet can be configured as a VPN-only subnet by routing traffic via a virtual private gateway.
Q11. What is a NAT gateway?
A11. NAT gateway is used to enable instances in a private subnet to connect to the internet or other AWS services, but prevent the internet from initiating a connection with those instances.
Q12. What is AWS trusted advisor used for?
A12. AWS Trusted Advisor is a tool that gives you real-time guidance to help you provision your resources following AWS best practices. Trusted Advisor checks help optimize your AWS infrastructure, increase security and performance, reduce your overall costs, and regularly monitor service limits.
Also Read: AWS Trusted Advisor
Q13. What is the difference between nat gateway and internet gateway?
A13. A NAT device forwards traffic from the instances in the private subnet to the internet or other AWS services, and then sends the response back to the instances while Internet Gateway is used to allow resources in your VPC to access the internet.
Q14. What are the different types of DNS Records?
A14. The different record types are as follows:
- A (Host address)
- AAAA (IPv6 host address)
- ALIAS (Auto resolved alias)
- CNAME (Canonical name for an alias)
- MX (Mail eXchange)
- NS (Name Server)
- PTR (Pointer)
- SOA (Start Of Authority)
Related Links/References
- AWS Solution Architect Questions Day 1: Introduction To Cloud & AWS
- AWS Solution Architect Training Day 2 & Day 3 FAQ’s
- AWS Solution Architect Training Day 4 & Day 5 FAQ’s
- Overview of Amazon Web Services & Concept
- How to create a free tier account in AWS
- AWS Certified DevOps Engineer Professional DOP-C01
- AWS Certified Solutions Architect: Roles & Responsibilities
Next Task For You
Begin your journey towards becoming a Certified AWS Solution Architect Associate by joining our FREE Informative Class on Amazon AWS Solution Architect Certification For Beginners & Q/A by clicking on the below image.
The post AWS Solution Architect Training Day 6 & Day 7 FAQ’s appeared first on Cloud Training Program.