Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 297 discussion

A. Yes, because Amazon CloudFront considers the case of parameter names and values when caching based on query string parameters , thus inconsistent query strings may cause CloudFront to forward mixed-cased/misordered requests to the origin. Triggering a Lambda@Edge function based on a viewer request event to sort parameters by name and force them to be lowercase is the best choice. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/QueryStringParameters.html#query-string-parameters-optimizing-caching https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-cloudfront-trigger-events.html B. No, because this will exacerbate the caching issue by sending all query string parameters requests to the origin C. No, because this won't help increase the cache hit ratio D. No, because a CloudFront distribution specifies information about the origin/source of your content and how to track and manage content delivery.

CloudFront does NOT support to specify casing-insensitive query string

Answer:D is best and cheap.

OMG so now I have to invoke and pay for a Lambda for every single GET request that traverses my CDN? No, F*** that. If D isn't supported then ciao bella s/Cloudfront/Cloudflare/g and say hello to Apache running mod_substitute thank you very much.

Caching based on query string parameters If you configure CloudFront to cache based on query string parameters, you can improve caching if you do the following: Configure CloudFront to forward only the query string parameters for which your origin will return unique objects.

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cache-hit-ratio.html

D is ans D. Casing-insensitive query string processing: This is the simplest and fastest solution to implement. It will treat requests with the same query string but different character casing as identical, boosting the cache hit ratio. It utilizes built-in functionality of CloudFront without requiring additional services or configurations. Remember, while other options might offer additional functionalities, the primary goal is to quickly improve the cache hit ratio. Specifying casing-insensitive query string processing achieves this with minimal impact and complexity.

Correct A.

its an A D would be nice if was supported

A - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html#lambda-examples-normalize-query-string-parameters

A - https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html#lambda-examples-normalize-query-string-parameters

D is out: CloudFront distributions do not have built-in support for specifying a case-insensitive query string. By default, CloudFront treats query strings as case-sensitive, meaning that a URL with a different case in the query string parameter would be treated as a separate object and potentially result in a cache miss.

A , same questions this version 1 https://www.examtopics.com/discussions/amazon/view/27789-exam-aws-certified-solutions-architect-professional-topic-1/

A is the answer -to sort parameters by name and force them to be lowercase

A check for the example in the below documentation https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-examples.html

A is answer

Correct Answer is A