You run a streaming API on GKE and need two subscription tiers (basic, premium) that limit daily requests per client app. Use Google-recommended practices while enforcing per-client quotas. What should you do?
Choose an answer
Tap an option to check your answer.
Correct answer: 1) Put the GKE service behind an Apigee proxy. 2) Issue API keys to client apps. 3) Configure an Apigee Quota policy per API key by subscription tier..
Why this is the answer
The correct option leverages Apigee, Google Cloud's API management platform, for robust quota enforcement. Apigee proxies provide a centralized control point for APIs, allowing for the application of policies like Quota. Issuing API keys enables Apigee to identify individual client applications. Configuring an Apigee Quota policy per API key, differentiated by subscription tier, directly addresses the requirement for per-client, tier-based daily request limits. The incorrect options fail for various reasons: Using an Apigee SpikeArrest policy is for protecting against sudden traffic spikes, not for enforcing daily quotas. Configuring separate projects and QPS quotas per project is not granular enough for per-client application quotas and requires clients to use different endpoints, which is less flexible. Deploying to two GKE clusters and applying separate rate limits per tier is overly complex and inefficient compared to Apigee's policy-driven approach.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed