exam questions

Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 1 question 137 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 137
Topic #: 1
[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?

  • A. Create 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.
  • B. Create 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.
  • C. Use a versioning strategy for the APIs that increases the version number on every backward-incompatible change.
  • D. Use 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 Hide Answer
Suggested Answer: C 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
kopper2019
Highly Voted 2 years, 12 months ago
It is C
upvoted 35 times
sebafranek
2 years, 11 months ago
https://cloud.google.com/apis/design/versioning
upvoted 9 times
[Removed]
1 year, 5 months ago
more specifically: https://cloud.google.com/apis/design/versioning#release-based_versioning
upvoted 5 times
...
...
...
VishalB
Highly Voted 2 years, 11 months ago
Answer C 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.
upvoted 23 times
...
de1001c
Most Recent 3 weeks, 3 days ago
Selected Answer: C
Breaking changes = version bump in the API url
upvoted 1 times
...
spuyol
4 months, 3 weeks ago
Answer is A Question asks: You are responsible for the API lifecycle and want to ensure stability for your customers in case the API makes backward-incompatible changes. Option C is a must for the API lifecycle but doing only that will not help your customers. In my opinion they have to be notified of backward-incompatible changes with time enough to stay ready
upvoted 1 times
...
convers39
5 months, 3 weeks ago
Selected Answer: C
This is not a GCP-specific or even cloud-specific question, but a development best practice. No need to look at other options.
upvoted 3 times
...
mastrrrr
6 months, 4 weeks ago
I had a test today. The overall question was almost the same, but question mentioned Apigee.
upvoted 4 times
...
heretolearnazure
10 months ago
C is correct
upvoted 1 times
...
BiddlyBdoyng
1 year ago
Maybe A on top of C but are we really going to mandate customers only have 1 month to be ready? I don't think so, use the version strategy and let them migrate when ready!
upvoted 1 times
...
Atanu
1 year, 1 month ago
Anyways option A is also a recommended best practice. Its version incompatible change afterall.
upvoted 1 times
...
gu_pp
1 year, 2 months ago
Selected Answer: C
Clearly C
upvoted 1 times
...
bharath2k5
1 year, 3 months ago
Selected Answer: C
c version numbers cannot be changed as given in d
upvoted 1 times
...
CGS22
1 year, 3 months ago
Selected Answer: C
The correct answer is: C. Use a versioning strategy for the APIs that increases the version number on every backward-incompatible change. A versioning strategy for the APIs that increases the version number on every backward-incompatible change is the best way to ensure stability for your customers in case the API makes backward-incompatible changes. This will allow you to track the changes that have been made to the API and allow your customers to easily identify the latest version of the API.
upvoted 3 times
...
zerg0
1 year, 5 months ago
Selected Answer: C
See @seafranek comment
upvoted 1 times
...
HenkH
1 year, 6 months ago
If 'A' is the correct answer, one would wonder why. The new version might be back-ward incompatible but does not necessarily mean its a breaking one. In that case A might be sufficient, although C remains mandatoryBest Practice imho.
upvoted 1 times
...
surajkrishnamurthy
1 year, 6 months ago
Selected Answer: C
C is the correct answer
upvoted 2 times
...
megumin
1 year, 7 months ago
Selected Answer: C
C is ok
upvoted 1 times
...
Balaji_Sakthi
1 year, 8 months ago
option C
upvoted 1 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 ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago