Exam Professional Cloud Developer topic 1 question 122 discussion

B is correct.

We need to have the following steps in Cloud Build to identify bugs" 1) Static code analysis 2) Code Vulnerability scanning 3) Docker Image vulnerability scanning Using Grype is one such example.

I say D. Both B and D could work. However why not use traditional git workflows and keep separate branches for separate tasks. This way each image can be tested independently.

Option B is appropriate because it uses Cloud Build, a service that can automatically build container images from code stored in Cloud Source Repositories based on Git tags. This allows developers to quickly identify bugs in their code before it is deployed to production, by automating the building process and improving developer feedback. Option A uses Spinnaker, which is a multi-cloud continuous delivery platform that can automate building, testing, and deploying container images. However, it does not specifically mention using git tags to trigger builds, thus for this particular use case it might not be the best fit.

B is the answer.

D ) You need to quickly identify bugs in the code before it is deployed to production. So it's for developer to fork the code and test the build. Later they can push the changes using PR to the master repo/branch.

cloud build is the google service so it stands to reason to use that.

I think b is correct

I vote D. Because every developer before merge to the master should test build in his branch. It will expose bugs. Once branch merged to the master, master build pipeline comes up.

I would disagree with A as Spinnaker is for deployment not for building images So either B or C : C is stating to deploy to production but the question is to give feedback to developer before it goes to production So the only close answer is B but it is half answer Perhaps choice A was poorly written instead deploy build then it could be A

I vote B