Courseiva
Using the Claude API →hardMultiple Choice

CCAO-F Using the Claude API Practice Question

An engineer is designing a multi-tenant SaaS feature that lets each customer supply their own Anthropic API key, which the backend stores encrypted and uses when calling the Messages API on that tenant's behalf. A security review asks how requests should be attributed so usage can be billed back and abuse isolated per tenant. Which practice best meets this requirement?

⚠ Common exam trap

The trap here is treating a message-level identifier such as the user field as a substitute for credential-level separation of rate limits and billing.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Have the backend call the Messages API with each tenant's own stored key so rate limits, usage, and audit trails are scoped to that tenant.

Credential boundaries are the cleanest way to achieve per-tenant attribution and isolation. When each tenant's traffic flows through that tenant's own API key, Anthropic's rate limiting, usage records, and audit logs partition automatically, and a compromised or abusive tenant cannot exhaust capacity belonging to others. The backend retains control over request construction and can layer additional quotas.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Have the backend call the Messages API with each tenant's own stored key so rate limits, usage, and audit trails are scoped to that tenant.

    Why this is correct

    Using the tenant's own key means Anthropic's rate limiting, usage reporting, and logs are naturally partitioned per credential, which gives clean billing attribution and contains abuse to a single tenant. The backend still controls the call path, so it can enforce its own quotas and redact sensitive fields before forwarding. This aligns the credential boundary with the tenant boundary, which is exactly what the security review needs.

  • ✗

    Proxy all tenant traffic through a single key and reconcile billing by counting tokens in the responses your backend receives.

    Why it's wrong here

    Counting tokens client-side can approximate cost but does not isolate rate limits, cannot prevent one tenant from starving others, and is vulnerable to discrepancies between your accounting and Anthropic's. It also leaves a single credential whose compromise exposes every tenant. The review is asking for attribution and isolation at the request level, which client-side counting cannot deliver even if the arithmetic is accurate.

  • ✗

    Issue each tenant the same platform key but append a unique tenant ID to the user field of every message.

    Why it's wrong here

    The user field is intended to carry an end-user identifier for abuse monitoring, not to partition billing or enforce per-tenant throughput. Sharing one key still means shared rate limits and blended usage metrics, so a single misbehaving tenant degrades service for all others. Tagging messages does not create the credential-level isolation the review requires, making this a cosmetic rather than structural fix.

  • ✗

    Send every tenant's request using a single shared platform API key and rely on the prompt contents to identify the tenant.

    Why it's wrong here

    A shared key pools all tenants into one rate-limit and billing bucket, so one noisy tenant can exhaust throughput for everyone and usage cannot be attributed cleanly. Embedding tenant identity in prompts is also unreliable for accounting because prompts are model input, not authenticated metadata. This design undermines both the isolation and the per-tenant billing goals the review is asking the engineer to satisfy.

About these practice questions

This CCAO-F question is part of Courseiva's 259-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Anthropic exam blueprint

This CCAO-F practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAO-F exam.