Amazon SOA-C02 Exam

Certification Provider: Amazon

Exam Name: AWS Certified SysOps Administrator - Associate

Number of questions in our database: 305

Exam Version: May. 25, 2023

SOA-C02 Exam Official Topics:

Topic 1: Troubleshoot or take corrective actions based on notifications and alarms/ Collect metrics and logs using the CloudWatch agent
Topic 2: Implement Amazon RDS replicas and Amazon Aurora Replicas/ Remediate issues based on monitoring and availability metrics
Topic 3: Implement metrics, alarms, and filters by using AWS monitoring and logging services/ Differentiate between horizontal scaling and vertical scaling
Topic 4: Configure Elastic Load Balancer and Amazon Route 53 health checks/ Configure Amazon EventBridge rules to trigger actions
Topic 5: Implement backup and restore strategies/ Create and maintain AWS Auto Scaling plans
Topic 6: Provision resources across multiple AWS Regions and accounts/ Use AWS Systems Manager Automation documents to take action based on AWS Config rules
Topic 7: Automate snapshots and backups based on use cases/ Implement high availability and resilient environments
Topic 8: Configure Amazon S3 Cross-Region Replication/ Select deployment scenarios and services
Topic 9: Schedule automated tasks by using AWS services/ Configure domains, DNS services, and content delivery
Topic 10: Implement fault-tolerant workloads/ Differentiate between the use of a single Availability Zone and Multi-AZ deployments
Topic 11: Implement networking features and connectivity/ Validate service control policies and permission boundaries
Topic 12: Implement data and infrastructure protection strategies/ Implement and manage security and compliance policies

Free Amazon SOA-C02 Exam Actual Questions

The questions for SOA-C02 were last updated On May. 25, 2023

Question #1

A company has an application that is deployed 10 two AWS Regions in an active-passive configuration. The application runs on Amazon EC2 instances behind an Application Load Balancer (ALB) in each Region. The instances are in an Amazon EC2 Auto Scaling group in each Region. The application uses an Amazon Route 53 hosted zone (or DNS. A SysOps administrator needs to configure automatic failover to the secondary Region.

What should the SysOps administrator do to meet these requirements?

AConfigure Route 53 alias records that point to each ALB. Choose a failover routing policy. Set Evaluate Target Health to Yes.

BConfigure CNAME records that point to each ALB. Choose a failover routing policy. Set Evaluate Target Health to Yes.

CConfigure Elastic Load Balancing (ELB) health checks for the Auto Scaling group. Add a target group to the ALB in the primary Region. Include the EC2 instances in the secondary Region as
targets.

DConfigure EC2 health checks for the Auto Scaling group. Add a target group to the ALB in the primary Region. Include the EC2 instances in the secondary Region as targets.

Reveal Solution

Correct Answer: A

Question #2

You need to update an existing AWS CloudFormation stack. If needed, a copy to the CloudFormation template is available in an Amazon SB bucket named cloudformation-bucket

1. Use the us-east-2 Region for all resources.

2. Unless specified below, use the default configuration settings.

3. update the Amazon EQ instance named Devinstance by making the following changes to the stack named 1700182:

a) Change the EC2 instance type to us-east-t2.nano.

b) Allow SSH to connect to the EC2 instance from the IP address range

192.168.100.0/30.

c) Replace the instance profile IAM role with IamRoleB.

4. Deploy the changes by updating the stack using the CFServiceR01e role.

5. Edit the stack options to prevent accidental deletion.

6. Using the output from the stack, enter the value of the Prodlnstanceld in the text box below:

AExplanation:
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/

Reveal Solution

Correct Answer: A

Question #3

A company has a memory-intensive application that runs on a fleet of Amazon EC2 instances behind an Elastic Load Balancer (ELB). The instances run in an Auto Scaling group. A Sysops administrator must ensure that the application can scale based on the number of users that connect to the application.

Which solution will meet these requirements?

ACreate a scaling policy that will scale the application based on the ActiveConnectionCount Amazon CloudWatch metric that is generated from the ELB.

BCreate a scaling policy that will scale the application based on the mem used Amazon CloudWatch metric that is generated from the ELB.

CCreate a scheduled scaling policy to increase the number of EC2 instances in the Auto Scaling group to support additional connections.

DCreate and deploy a script on the ELB to expose the number of connected users as a custom Amazon CloudWatch metric. Create a scaling policy that uses the metric.

Reveal Solution

Correct Answer: D

This solution will allow the application to scale based on the number of users that connect to the application. The other solutions (creating a scaling policy that uses the ActiveConnectionCount Amazon CloudWatch metric generated from the ELB, creating a scaling policy that uses the mem used Amazon CloudWatch metric generated from the ELB, or creating a scheduled scaling policy to increase the number of EC2 instances in the Auto Scaling group to support additional connections) will not meet the requirements, as they do not allow the application to scale based on the number of users that connect to the application.

Question #4

You need to update an existing AWS CloudFormation stack. If needed, a copy to the CloudFormation template is available in an Amazon SB bucket named cloudformation-bucket

1. Use the us-east-2 Region for all resources.

2. Unless specified below, use the default configuration settings.

3. update the Amazon EQ instance named Devinstance by making the following changes to the stack named 1700182:

a) Change the EC2 instance type to us-east-t2.nano.

b) Allow SSH to connect to the EC2 instance from the IP address range

192.168.100.0/30.

c) Replace the instance profile IAM role with IamRoleB.

4. Deploy the changes by updating the stack using the CFServiceR01e role.

5. Edit the stack options to prevent accidental deletion.

6. Using the output from the stack, enter the value of the Prodlnstanceld in the text box below:

Reveal Solution

Correct Answer: A

Question #5

A webpage is stored in an Amazon S3 bucket behind an Application Load Balancer (ALB). Configure the SS bucket to serve a static error page in the event of a failure at the primary site.

1. Use the us-east-2 Region for all resources.

2. Unless specified below, use the default configuration settings.

3. There is an existing hosted zone named lab-

751906329398-26023898.com that contains an A record with a simple routing policy that routes traffic to an existing ALB.

4. Configure the existing S3 bucket named lab-751906329398-26023898.com as a static hosted website using the object named index.html as the index document

5. For the index-html object, configure the S3 ACL to allow for public read access. Ensure public access to the S3 bucketjs allowed.

6. In Amazon Route 53, change the A record for domain lab-751906329398-26023898.com to a primary record for a failover routing policy. Configure the record so that it evaluates the health of the ALB to determine failover.

7. Create a new secondary failover alias record for the domain lab-751906329398-26023898.com that routes traffic to the existing 53 bucket.

AExplanation:
Here are the steps to configure an Amazon S3 bucket to serve a static error page in the event of a failure at the primary site:
Log in to the AWS Management Console and navigate to the S3 service in the us-east-2 Region.
Find the existing S3 bucket named lab-751906329398-26023898.com and click on it.
In the 'Properties' tab, click on 'Static website hosting' and select 'Use this bucket to host a website'.
In 'Index Document' field, enter the name of the object that you want to use as the index document, in this case, 'index.html'
In the 'Permissions' tab, click on 'Block Public Access', and make sure that 'Block all public access' is turned OFF.
Click on 'Bucket Policy' and add the following policy to allow public read access:
{
'Version': '2012-10-17',
'Statement': [
{
'Sid': 'PublicReadGetObject',
'Effect': 'Allow',
'Principal': '*',
'Action': 's3:GetObject',
'Resource': 'arn:aws:s3:::lab-751906329398-26023898.com/*'
}
]
}
Now navigate to the Amazon Route 53 service, and find the existing hosted zone named lab-751906329398-26023898.com.
Click on the 'A record' and update the routing policy to 'Primary - Failover' and add the existing ALB as the primary record.
Click on 'Create Record' button and create a new secondary failover alias record for the domain lab-751906329398-26023898.com that routes traffic to the existing S3 bucket.
Now, when the primary site (ALB) goes down, traffic will be automatically routed to the S3 bucket serving the static error page.
Note:
You can use CloudWatch to monitor the health of your ALB.
You can use Amazon S3 to host a static website.
You can use Amazon Route 53 for routing traffic to different resources based on health checks.
You can refer to the AWS documentation for more information on how to configure and use these services:
https://aws.amazon.com/s3/
https://aws.amazon.com/route53/
https://aws.amazon.com/cloudwatch/