AWS Certified Associate SOA-C02 Passing Score

Using the ALB’s RequestCount metric will allow the SysOps administrator to collect information about total requests for a 2-week period and determine when requests exceeded the threshold of 100 requests per second. Configuring a time range of 2 weeks and a period of 1 minute will ensure that the data can be accurately examined to determine peak traffic times and volumes.

Step-by-Step Explanation:

Understand the Problem:

Setting up an AWS managed VPN connection requires creating a customer gateway resource.

The customer gateway device is behind a NAT gateway in the data center.

Analyze the Requirements:

The customer gateway resource needs to be created using an IP address that can be reached by AWS.

Evaluate the Options:

Option A: The private IP address of the customer gateway device.

A private IP address is not reachable by AWS over the internet.

Option B: The MAC address of the NAT device.

MAC addresses are not used for identifying gateways in AWS.

Option C: The public IP address of the customer gateway device.

This would be correct if the device were directly connected to the internet, but it is behind a NAT.

Option D: The public IP address of the NAT device in front of the customer gateway device.

The NAT device's public IP address is reachable by AWS and will route traffic to the customer gateway device.

Select the Best Solution:

Option D: Using the public IP address of the NAT device ensures that AWS can establish a VPN connection with the customer gateway device behind the NAT.

References:

AWS Site-to-Site VPN Documentation

Customer Gateway Devices Behind a NAT

Specifying the public IP address of the NAT device ensures proper routing of VPN traffic to the customer gateway device.

To share an encrypted Amazon RDS DB instance snapshot across accounts, the least administrative overhead involves directly managing permissions on the AWS KMS key and sharing the snapshot. Here’s how to do it:

Take a Snapshot: Initiate a snapshot of your Amazon RDS DB instance in the production account. This captures the current state of the database.

Modify KMS Key Policy: Adjust the policy of the KMS key used for encryption (identified by the alias 'production-rds-key') to grant the kms:Decrypt permission to the migration account’s root user. This step is crucial as it allows the migration account to use the same encryption key to decrypt the snapshot.

Share the Snapshot: Share the newly created snapshot with the migration account using the RDS console or AWS CLI. The migration account will now be able to see and use this snapshot to create a new RDS instance.

AWS Documentation Reference:You can refer to the AWS documentation on sharing encrypted snapshots: Sharing Encrypted Snapshots.

To resolve issues with high disk I/O during the bootstrap process:

Increase EBS Volume IOPS: Higher IOPS allows the EBS volume to handle more input/output operations per second, which is critical for high I/O demands like downloading large Docker images.

Increase EBS Volume Throughput: Boosting throughput allows for faster data transfer rates, which is useful when the workload requires sustained high data throughput during initialization.

Increasing the instance size or changing the instance type is not necessary if the root cause is related specifically to EBS performance. Nitro instances generally provide higher performance and are well-suited for high I/O tasks.