SOA-C02 Exam Dumps - AWS Certified SysOps Administrator - Associate (SOA-C02)

Using CloudFormation Stack Sets:

CloudFormation stack sets allow you to deploy CloudFormation stacks across multiple AWS accounts and regions.

Steps:

Go to the AWS Management Console.

Navigate to CloudFormation and select "StackSets."

Click on "Create StackSet."

Provide the template URL or upload a template file.

Configure the stack set options and specify the accounts and regions.

Deploy the stack set to the specified accounts and regions.

To manage common components across multiple CloudFormation templates efficiently:

Create Nested Stacks:

Develop separate CloudFormation templates for the common components.

Use these templates as nested stacks within the main templates.

Enable deletion protection for the DynamoDB tables:

Deletion protection is a feature that prevents accidental deletion of DynamoDB tables. When enabled, it requires an additional step to disable this protection before the table can be deleted.

Steps:

Go to the AWS Management Console.

Navigate to DynamoDB.

Select the table you want to protect.

Choose the "Overview" tab.

Under "Deletion protection," click "Enable deletion protection."

The MixedInstancesPolicy feature in Auto Scaling groups allows for the configuration of both On-Demand and Spot Instances within a single Auto Scaling group, balancing cost savings and high availability:

MixedInstancesPolicy: Enables configuration to maintain a minimum of three On-Demand Instances and add Spot Instances when prices drop, without the need to create separate launch templates.

Setting Maximum Spot Price: Ensures that additional Spot Instances are launched only when within the defined budget.

This solution offers the least management overhead, as it combines both On-Demand and Spot instances seamlessly in one configuration.

https://aws.amazon.com/blogs/compute/using-amazon-rds-proxy-with-aws-lambda/

RDS Proxy acts as an intermediary between your application and an RDS database. RDS Proxy establishes and manages the necessary connection pools to your database so that your application creates fewer database connections. Your Lambda functions interact with RDS Proxy instead of your database instance. It handles the connection pooling necessary for scaling many simultaneous connections created by concurrent Lambda functions. This allows your Lambda applications to reuse existing connections, rather than creating new connections for every function invocation.

Check "Database proxy for Amazon RDS" section in the link to see how RDS proxy help Lambda handle huge connections to RDS MySQL https://aws.amazon.com/blogs/com pute/using-amazon-rds-proxy-with-aws-lambda/

Step-by-Step Explanation:

Understand the Problem:

The web application experiences performance degradation during random periods of increased traffic.

Analyze the Requirements:

Implement a scalable solution to handle varying traffic loads.

Maintain application performance during traffic spikes.

Evaluate the Options:

Option A: Monitor application latency with CloudWatch alarm and increase instance size.

Manually resizing instances is not efficient for handling random traffic spikes.

Option B: Use EventBridge rule to add EC2 instance to ALB.

This approach is not as efficient as Auto Scaling for dynamic traffic management.

Option C: Deploy to an Auto Scaling group with target tracking scaling policy.

Automatically adjusts the number of instances based on traffic demand.

Ensures consistent application performance by scaling in response to traffic changes.

Option D: Deploy to an Auto Scaling group with scheduled scaling policy.

Suitable for predictable traffic patterns but not for random traffic spikes.

Select the Best Solution:

Option C: Using an Auto Scaling group with a target tracking scaling policy ensures the application scales dynamically based on traffic, maintaining performance.

References:

Amazon EC2 Auto Scaling

Target Tracking Scaling Policies

Auto Scaling with a target tracking policy provides a robust solution for handling random traffic increases by dynamically adjusting the number of instances.

When a portfolio is shared between AWS accounts in AWS Service Catalog, the administrator of the second account can import the shared portfolio and add products from the imported portfolio to their local portfolio. However, they cannot modify the imported portfolio directly.

Import the Shared Portfolio:

In the second AWS account, open the AWS Service Catalog console at AWS Service Catalog Console.

Navigate to Portfolios and choose Import portfolio.

Add Products to a Local Portfolio:

Once the portfolio is imported, the administrator can select products from the imported portfolio and add them to a local portfolio for easier management and deployment.

References:

Sharing Portfolios Across Accounts

AWS Service Catalog Admin Guide

AWS WAF (Web Application Firewall) helps protect your web applications from common web exploits and bots. A rate-based rule allows you to control the rate of requests to your application.

Create a Global-Scoped AWS WAF Web ACL:

Navigate to the AWS WAF console.

Create a new Web ACL and choose "Global" for the scope.

Set the default action to "Allow".

Configure a Rate-Based Rule:

Within the Web ACL, add a new rule and select "Rate-based rule".

Define the rate limit (e.g., 2000 requests per 5 minutes).

Set the action to "Block".

Associate Web ACL with CloudFront Distribution:

After creating the Web ACL and rule, go to your CloudFront distribution settings.

In the "General" tab, associate the Web ACL with your CloudFront distribution.

Review and Confirm:

Review the configuration and ensure the Web ACL is correctly associated with the CloudFront distribution.

References:

AWS WAF Rate-Based Rules

Associating AWS WAF with CloudFront