Amazon Web Services SOA-C02 Actual Questions

 Enable Access Logging for the ALB:

Access logging provides detailed information about requests sent to your load balancer.

Steps:

Go to the AWS Management Console.

Navigate to EC2 and select "Load Balancers."

Select your Application Load Balancer.

Under the "Attributes" tab, enable "Access logs."

Specify an S3 bucket where the logs will be saved.

Enable Access Logs for Your Load Balancer

 Use Amazon Athena to Query the ALB Logs:

Athena allows you to run SQL queries on data stored in S3.

Steps:

Go to the AWS Management Console.

Navigate to Athena.

Create a table for the ALB logs using the appropriate schema.

Run queries to calculate the total bytes sent and received, grouped by the target

field.

Example query:

SELECT target, SUM(received_bytes) as total_received, SUM(sent_bytes) as total_sent

FROM alb_logs

GROUP BY target, port

To ensure that EC2 instances in private subnets can access the internet for software updates while complying with the security policy that requires instances to be in private subnets, you should use a NAT gateway. A NAT gateway allows instances in private subnets to initiate outbound traffic to the internet but prevents the internet from initiating connections to those instances.

Steps:

Create a NAT Gateway:

Open the Amazon VPC console.

In the navigation pane, choose "NAT Gateways".

Choose "Create NAT Gateway".

Select the public subnet where you want to create the NAT gateway.

Choose an Elastic IP address for the NAT gateway.

Choose "Create a NAT Gateway".

Update the Route Table for Private Subnets:

Open the Amazon VPC console.

In the navigation pane, choose "Route Tables".

Select the route table associated with your private subnets.

Choose the "Routes" tab and then "Edit routes".

Add a route with the destination 0.0.0.0/0 and the target as the NAT gateway ID.

Save the changes.

This setup ensures that instances in private subnets can access the internet via the NAT gateway in the public subnet.

To address the performance issues of a CPU-heavy application running on a t2.large EC2 instance, the best course of action is to upgrade to a compute-optimized instance. Compute-optimized instances provide a higher ratio of CPU resources compared to memory, making them ideal for applications that require high CPU performance.

Upgrade to a Compute-Optimized Instance:

Identify a suitable compute-optimized instance type, such as the c5.large, which offers better CPU performance compared to the t2.large.

Stop the current EC2 instance and change the instance type to the chosen compute-optimized instance.

To automate the process of disabling unused IAM user accounts that have not been active for 90 days, using an AWS Config managed rule with an AWS Systems Manager automation runbook is the most operationally efficient method.

Set Up AWS Config Managed Rule:

Open the AWS Config console.

Create a rule using the managed rule iam-user-no-policies-check.

Configure the rule to trigger when IAM users have not been active for 90 days.

AWS Systems Manager Automation Runbook:

Create a Systems Manager automation document (runbook) to disable the access keys for inactive IAM users.

Use the aws:executeAutomation action to disable access keys and passwords.

Schedule the Automation:

Use Amazon EventBridge (formerly CloudWatch Events) to schedule the automation to run periodically.

AWS Config Managed Rules

AWS Systems Manager Automation

Scheduling AWS Systems Manager Automation