AWS - Cloud Computing FundamentalsA user reports that CloudFront is serving stale content. What is a likely cause?AEdge locations are not enabledBThe origin server is downCThe cache TTL is set too highDThe distribution is disabledCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand stale content causeIf TTL is too high, cached content stays longer than desired, causing staleness.Step 2: Exclude other causesOrigin down causes errors, not stale content; edge locations are always enabled; disabled distribution stops serving.Final Answer:The cache TTL is set too high -> Option CQuick Check:High TTL causes stale cache [OK]Quick Trick: High TTL keeps old content longer [OK]Common Mistakes:Assuming origin down causes stale contentThinking edge locations can be disabledConfusing distribution status with caching
Master "Cloud Computing Fundamentals" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes AWS Account and Billing - Why account management matters - Quiz 8hard AWS Account and Billing - Billing dashboard overview - Quiz 4medium AWS Account and Billing - AWS Cost Explorer basics - Quiz 4medium Cloud Computing Fundamentals - AWS Management Console walkthrough - Quiz 12easy EC2 Fundamentals - Instance metadata and user data - Quiz 6medium EC2 Fundamentals - Why EC2 matters for compute - Quiz 7medium EC2 Fundamentals - Instance types and families - Quiz 13medium S3 Fundamentals - Uploading and downloading objects - Quiz 7medium S3 Fundamentals - S3 storage classes (Standard, IA, Glacier) - Quiz 8hard VPC Fundamentals - NAT Gateway for private subnet internet - Quiz 14medium