Plan and manage an Azure AI solution →hardMultiple Choice

AI-102 Plan and manage an Azure AI solution Practice Question

Exhibit

{
  "properties": {
    "policies": [
      {
        "key": "rate",
        "value": "20:1"
      },
      {
        "key": "renewal-deployment-period",
        "value": "PT10H"
      },
      {
        "key": "quota",
        "value": 100
      }
    ]
  }
}

Refer to the exhibit. You are reviewing a content safety policy for an Azure AI Foundry deployment. The policy rate limits to 20 requests per minute. A user submits 50 requests in one minute. How many requests are allowed?

⚠ Common exam trap

Microsoft often tests the misconception that exceeding a rate limit blocks all requests, when in fact the limit is a threshold that allows the first N requests and denies the rest.

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

✓

The content safety policy enforces a rate limit of 20 requests per minute. When a user submits 50 requests in one minute, the rate limiter allows only the first 20 requests and blocks the remaining 30. This is a standard token-bucket or sliding-window rate-limiting behavior in Azure AI Foundry, where exceeding the limit results in HTTP 429 (Too Many Requests) for excess requests.

Answer analysis

Option-by-option breakdown

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

✓
20
Why this is correct
The rate limit caps throughput at 20 requests per minute, so only the first 20 submissions are processed; the remaining 30 are rejected with HTTP 429 responses. This satisfies the policy's stated constraint directly, regardless of how many requests the user submits within that window.
✗
50
Why it's wrong here
Rate limiting caps throughput at 20 requests per minute, so the remaining 30 are throttled with HTTP 429 responses rather than processed. Choosing 50 assumes unlimited capacity, which is tempting because Azure AI Foundry quotas can be raised on request — but that requires a support ticket and revised limit, not automatic bursting within the current policy.
✗
100
Why it's wrong here
The policy's 20-requests-per-minute limit is enforced by the service, so only 20 of the 50 submissions are permitted; the remainder are throttled with 429 responses. Choosing 100 likely confuses this with a token or quota allowance, which applies when calculating capacity for provisioned throughput rather than a per-minute request rate cap.
✗
None, all are blocked.
Why it's wrong here
Rate limiting caps throughput at 20 requests per minute; excess requests are throttled or rejected, not all blocked. The first 20 within the window are permitted, with the remaining 30 refused. The option assumes a blanket denial, confusing rate limiting with a content filter that blocks every submission.

Go deeper

AI-102 Plan and manage an Azure AI solution Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question