Exam Professional Cloud Developer topic 1 question 140 discussion

AC is correct.

Apart from A and C, one more good option would be to copy the app directory only after RUN pip install so that we can avoid this copying part repeatedly after each layer build.

A is correct because a high-CPU virtual machine type can increase the speed of your build. B is not correct because a Container Registry on a VM will not speed up the build. C is correct because the same container is used in subsequent steps for testing and to be pushed to the registry. D is not correct because an ubuntu container image will be significantly larger than the python:3.7-alpine image. E is not correct because storing the application source code on Cloud Storage does not decrease the time to build the application.

https://cloud.google.com/build/docs/optimize-builds/increase-vcpu-for-builds https://cloud.google.com/build/docs/optimize-builds/building-leaner-containers#building_leaner_containers Yes, answer A and C are both valid solutions based on the articles you linked. Increasing the number of vCPUs allocated to the Cloud Build VM can help to decrease build time because it provides the build environment with more CPU resources to use, which can help to speed up the build process. This can be achieved by selecting a VM size with higher CPU for Cloud Build runs. as mentioned, caching the Docker image for subsequent builds can also help to decrease build time by reusing previously built image layers. This can be achieved by adding the --cache-from argument to the build command in the build config file, which tells Cloud Build to use the specified images as a cache source.

https://cloud.google.com/build/docs/optimize-builds/increase-vcpu-for-builds Answer A https://cloud.google.com/build/docs/optimize-builds/building-leaner-containers#building_leaner_containers Answer C

AC is the answer. https://cloud.google.com/build/docs/optimize-builds/increase-vcpu-for-builds By default, Cloud Build runs your builds on a standard virtual machine (VM). In addition to the standard VM, Cloud Build provides several high-CPU VM types to run builds. To increase the speed of your build, select a machine with a higher vCPU to run builds. Keep in mind that although selecting a high vCPU machine increases your build speed, it may also increase the startup time of your build as Cloud Build only starts non-standard machines on demand. https://cloud.google.com/build/docs/optimize-builds/speeding-up-builds#using_a_cached_docker_image The easiest way to increase the speed of your Docker image build is by specifying a cached image that can be used for subsequent builds. You can specify the cached image by adding the --cache-from argument in your build config file, which will instruct Docker to build using that image as a cache source.

A and C are correct

why don't I see community voted progress bar?

IMHO D - alpine is a much smaller distro B and E - does not make sense https://cloud.google.com/build/docs/optimize-builds/increase-vcpu-for-builds https://cloud.google.com/build/docs/optimize-builds/speeding-up-builds