Google Professional Cloud Architect Exam - Topic 1 Question 101 Discussion

Actual exam question for Google's Professional Cloud Architect exam

Question #: 101
Topic #: 1

[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?

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.

Show Suggested Answer

Suggested Answer: C

by Mari at Jan 27, 2025, 04:44 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Miesha

3 months ago

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

upvoted 0 times

...

Boris

3 months ago

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

upvoted 0 times

...

Rima

3 months ago

C sounds risky with that minute check, right?

upvoted 0 times

...

Kiera

4 months ago

I disagree, A seems simpler for a single container.

upvoted 0 times

...

Jesus

4 months ago

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

upvoted 0 times

...

Gilma

4 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.

upvoted 0 times

...

Leontine

4 months 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.

upvoted 0 times

...

Carol

4 months 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.

upvoted 0 times

...

Isabella

5 months 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.

upvoted 0 times

...

Tyisha

5 months 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.

upvoted 0 times

...

Salena

5 months 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.

upvoted 0 times

...

Flo

5 months 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.

upvoted 0 times

...

Anisha

5 months 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.

upvoted 0 times

...