Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Google Cloud Certified Professional Cloud DevOps Engineer · Google Cloud
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Option D
That said, I send the question back to you, how about the developers?: "is concerned that developers or operators could circumvent" Developer will push code direct to master, with bug that is not caught by the tests and here we go: you do have a signed imaged, attested, with a BUG or something like that will be deployed so the question depends on the point of view, the combination of both are right and one more thing, D prevent to push to the registry, but the operator can get the kubernetes deployment yaml and point to other GCR...
If you are not familiarised, Pull Requests are one way to bring changes from one branch (e.g. develop) into protected branches (e.g. master, main). 1. First you need to protect the production branch (e.g, master, main) 2. If a developer attempts to push new code to a production (now protected) it will trow a Permission denied error like this: remote: Permission denied to update branch master. To git.com:org/repository.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'git.com:org/repository.git' 3. in order to push their code to production branch, the developers will need to open a Pull Request (If you are using GitLab, it is called Merge Request) and ask someone to Review and Approve your changes. 4. The pipeline points to the protected branch; any new code pushed trigger the pipeline, and runs the tests and then deploy it. This is how we do devops.