Answer-first summary for fast verification
Answer: CloudFront fails over to the secondary origin only when the HTTP method of the viewer request is GET, HEAD or OPTIONS, CloudFront routes all incoming requests to the primary origin, even when a previous request failed over to the secondary origin
Overall explanation Correct options: CloudFront routes all incoming requests to the primary origin, even when a previous request failed over to the secondary origin CloudFront routes all incoming requests to the primary origin, even when a previous request failed over to the secondary origin. CloudFront only sends requests to the secondary origin after a request to the primary origin fails. CloudFront fails over to the secondary origin only when the HTTP method of the viewer request is GET, HEAD or OPTIONS CloudFront fails over to the secondary origin only when the HTTP method of the viewer request is GET, HEAD, or OPTIONS. CloudFront does not failover when the viewer sends a different HTTP method (for example POST, PUT, and so on).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A video streaming application leverages Amazon CloudFront for distributing its content globally. To ensure high availability and fault tolerance, the development team has opted to configure CloudFront with origin failover using Origin Groups. Origin failover allows CloudFront to switch to a backup origin if the primary origin becomes unavailable.
Which of the following considerations are correct when setting up CloudFront with Origin Groups for this purpose? (Select two)
A
In the Origin Group of your distribution, all the origins are defined as primary for automatic failover in case an origin fails
B
To set up origin failover, you must have a distribution with at least three origins
C
CloudFront fails over to the secondary origin only when the HTTP method of the viewer request is GET, HEAD or OPTIONS
D
When there’s a cache hit, CloudFront routes the request to the primary origin in the origin group
E
CloudFront routes all incoming requests to the primary origin, even when a previous request failed over to the secondary origin
No comments yet.