Discuss Google Professional Cloud Architect (PR000213) Exam Topic 1 Question 101

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?

A1. Configure a trigger in Cloud Build for new source changes.
2. Invoke Cloud Build to build one container image, and tag the image with the label 'latest.'
3. Push the image to the Artifact Registry.

B1. Configure a trigger in Cloud Build for new source changes.
2. Invoke Cloud Build to build container images for each microservice, and tag them using the code commit hash.
3. Push the images to the Artifact Registry.

C1 Create a Scheduler job to check the repo every minute.
2. For any new change, invoke Cloud Build to build container images for the microservices.
3. Tag the images using the current timestamp, and push them to the Artifact Registry.

D1. Configure a trigger in Cloud Build for new source changes.
2. The trigger invokes build jobs and build container images for the microservices.
3. Tag the images with a version number, and push them to Cloud Storage.

Suggested Answer: C

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

26 comments · newest first

Miesha 11 months ago

Wait, why would you tag with a timestamp? That’s confusing!

Boris 11 months ago

D is outdated, Cloud Storage isn't ideal for this.

Rima 11 months ago

C sounds risky with that minute check, right?

Kiera 11 months ago

I disagree, A seems simpler for a single container.

Jesus 12 months ago

B is the way to go! Tagging with the commit hash is smart.

Gilma 12 months ago

I vaguely recall that pushing to Artifact Registry is preferred over Cloud Storage for container images. So, I think options A and B are more aligned with best practices.

Leontine 1 year ago

I feel like we practiced a similar question where we had to choose between tagging strategies. I think tagging with the commit hash is a good idea for tracking changes, which makes me favor option B.

Carol 1 year ago

I'm not entirely sure, but I think using a Scheduler job like in option C might not be the best practice. It seems a bit inefficient compared to triggers.

Isabella 1 year ago

I remember we discussed the importance of tagging images with version numbers instead of just 'latest' to avoid confusion. So, I'm leaning towards option B.

Tyisha 1 year ago

This looks like a straightforward question on continuous integration and deployment practices. I think I can handle this one.Aditya: Hmm, I'm a bit confused about the different options here. I'll need to carefully read through each one and think about the Google-recommended practices mentioned in the question.Olivia: Okay, the key here is to follow the Google-recommended practices. I think option B is the way to go - building and tagging the container images with the commit hash seems like the best approach.Liam: I'm not too familiar with Cloud Build and Artifact Registry, but I'll give it my best shot. I'll need to make sure I understand the differences between the options before selecting an answer.

Salena 1 year ago

I'm not too familiar with Cloud Build and Artifact Registry, but I'll give it my best shot. I'll need to make sure I understand the differences between the options before selecting an answer.

Flo 1 year ago

Okay, the key here is to follow the Google-recommended practices. I think option B is the way to go - building and tagging the container images with the commit hash seems like the best approach.

Anisha 1 year ago

Hmm, I'm a bit confused about the different options here. I'll need to carefully read through each one and think about the Google-recommended practices mentioned in the question.

Allene 1 year ago

This looks like a straightforward question on continuous integration and deployment practices. I think I can handle this one.

Salome 2 years ago

I think D is the correct answer because it mentions version numbers.

Cherry 2 years ago

I'm leaning towards C, it makes more sense to me.

Evangelina 2 years ago

I disagree, I believe the answer is B.

Brock 2 years ago

I think the answer is A.

Claribel 2 years ago

Option A looks good, but I'm not sure about the 'latest' tag. Wouldn't it be better to use the commit hash like in Option B?

Stephanie 2 years ago

↳ replying to Claribel

But using the current timestamp like in Option C could also be a good approach for versioning.

Gail 2 years ago

↳ replying to Claribel

I agree, using the commit hash for tagging seems more reliable.

Alaine 2 years ago

Haha, a Scheduler job to check the repo every minute? That's overkill! I'd go with Option B and keep it simple.

Dierdre 2 years ago

Option B is the way to go! Tagging the images with the commit hash is a great way to track the source code version.

Dannette 2 years ago

↳ replying to Dierdre

It's important to follow Google-recommended practices for building and storing artifacts.

Altha 2 years ago

↳ replying to Dierdre

Tagging the images with the commit hash is a smart move for microservices.

Merlyn 2 years ago

↳ replying to Dierdre

I agree, option B is the best choice for tracking source code versions.

Google Professional Cloud Architect (PR000213) Exam - Topic 1 Question 101 Discussion