SOA-C02 · Question #594
SOA-C02 Question #594: Real Exam Question with Answer & Explanation
The correct answer is A: Enable CloudFront Origin Shield for the required AWS Regions.. Why A and E are correct: A (Origin Shield) adds an additional caching layer between CloudFront edge locations and the origin, so more requests are served from cache rather than forwarding to the origin - directly boosting the cache hit ratio. E (Increase TTL) keeps objects in the
Question
A SysOps administrator notices that the cache hit ratio for an Amazon CloudFront distribution is less than 10%. Which combination of actions should the SysOps administrator take to increase the cache hit ratio for the distribution? (Choose two.)
Options
- AEnable CloudFront Origin Shield for the required AWS Regions.
- BChange the viewer protocol policy to use HTTPS only.
- CConfigure the distribution to use presigned cookies and URLs.
- DTurn on automatic compression of objects in the cache behavior settings.
- EIncrease the CloudFront TTL values in the cache behavior settings.
Explanation
Why A and E are correct:
A (Origin Shield) adds an additional caching layer between CloudFront edge locations and the origin, so more requests are served from cache rather than forwarding to the origin - directly boosting the cache hit ratio. E (Increase TTL) keeps objects in the cache longer, meaning more subsequent requests find a cached copy before it expires - a fundamental lever for improving hit ratio.
Why the distractors are wrong:
- B (HTTPS only) changes the security protocol for viewers but has no effect on whether objects are cached or for how long.
- C (Presigned cookies/URLs) is an access control mechanism; it restricts who can access content, not how efficiently it's cached - and can actually hurt caching if not configured carefully.
- D (Automatic compression) reduces object size to improve transfer speed, but doesn't increase the likelihood that a request finds a cached object.
Memory tip: Think "cache hit ratio = more caching." Any answer that adds a caching layer (Origin Shield) or keeps objects cached longer (higher TTL) directly addresses the problem. HTTPS, presigned URLs, and compression all serve other purposes - they're red herrings here.
Topics
Community Discussion
No community discussion yet for this question.