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

To ensure high availability and disaster recovery for the RDS for MySQL database, follow these steps:

Create a Cross-Region Read Replica:

In the RDS console, create a cross-Region read replica of the primary database instance. This read replica will provide high availability and the lowest RTO and RPO in case of a disaster.

Using AWS Systems Manager to schedule a maintenance window for restarting EC2 instances outside business hours provides a straightforward and automated approach.

AWS Systems Manager Maintenance Window: Allows for daily scheduling, ensuring that restarts occur consistently outside of business hours.

AWS-RestartEC2Instance Runbook: This runbook can be assigned to the maintenance window, automating the reboot process and minimizing manual intervention.

Reduced Disruption: The scheduled restart ensures the application remains operational during business hours.

AWS CloudFormation StackSets extends the capability of stacks by enabling you to create, update, or delete stacks across multiple accounts and AWS Regions

If a Lambda function is not being invoked by an Amazon EventBridge (formerly CloudWatch Events) rule, the likely issue is a missing permission. The Lambda function needs permission to be invoked by the EventBridge rule.

Steps:

Add Permission to Lambda Function:

Open the AWS Lambda console.

Select your Lambda function.

Choose "Configuration" and then "Permissions".

Under the "Resource-based policy" section, add a policy that grants EventBridge permission to invoke your function.

Example policy:

json

Copy code

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Principal": {

"Service": "events.amazonaws.com"

},

"Action": "lambda:InvokeFunction",

"Resource": "arn:aws:lambda:REGION:ACCOUNT_ID:function:FUNCTION_NAME",

"Condition": {

"ArnLike": {

"AWS:SourceArn": "arn:aws:events:REGION:ACCOUNT_ID:rule/RULE_NAME"

}

}

}

]

}

Verify the EventBridge Rule:

Open the Amazon EventBridge console.

Select the rule that targets your Lambda function.

Ensure that the rule is correctly configured to match events and the target is your Lambda function.

References:

AWS Lambda Permissions Model

Amazon EventBridge Rules

For high-performance computing (HPC) applications that require minimized network latency and maximized network throughput, the best strategy is to use a cluster placement group. Here’s why:

Cluster Placement Group:

Instances in a cluster placement group are placed within a single Availability Zone, which allows them to communicate using high-bandwidth, low-latency connections.

This is ideal for HPC workloads that require high network throughput and low latency.

https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-records-examples.html#flow-log-example-accepted-rejected

https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-records-examples.html#

Accepted and rejected traffic: In this example, RDP traffic (destination port 3389, TCP protocol) to network interface eni-1235b8ca123456789 in account 123456789010 was rejected. 2 123456789010 eni-1235b8ca123456789 172.31.9.69 172.31.9.12 49761 3389 6 20 4249 1418530010 1418530070 REJECT OK

VPC peering allows two VPCs to communicate with each other securely. By configuring VPC peering between the two VPCs, the SysOps administrator will be able to give the EC2 instance in VPC1 the ability to connect to the database in VPC2. Once the VPC peering is configured, the EC2 instance will be able to communicate with the database using the private IP address of the DB instance in the private subnet.

STORAGE_FULL State:

When an RDS instance is in the STORAGE_FULL state, automated backups cannot be performed because there is insufficient storage available.

Steps to Resolve:

Go to the AWS Management Console.

Navigate to RDS and select the DB instance.

Check the storage metrics to confirm the STORAGE_FULL state.

Increase the allocated storage for the DB instance to provide sufficient space for automated backups.

To achieve maximum cost savings and flexibility for a 24/7 running application across different AWS regions and operating systems, the best approach is to use a Compute Savings Plan. Compute Savings Plans provide the most flexibility by automatically applying to any EC2 instance usage regardless of instance family, size, OS, tenancy, or AWS Region, and also apply to AWS Fargate and AWS Lambda usage.

Understand Compute Savings Plans:

Compute Savings Plans offer significant savings over On-Demand prices, with the flexibility to use the compute option that best suits your needs.

Purchase a Compute Savings Plan:

Login to the AWS Management Console.

Navigate to the Savings Plans section.

Choose Purchase Savings Plan and select Compute Savings Plan.

Define the hourly commitment amount and the term length (one or three years).

Monitor and Optimize Usage:

Ensure that your usage aligns with the Savings Plan to maximize savings.

Use AWS Cost Explorer and Savings Plans Utilization reports to monitor usage.

References:

Savings Plans

Compute Savings Plans