Implement generative AI solutions →hardMultiple ChoiceObjective-mapped

AI-102 Implement generative AI solutions Practice Question

Exhibit

Refer to the exhibit.

$response = Invoke-RestMethod -Uri "https://myfoundry.openai.azure.com/openai/deployments/gpt-4/chat/completions?api-version=2024-02-15-preview" -Method Post -Headers @{
    "Authorization" = "Bearer my-key"
} -Body (ConvertTo-Json @{
    messages = @(
        @{ role = "system"; content = "You are an AI assistant." },
        @{ role = "user"; content = "Tell me a joke." }
    )
    max_tokens = 50
    temperature = 0.7
})

Refer to the exhibit. A developer runs this PowerShell script to call Azure OpenAI. The script fails with an authentication error. What is the most likely cause?

⚠ Common exam trap

A common mix-up: candidates confuse Azure OpenAI's API key authentication with Azure AD token authentication, assuming 'Authorization: Bearer' is always correct, when in fact the header name differs based on the authentication method.

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 script uses the wrong HTTP header; it should use 'api-key' instead of 'Authorization: Bearer'.

The script uses 'Authorization: Bearer' header, but Azure OpenAI requires the API key to be passed in the 'api-key' header. The 'Authorization: Bearer' header is used for Azure AD token-based authentication, not for direct API key authentication. Since the script is using an API key (as indicated by the PowerShell script), the correct header is 'api-key'.

Answer analysis

Option-by-option breakdown

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

✓
The script uses the wrong HTTP header; it should use 'api-key' instead of 'Authorization: Bearer'.
Why this is correct
Azure OpenAI uses the 'api-key' header for key-based authentication.
✗
The script uses the wrong HTTP method; it should use GET.
Why it's wrong here
Chat completions require POST.
✗
The API version is incorrect.
Why it's wrong here
The API version '2024-02-15-preview' is valid.
✗
The endpoint URI is missing the resource name.
Why it's wrong here
The URI includes the resource name 'myfoundry'.

Go deeper

AI-102 Implement generative AI solutions Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question