AWS Certified Associate SOA-C02 Syllabus Exam Questions Answers

To configure replication of a DynamoDB table to another AWS Region for disaster recovery, you should use DynamoDB Global Tables. Global Tables use DynamoDB Streams to replicate changes across multiple regions.

Enable DynamoDB Streams:

Navigate to the DynamoDB console.

Select your table and enable DynamoDB Streams.

Add a Global Table Region:

With Streams enabled, go to the Global Tables tab.

Add a new region to the table, specifying the region where you want to replicate the data.

Automatic Replication:

DynamoDB will handle the replication of data across regions automatically, ensuring data consistency and high availability.

DynamoDB Global Tables

Enabling DynamoDB Streams

The AWS Personal Health Dashboard provides a personalized view into the performance and availability of the AWS services underlying your AWS resources. It can alert you about upcoming hardware maintenance that could affect your EC2 instances.

Access AWS Personal Health Dashboard:

Open the AWS Personal Health Dashboard at AWS Personal Health Dashboard.

View Service Health:

The dashboard shows a list of recent events, including upcoming scheduled maintenance that might impact your EC2 instances.

You can filter events to view those that specifically affect your EC2 instances.

Set Up Notifications:

You can configure AWS CloudWatch Events or Amazon SNS to send notifications based on Personal Health Dashboard events.

AWS Personal Health Dashboard

Monitoring AWS Health Events with Amazon CloudWatch Events

To address high I/O requirements during the bootstrap process, increasing both IOPS and throughput on the EBS volume is recommended:

Increase EBS Volume IOPS: Enhances the instance’s ability to handle multiple read and write operations per second, essential for data-heavy tasks like downloading Docker images.

Increase EBS Volume Throughput: Provides higher data transfer rates, reducing bottlenecks during intensive I/O operations.

Increasing instance size is unnecessary if the primary issue is disk I/O, and changing from Nitro-based instances would not address the underlying storage performance need.

AWS Config rules can be used to automatically detect and remediate noncompliant resources, such as security groups that allow inbound traffic from 0.0.0.0/0.

Steps:

Create a Custom AWS Config Rule:

Open the AWS Config console.

Choose "Rules" and then "Add rule".

Create a custom rule or use a predefined rule such as security-group-rule-restricted.

Configure Remediation:

Use AWS Config to set up automatic remediation.

Define an AWS Systems Manager Automation document that changes the source address from 0.0.0.0/0 to the approved CIDR block.

Associate this automation document with the AWS Config rule.

Deploy Across Accounts:

Use AWS Config Aggregator to aggregate the compliance data across multiple accounts.

Ensure the remediation actions are consistently applied across all accounts.