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

# Enable instance scale-in protection for specific instance.

aws autoscaling set-instance-protection --instance-ids i-5f2e8a0d --auto-scaling-group-name my-asg --protected-from-scale-in

# Disable instance scale-in protection for the specified instance.

aws autoscaling set-instance-protection --instance-ids i-5f2e8a0d --auto-scaling-group-name my-asg --no-protected-from-scale-in

https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-auto-scaling-instance-protection.html

To ensure that EC2 instances in an Auto Scaling group are not interrupted during message processing, the most effective method is to implement scale-in protection for the instances while they are actively processing messages. This can be done programmatically by modifying the Auto Scaling group's settings using the Amazon EC2 Auto Scaling API.

Starting Message Processing: When an instance begins processing a message, your application should make an API call to enable scale-in protection. This is done using the SetInstanceProtection action, setting the ProtectedFromScaleIn parameter to true for that specific instance.

Completing Message Processing: Once the message has been processed, another API call should be made to disable scale-in protection. This is done by calling the SetInstanceProtection action again, but this time setting the ProtectedFromScaleIn parameter to false.

This method ensures that while messages are being processed, the instances are not terminated by the Auto Scaling group regardless of any scale-in activities that might be triggered by other parameters like CPU utilization or a decrease in the number of messages in the queue.

AWS Documentation Reference:

You can refer to the AWS documentation on managing instance scale-in protection in Auto Scaling groups for more details: Instance Scale-In Protection.

Using an RDS read replica will improve the performance and availability of the RDS instance by offloading read queries to the replica. This will also ensure that the reporting job completes in a timely manner and does not affect the performance of other queries that might be running on the RDS instance. Additionally, updating the reporting job to query the reader endpoint will ensure that all read queries are directed to the read replica.

To serve static websites using S3 and Route 53, AWS requires the bucket name to match the custom domain name (e.g., www.example.com), not just a random bucket like example-website-hosting-bucket.

From the Amazon S3 Static Website Hosting Guide:

To use Amazon Route 53 to route domain traffic to an S3 bucket that is configured as a static website, the bucket name must match the name of the domain or subdomain.

This means:

To host www.example.com, you must create an S3 bucket named www.example.com

Then configure static website hosting on that bucket

In Route 53, you can then create an alias record pointing to the S3 website endpoint

❌ Why the other options are incorrect:

A. ARNs are not valid alias targets in Route 53.

B. ARN changes do not affect Route 53; also, you cannot rename an S3 bucket via ARN changes.

C. Access Points do not support static website hosting. They are for programmatic access via APIs.