Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Developer Topic 13 Question 72 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 72
Topic #: 13
[All Professional Cloud Developer Questions]

You are developing a new web application using Cloud Run and committing code to Cloud Source Repositories. You want to deploy new code in the most efficient way possible. You have already created a Cloud Build YAML file that builds a container and runs the following command: gcloud run deploy. What should you do next?

Show Suggested Answer Hide Answer
Suggested Answer: B

https://cloud.google.com/build/docs/triggers

Cloud Build uses build triggers to enable CI/CD automation. You can configure triggers to listen for incoming events, such as when a new commit is pushed to a repository or when a pull request is initiated, and then automatically execute a build when new events come in. You can also configure triggers to build code on any changes to your source repository or only on changes that match certain criteria.


Contribute your Thoughts:

Dominga
6 months ago
Haha, can you imagine setting up a cron job to deploy every 24 hours? Talk about inefficient! That's like the tortoise of deployment strategies.
upvoted 0 times
...
Joana
6 months ago
I agree, the build trigger is probably the best choice here. Plus, it's more secure than using a public webhook, right? I don't want to risk any unauthorized access to our code.
upvoted 0 times
Jestine
5 months ago
B: I agree, we definitely need to prioritize security when setting up our deployment process.
upvoted 0 times
...
Brett
5 months ago
A: That's right, unauthorized access to our code can lead to serious consequences.
upvoted 0 times
...
Renato
6 months ago
B: And it ensures that only authorized code changes trigger the deployment process.
upvoted 0 times
...
Dorian
6 months ago
A: Absolutely, security is crucial when deploying code. The build trigger provides a controlled way to automate our deployments.
upvoted 0 times
...
Donte
6 months ago
B: I think using a build trigger is a good idea. It's a more secure option and keeps our code safe.
upvoted 0 times
...
Hillary
6 months ago
A: Create a Pub/Sub topic to be notified when code is pushed to the repository. Create a Pub/Sub trigger that runs the build file when an event is published to the topic.
upvoted 0 times
...
...
Felix
6 months ago
Well, if we want the most efficient deployment, I'd say the build trigger is the way to go. That way, the build file runs automatically when the code is pushed, no need to wait for a cron job or anything.
upvoted 0 times
...
Billye
6 months ago
Ooh, this Cloud Run question looks tricky! I'm not sure if I should go with the Pub/Sub option or the build trigger. Decisions, decisions.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77