Responses API Image Input for Vision Models on AI-901
HOTSPOT
Select the answer that correctly completes the sentence.

Community Insight
The test checks whether you know the only two accepted image input formats for the Responses API — inline base64-encoded data or a URL — and the trap is picking a file-format or credential term (CSV, MP4, SAS token) that has nothing to do with image transport.
This AI-901 hotspot asks how the Responses API accepts an image when calling a vision-enabled model such as a GPT-4o-class model in Azure AI Foundry/OpenAI. The sentence is correctly completed with a base64-encoded image data string, because the API supports exactly two image input formats: inline base64-encoded data or a public image URL.
Choosing an SAS token, a CSV file, or an MP4 video, because these are common items seen around AI workloads. None of them deliver pixel data to the model: an SAS token is only a storage-access credential, and CSV/MP4 are unrelated file formats rather than image payload formats.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
When a vision-enabled model is called through the Responses API, the image content must be delivered inside the request payload, and the two supported ways to do that are a base64-encoded image data string embedded inline or a URL pointing to a publicly reachable image. Base64 encoding converts the raw bytes of a JPG or PNG into a text-safe character stream that can travel in a JSON payload without multipart handling, which is exactly what a REST-based Responses call requires. Therefore the blank must be completed with base64-encoded image data, since the alternative valid format (a URL) is not offered as a choice in this hotspot.Why Other Candidate Answers Are Wrong
A CSV file is a delimited text format for tabular data and carries no image pixels, so passing it would give the model nothing visual to analyze. An MP4 is a compressed video container, and although some multimodal endpoints accept video, the Responses API image slot described here is specifically about image input, not video ingestion. An SAS token is merely a time-limited authorization string for Azure Blob or container access; it may accompany a URL, but it is not itself a way of passing image content to the model, so it does not complete the sentence.Community Comment Notes
Commenters converge on the same verdict, with derafazu noting the answerOfficial Reference
Exam Strategy
When a hotspot asks how an API receives multimodal content, think in terms of transport formats (inline encoded bytes versus URL references), not file extensions or credentials. Eliminate any candidate that is an authorization artifact or an unrelated media container before selecting the encoded-data option.
Frequently Asked Questions
What image formats does the Responses API accept when calling a vision-enabled model?
It accepts the image either as inline base64-encoded image data embedded in the JSON payload or as a publicly accessible image URL. No other transport, such as CSV or MP4, is used for this image input.
Why is an SAS token not the correct completion for the image-passing sentence?
An SAS token is only a time-limited credential that grants access to stored blobs; it does not contain image content. It might accompany a URL, but the image itself is passed as base64 data or a URL.
Related Analysis
Practice All AI-901 Questions
Access 105 questions with complete answers and detailed explanations.
View Full AI-901 Practice Test →