Which statement compares S2I BuildConfigs and Dockerfile-based BuildConfigs in OpenShift?

• A. Dockerfile-based builds rely on a builder image to assemble the application.
• B. S2I builds combine source with a builder image to produce an application image.
• C. S2I builds create images without using a builder image.
• D. Dockerfile-based builds automatically promote images after build.

Answer: (B)

OpenShift S2I builds rely on a builder image to assemble the final application image from your source code. The builder image already contains the tools and runtime needed to compile and package the app, so the build process combines your source with that builder image to produce the application image. That exact dynamic is what makes S2I distinct: a separate builder image participates in creating the final image.

In contrast, Dockerfile-based builds use the instructions in a Dockerfile to build the image directly from a base image, without a separate, reusable builder image driving the build process. The other statements either misstate the role of a builder image or describe behavior (like automatic promotion) that isn’t a built-in part of Dockerfile-based builds.