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

Objective:

Receive a notification when both disk space usage and DiskReadOps exceed threshold values.

Composite Alarms:

Composite alarms allow combining multiple metric alarms into a single alarm. Notifications are triggered only when all conditions are met.

Steps to Implement:

Step 1: Install the CloudWatch agent on the EC2 instances and configure it to monitor disk space.

Step 2: Create individual metric alarms:

One for disk space usage.

One for the DiskReadOps metric.

Step 3: Create a composite alarm:

Include both metric alarms.

Configure the composite alarm to send notifications to the SNS topic when both conditions are met.

AWS References:

Composite Alarms in CloudWatch:Creating Composite Alarms

CloudWatch Agent Installation:Install CloudWatch Agent

Why Other Options Are Incorrect:

Option B: This would trigger notifications for either condition, not both simultaneously.

Option C: EBSByteBalance% is unrelated to free disk space.

Option D: Detailed monitoring is not required for composite alarms.

To reduce the cost of EC2 instances with a 1-year commitment across different regions, purchasing a Compute Savings Plan is the most suitable option.

Compute Savings Plan:

Compute Savings Plans provide the most flexibility and help to reduce your costs by up to 66%, offering savings on a variety of EC2 instance usage.

These plans apply to usage across any AWS Region, and they also apply to AWS Lambda and AWS Fargate usage.

Flexibility Across Regions:

Unlike Reserved Instances, which are tied to a specific instance family and region, Compute Savings Plans provide savings across any EC2 instance usage, regardless of region, instance family, operating system, or tenancy.

This flexibility is ideal for the company's requirement to migrate workloads from the eu-west-1 region to the eu-west-3 region within the commitment period.

Implementation:

Open the AWS Cost Management console.

Navigate to the "Savings Plans" section.

Purchase a Compute Savings Plan with a 1-year term.

References:

AWS Savings Plans

Compute Savings Plans

Here are the steps to update an existing AWS CloudFormation stack:

Log in to the AWS Management Console and navigate to the CloudFormation service in the us-east-2 Region.

Find the existing stack named 1700182 and click on it.

Click on the "Update" button.

Choose "Replace current template" and upload the updated CloudFormation template from the Amazon S3 bucket named "cloudformation-bucket"

In the "Parameter" section, update the EC2 instance type to us-east-t2.nano and add the IP address range 192.168.100.0/30 for SSH access.

Replace the instance profile IAM role with IamRoleB.

In the "Capabilities" section, check the checkbox for "IAM Resources"

Choose the role CFServiceR01e and click on "Update Stack"

Wait for the stack to be updated.

Once the update is complete, navigate to the stack and click on the "Stack options" button, and select "Prevent updates to prevent accidental deletion"

To get the value of the Prodlnstanceld , navigate to the "Outputs" tab in the CloudFormation stack and find the key "Prodlnstanceld". The value corresponding to it is the value that you need to enter in the text box below.

Note:

You can use AWS CloudFormation to update an existing stack.

You can use the AWS CloudFormation service role to deploy updates.

You can refer to the AWS CloudFormation documentation for more information on how to update and manage stacks: https://aws.amazon.com/cloudformation/

Here are the steps to configure Amazon EventBridge to meet the above requirements:

Log in to the AWS Management Console by using the AWS Management Console shortcut from the VM desktop. Make sure that you are logged in to the desired AWS account.

Go to the EventBridge service in the us-east-2 Region.

In the EventBridge service, navigate to the "Event buses" page.

Click on the "Create event bus" button.

Give a name to your event bus, and select "default" as the event source type.

Navigate to "Rules" page and create a new rule named "RunFunction"

In the "Event pattern" section, select "Schedule" as the event source and set the schedule to run every 15 minutes.

In the "Actions" section, select "Send to Lambda" and choose the existing AWS Lambda function named "LogEventFunction"

Create another rule named "SpotWarning"

In the "Event pattern" section, select "EC2" as the event source, and filter the events on "EC2 Spot Instance interruption"

In the "Actions" section, select "Send to SNS topic" and create a new standard Amazon SNS topic named "TopicEvents"

In the "Input Transformer" section, set the Input Path to {“instance” : “$.detail.instance-id”} and Input template to “The EC2 Spot Instance has been interrupted on account.

Now all Amazon EC2 events in the default event bus will be replayable for past 90 days.

Note:

You can use the AWS Management Console, AWS CLI, or SDKs to create and manage EventBridge resources.

You can use CloudTrail event history to replay events from the past 90 days.

You can refer to the AWS EventBridge documentation for more information on how to configure and use the service: https://aws.amazon.com/eventbridge/