Google Exam Professional Cloud Architect 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%

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

upvoted 0 times

Stephanie

4 months ago

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

upvoted 0 times

...

Gail

4 months ago

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

upvoted 0 times

...

Alaine

5 months ago

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

upvoted 0 times

...

5 months ago

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

upvoted 0 times

...