Compare ephemeral container agents versus persistent build agents
WHAT IT TESTS: Tradeoffs between isolation and speed. ANSWER OUTLINE: Ephemeral agents ensure clean state but add cold-start latency; persistent agents speed builds via caching yet risk config drift.
WHAT IT TESTS: Your grasp of tradeoffs between reproducible ephemeral environments and optimized persistent infrastructure. ANSWER OUTLINE: First, ephemeral agents guarantee clean state but add image pull latency and lack warm caches. Second, persistent agents minimize startup overhead and preserve artifacts yet require maintenance and risk drift. Third, hybrid patterns like cached container layers blend both models. RED FLAG: Recommending one approach without asking about build frequency, artifact size, security boundaries, or team size.
Read the original → learn.microsoft.com
- #ci/cd
- #build agents
- #infrastructure
- #devops
- #azure pipelines
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.