Google Professional Cloud Developer
Get started today
Ultimate access to all questions.
You're building a customer-facing application on GKE that exposes a streaming API. You need to implement two subscription tiers ("basic" and "premium") that limit daily API request quotas for client applications. How should you architect this solution while adhering to Google's best practices?
You're building a customer-facing application on GKE that exposes a streaming API. You need to implement two subscription tiers ("basic" and "premium") that limit daily API request quotas for client applications. How should you architect this solution while adhering to Google's best practices?
Explanation:
Option A is the correct choice because it effectively uses Apigee's Quota policy to manage daily request limits based on subscription tiers, which is a Google-recommended practice for API management. This approach allows for the identification of client applications through API keys and the application of quota policies based on the subscription tier, ensuring a scalable and manageable solution. Options B, C, and D either do not address the requirement of daily request limits based on subscription tiers or introduce unnecessary complexity without providing a clear benefit.