Pass AZ-204 faster with an AI system that shows you exactly what to study next.

The correct answer is: To reduce final image size by separating build dependencies from runtime components. Multi-stage builds in Docker are specifically designed to optimize container images by allowing developers to use multiple FROM statements in a single Dockerfile. The primary purpose is to separate the build environment from the runtime environment. Here's how it works: - In the first stage(s), you include all the tools, compilers, and dependencies needed to build your application (like SDKs, build tools, npm packages, etc.) - In the final stage, you only copy the compiled artifacts or built application from previous stages - The build dependencies and intermediate files are left behind in earlier stages and don't appear in the final image - This results in a much smaller, more secure final image that only contains what's necessary to run the application Why the other answers are incorrect: The option about parallel execution across availability zones is incorrect because multi-stage builds are a Dockerfile feature for image optimization, not a runtime orchestration or scaling feature. Container orchestration and availability zones are handled by platforms like Kubernetes or Azure Container Instances, not by Docker build features. The option about compiling source code in layers that persist through all stages is incorrect because it contradicts the fundamental principle of multi-stage builds. The whole point is that layers from earlier stages do NOT persist in the final image unless explicitly copied. Only the artifacts you choose to copy forward are included. The option about creating separate images for development and production is incorrect because multi-stage builds produce a single optimized image, not separate images. While you can use build arguments to customize behavior, the primary purpose is size reduction, not creating multiple distinct images. Separate dev and prod images are typically managed through different Dockerfiles or build targets, not multi-stage builds.