AWS Interview Questions and Answers
Question - 91 : - What are the different uses of the various load balancers in AWS Elastic Load Balancing?
Answer - 91 : -
Application Load Balancer
Used if you need flexible application management and TLS termination.
Network Load Balancer
Used if you require extreme performance and static IPs for your applications.
Classic Load Balancer
Used if your application is built within the EC2 Classic network
Question - 92 : - How can you use AWS WAF in monitoring your AWS applications?
Answer - 92 : -
AWS WAF or AWS Web Application Firewall protects your web applications from web exploitations. It helps you control the traffic flow to your applications. With WAF, you can also create custom rules that block common attack patterns. It can be used for three cases: allow all requests, prevent all requests, and count all requests for a new policy.
Question - 93 : - What are the different AWS IAM categories that you can control?
Answer - 93 : -
Using AWS IAM, you can do the following:
- Create and manage IAM users
- Create and manage IAM groups
- Manage the security credentials of the users
- Create and manage policies to grant access to AWS services and resources
Question - 94 : - What are the policies that you can set for your users’ passwords?
Answer - 94 : -
Here are some of the policies that you can set:
- You can set a minimum length of the password, or you can ask the users to add at least one number or special characters in it.
- You can assign requirements of particular character types, including uppercase letters, lowercase letters, numbers, and non-alphanumeric characters.
- You can enforce automatic password expiration, prevent reuse of old passwords, and request for a password reset upon their next AWS sign in.
- You can have the AWS users contact an account administrator when the user has allowed the password to expire.
Question - 95 : - What is the difference between an IAM role and an IAM user?
Answer - 95 : -
The two key differences between the IAM role and IAM user are:
- An IAM role is an IAM entity that defines a set of permissions for making AWS service requests, while an IAM user has permanent long-term credentials and is used to interact with the AWS services directly.
- In the IAM role, trusted entities, like IAM users, applications, or an AWS service, assume roles whereas the IAM user has full access to all the AWS IAM functionalities.
Question - 96 : - What are the managed policies in AWS IAM?
Answer - 96 : -
There are two types of managed policies; one that is managed by you and one that is managed by AWS. They are IAM resources that express permissions using IAM policy language. You can create, edit, and manage them separately from the IAM users, groups, and roles to which they are attached.
Question - 97 : - How does AWS IAM help your business?
Answer - 97 : -
IAM enables to:
- Manage IAM users and their access - AWS IAM provides secure resource access to multiple users
- Manage access for federated users – AWS allows you to provide secure access to resources in your AWS account to your employees and applications without creating IAM roles
Question - 98 : - What Is Amazon Route 53?
Answer - 98 : -
Amazon Route 53 is a scalable and highly available Domain Name System (DNS). The name refers to TCP or UDP port 53, where DNS server requests are addressed.
Question - 99 : - What Is Cloudtrail and How Do Cloudtrail and Route 53 Work Together?
Answer - 99 : -
CloudTrail is a service that captures information about every request sent to the Amazon Route 53 API by an AWS account, including requests that are sent by IAM users. CloudTrail saves log files of these requests to an Amazon S3 bucket. CloudTrail captures information about all requests. You can use information in the CloudTrail log files to determine which requests were sent to Amazon Route 53, the IP address that the request was sent from, who sent the request, when it was sent, and more.
Question - 100 : - What is the difference between Latency Based Routing and Geo DNS?
Answer - 100 : -
The Geo Based DNS routing takes decisions based on the geographic location of the request. Whereas, the Latency Based Routing utilizes latency measurements between networks and AWS data centers. Latency Based Routing is used when you want to give your customers the lowest latency possible. On the other hand, Geo Based routing is used when you want to direct the customer to different websites based on the country or region they are browsing from.