Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam SOA-C02 Topic 12 Question 106 Discussion

Actual exam question for Amazon's SOA-C02 exam
Question #: 106
Topic #: 12
[All SOA-C02 Questions]

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.

Show Suggested Answer Hide Answer
Suggested Answer: A

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/


Contribute your Thoughts:

Luisa
1 months ago
Yep, gotta cover all the bases. Can't have any gaps in the configuration or the whole thing will fall apart.
upvoted 0 times
Emilio
15 days ago
And make sure to update the Route 53 records for failover routing based on the ALB health.
upvoted 0 times
...
Dacia
15 days ago
Don't forget to allow public read access to the index.html object in the S3 bucket.
upvoted 0 times
...
Lindsey
20 days ago
Make sure to set up the S3 bucket as a static website with the index.html as the index document.
upvoted 0 times
...
...
Lettie
1 months ago
Haha, public access to the S3 bucket? That's a bold move, Cotton. Let's see if it pays off for them.
upvoted 0 times
Rozella
19 days ago
I wonder how they will handle potential security risks.
upvoted 0 times
...
Stanford
21 days ago
Yeah, public access can be dangerous if not managed correctly.
upvoted 0 times
...
Onita
28 days ago
Hopefully they have proper security measures in place.
upvoted 0 times
...
Leota
1 months ago
I know right, it's risky but sometimes necessary.
upvoted 0 times
...
...
Tasia
1 months ago
That's right. We also need to create a secondary failover alias record for the domain.
upvoted 0 times
...
Lauryn
1 months ago
And we need to change the A record in Route 53 to a primary record for failover routing policy.
upvoted 0 times
...
Penney
2 months ago
Wait, we need to make sure the S3 bucket has public access allowed too, not just the index.html object. Otherwise, the failover won't work properly.
upvoted 0 times
...
Ruthann
2 months ago
This seems straightforward. Configure the S3 bucket as a static website, set the ACL to allow public read access, and create the failover routing policy in Route 53. Looks good to me!
upvoted 0 times
Olen
15 days ago
Looks like we have everything covered. Good job!
upvoted 0 times
...
Esteban
16 days ago
After that, we can create the failover routing policy in Route 53.
upvoted 0 times
...
Oliva
21 days ago
Next, we need to set the ACL to allow public read access for the index.html object.
upvoted 0 times
...
Truman
1 months ago
Let's start by configuring the S3 bucket as a static website.
upvoted 0 times
...
...
Tasia
2 months ago
Yes, we should use the us-east-2 Region for all resources as specified in the question.
upvoted 0 times
...
Lauryn
2 months ago
I think we need to configure the S3 bucket to serve a static error page in case of a failure.
upvoted 0 times
...

Save Cancel