AI-900 Practice Question: Describe features of generative AI workloads on Azure

Answer analysis

Option-by-option breakdown

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

• ✗

  A product listing of Azure AI hardware accelerators available for purchase

  Why it's wrong here

  This mischaracterises the catalogue as infrastructure procurement. Azure's model catalogue contains versioned software assets — ONNX, MLflow, and Transformers artifacts — that you can deploy onto computing targets such as CPU instances, GPU VMs, or Azure Machine Learning endpoints; it never lists purchasable silicon. Hardware accelerators are offered in the Azure compute product lineup and marketplace, on a separate resource and billing hierarchy, so 'available for purchase' does not apply to catalogue entries.

• ✓

  A curated collection of AI models from multiple providers available for deployment in Azure

  Why this is correct

  The model catalogue in Azure AI Foundry (formerly Azure AI Studio) is a curated, searchable library of pretrained models from OpenAI, Hugging Face, Meta, Microsoft, and other providers, offering model cards, version histories, benchmarks, and one-click deployment to managed endpoints or serverless APIs. It acts as a discovery and deployment hub, enabling teams to compare and select the right model for a given workload — not merely a static documentation list.

• ✗

  A directory of all Azure AI customer support contacts organised by model type

  Why it's wrong here

  This is incorrect because the model catalogue contains metadata about deployable AI artifacts — model weights, tokenizers, inference schemas, and deployment payloads — not human contacts. Customer support operatives would be found in Azure support resources or a support portal, and organising them 'by model type' has no operational meaning for provisioning or invoking an AI model. The catalogue is a technical library, not an org chart.

• ✗

  A registry of all models that have passed Microsoft's responsible AI certification

  Why it's wrong here

  Although some models in Azure's catalogue may undergo Microsoft's responsible AI reviews, the catalogue is not — and cannot be — an exclusive registry of formally 'certified' models. Responsible AI in Azure is a suite of tools (error analysis, fairness metrics, content safety, transparency) that customers apply to their own data and deployments, and many open-source models are listed simply because they are useful and deployable, not because they passed a central certification body. Treating the catalogue as a compliance list conflates governance tooling with model inventory.

Go deeper

Related to this question