Multi-stage Builds Session

Question 1 of 12

What is the primary benefit of using multi-stage builds in Docker?

Increased image size due to the inclusion of build tools. Reduced image size by discarding unnecessary build artifacts. Slower build times due to the added complexity. Limited flexibility in choosing base images.

Question 2 of 12

In a

Dockerfile

, how do you define a new stage?

Using the

NEW_STAGE

instruction. Using the

STAGE

instruction. Stages are defined automatically based on the order of commands. Using the

FROM

instruction with a different base image.

Question 3 of 12

How do you copy artifacts from one stage to another in a multi-stage

Dockerfile

?

Using the

COPY --from=stage_name

instruction. Using the

MOVE --from=stage_name

instruction. Artifacts are automatically shared between stages. Using the

LINK --from=stage_name

instruction.

Question 4 of 12

Which of the following is NOT a typical use case for multi-stage builds?

Including debugging tools in the final image for easier troubleshooting. Compiling source code in one stage and copying the binaries to a smaller runtime image. Using a larger image with build tools for compilation and a smaller image for running the application. Separating build dependencies from runtime dependencies.

Question 5 of 12

What happens if you don't specify a name for a stage in a multi-stage

Dockerfile

?

Docker automatically assigns a numerical index to the stage, starting from 0. The build will fail because all stages must have names. Docker uses the base image name as the stage name. The stage will be ignored during the build process.

Question 6 of 12

In a multi-stage build, can you use the same base image for multiple stages?

No, each stage must use a different base image. Yes, you can use the same base image for multiple stages. Only if the stages are named differently. Only if the base image is available locally.

Question 7 of 12

What is the purpose of the

AS

keyword when defining a stage in a

Dockerfile

?

It defines an alias for a command within the stage. It specifies the architecture of the base image. It assigns a name to the stage for referencing it later. It defines environment variables for the stage.

Question 8 of 12

Which instruction is used to execute commands within a stage in a multi-stage

Dockerfile

?

CMD

RUN

EXEC

ENTRYPOINT

Question 9 of 12

If you have multiple

FROM

instructions in a

Dockerfile

without specifying a target stage when building, which stage will be the final image?

The first stage defined. A random stage. The last stage defined. The build will fail.

Question 10 of 12

How can you target a specific stage when building a multi-stage

Dockerfile

?

Using the

--from

flag with the

docker build

command. Using the

--stage

flag with the

docker build

command. Using the

--target

flag with the

docker build

command. You cannot target a specific stage; the entire Dockerfile is always built.

Docker | Multi-Stage Builds

Question 1 of 12

Question 2 of 12

Question 3 of 12

Question 4 of 12

Question 5 of 12

Question 6 of 12

Question 7 of 12

Question 8 of 12

Question 9 of 12

Question 10 of 12