Amazon Web Services Updated SOA-C02 Exam Questions and Answers by nell

To create a backup strategy for all Amazon EC2 instances across all the company's AWS accounts using AWS Organizations, AWS Backup is the most operationally efficient solution.

AWS Backup:

AWS Backup provides centralized backup management and automates the backup of data across AWS services.

It supports creating backup plans that can apply to resources across multiple AWS accounts within an AWS Organization.

Using AWS Backup:

Open the AWS Backup console in the management account.

Create a backup plan and define backup policies (e.g., frequency, retention).

Use the backup policies to automatically apply to all EC2 instances in all member accounts of the AWS Organization.

References:

AWS Backup

AWS Backup for Multi-Account

Weighted routing in Route 53 allows you to direct a percentage of traffic to different resources by configuring specific weights. For this requirement, you can:

Weighted Routing Policy: This is the most suitable approach for gradually rolling out a new version by controlling traffic distribution.

Weight Configuration: Setting a weight of 80 for the original resource and 20 for the new resource ensures that 80% of the traffic continues to go to the existing version, while 20% is directed to the new version.

Other routing policies, such as failover and multivalue answer, are not intended for traffic distribution based on percentage; they serve different use cases.

To meet the requirement of directing users to the Region closest to them and providing automated failover, the SysOps administrator should perform the following steps:

Create Amazon CloudWatch Alarms:

Create CloudWatch alarms that monitor the health of the ALB in each Region. This ensures that the system can detect unhealthy endpoints and trigger the failover mechanism.

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.