Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam Professional Cloud Architect topic 10 question 5 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 5
Topic #: 10
[All Professional Cloud Architect Questions]

For this question, refer to the TerramEarth case study. You are building a microservice-based application for TerramEarth. The application is based on Docker containers. You want to follow Google-recommended practices to build the application continuously and store the build artifacts. What should you do?

  • A. Configure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build container images for each microservice, and tag them using the code commit hash. Push the images to the Container Registry.
  • B. Configure a trigger in Cloud Build for new source changes. The trigger invokes build jobs and build container images for the microservices. Tag the images with a version number, and push them to Cloud Storage.
  • C. Create a Scheduler job to check the repo every minute. For any new change, invoke Cloud Build to build container images for the microservices. Tag the images using the current timestamp, and push them to the Container Registry.
  • D. Configure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build one container image, and tag the image with the label 'latest.' Push the image to the Container Registry.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
meh_33
Highly Voted 2 years, 8 months ago
https://cloud.google.com/architecture/best-practices-for-building-containers#tagging_using_the_git_commit_hash A is ok
upvoted 30 times
ashish_t
2 years, 6 months ago
Just above that section, there is a section for the version number. https://cloud.google.com/architecture/best-practices-for-building-containers#tagging_using_semantic_versioning The difference between A and B is how it gets triggered. A has "Invoke Cloud Build to build container images" same with C and D. B has "The trigger invokes build jobs" Your pipeline should not have manual steps. That's why I would choose B. B is correct.
upvoted 7 times
cloudmon
2 years, 1 month ago
B talks about pushing the images to Cloud Storage, which is not a best practice. A is correct
upvoted 15 times
...
...
...
KillerGoogle
Highly Voted 2 years, 8 months ago
A, commit hash is required
upvoted 9 times
...
Gino17m
Most Recent 2 weeks, 3 days ago
Selected Answer: A
I vote for A
upvoted 1 times
...
mesodan
2 months, 2 weeks ago
Selected Answer: A
Commit Hash Tagging: Tagging images with the code commit hash improves version control and allows identifying the specific code used in each image. Container Registry Storage: Pushing images to the Container Registry is a Google-managed service specifically designed for storing container images, providing security, access control, and integration with other Google Cloud services.
upvoted 2 times
...
thewalker
5 months, 3 weeks ago
Selected Answer: A
A Container Registry and not Cloud Storage.
upvoted 1 times
...
Prakzz
7 months, 1 week ago
Selected Answer: B
Always give a version number for all images in container registry. No latest hash or anything
upvoted 2 times
...
omermahgoub
1 year, 4 months ago
A. Configure a trigger in Cloud Build for new source changes. Invoke Cloud Build to build container images for each microservice, and tag them using the code commit hash. Push the images to the Container Registry. This option follows Google-recommended practices for building and storing the build artifacts for a microservice-based application. By configuring a trigger in Cloud Build, you can automate the build process and ensure that the build artifacts are created whenever there are new source changes. By tagging the images with the code commit hash, you can track the changes and have a record of the build history. Finally, by storing the images in the Container Registry, you can manage and deploy the artifacts easily.
upvoted 5 times
...
surajkrishnamurthy
1 year, 5 months ago
Selected Answer: A
A is the correct answer
upvoted 1 times
...
Mahmoud_E
1 year, 7 months ago
Selected Answer: A
A is correct
upvoted 1 times
...
AzureDP900
1 year, 7 months ago
A is fine
upvoted 1 times
...
AzureDP900
1 year, 10 months ago
A is perfect
upvoted 2 times
...
omodara
1 year, 11 months ago
A is the correct answer. The question referred to Docker containers not cloud storage. https://cloud.google.com/architecture/best-practices-for-building-containers#tagging_using_the_git_commit_hash
upvoted 2 times
...
amxexam
2 years ago
Selected Answer: A
I will go with commit hash to tag inwages or time stamp A is better than C so A.
upvoted 2 times
...
mad314
2 years ago
Selected Answer: A
Had this question on my exam.
upvoted 3 times
...
sergaebi
2 years, 1 month ago
Selected Answer: A
Vote for A
upvoted 2 times
...
Aiffone
2 years, 4 months ago
I go with B rather than A because the trigger should invoke the build and versioning is a better way to tag rather than commit coments
upvoted 1 times
...
Bobch
2 years, 5 months ago
Selected Answer: A
A is correct answer. Google Cloud has two services for storing and managing container images such as Artifact Registry and Container Registry. https://cloud.google.com/container-registry/docs/overview
upvoted 4 times
mesodan
2 years, 2 months ago
Agree. B could be an option only if it wasn't for Cloud Storage which can't be used to store container images.
upvoted 3 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...