A regional transit agency sells partner access to a real-time arrival API on OCI API Gateway. Product wants per-second rates, monthly quotas, and a list of which deployments each subscriber may call, using a client token only for metering. What does a usage plan provide in this model?
Select an answer to reveal the explanation.
Short Explanation
A usage plan is like a library card that tracks how many books you may borrow per day—it meters and tiers access, but it is not your government ID. Entitlements set per-second rate, quota over a window, and which deployments a subscriber may call. Official guidance: those client tokens are for metering; you still need a separate authentication policy.
Full Explanation
OCI API Gateway usage plans define entitlements with a per-second rate, a quota over a time window, and the deployments a subscriber may call. A usage-plan request policy demands a client token used for metering and tiering. Official documentation notes those tokens are not authentication or authorization—you still need an authn policy. Do not confuse the plan-manager role or usage-plan tokens with IAM authentication.