AWS Certified Associate SOA-C02 Syllabus Exam Questions Answers

Modifying the DB instance to a Multi-AZ deployment is the recommended solution for failover and high availability in RDS. Multi-AZ RDS automatically provisions and maintains a synchronous standby replica in a different Availability Zone, allowing automatic failover in case of an instance or Availability Zone failure.

Multi-AZ Deployment: Provides resilience with automatic failover and minimizes application downtime.

No Application Changes Needed: Multi-AZ is managed by AWS, so the failover is transparent to the application.

Read replicas and Auto Scaling groups do not provide automatic failover for write operations, and RDS Proxy only improves connection management rather than high availability.

Storage Auto Scaling:

Aurora storage auto scaling automatically increases the storage capacity of the database cluster when free storage space is running low.

Steps:

Go to the AWS Management Console.

Navigate to RDS and select your Aurora DB cluster.

Modify the DB cluster configuration to enable storage auto scaling.

Apply the changes.

https://docs.aws.amazon.co m/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html

To ensure that users access objects in Amazon S3 by using only CloudFront URLs, the SysOps administrator should create an origin access identity (OAI) and grant it permissions to read objects in the S3 bucket.

Create an Origin Access Identity (OAI):

OAI is a special CloudFront user that you associate with your distribution to restrict access to the S3 bucket.

This ensures that only CloudFront can access the S3 bucket directly, and users must go through CloudFront to access the content.

Steps to Implement:

Open the CloudFront console.

Select your distribution and go to the "Origins and Origin Groups" tab.

Edit the S3 origin and create a new OAI or use an existing one.

Update the S3 bucket policy to grant the OAI read permissions.

Bucket Policy Example:

{

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

"Statement": [

{

"Effect": "Allow",

"Principal": {

"AWS": "arn:aws:iam::cloudfront:user/CloudFront Origin Access Identity [OAI_ID]"

},

"Action": "s3:GetObject",

"Resource": "arn:aws:s3:::your-bucket-name/*"

}

]

}

References:

Using an Origin Access Identity to Restrict Access to Your S3 Content

Using an AMI with CloudWatch Agent:

The CloudWatch agent can collect memory utilization metrics and send them to CloudWatch.

Steps:

Create or use an existing AMI that includes the CloudWatch agent installed and configured.

Ensure the CloudWatch agent is configured to collect memory metrics.

Use this AMI for instances in the Auto Scaling group.