Skip to content

Commit 5a406dd

Browse files
author
Sherry Yang
committed
Update for acrolinx.
1 parent 01f57d6 commit 5a406dd

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

learn-pr/wwl-data-ai/get-started-vision-azure/6-knowledge-check.yml

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -27,14 +27,14 @@ quiz:
2727
choices:
2828
- content: "By sending text prompts through the OpenAI Responses API using a deployed image model"
2929
isCorrect: true
30-
explanation: "Image generation models in Foundry can be accessed programmatically using the OpenAI Responses API (or image generation APIs), where developers submit text prompts and retrieve generated images."
30+
explanation: " Developers can submit text prompts and retrieve generated images from Foundry models using the OpenAI Responses API."
3131
- content: "By uploading images through the Foundry Playground UI."
3232
isCorrect: false
3333
explanation: "The Foundry Playground UI is for interacting with models, not for programmatically generating images."
3434
- content: "By calling the GPT-4.1 model endpoint."
3535
isCorrect: false
36-
explanation: "GPT-4.1 is a multimodal GPT model that can process text and images together. It cannot generate images."
37-
- content: "When generating images programmatically using the OpenAI Python SDK with Microsoft Foundry, which value should be passed as the model parameter in the request?"
36+
explanation: "GPT-4.1 is a multimodal model that can process text and images together. It can't generate images."
37+
- content: "When you generate images programmatically using the OpenAI Python SDK with Microsoft Foundry, which value should you pass as the model parameter in the request?"
3838
choices:
3939
- content: "The original base model name (for example, gpt-image-1.5)."
4040
isCorrect: false
@@ -47,12 +47,12 @@ quiz:
4747
explanation: "You need to provide the deployment name of the model, not the Foundry resource name, when making API calls to generate images."
4848
- content: "Why is video generation with Sora models in Microsoft Foundry handled as an asynchronous job?"
4949
choices:
50-
- content: "Because video generation requires user interaction during rendering."
50+
- content: "Because, video generation requires user interaction during rendering."
5151
isCorrect: false
52-
explanation: "Video generation does not require user interaction during rendering."
53-
- content: "Because the REST API does not support synchronous requests."
52+
explanation: "Video generation doesn't require user interaction during rendering."
53+
- content: "Because, the REST API doesn't support synchronous requests."
5454
isCorrect: false
5555
explanation: "REST APIs absolutely can be synchronous. In this content, the reason given for async is workload duration and compute cost, not that it's not possible to process synchronously."
56-
- content: "Because video generation is resource‑intensive and takes time to complete"
56+
- content: "Because, video generation is resource‑intensive and takes time to complete."
5757
isCorrect: true
58-
explanation: "Video generation is computationally intensive and can take several minutes to complete. For this reason, Foundry runs video generation as an asynchronous process where you create a job, poll for its status, and download the video once it is finished."
58+
explanation: "Video generation is computationally intensive and can take several minutes to complete. For this reason, Foundry runs video generation as an asynchronous process where you create a job, poll for its status, and download the video once it's finished."

0 commit comments

Comments
 (0)