Professional Cloud Architect Exam QuestionsBrowse all questions from this exam

Professional Cloud Architect Exam - Question 126


Your team will start developing a new application using microservices architecture on Kubernetes Engine. As part of the development lifecycle, any code change that has been pushed to the remote develop branch on your GitHub repository should be built and tested automatically. When the build and test are successful, the relevant microservice will be deployed automatically in the development environment. You want to ensure that all code deployed in the development environment follows this process. What should you do?

Show Answer
Correct Answer: C

To ensure that all code deployed in the development environment is built and tested automatically when pushed to the develop branch, a Cloud Build trigger should be created. This trigger should be based on the development branch and will handle testing the code, building the container, and storing it in the Container Registry. Then, a deployment pipeline should be set up to watch for new images and deploy them automatically to the development cluster. This approach ensures a consistent, automated process for building, testing, and deploying code, minimizing human error and ensuring that all code meets the required quality standards before being deployed.

Discussion

17 comments
Sign in to comment
TotoroChinaOption: C
Jul 1, 2021

Answer should be C, obviously.

AdGladOption: C
Jul 17, 2021

Questions say "relevant microservice will be deployed automatically in the development environment." Therefore A and B are out. D says "Rely on Vulnerability Scanning to ensure the code tests succeed." Vulnerability Scanning is not test so D is out. The correct Answer is therefore C.

omermahgoubOption: C
Dec 25, 2022

The correct answer is C: Create a Cloud Build trigger based on the development branch that tests the code, builds the container, and stores it in Container Registry. Create a deployment pipeline that watches for new images and deploys the new image on the development cluster. Ensure only the deployment tool has access to deploy new versions. To automate the build and deployment process for your microservices in the development environment, you can use Cloud Build to set up a trigger that listens for code pushes to the development branch on your GitHub repository. When a code change is pushed to the branch, Cloud Build can test the code, build the container image, and store it in Container Registry. You can then create a deployment pipeline that watches for new images in Container Registry and deploys them automatically on the development cluster. To ensure that only code that has been properly tested and built is deployed in the development environment, you should ensure that only the deployment tool has access to deploy new versions.

omermahgoub
Dec 25, 2022

Option A is incorrect because installing a pre-commit hook on each developer's workstation does not ensure that the build and test process is followed consistently for all code changes. It also does not provide a centralized way to track the deployments in the development environment. Option B is incorrect for the same reason. A post-commit hook on the remote repository does not provide a centralized way to manage the build and deployment process for all code changes in the development environment. Option D is incorrect because relying on Vulnerability Scanning alone is not sufficient to ensure that the code changes are properly tested and built before being deployed in the development environment. A more comprehensive build and test process, such as the one described in option C, is recommended to ensure the quality and reliability of the code being deployed.

shaykeOption: C
Aug 2, 2022

C- the only answer

Amit_archOption: D
Sep 15, 2022

C doesn't include test success. D should be the option.

zellck
Sep 18, 2022

Vulnerability Scanning is not relevant though for the question.

zr79
Oct 18, 2022

It does include tests succuss, the question is using CI/CD

minmin2020Option: C
Oct 17, 2022

C. Create a Cloud Build trigger based on the development branch that tests the code, builds the container, and stores it in Container Registry. Create a deployment pipeline that watches for new images and deploys the new image on the development cluster. Ensure only the deployment tool has access to deploy new versions.

meguminOption: C
Nov 14, 2022

C is ok

madmike123Option: C
Dec 22, 2022

"any code change that has been pushed to the remote develop branch on your GitHub repository should be built"...this excludes A and B since both happen locally before a push. Answer 'D' only performs security scanning (no test) and is not automatically deployed which is what was requested.

Dr_RamzusOption: C
Jan 29, 2023

Clearly C

kopasz93Option: C
Mar 27, 2023

The answer is C.

balajisreenivasOption: C
Apr 1, 2023

By elimination method, the answer is C.

AdityaGuptaOption: C
Oct 6, 2023

Agreed with omermahgoub Answer should be C.

AWS_SamOption: C
Jan 3, 2024

The correct answer is C.

convers39Option: C
Jan 11, 2024

Nah, no way to be A.

GallOption: C
Feb 14, 2024

C but.... "build container and add to the registry" ???? Not container but image.

Gino17mOption: C
Apr 24, 2024

Automatic deployment required in the question and manual deployment by developer in answer marked as correct ! Ance again....Who is responsible for marking answers as correct on examtopics platform ? Enyone from examtopics read responses from community and correct wrong answers ??? A few days after purchasing full access to this platform, I am disgusted :(

ccpmad
Jun 8, 2024

Do not be angry. That the answers are incorrect is on purpose. First so that the pdf is not shared and they are left without business. And secondly so that Google does not change the questions because then there are no correct answers filtered.

de1001cOption: C
Jun 7, 2024

Automatic, no developer running stuff, plus relying in pre-commit hooks alone is not a CD strategy. The C over D is because the pipeline in cloudbuild should run the tests, not the Vulnerability Scanner. While vulnerability scanner is useful, it's not required in this context, and there're no tests run in answer D.