Reinforce AI-200 concepts with active-recall study cards covering all 4 blueprint domains. Each card shows the question on the front and the correct answer with a full explanation on the back.
Flashcards work through active recall — the process of retrieving information from memory rather than passively re-reading it. Research consistently shows that active recall produces stronger, longer-lasting memory than re-reading study guides. For AI-200 preparation, this means flashcards are one of the highest-return study tools available.
Attempt recall first
Read the AI-200 question on each card, pause, and attempt to formulate the answer in your own words before revealing. This retrieval attempt — even if wrong — dramatically strengthens memory compared to immediately reading the answer.
Review wrong cards again
When you get a card wrong, note it and add it back to your review pile. Spaced repetition — seeing difficult cards more frequently — is the mechanism that makes flashcard study far more efficient than linear reading.
Study by domain
Group your AI-200 flashcard sessions by domain for the first 3–4 weeks. Master one domain before moving to the next. In the final week, shuffle all cards together to test cross-domain recall — which is what the real AI-200 exam requires.
Short sessions beat marathon reviews
20–30 flashcard cards per session, done daily, produces better retention than a single 200-card marathon session. Five short daily sessions per week over 4 weeks gives you over 400 total card reviews — enough to reliably pass AI-200.
Sample cards from the AI-200 flashcard bank. Read the question, think of the answer, then read the explanation below.
Your enterprise AI solution runs on Azure Kubernetes Service (AKS) and utilizes Azure Key Vault to store secrets and API keys for cognitive services. You need to provide pods with secure, credential-less access to Azure Key Vault without storing connection strings in Kubernetes secrets or environment variables. Which integration should you implement?
Azure Key Vault Provider for Secrets Store CSI Driver with Microsoft Entra ID Workload Identity
The Azure Key Vault Provider for Secrets Store CSI Driver mounts Key Vault secrets directly into pods as volumes, and when combined with Microsoft Entra ID Workload Identity, the pod authenticates to Key Vault using a federated Kubernetes service account token — no stored credentials, connection strings, or environment variables. This is the recommended credential-less pattern for AKS.
Your team is building an asynchronous order processing pipeline. If a downstream AI service fails to process a message from a Service Bus queue after 5 delivery attempts, the message must be automatically removed from active processing and preserved for manual inspection. What should you configure?
Configure the Max Delivery Count property on the queue and enable dead-lettering on message expiration or failure.
Configuring Max Delivery Count on the queue (for example, 5) combined with dead-lettering on message expiration or delivery failure ensures that after five unsuccessful delivery attempts the message is moved to the dead-letter queue (DLQ) rather than being retried indefinitely or discarded. The DLQ preserves the message payload and failure metadata for manual inspection and reprocessing. This is the native Service Bus mechanism for poison-message handling.
When configuring an Azure Cosmos DB for NoSQL container to store embeddings, what data type must the vector property be stored as within the JSON document?
An array of 32-bit floating-point numbers
Azure Cosmos DB for NoSQL stores vector embeddings as a JSON array of 32-bit floating-point numbers (float32), which is the format its native vector indexing and DiskANN-based similarity search expect. Each element represents one dimension of the embedding, and the container's vector policy declares dimensions and the float32 data type.
You have an AI model container hosted in Azure Container Registry. You want to ensure that every container image pushed to the registry is automatically scanned for known vulnerabilities before deployment. Which ACR feature should you enable?
Microsoft Defender for Cloud vulnerability scanning
Microsoft Defender for Cloud vulnerability scanning is correct because it provides integrated image vulnerability assessment for Azure Container Registry, automatically scanning images on push and continuously re-scanning for newly disclosed CVEs. Enabling the Defender for Containers plan surfaces scan results in Defender for Cloud and can gate deployments via Azure Policy. This directly satisfies the requirement to scan every pushed image before deployment.
You are implementing a RAG solution where user queries are matched against an Azure AI Search vector index. You want to ensure that search results only return documents where a specific metadata field 'securityLevel' matches the user's clearance. How should you apply this filter?
Pass an OData filter expression in the 'filter' parameter of the search query request
Passing an OData filter expression in the 'filter' parameter of the search query request is the correct way to restrict results by metadata such as securityLevel. Azure AI Search supports OData filter syntax on filterable fields, and the filter is applied alongside vector search to return only documents matching the predicate. This enforces security trimming at query time without duplicating services or embedding metadata into vectors.
You are optimizing search performance in Azure AI Search. You notice that vector queries are consuming excessive memory and slowing down. You decide to enable exhaustive k-NN fallback for specific queries. What does exhaustive k-NN do?
It searches all vectors exactly without relying on an approximate nearest neighbor graph
Exhaustive k-NN (also called brute-force or exact k-NN) computes the distance between the query vector and every vector in the index, returning the exact nearest neighbors without relying on an approximate graph like HNSW. It is used when recall must be perfect, at the cost of higher latency and memory.
You are configuring a vector index in Azure AI Search and want to apply scalar quantization to reduce the memory footprint. What is the primary effect of scalar quantization on float32 vector data?
It compresses float32 vectors to int8 integers, reducing memory usage by approximately 75%
Scalar quantization in Azure AI Search compresses each float32 component of a vector into an 8-bit integer (int8), reducing storage from 4 bytes to 1 byte per dimension — roughly a 75% memory reduction. This allows larger vector indexes to fit in memory and lowers cost, with only a small recall degradation that is typically acceptable for most RAG workloads.
You are designing an enterprise event-driven architecture where microservices across different Azure subscriptions need to subscribe to domain events published by a central Order Service. Which Azure Event Grid architecture should you implement?
Deploy an Azure Event Grid Event Domain and create event subscriptions under the domain for each consuming team.
Azure Event Grid Event Domains are purpose-built for multi-tenant, multi-subscription event distribution scenarios. An Event Domain acts as a namespace that can host thousands of topics, allowing each consuming team or subscription to create its own event subscriptions under the domain without the publisher needing to manage individual topics per consumer. This decouples the central Order Service from consumer onboarding and scales cleanly across subscriptions.
You want to ensure that no AI services can be created in unauthorized Azure regions across your entire subscription. Which Azure governance tool should you use to enforce this restriction?
Azure Policy with the 'Allowed locations' definition
Azure Policy with the built-in 'Allowed locations' definition restricts resource creation to approved Azure regions at the subscription or management group scope, enforcing the restriction across all AI services. Assigning this policy denies deployments in unauthorized regions.
You are deploying a web application container to Azure Container Apps and want to enable external HTTPS traffic. Which ingress setting must you configure?
Enable ingress with external traffic permitted
To expose a Container App to the public internet over HTTPS, you must enable ingress and set it to accept external traffic. Container Apps then provisions a fully qualified domain name (FQDN) and a managed TLS certificate automatically, terminating HTTPS at the ingress layer. Without external ingress enabled, the app is only reachable inside the environment.
Your AI ingestion pipeline ingests millions of clickstream events per second from IoT devices and streams them into an Azure ML training pipeline. Which Azure service is specifically designed for high-throughput, low-latency telemetry ingestion at this scale?
Azure Event Hubs
Azure Event Hubs is designed for high-throughput, low-latency ingestion of telemetry data, capable of handling millions of events per second. It is optimized for streaming scenarios like IoT telemetry and clickstream data, making it ideal for this use case.
You are designing an application that requires low-latency vector search for a high-traffic AI chatbot. You need to ensure the vector index remains performant as the dataset grows into millions of documents. Which index configuration in Azure AI Search should you implement to optimize for speed over absolute recall accuracy?
HNSW
HNSW (Hierarchical Navigable Small World) is a graph-based approximate nearest neighbor (ANN) algorithm that builds a multi-layer navigable graph, delivering sub-linear query latency with high recall. In Azure AI Search, HNSW is the recommended index configuration for high-traffic, low-latency vector search over millions of documents when you can trade a small amount of recall for speed.
You are designing the data architecture for an AI-powered document search application. You choose Azure AI Search because you need multi-lingual support, faceted navigation, and vector search. What is the maximum number of vector fields allowed per index in Azure AI Search?
Multiple vector fields are supported per index
Azure AI Search supports multiple vector fields per index, allowing you to store and query different embeddings (e.g., text, image, or multi-model vectors) within the same index. Each vector field is defined with its own dimensions and similarity metric, and you can target specific fields in vector queries. This flexibility is essential for hybrid and multi-modal search scenarios.
You need to ensure that all data sent to Azure OpenAI Service is encrypted at rest using a custom encryption key that your organization controls and rotates. Which feature must you configure?
Customer-managed keys (CMK) stored in Azure Key Vault
Customer-managed keys (CMK) in Azure Key Vault let you supply your own encryption key that Azure OpenAI uses for data-at-rest encryption, and you control rotation and revocation through Key Vault. This satisfies the requirement for organization-controlled, rotatable encryption keys for stored data.
An application publishes custom events to an Azure Event Grid topic. You want to inspect the dead-lettered events that failed delivery after the maximum retry period. Where must you configure the dead-letter destination?
Azure Blob Storage container
Event Grid dead-lettering requires an Azure Blob Storage container as the destination, configured on the event subscription. When an event fails all delivery retries (default 30 attempts over 24 hours), it is written to that container as a blob so you can inspect and reprocess it. Blob Storage is the only supported dead-letter target for Event Grid.
You need to restrict access to an Azure OpenAI resource so that only requests originating from a specific Azure Virtual Network are permitted. What should you configure?
Configure the Azure OpenAI resource networking settings to allow access from 'Selected networks' and add your Virtual Network subnet.
Virtual network rules (service endpoints or private endpoints) on the Azure OpenAI firewall can restrict access to specific VNets.
You are designing a data layer architecture in Azure Cosmos DB for NoSQL for an AI application that performs high-frequency writes and real-time vector searches. You need to understand how vector indexing impacts write operations. What is the primary trade-off?
Writing documents consumes more Request Units (RUs) because vector indexes must be updated
Writing documents consumes more Request Units (RUs) because vector indexes must be updated on every write. In Azure Cosmos DB for NoSQL, vector indexing adds overhead to write operations since the index must be maintained as documents are inserted or updated. This is the primary trade-off: faster vector search at the cost of higher write RU consumption.
You are configuring an Azure AI Search vector index for a retrieval-augmented generation (RAG) application. You need to select an algorithm for vector similarity search that balances recall speed with accuracy while allowing approximate nearest neighbor (ANN) search. Which vector search algorithm configuration should you select?
Hierarchical Navigable Small World (hnsw)
Hierarchical Navigable Small World (hnsw) is the correct algorithm because it provides approximate nearest neighbor search with a tunable balance between recall and latency, using a multi-layer graph that enables fast traversal. Azure AI Search supports hnsw as a vector search algorithm configuration, and it is the recommended choice for RAG workloads that need low-latency, high-recall retrieval over large vector indexes. It directly satisfies the requirement for ANN with balanced speed and accuracy.
You want to limit the CPU resources that a specific AI inference pod can consume. Which Kubernetes field do you configure?
resources.limits.
The `resources.limits` field in a Kubernetes pod spec sets the maximum CPU and memory a container can consume. When a container exceeds its CPU limit, it is throttled; when it exceeds its memory limit, it is OOM-killed. This is the correct field to cap CPU for an inference pod.
You are deploying an AI workload to AKS and want to ensure that pods belonging to your application are distributed across different fault domains (availability zones) for high availability. Which Kubernetes feature should you configure?
Topology spread constraints
Topology spread constraints let you control how pods are distributed across topology domains such as zones or nodes, using label selectors and maxSkew to enforce even spreading. By setting topologyKey to topology.kubernetes.io/zone and a maxSkew of 1, you ensure pods are spread across availability zones, providing fault tolerance if a zone fails.
You are debugging a Python application integrated with Application Insights. You notice that custom telemetry events generated in a background worker thread are not appearing in Application Insights. What is the most likely cause of this issue?
The application terminated or the worker thread exited before the telemetry client buffer was flushed
The Application Insights Python SDK buffers telemetry in memory and sends it asynchronously in batches. If the background worker thread exits or the application terminates before the buffer is flushed, the queued telemetry events are lost and never reach Application Insights. This is the most common cause of missing custom events from short-lived threads.
The AI-200 flashcard bank covers all 4 official blueprint domains published by Microsoft. Cards are distributed proportionally, so domains with higher exam weight have more cards.
Domain Coverage
Security And Observability
Event Driven Integration
Data Management Services And Vector Search
Containerized AI Workloads
Both flashcards and practice questions are evidence-based study tools. The difference is in what they train:
Flashcards — concept retention
Best for memorising definitions, acronyms, protocol behaviours, command syntax, and conceptual distinctions. Use flashcards to build the foundational vocabulary that AI-200 questions assume you know.
Best in: weeks 1–3
Practice tests — application
Best for applying concepts to realistic scenarios, eliminating distractors, and building exam stamina.AI-200 questions test scenario reasoning — not just recall — so practice tests are essential.
Best in: weeks 3–6
The most effective AI-200 study plan combines both: use flashcards for the first 2–3 weeks to build conceptual foundations, then shift to practice tests and mock exams in the final 2–3 weeks to apply and benchmark that knowledge. Most candidates who pass on their first attempt use both tools.
Yes. Courseiva provides free AI-200 flashcards across all official exam domains. Every card includes the correct answer and a full explanation of why it is right and why the distractors are wrong. The platform also includes topic-based practice, mock exams, and readiness tracking — no account required.
Courseiva has 418+ original AI-200 flashcards across all 4 exam blueprint domains. New cards are added regularly as the question bank grows. All cards are checked against the official Microsoft exam objectives, with editorial oversight from an experienced network and security engineer.
Courseiva flashcards are purpose-built for IT certification exams. Unlike generic flashcard platforms where content quality varies, every Courseiva card is mapped to the official AI-200 exam blueprint, written by engineers who hold the certification, and includes a full explanation of the correct answer and why the distractors are wrong. This explanation quality is what separates genuine learning from rote memorisation.
Courseiva is a web platform — an internet connection is required. For offline study, we recommend creating free Courseiva account, using the platform in your browser, and using your device's offline capabilities if your browser supports offline web apps.
Save your results, see which domains need more work, and get spaced repetition recommendations — all free.
Sign Up FreeFree forever · Every certification included