Exam Professional Cloud Developer topic 1 question 219 discussion

C: “For example, use buildpacks to build the source code of your Cloud Run service into a container image.” - https://cloud.google.com/docs/buildpacks/build-application Also, https://cloud.google.com/blog/products/containers-kubernetes/google-cloud-now-supports-buildpacks D: “If no Dockerfile is present in the source code directory, Google Cloud's buildpacks automatically detects the language you are using and fetches the dependencies of the code to make a production-ready container image, using a secure base image managed by Google.” - https://cloud.google.com/run/docs/deploying-source-code

The actual question is "How should you build your container using Google Cloud services?", so it doesn't mention how to deploy it. Also, if we exclude B, how is the image build in C ending up at the central container repository?

C is packeto build pack to create an image. This is a very efficient way of creating images explicitly. D is through gcloud run command. Not sure what framework cloud build uses to create an image.

i choose cd

pack build [IMAGE-NAME] --builder [BUILDER-IMAGE] --path [APPLICATION-DIRECTORY] gcloud run deploy [SERVICE-NAME] --image [IMAGE-NAME] --source [APPLICATION-DIRECTORY]

https://cloud.google.com/run/docs/deploying-source-code

A and B are the correct options because they both involve using Cloud Build to build the container image. Option A, Push your source code to Artifact Registry, allows you to store the source code of your application in a central location, making it easier to manage and version control. Option B, Submit a Cloud Build job to push the image, allows you to use Cloud Build to build the container image, which is a recommended method for building container images in a production environment. It allows you to automate the build process, test the image, and push it to a container registry.

The Cloud run use the buildpacks to automatically build container images from source code but you need to use source code flag so you need to add the --source flag to your command gcloud run deploy --source=/PATH/ Answer C & D

CD is the answer. https://cloud.google.com/run/docs/deploying-source-code This page describes how to deploy new services and new revisions to Cloud Run directly from source code using a single gcloud CLI command, gcloud run deploy with the --source flag. Behind the scenes, this command uses Google Cloud's buildpacks and Cloud Build to automatically build container images from your source code without having to install Docker on your machine or set up buildpacks or Cloud Build.

C & D are correct

C and D. C: Google Cloud for buildpacks—an open-source technology that makes it fast and easy for you to create secure, production-ready container images from source code and without a Dockerfile. https://cloud.google.com/blog/products/containers-kubernetes/google-cloud-now-supports-buildpacks (also mentioned by TNT87) D: Deploying from source code. "This page describes how to deploy new services and new revisions to Cloud Run directly from source code using a single gcloud CLI command, gcloud run deploy with the --source flag." https://cloud.google.com/run/docs/deploying-source-code A is incorrect because Artifact Registry is for container images, not source code. B is incorrect because only the built image is needed to be deployed to Cloud Run. "A centrally managed container repository" can be somewhere outside of Google, so as the build tool. It doesn't necessary to be built on Cloud Build. E is irrelevant in this case, as K8S is not involved in this question.

https://dev.to/alvardev/gcp-cloud-run-containers-without-dockerfile-2jh3

Answer A https://cloud.google.com/run/docs/deploying#images Answer C https://cloud.google.com/blog/products/containers-kubernetes/google-cloud-now-supports-buildpacks