Score Higher on Verified SOA-C02 | AWS Certified SysOps Administrator - Associate (SOA-C02) Exam Questions with Answers

The company wants to:

Distribute traffic across two AWS Regions

Minimize response time

From the Route 53 Routing Policies Documentation:

Latency-based routing allows you to route traffic to the AWS Region that provides the lowest latency for the user.

Ideal for applications deployed in multiple AWS Regions.

This matches the scenario exactly.

AWS WAF (Web Application Firewall) is designed to protect web applications from common web exploits that could affect application availability, compromise security, or consume excessive resources. AWS WAF can help mitigate cross-site scripting (XSS) vulnerabilities by allowing users to create rules to filter specific types of HTTP requests.

Create a Web ACL:

Go to the AWS WAF & Shield console.

Click "Create web ACL" and specify a name and the AWS resource to protect (e.g., an Application Load Balancer).

Add Rules to Mitigate XSS:

Within the Web ACL, add a new rule.

Select "Rule builder" and choose a rule type. For mitigating XSS, use "AWS Managed Rules" or create a custom rule.

AWS Managed Rules include a predefined set for XSS that you can enable.

Configure the XSS Rule:

If using a custom rule, configure it to inspect requests and block any that contain XSS patterns.

Use regular expressions or specific patterns to identify malicious scripts.

Deploy the Web ACL:

Once configured, save the Web ACL.

Associate it with your Application Load Balancer or CloudFront distribution to start filtering requests.

Monitor and Adjust:

Monitor the requests being blocked by AWS WAF.

Adjust the rules as necessary to ensure legitimate traffic is not affected and the application remains protected.

AWS WAF Developer Guide

AWS WAF Managed Rules

To meet the requirement of having 50% CPU available to accommodate bursts of traffic and to handle the significant load increase between 09:00 and 17:00, you need a combination of target tracking and scheduled scaling policies.

Target Tracking Scaling Policy:

Create a target tracking scaling policy that keeps the CPU utilization at 50%. This ensures that the fleet scales in or out to maintain the target CPU utilization.

This policy will ensure that the fleet scales automatically based on actual CPU usage, maintaining availability and performance.

Scheduled Scaling Policies:

First Policy: Create a scheduled scaling policy to scale out the fleet at 09:00 when the load increases.

In the AWS Management Console, navigate to the EC2 Auto Scaling Groups.

Select your Auto Scaling group and choose Actions > Edit.

Add a new scheduled action to increase the desired capacity at 09:00.

Second Policy: Create another scheduled scaling policy to scale in the fleet at 17:00 when the load decreases.

Similarly, add another scheduled action to decrease the desired capacity at 17:00.

This approach ensures that the fleet is prepared for the increased load during peak hours while maintaining efficient resource usage during off-peak times.

Target Tracking Scaling Policies

Scheduled Scaling