Amazon Web Services Updated CLF-C02 Exam Questions and Answers by kiera

 IAM roles are a secure way to grant permissions to applications running on an Amazon EC2 instance to make calls to other AWS services. IAM roles are entities that have specific permissions policies attached to them. You can create an IAM role and associate it with an EC2 instance when you launch it or later. The applications on the instance can then use the temporary credentials provided by the role to access AWS resources that the role allows. This way, you do not have tostore any long-term credentials or access keys on the instance, which reduces the risk of compromise or misuse12.

The other options are not correct, because:

Security groups are virtual firewalls that control the inbound and outbound traffic for your EC2 instances. Security groups do not grant permissions to access other AWS services, but rather filter the network traffic based on rules that you define3.

AWS Firewall Manager is a service that helps you centrally configure and manage firewall rules across your accounts and resources. AWS Firewall Manager works with AWS WAF, AWS Shield Advanced, and Amazon VPC security groups. AWS Firewall Manager does not grant permissions to access other AWS services, but rather helps you enforce consistent security policies across your AWS infrastructure4.

IAM user SSH keys are credentials that allow you to connect to your EC2 instance using SSH. SSH keys do not grant permissions to access other AWS services, but rather authenticate your identity when you log in to your instance5.

Using an IAM role to grant permissions to applications running on Amazon EC2 instances - AWS Identity and Access Management

IAM roles for Amazon EC2 - Amazon Elastic Compute Cloud

Security groups for your VPC - Amazon Virtual Private Cloud

What is AWS Firewall Manager? - AWS Firewall Manager

Connecting to your Linux instance using SSH - Amazon Elastic Compute Cloud

According to the AWS shared responsibility model, AWS is responsible for the security of the cloud, while the customer is responsible for the security in the cloud. This means that AWS is responsible for protecting the infrastructure that runs all of the services offered in the AWS Cloud, such as the global network, the hardware, the software, and the facilities. The customer is responsible for properly configuring the security of the provided service, such as the guest operating system, the application software, the data, and the network traffic. For abstracted services, such as Amazon RDS, AWS operates the infrastructure layer, the operating system, and the database software, while the customer is responsible for managing their data, classifying their assets, and using IAM tools to apply the appropriate permissions12.

Therefore, the tasks that are the customer’s responsibility are:

Perform client-side data encryption: The customer is responsible for encrypting their data before sending it to AWS, and decrypting it after receiving it from AWS. This ensures that the data is protected in transit and at rest. AWS provides various encryption options, such as AWS Key Management Service (AWS KMS), AWS CloudHSM, and AWS Certificate Manager (ACM)3.

Configure IAM credentials: The customer is responsible for creating and managing IAM users, groups, roles, and policies that control the access to AWS resources and services. IAM credentials include user names, passwords, access keys, and permissions4.

The tasks that are not the customer’s responsibility are:

Establish the global infrastructure: AWS is responsible for building and maintaining the global network of regions, availability zones, and edge locations that provide low latency, high availability, and fault tolerance for the AWS Cloud5.

Secure edge locations: AWS is responsible for protecting the physical security of the edge locations, which are sites that deliver cached content to end users with improved performance6.

Patch Amazon RDS DB instances: AWS is responsible for applying patches and updates to the operating system and the database software of the Amazon RDS DB instances, which are managed relational database service for MySQL, PostgreSQL, Oracle, SQL Server, and Amazon Aurora. References:

Shared Responsibility Model - Amazon Web Services (AWS)

Shared responsibility model - Amazon Web Services: Risk and Compliance

Encryption - Amazon Web Services (AWS)

What Is IAM? - AWS Identity and Access Management

Global Infrastructure - Amazon Web Services (AWS)

Amazon CloudFront Features - Content Delivery Network (CDN)

[What Is Amazon Relational Database Service (Amazon RDS)? - Amazon Relational Database Service]

AWS CloudFormation is a service that allows you to model and provision your AWS resources using templates. You can define your infrastructure as code and automate the creation and update of your resources. AWS CloudFormation also supports nested stacks, change sets, and rollback features to help you manage complex and dynamic environments34. References:

AWS CloudFormation

AWS Certified Cloud Practitioner Exam Guide

AnApplication Load Balancer (ALB)is the best choice for distributing incoming HTTP/HTTPS traffic evenly across multiple Amazon EC2 instances. It operates at theapplication layer (Layer 7 of the OSI model) and is specifically designed to handle HTTP and HTTPS traffic, which is ideal for web applications.

Here is why the ALB is the correct choice:

Layer 7 Load Balancing: The ALB works at the application layer and provides advanced routing capabilities based on content. It can inspect the incoming HTTP requests and make decisions on how to route traffic to various backend targets, which include Amazon EC2 instances, containers, or Lambda functions. This is particularly useful for web applications where you need to make routing decisions based on HTTP headers, paths, or query strings.

HTTP and HTTPS Support: The ALB natively supports HTTP and HTTPS protocols, making it the ideal load balancer for web-based applications. It can efficiently manage and route these types of traffic and handle tasks such as SSL/TLS termination.

Health Checks: The ALB can continuously monitor the health of the registered EC2 instances and only route traffic to healthy instances. This ensures high availability and reliability of the web application.

Path-based and Host-based Routing: The ALB can route traffic based on the URL path or host header. This feature allows the same load balancer to serve multiple applications hosted on different domains or subdomains.

Integration with Auto Scaling: The ALB can integrate seamlessly with Amazon EC2 Auto Scaling. As the number of EC2 instances increases or decreases, the ALB automatically includes the new instances in its traffic distribution pool, ensuring even distribution of incoming requests.

WebSocket Support: It also supports WebSocket and HTTP/2 protocols, which are essential for modern web applications that require real-time, bidirectional communication.

Why other options are not suitable:

A. Amazon EC2 Auto Scaling: This service is used to automatically scale the number of EC2 instances up or down based on specified conditions. However, it does not provide load balancing capabilities. It works well with load balancers but does not handle the distribution of incoming traffic by itself.

C. Gateway Load Balancer: This is designed to distribute traffic to virtual appliances like firewalls, IDS/IPS systems, or deep packet inspection systems. It operates at Layer 3 (Network Layer) and is not ideal for distributing HTTP/HTTPS traffic to EC2 instances.

D. Network Load Balancer: This load balancer operates at Layer 4 (Transport Layer) and is designed to handle millions of requests per second while maintaining ultra-low latencies. It is best suited for TCP, UDP, and TLS traffic but does not provide advanced Layer 7 routing features required for HTTP/HTTPS traffic.