Topic 1 Question 137
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?
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.
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.
Use a versioning strategy for the APIs that increases the version number on every backward-incompatible change.
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.
ユーザの投票
コメント(17)
It is C
👍 33kopper20192021/07/02Answer 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.
👍 20VishalB2021/07/13- 正解だと思う選択肢: C
versioning can be done using API gateway APIGEE
👍 4kummimhk2022/06/06
シャッフルモード