GCP - Cloud Load BalancingAfter enabling Cloud CDN, users report stale content is served. What configuration change can fix this?AIncrease backend instance sizeBSet Cache-Control: max-age to a lower value or use Cache InvalidationCDisable Cloud CDN to force backend responsesDRemove HTTP(S) Load Balancer from the setupCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand stale content causeLong max-age or lack of cache invalidation causes CDN to serve outdated content.Step 2: Apply corrective actionsLower max-age or explicitly invalidate cache to refresh content promptly.Final Answer:Set Cache-Control: max-age to a lower value or use Cache Invalidation -> Option BQuick Check:Fix stale cache = Lower max-age or invalidate [OK]Quick Trick: Use cache invalidation or reduce max-age to refresh content [OK]Common Mistakes:Disabling CDN instead of fixing cache settingsScaling backend unrelated to cache freshnessRemoving load balancer breaks CDN
Master "Cloud Load Balancing" in GCP9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More GCP Quizzes Cloud Firestore and Bigtable - Firestore document model - Quiz 8hard Cloud Functions - Function deployment and testing - Quiz 2easy Cloud Functions - Cold start behavior - Quiz 12easy Cloud Functions - Why serverless functions matter - Quiz 1easy Cloud IAM Advanced - Policy troubleshooter - Quiz 2easy Cloud IAM Advanced - Why advanced IAM matters - Quiz 3easy Cloud Run - Cloud Run vs Cloud Functions decision - Quiz 11easy Cloud SQL and Databases - Cloud Spanner for global distribution - Quiz 13medium Cloud SQL and Databases - Cloud Spanner for global distribution - Quiz 14medium Cloud SQL and Databases - High availability configuration - Quiz 15hard