Bird
0
0

Why might Docker layer caching in CI sometimes fail to speed up builds even when configured correctly?

hard📝 Conceptual Q10 of 15
Docker - in CI/CD
Why might Docker layer caching in CI sometimes fail to speed up builds even when configured correctly?
ABecause cache invalidation occurs if build context or Dockerfile changes frequently
BBecause Docker always rebuilds all layers regardless of cache
CBecause caching requires manual deletion of old images
DBecause cache is only used for base images, not application layers
Step-by-Step Solution
Solution:

  1. Step 1: Understand cache invalidation triggers

    Changes in build context files or Dockerfile instructions cause cache invalidation.

  2. Step 2: Identify why caching might not speed builds

    If files change often, cache is not reused, so builds take full time despite caching setup.

  3. Final Answer:

    Because cache invalidation occurs if build context or Dockerfile changes frequently -> Option A

  4. Quick Check:

    Frequent changes cause cache invalidation [OK]
Quick Trick: Frequent changes cause cache invalidation, slowing builds [OK]
Common Mistakes:
  • Believing Docker always rebuilds all layers
  • Thinking manual image deletion affects caching
  • Assuming cache only applies to base images

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Docker Quizzes
Docker Security - Secrets management - Quiz 2easy Docker Security - Read-only filesystem containers - Quiz 10hard Docker Security - Read-only filesystem containers - Quiz 4medium Docker in CI/CD - Running tests in containers - Quiz 1easy Docker in CI/CD - GitLab CI with Docker - Quiz 1easy Production Patterns - Sidecar container pattern - Quiz 13medium Production Patterns - Canary deployment pattern - Quiz 2easy Production Patterns - Container orchestration in production - Quiz 15hard Production Patterns - Sidecar container pattern - Quiz 2easy Resource Management - Memory limits and reservations - Quiz 15hard