Practise the language of remote build caches in monorepos: cache keys, hits and misses, artifact reuse, and read/write tokens.
0 / 5 completed
1 / 5
When a build finds a previously computed result in the remote cache and skips re-running the task, that is a cache ___.
A cache hit means the inputs hashed to a key already present in the cache, so the stored artifact is reused instead of recomputed.
2 / 5
The remote cache decides reuse by computing a ___ from the task's inputs.
A cache key is a hash of inputs (source files, deps, config). Identical inputs produce the same key, enabling artifact reuse across machines.
3 / 5
A CI machine that may download but not upload artifacts has ___ access to the cache.
Read-only access lets a runner benefit from cached results without being trusted to populate the cache, a common security setup for untrusted PR builds.
4 / 5
Stored compiled outputs that the cache serves on a hit are called ___.
Artifacts are the build outputs (bundles, compiled libs, test results) cached under a key and replayed on a hit.
5 / 5
Sharing one cache across all developers and CI so everyone reuses each other's results is the main benefit of a ___ cache.
A remote (shared) cache lets the whole team and CI reuse builds, so work done once on any machine speeds up everyone.