Google Professional Cloud Architect Exam - Topic 2 Question 9 Discussion

Actual exam question for Google's Professional Cloud Architect exam

Question #: 9
Topic #: 2

[All Professional Cloud Architect Questions]

Your company provides a recommendation engine for retail customers. You are providing retail customers with an API where they can submit a user ID and the API returns a list of recommendations for that user. You are responsible for the API lifecycle and want to ensure stability for your customers in case the API makes backward-incompatible changes. You want to follow Google-recommended practices. What should you do?

ACreate a distribution list of all customers to inform them of an upcoming backward-incompatible change at least one month before replacing the old API with the new API.

BCreate an automated process to generate API documentation, and update the public API documentation as part of the CI/CD process when deploying an update to the API.

CUse a versioning strategy for the APIs that increases the version number on every backward-incompatible change.

DUse a versioning strategy for the APIs that adds the suffix ''DEPRECATED'' to the current API version number on every backward-incompatible change. Use the current version number for the new API.

Show Suggested Answer

Suggested Answer: C

https://cloud.google.com/apis/design/versioning

All Google API interfaces must provide a major version number, which is encoded at the end of the protobuf package, and included as the first part of the URI path for REST APIs. If an API introduces a breaking change, such as removing or renaming a field, it must increment its API version number to ensure that existing user code does not suddenly break.

by Loreta at May 06, 2022, 04:39 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

Antione

5 months ago

Wait, what if customers don’t check their emails for updates?

upvoted 0 times

...

Malika

5 months ago

B is essential for keeping docs up to date, can't skip that!

upvoted 0 times

...

Farrah

5 months ago

A month notice is nice, but is it really enough?

upvoted 0 times

...

Donte

5 months ago

I think D is a bit confusing, why add "DEPRECATED"?

upvoted 0 times

...

Jaleesa

5 months ago

Definitely go with option C, versioning is key!

upvoted 0 times

...

Kasandra

5 months ago

I practiced a similar question where we had to ensure API stability. I think option B is crucial for keeping documentation up to date, but I wonder if it addresses backward compatibility directly.

upvoted 0 times

...

Emogene

5 months ago

I feel like option D could be a good choice too, especially since it highlights deprecated versions. But does adding "DEPRECATED" really help customers?

upvoted 0 times

...

Jerry

5 months ago

I remember discussing the importance of versioning in our last class. I think option C makes sense, but I'm not entirely sure if it's the best approach.

upvoted 0 times

...

Chauncey

5 months ago

I’m leaning towards option C for versioning, but I recall some debate about how often we should increment version numbers. It might be more complex than it seems.

upvoted 0 times

...

Erin

6 months ago

Okay, let's see here. The question is asking what happens when the audit indicates two items with a warning. I think the key is figuring out how that affects the deployment of the email.

upvoted 0 times

...

Vincenza

6 months ago

Okay, let me double-check. We have "to=el" and "toScript=Latn" covered. But do we also need "from=el" to specify the source language? I'm not 100% sure about that one.

upvoted 0 times

...