Q83 — AWS DOP-C02 Ch.1
Question 83 of 100 | ← Chapter 1
A company hosts a static website from an Amazon S3 bucket. Users access the website at example.com. The company uses Amazon Route 53 weighted routing policy with a TTL of 1 day. The company has decided to replace the static website with a dynamic web application running on a set of Amazon EC2 instances behind an Application Load Balancer (ALB). On launch day, the company creates an additional Route 53 weighted DNS record pointing to the ALB, with weight 255 and TTL 1 second. After 24 hours, a DevOps engineer notices that when users navigate to example.com, the static website still appears. How should the DevOps engineer ensure the company serves only dynamic content for example.com?
- A. Delete all objects—including previous versions—from the S3 bucket containing the static website content.
- B. Update the weighted DNS record pointing to the S3 bucket. Apply weight 0. Specify domain reset option to propagate the change immediately.
- C. Configure website redirect requests on the S3 bucket to redirect to the ALB’s hostname.
- D. Delete the weighted DNS record pointing to the S3 bucket from the example.com hosted zone. Wait for DNS propagation to complete. ✓
Correct Answer: D. Delete the weighted DNS record pointing to the S3 bucket from the example.com hosted zone. Wait for DNS propagation to complete.
Explanation
Because a prior Route 53 weighted DNS record pointing to the static website remains active, users may still resolve to the static site due to DNS caching—even after adding a new record pointing to the ALB. Option D is correct: deleting the S3-targeted weighted DNS record from the example.com hosted zone and waiting for DNS propagation ensures no valid DNS record points to the static site, guaranteeing only dynamic content is served. Option A fails because deleting S3 objects does not affect DNS resolution. Option B sets weight to 0 but does not guarantee immediate cessation of traffic due to TTL and caching behavior. Option C configures redirects at the S3 level but does not eliminate the underlying DNS record, introducing latency and potential failure points. Thus, D is the definitive solution.