Practice Test 3 | AWS Certified Solutions Architect Associate | SAA-C03 | Dumps | Mock Test
Your company has been hosting a static website in an S3 bucket for several months and gets a fair amount of traffic. Now you want your registered .com domain to serve content from the bucket. Your domain is reached via https://www.myfavoritedomain.com. However, any traffic requested through https://www.myfavoritedomain.com is not getting through. What is the most likely cause of this disruption?
A. The new domain name is not registered in CloudWatch monitoring
B. The S3 bucket has not been configured to allow Cross Origin Resource Sharing (CORS)
C. The S3 bucket was not created in the correct region
D. Https://www.myfavoritedomain.com wasn’t registered with AWS Route 53 and therefore won’t work
Explanation:
Answer: B
- B. The S3 bucket has not been configured to allow Cross Origin Resource Sharing (CORS). In order to keep your content safe, your web browser implements something called the same origin policy.
The default policy ensures that scripts and other active content loaded from one site or domain cannot interfere or interact with content from another location without an explicit indication that this is the desired behavior.
Incorrect:
- A. Enabling Cloudwatch doesn’t affect Cross Origin Resource Sharing (CORS)
- C. S3 buckets are not region-specific
- D. The domain can be registered with any online registrar, not just AWS Route53
Reference:
Comments are closed, but trackbacks and pingbacks are open.