Question-25: There are three key stages that make up the API lifecycle: the create, control, and consume phases. During the step known as create, you will construct your API and document it. During the control phase, you will implement the established security rules. In the consumption phase, you will publish APIs and begin to monetise them. Customers that shop at retail establishments may use your company's recommendation engine. You are making an application programming interface (API) available to retail consumers so that they may input a user ID and get a list of suggestions tailored to that user. You are in charge of the lifespan of the API and want to make sure that your clients are not disrupted in the event that the API undergoes modifications that are not backward compatible. You should adhere to the best practises advocated by Google. What action should you take?
A. At least one month before switching over to the new API from the older one, compile a list of all of your clients and send them an email informing them of an upcoming change that will break backward compatibility.
B. Establish an automated procedure for the generation of API documentation, and make it a part of the continuous integration and continuous delivery process so that it may be updated whenever an API change is sent.
C. Make use of a versioning approach for the APIs that raises the version number after each change that is incompatible with previous versions.
D. Make use of a versioning technique for the APIs that appends the suffix DEPRECATED to the number of the most recent version of the API if there is a change that is incompatible with previous versions. For the new API, use the version number that is currently in use.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 3 Explanation: The major version number is encoded at the very end of the protobuf package and is given as the first component of the URI path for REST APIs. This number is required to be provided by all Google API interfaces. In the event that an API makes a modification that is incompatible with previously written user code, such as deleting or renaming a field, the API's version number must be increased. This will guarantee that previously written user code will not suddenly become inoperable. Users have the ability to establish a LoadBalancer that is distributed across clusters and associate it with an anycast IP by using a tool called kubemci. This is a tool that is used to configure Kubernetes ingress to load balance traffic across several Kubernetes clusters. This method is no longer advised and has been superseded by Ingress for Anthos as the method of choice for deploying multi-cluster ingress going forward. Versioning In this subject, the versioning mechanisms that are used by Google APIs will be discussed. These tactics, in principle, are applicable to any service that is handled by Google. It may sometimes be required to make modifications to an API that are backwards incompatible, often known as breaking such changes. Changes of this nature have the potential to bring about problems or even cause the code to fail if it is dependent on the original functionality. The Google Application Programming Interfaces (APIs) make use of a versioning system to avoid breaking updates. In addition, some features of Google APIs are not accessible until the system reaches a certain degree of reliability, such as alpha or beta components.