Most Recent Amazon SOA-C02 Exam Dumps

AWS Global Accelerator and Amazon CloudFront are separate services that use the AWS global network and its edge locations around the world. CloudFront improves performance for both cacheable content (such as images and videos) and dynamic content (such as API acceleration and dynamic site delivery). Global Accelerator improves performance for a wide range of applications over TCP or UDP by proxying packets at the edge to applications running in one or more AWS Regions. Global Accelerator is a good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP, as well as for HTTP use cases that specifically require static IP addresses or deterministic, fast regional failover. Both services integrate with AWS Shield for DDoS protection.

https://medium.com/awesome-cloud/aws-difference-between-application-load-balancer-and-network-load-balancer-cb8b6cd296a4 https://aws.amazon.com/global-accelerator/faqs/?nc1=h_ls

AWS WAF (Web Application Firewall) helps protect web applications from common web exploits that could affect availability, compromise security, or consume excessive resources. It can be used to mitigate cross-site scripting (XSS) vulnerabilities.

Set Up AWS WAF:

Open the AWS WAF console at AWS WAF Console.

Create a new Web ACL.

Add Rules for Protection:

Add managed rules that include protection against common vulnerabilities, including XSS.

AWS provides managed rule groups, such as the AWS Managed Rules for Common Vulnerabilities and Exposures (CVE) which include protections against XSS.

Associate WAF with the Application:

Associate the Web ACL with the resources you want to protect (e.g., CloudFront distribution, Application Load Balancer).

AWS WAF

AWS WAF Managed Rules

The issues experienced by users with legacy browsers typically stem from the SSL/TLS ciphers that are supported or enforced by the ALB. Modern security policies may exclude older ciphers that are necessary for compatibility with older browsers. Here's how to resolve it:

Access the ALB Settings: Go to the AWS Management Console, navigate to the ALB settings, and locate the SSL negotiation configurations.

Modify Security Policy: Update the SSL/TLS security policy on the ALB to include ciphers that are compatible with legacy browsers. AWS provides predefined security policies, and some of these policies are designed to support older ciphers while still maintaining a level of security that complies with general best practices.

Apply Changes: Once the security policy is updated, the ALB will start using this new configuration, which should resolve compatibility issues with legacy browsers without needing to replace the SSL certificate or alter the infrastructure.

This solution maintains the operational efficiency of the setup and avoids the need for additional resources like a second ALB or new certificates.

To implement a highly available solution that provides the functionality to use a minimum of three On-Demand instances and three Spot instances when prices are at a certain threshold, defining an Amazon EC2 Auto Scaling group using a launch template is the most suitable solution. This approach minimizes operational overhead by consolidating configuration and management tasks.

Define a Launch Template:

Use the provided AMI in the launch template.

Configure the instance type, key pair, security groups, and other necessary parameters.

Create an Auto Scaling Group:

Use the launch template for the Auto Scaling group.

Specify a desired capacity of three On-Demand instances.

Configure the Auto Scaling group to use mixed instances policies, which allow you to specify a combination of On-Demand and Spot instances.

Set the maximum price for Spot instances in the launch template to ensure that Spot instances are used only when their prices are below the specified threshold.

Configuration Steps:

Open the EC2 console and navigate to 'Launch Templates.'

Create a new launch template with the necessary configurations.

Navigate to 'Auto Scaling Groups' and create a new Auto Scaling group using the launch template.

Configure the desired capacity, minimum capacity, and maximum capacity.

Under 'Advanced Options,' specify the mixed instances policy and set the maximum price for Spot instances.

Amazon EC2 Auto Scaling Launch Templates

Auto Scaling Mixed Instances Policies

Objective:

Address high and unpredictable CPU usage by automating the scaling of resources.

Using Auto Scaling Policies:

Scaling policies can dynamically adjust the number of instances in an Auto Scaling group based on metrics like CPU utilization.

Steps to Implement:

Step 1: Increase the maximum capacity of the Auto Scaling group (e.g., from 2 to a higher value like 5).

Step 2: Create a scaling policy:

Use a target tracking scaling policy with a threshold of 80% CPU utilization.

When the CPU usage exceeds 80%, additional instances will be launched automatically.

Step 3: Monitor scaling behavior and adjust thresholds or capacities if necessary.

AWS Reference:

Target Tracking Scaling Policies: Scaling Policies for Auto Scaling Groups

Dynamic Scaling Best Practices: Dynamic Scaling in Auto Scaling

Why Other Options Are Incorrect:

Option A: Deploying additional instances outside the Auto Scaling group is not scalable and defeats the purpose of automation.

Option B: Switching to burstable instances does not resolve the issue since the workload is CPU-bound and consistently high.

Option D: Increasing desired capacity does not account for the unpredictability of peak periods, as it sets a static scaling behavior rather than dynamic.