ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 873 - SAP-C01 discussion

Report
Export


A company is using an Amazon CloudFront distribution to distribute both static and dynamic content from a web application running behind an Application Load Balancer The web application requires user authorization and session tracking tor dynamic content The CloudFront distribution has a single cache behavior configured to forward the Authorization, Host, and Agent HTTP allow list headers and a session cookie to the origin All other cache behavior settings are set to their default value A valid ACM certificate is applied to the CloudFront distribution with a matching CNAME in the distribution settings The ACM certificate is also applied to the HTTPS listener for the Application Load Balancer The CloudFront origin protocol policy is set to HTTPS only Analysis of the cache statistics report shows that the miss rate for this distribution is very high What can the solutions architect do to improve the cache hit rate for this distribution without causing the SSL/TLS handshake between CloudFront and the Application Load Balancer to fail?

A.
Create two cache behaviors for static and dynamic content Remove the user-Agent and Host HTTPheaders from the allow list headers section on both of the cache behaviors Remove the sessioncookie from the allow list cookies section and the Authorization HTTP header from the allow listheaders section for cache behavior configured for static content
Answers
A.
Create two cache behaviors for static and dynamic content Remove the user-Agent and Host HTTPheaders from the allow list headers section on both of the cache behaviors Remove the sessioncookie from the allow list cookies section and the Authorization HTTP header from the allow listheaders section for cache behavior configured for static content
B.
Remove the user-Agent and Authorization HTTP headers from the allow list headers section of thecache behaviour. Then update the cache behaviour to use resigned cookies for authorization
Answers
B.
Remove the user-Agent and Authorization HTTP headers from the allow list headers section of thecache behaviour. Then update the cache behaviour to use resigned cookies for authorization
C.
Remove the Host HTTP header from the allow list headers section and remove the session cookiefrom the allow list cookies section for the default cache behaviour Enable automatic objectcompression and use Lambda@Edge viewer request events for user authorization
Answers
C.
Remove the Host HTTP header from the allow list headers section and remove the session cookiefrom the allow list cookies section for the default cache behaviour Enable automatic objectcompression and use Lambda@Edge viewer request events for user authorization
D.
Create two cache behaviours for static and dynamic content Remove the User-Agent HTTP headerfrom the allow list headers section on both of the cache behavioursRemove the session cookie from the allow list cookies section and the Authorization HTTP headerfrom the allow list headers section for cache behaviour configured for static content
Answers
D.
Create two cache behaviours for static and dynamic content Remove the User-Agent HTTP headerfrom the allow list headers section on both of the cache behavioursRemove the session cookie from the allow list cookies section and the Authorization HTTP headerfrom the allow list headers section for cache behaviour configured for static content
Suggested answer: D

Explanation:

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/understanding-the-cachekey.htmlRemoving the host header will result in failed flow between CloudFront and ALB, because they havesame certificate.

asked 16/09/2024
Kimon Pope
32 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first